The process starts with phone screens. Sometimes there's more than one screening, as candidates are brought in to interview with 2-3 different teams. This is one reason it takes time.

It took three weeks after the first phone screen, where I was told the interviewer was recommending me for an onsite interview and that I should hear from HR within a few days, to get a second interview and finally be called for a full-day onsite interview.

Phone screens are typical and include basic questions covering volatile and static concepts, as well as RTOS concepts.

There was one interview with a staffing specialist explaining the procedure and recruitment process, and benefits. After that, I had 5 one-on-one interviews: 2 with the security team and 3 with the Core-BSP and device drivers team.

There was a lot of board work; one engineer asked me to write code on his computer.

What is volatile? What is static?

How would using the static keyword for a large array inside a function affect it?

What are sections of memory, and what kind of variables are stored where?

How can an OS be made real-time? Name a few RTOSs.

How can memcopy be made fast?

Code was written on a board, and problems had to be identified, such as memory leaks or accessing unallocated memory locations.

How does a packet travel between two hosts connected in the same network? What is a subnet mask?

Puzzle: If there are 72 legs in total and 28 animals involving chickens and horses, how many are horses and how many are chickens? Solve without using equations.

How does a vending machine work? Describe the blocks and functions, just to see if I can break down the problem into small modules and analyze.

How does a bootloader work? What is priority inversion, and how is it solved? Compare the ways.