I had a total of two coding interview rounds on two different days.
First round: 1-hour round. Second round: 2.5-hour round (30-minute break in between).
Prepare well on data structures like linked lists, stacks, queues, pointers, state machines, and bit manipulation. You can expect typical embedded coding rounds.
Practice well, all the best!
First Round
The focus was on data structures, including linked lists, stacks, and queues. I was given a specific question and had to create a data structure to address it.
Second Round
This round was divided into two parts. The first part lasted for one hour, followed by a 30-minute break, and then another one-hour session with a different interviewer.
First Half of Second Round (1 hour)
The interviewer instructed me to copy the contents to memory without using malloc and free. Instead, they provided APIs to use. My task was to define a function that receives a struct pointer. When the pointer is dereferenced, I needed to access specific members and copy them into memory. Additionally, I was required to manage memory allocation using the provided APIs and ensure proper deallocation after copying.
Second Half of Second Round (1 hour)
The second interviewer tasked me with creating a state machine. The scenario involved capturing an image with various attributes such as ID, payload, and payload length. The challenge was to load an output buffer in a specific format based on different commands. These commands were structured in a state machine design.
The following metrics were computed from 1 interview experience for the Amazon Firmware Engineer (Co-op) role in North Reading, Massachusetts.
Amazon's interview process for their Firmware Engineer (Co-op) roles in North Reading, Massachusetts is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Amazon's Firmware Engineer (Co-op) interview process in North Reading, Massachusetts.