J'ai postulé via un recruteur. J'ai passé un entretien chez Amazon
Entretien
I got called from their talent team about a new job opportunity. I got told that the job was for a software Engineer. I explained to them that I am an Embedded software engineer and would not be looking at a position for a pure software role focused on cloud.
But they said that now on Amazon they dont have specific roles. You apply for a generic "software role" and if you accepted, they will find the best position for you.
I reluctantly said okay but that was when everything went downhill. The interviewer I got assigned, was someone who worked at their AWS backend and didnt understand anything about the embedded development. All of the questions I got asked were generic pure software questions about situations that almost never occur in embedded software development. (e.g. dictionary/hash tables manipulation). They guy didnt know how C/C++ worked which is what is used 99% of time in embedded industry.
Their was a complete lack of focus during the interview. All of this due to this weird process of hiring "generic software developers" and then assigning them on different roles after interview process.
Questions d'entretien [1]
Question 1
Create a list. Implement methods to add, find and remove.
Medium technical problem that could be solved within time. I wish there were more behavioral questions but interviewer provided only technical problems. The interviewer didn't seem interested in going over resume or my particular skill, which led to providing non-tailored technical problems.
Recruiter call, online coding assessment, online interview, in person interview. Incompetent recruiter told me that the interview was going to be about embedded coding but it was actually system design.
The entire process went smoothly, starting with the initial recruiter phone call and followed by a technical interview with a software engineer. The technical discussion was heavily focused on embedded‑systems concepts, particularly bit manipulation, bitwise operations, and low‑level programming fundamentals.