Marvell Technology Firmware Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 15 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Marvell Technology.
Marvell Technology
Firmware Engineer Intern
Intern Average Positive experience Decline offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical
So there were two interviews. The first one was a quick 15-minute chat with the hiring manager. Then, the second interview was a longer 45-minute technical one where I talked to four staff engineers.
Confirmed questions4 questions
- Can you tell me about the volatile qualifier in embedded C?
- Do you have experience with basic embedded C concepts?
- What do you know about NAND Flash?
Marvell Technology
Senior Firmware Engineer
Senior Easy Negative experience Decline offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding Behavioral
The interview process involved discussing ARM ISRs, IPC mechanisms, code memory layout changes, and memory allocation for different alignments. There was also a part about why I changed jobs and my old projects.
Confirmed questions6 questions
- Can you explain the ARM ISR process?
- Describe different IPC mechanisms.
- How are code memory layouts changed?
Marvell Technology
Firmware Engineer
Mid Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Behavioral
I only had contact via email to access a page to schedule a virtual interview. I must point out that the contact was only by email even though they have all my other details, and by chance I saw that I had received the email among several others from spam since I don't check my email inbox every day. The process was supposed to continue with a second interview with a technical test. I rate the process as negative because in the first interview they probed me for two openings and no one told me it was going to be like that, the email for the second interview arrived about two weeks later, and I saw it two days late. I asked the recruiter which position the second interview would be for to prepare for the technical test, and they never responded. Finally, I was never able to do the second interview, and the recruiter never responded to my messages. And the most important point to rate the process as negative is that I have a great interest in being part of the company.
Confirmed questions4 questions
- What is your knowledge of software QA?
- What programming languages do you know?
- What experience do you have with embedded systems?
Marvell Technology Firmware Engineer Interview Questions
Quoted word for word from Marvell Technology interview reports.
“Can you explain the purpose of init() in Python?”
Read reports →“How do you find the min and max elements in an array using C?”
Read reports →“What's the difference between polling and interrupts?”
Read reports →“What is the role of a timer in an embedded system?”
Read reports →“Could you describe the functionality of the 'cd' command in Linux?”
Read report →“Can you explain endianness and how to store an address using a pointer?”
Read report →“How would you implement the Two Sum problem in C?”
Read report →“Can you tell me about the volatile qualifier in embedded C?”
Read report →“How would you allocate continuous memory for 64-byte aligned, 32-byte aligned, and 16-byte aligned requirements?”
Read report →Formats, difficulty and experience
Across all 15 Marvell Technology interview reports.