Skip to contentSkip to footer

Firmware Engineer Interview Questions

Salaries
Interviews

2,358 firmware engineer interview questions shared by candidates

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.
avatar

Firmware Engineer (Co-op)

Interviewed at Amazon

3.5★
Aug 22, 2023

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.

First Round (1 hour) - Technical Round: Questions related to projects on your resume: This is to gauge your practical experience and understanding of the projects you've worked on. Interrupts: Understanding of how interrupts work, their importance in real-time systems, and how to handle them. RTOS (Real-Time Operating System): Assessing your knowledge of thread synchronization, priority management, types of locks, memory management, deadlocks, and Inter-Process Communication (IPC). Debugging techniques: Your ability to identify and troubleshoot issues in code and systems. Linux environment experience: Cross-compilation, Yocto Project, Buildroot, and Linux command line familiarity. Second Round (2 hours) - Technical and Coding: First Half: Technical questions on projects and technical skills: Deeper exploration of your project experiences and understanding of technical concepts. Questions might cover handling multiple interrupts, differences between polling and interrupts, and deadlock resolution strategies. Second Half: Coding challenges: Linked list: Assessing your ability to work with fundamental data structures. BST (Binary Search Tree): Testing your knowledge of tree data structures and basic operations like insertion and deletion. State machine: Evaluating your ability to design and implement complex logic using state machines. Last 15 minutes: A chance for you to ask any questions you might have about the company, role, or interview process.
avatar

Firmware Intern

Interviewed at Marvell Technology

4.3★
Aug 22, 2023

First Round (1 hour) - Technical Round: Questions related to projects on your resume: This is to gauge your practical experience and understanding of the projects you've worked on. Interrupts: Understanding of how interrupts work, their importance in real-time systems, and how to handle them. RTOS (Real-Time Operating System): Assessing your knowledge of thread synchronization, priority management, types of locks, memory management, deadlocks, and Inter-Process Communication (IPC). Debugging techniques: Your ability to identify and troubleshoot issues in code and systems. Linux environment experience: Cross-compilation, Yocto Project, Buildroot, and Linux command line familiarity. Second Round (2 hours) - Technical and Coding: First Half: Technical questions on projects and technical skills: Deeper exploration of your project experiences and understanding of technical concepts. Questions might cover handling multiple interrupts, differences between polling and interrupts, and deadlock resolution strategies. Second Half: Coding challenges: Linked list: Assessing your ability to work with fundamental data structures. BST (Binary Search Tree): Testing your knowledge of tree data structures and basic operations like insertion and deletion. State machine: Evaluating your ability to design and implement complex logic using state machines. Last 15 minutes: A chance for you to ask any questions you might have about the company, role, or interview process.

Viewing 1211 - 1220 interview questions

Glassdoor has 2,358 interview questions and reports from Firmware engineer interviews. Prepare for your interview. Get hired. Love your job.