
Motorola Solutions Embedded Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Motorola Solutions.
Embedded Software Engineer
So the whole thing kicked off around 9:30am and wrapped up by 3pm. They were nice enough to give us a 1-hour lunch break, which they covered, at this place called Chills. First up was a chat with two of the Software Leads. After that, I had another session with two Software Leads and a Project Manager, where we got to write stuff on a whiteboard. Then, lunch, and after that, a behavioral chat with three folks from the Software department.
- Tell me about typical behavior questions.
- What is the software development cycle?
- Which programming language has the best garbage collection?
Embedded Software Engineer
I did a quick skill test at the hiring fair, then they invited me for an in-person interview at their place. The whole day was from 9am to 4pm and included technical interviews with seven different people. Everyone was really nice and made me feel welcome. It felt like a good sign, but I never heard back about whether the job was filled. I asked them about it via email once, and they said it could take a few weeks. After two months, I followed up again to see if I could even apply for other jobs. That's when they told me the first position was no longer open.
- Could you draw a state event diagram?
- Write a program for a game that outputs "Buzz"?
- Create an observer design pattern.
Embedded Software Engineer
applied online, then had a phone call with the Recruiter about my background and coursework. This led to an on-site interview about 2 weeks later. The interview itself had 3 rounds, first with a panel of 7 people, then 2 people, and then another 2 people. They asked some pretty simple coding questions like big v little endian and the difference between & and && comparator. Got an offer about 3 weeks after all that.
- Have you ever worked on any personal projects?
- Can you explain big v little endian?
- What is the difference between the & and && comparators?
Motorola Solutions Embedded Engineer Interview Questions
Quoted word for word from Motorola Solutions interview reports.
“What is the difference between the & and && comparators?”
Read reports →“What does deadlocking mean?”
Read reports →“Create an observer design pattern.”
Read reports →“Which programming language has the best garbage collection?”
Read reports →“Write a program for a game that outputs "Buzz"?”
Read report →“And what's the benefit of using inheritance?”
Read report →“Can you explain big v little endian?”
Read report →“Could you explain the difference between stack and heap memory?”
Read report →“How is memory allocated?”
Read report →Formats, difficulty and experience
Across all 11 Motorola Solutions interview reports.