Xrfgtjtk

Assuming this is the US and you did not falsify the information you provided, worst they can practically do is to fire you for incompetence if you lack the skills required. Chances are if you put embedded programming on your resume and they saw that, with a position possibly matching it they have likely been trying to fill for some time, they tried to see if you could qualify. And seems like they were satisfied at the interview so they extended you the position.

Most of the time the experience requirements and such are arbitrary and even put there by recruiters just filling out a form and putting in semi-arbitrary numbers. Once past an interview it does not really matter. I would take it as a sign of good luck and take it, and dedicate some of my free time to catch up to speed if that seems like would be an issue.

As far as them not explicitly telling you this, the HR might have passed your resume to the team knowing it is a hard to fill role, with both sides assuming the other side told you about considering you for a different position.

The fact that it says "10+ years experience of C" in the job advert doesn't necessarily mean that is what you really need, or what the company expects to get.

The key fact is that the interviewer spent an hour discussing embedded programming with you and presumably liked what he/she heard. There would be no sense in continuing the discussion for an hour if it was obvious within 10 minutes that you were not suitable for the job.

Whatever you have learned from your practical hobby experience might be a lot more valuable to the company than a computer science graduate with a head full of theory but not much else.

In brief :

1. Embeded programming is your hobby this is every recruiters dream to engage an employee who considers work as hobby




2. Employers employ based on their needs! They think you are a perfect fit for the offered position. It is quite rare if they have mistaken you with someone else.

I believe it is a good opportunity for you, don’t miss it!

I can't believe this hasn't been suggested yet:

Pick up the phone and call your main point of contact at the company (hiring manager or recruiter) to discuss.

Or email.

It's really that simple. Now that the offer is in your hands, the company should be very accommodating and more open to discussing the job details back to you. If they really are hiring you for embedded work, this is your chance to ask clarifying question about the position and how strong of experience they really need. Be fully transparent about your trepidation and work experience. Either one of two things will come across in the follow up conversations:

• They speak with assurances. They will tell you something positive and possibly mention a mentoring aspect to the job. Yay - they want to invest in you.

OR

• They speak as if you are expendable. They aren't forthcoming or speak of excitement to hire you. They use phrases like, "we think we can take a chance on you." or "it's up to you." Walk away if this is the case.

Honestly, I would never accept a offer for an engineering role until I've looped back with the hiring manager. This is your chance to interview them before you make a huge career decision.

I think the extent of your trouble may be getting sacked without notice in the first month. Potentially.

It's impossible to tell what this employer has in mind about you, perhaps they are keen on you because you were keen on embedded programming, who knows? So what I would do is ask them for an additional meet with the hiring manager, preferably face-to-face. And clarify this with them. Better come out honest than otherwise.

If it was a mistake they will potentially offer you the webdev position, and if it wasn't - even better, and you get so much more credit going forward.

There are not that many highly qualified embedded developers around. And lots of highly qualified desktop / mobile / server developers may not be interested in an embedded development job.

So it seems that what you showed in your interview was enough to convince them that you can do the job - or at least that you are the best candidate for an embedded development job that they are going to find.

If you are OK with doing embedded development for a much higher rate than your normal web development jobs, then go for it. Be prepared to do your best during the working day and lookup things you are missing in the evening, but that phase will be over soon, and the higher salary will stay.

Maybe you shouldn't mention in the company what happened, but then it is quite possible that the guy looking for a web developer saw your hobbies, and knew that someone else in the company is in dire need for an embedded developer, and passed you on knowing that he can find another web developer any time.

If you are smart and think you are up to it, then go for it. It's not as if you have no experience; you have experience with embedded development, and with development in general.

I saw a very similar situation play out live. (see below)

I would advise honesty, and that imply not lying by omission.

Lying about experience is pointless: it's stressful, and you'll be found out eventually anyway. There's no way it'll end well. On the contrary, honesty brings out good will and starts you up on the right foot to build a long-lasting relationship with your employer. It doesn't even matter if you don't plan to stay there for long: a happy employer is one you can use for references, one you can come back to in a couple years, etc...

Instead, be pro-active and contact HR. Then, depending on which of the job you want:

• Embedded: mention that you are excited about the position, though surprised that a senior position was offered to someone with no professional, only hobby, experience. If hired for the role, mention your lack of experience again with your boss on the first day. They may simply have decided to take on a junior-level developer rather than keep waiting for the hypothetical senior who never comes; you can be trained on the job as long as they are aware of your level of experience.


• Web: mention that you are honored about the position, however you applied for a web development position and have no prior experience doing embedded. Suggest shifting to a web development role.

In either case, you now have a foot in the door, it's time to make the best of it.

Story time.

