
Zebra Technologies Firmware Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 5 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Zebra Technologies.
Firmware Engineer
They schedule you to come in for a 2.5 hour block of interviews, four interviews total. The first and last interviews aren't technical, rather with managers, the first giving you a really good description of the job. The middle two interviews are more technical in nature, but more along the lines of "describe some projects you've done" rather than "write code on this whiteboard". The last interview is with a manager, more of a "get to know you" kind of talk. All told, the process is relatively painless.
- Can you read this code, tell me what the output is, and then explain how to fix it to produce the intended result?
Firmware Engineer
The interview process started with a phone call with the hiring manager. It was pretty basic, asking about myself, how my skills fit the job, the transition from academic to industry code size, comparing C, C++, and C# and my preferences, and considerations for embedded programming. The manager seemed pleased. The onsite interview began with lunch, during which I asked questions that led the interviewer to provide a detailed overview of the role, its function, and the ideal candidate. The subsequent interviews were mostly non-technical, covering my interest in Zebra and embedded systems, discussions about work culture, Zebra's evolution, my strengths and weaknesses. The final interview was technical, asking about concepts like priority inversion, bitfields, and RTOS. I was then presented with a scenario involving loading bits from a bitmap to a printer head via a shift register and asked to explain the process without an RTOS. The interviewer appeared satisfied with my answers. Although the lunch interviewer indicated I might get an offer, the position ultimately went to a more qualified candidate.
- Can you explain the process of loading bits from a bitmap onto a printer head using a shift register, assuming no RTOS is present?
- Could you describe the process of loading bits from a bitmap onto a printer head using a shift register, in a situation where an RTOS is not available?
Firmware Engineer
I applied through the campus website. There were three rounds of interviews: HR, a technical person, and the manager. The HR person asked about my available date, desired salary, and some company culture stuff like catching up on deadlines. The technical interview involved questions about my resume and wireless communication. I also got some questions from the manager, but I didn't answer them very well, like the one about the 'violate' keyword in C/C++. I didn't get an offer and they let me know about two weeks later.
- When can you start?
- What are your salary expectations?
- How do you handle meeting deadlines?
Zebra Technologies Firmware Engineer Interview Questions
Quoted word for word from Zebra Technologies interview reports.
“What is the significance of the 'violate' keyword in C/C++?”
Read reports →“Can you explain the difference between a semaphore and a mutex?”
Read reports →“Can you read this code, tell me what the output is, and then explain how to fix it to produce the intended result?”
Read reports →“When can you start?”
Read reports →“Could you write some C code on the whiteboard?”
Read report →“Do you have any knowledge of wireless communication?”
Read report →“What are your aspirations for the future?”
Read report →“Tell me about what you enjoy doing in your free time.”
Read report →“How do you handle meeting deadlines?”
Read report →Formats, difficulty and experience
Across all 5 Zebra Technologies interview reports.