Not 4 months ago, we had two newcomers starting, a senior and a junior. We helped them configure their environments, and after a day or two noticed the junior seemed quite uncomfortable. My boss talked to him and realized there had been a mistake: my boss had been brought in for the interview so assumed it was for a C++ position, when in fact HR had been scrambling to fill in for a sick interviewer for a Java position. The junior didn't feel like he could do a good job in C++, my boss apologized for the mix-up, and he was moved to a Java team.

Honesty is definitely the best policy but first you need to realise there is often a big disconnect between what an advert says, what HR described and what the Hiring Manager really wants!

You need to find out if the person who interviewed you is the Hiring Manager. If so, then it's quite likely that they're struggling to fill the role and think you can, at the very minimum, grow into it.

So pick up the phone, speak to HR and tell them that you are delighted to have been offered this position even though you applied for a different one and you just wanted to double check they understood the situation. Don't be bashful or apologetic though - you spent an hour impressing a hiring manager on a subject that wasn't expected to be your main focus!

"I'm really excited to be offered this role, I think I can do a great job for you and the interview seemed to go well but I just want to double check with you as the job I was offered wasn't the one I applied for. I don't have a problem with that but just wanted to double check it's all OK at your end."

So we discussed embedded programming for almost an hour - then he tells me they'll get back to me.

Always assume that if an interviewer talks to you for an hour, that they are evaluating your fitness in the area they are talking about. If they write 10+ years of C experience but came (after a 1h interview in that direction) to the conclusion that you other professional experience plus your hobby skills are enough, it should be - I do something like this (placing people on different jobs than they applied to) quite regularly in technical interviews.

For me there are three scenarios:

• an mix-up of the application but not the offer (which could be lucky if you want to get into such a kind of job)




• an mix-up of the offer (that would be the only bad thing)




• no mix-up at all, but the company has two "placeholder positions" which cover the interesting range and enable some pre-sorting (sometimes my employer does it in this way)

Anyway, the best is to contact the HR by phone - you assert that everything is in order regarding the decision, but you want to confirm. Something like "I would just like to confirm that the job you would like to place me on is ...;"

EDIT: The only thing you should be careful for if the job has a function in a regulated process (Aircraft, Medical devices etc....).

I don't think you should go for it.

I'm saying this because it could make your own life miserable. Doing something as a hobby is completely different than doing it under pressure at workplace. Pay is much higher in embedded programming field because it's way more complicated than web development.

Think about what you would like to do in the future before deciding.

[It is at least better than some company that hire you for the (right?) position then assign tasks among your (hobbies?) as well...;)]

If you feel the passion for doing the job and undertaking the responsibility it is fine. If you feel like allocating some your free time preparing for and catching up with potential scenarios you will face later at your job then better. (It is still your hobby, isn't it?)

Go strong way and accept their occasional web development as well, but tell them at the first place. Don't let it continue as their mistake, make it clear like this:

Thank you for evaluating my capabilities in embedded field as a fit for your current position available in embedded engineering, I am happy to accept the position as well as being able to undertake some tasks in web development which I originally filed application for....

Anyway, if it is left unclear, it might make troubles (may be not for you, but for them perhaps).

Interviewing is like dating.

You start out dreaming of who your perfect match might be. Then you see who's really out there and things change.

I've been a web developer. I've been an embedded developer. I've done well in both. I didn't start out with anything close to what was asked for in the job posting. In fact after decades at this I still haven't found a job that didn't ask for more than I had. When I did the embedded developer thing I hadn't even touched a PIC32 yet. Passion about the subject is so much more important than what you can do now. If you can sincerely show that it doesn't surprise me at all that they are interested in you.

Understand that people hiring you for a job are human and are prone to dream of better than they are going to get. You're judging them based on what they thought when they dreamed up the position. Not what they learned after interviewing candidates.

Your concerns are valid and do you credit. But don't exclude yourself from the job because they asked for more than you have. If you really think they made a mistake then offer an updated resume targeted to the embedded developer job. This gives them a chance to realize if it is a mistake and if not can be seen as you simply covering your interviewers butt in case anyone else wonders about this.

Far more importantly is you need to interview the company before accepting the offer. You're justifiably nervous. You want to know you'll do well. Go talk to them again and take a hard look at who they are, what they're asking you to do, and be sure you're ready for it. Odds are good that you are. But you'll be in hell if you accept the job before you're sure.

The company that hired you put those regulations in place to filter out those who are incapable of that position. IF the company, at some point, finds out that you do not have the experience that was required, they may fire you.

HOWEVER, if you prove that you are capable of that job without the "requirements", they will likely keep you anyway, as opposed to going through the hassle of hiring another developer.