Motorola Solutions logo

Motorola Solutions Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 233 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
72% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Motorola Solutions.

Showing 3 of 233
Motorola Solutions logo
Motorola Solutions

Senior Software Engineer

Engineering · nearly a year ago

Mid Average Neutral experience Decline offer 1 round

So the onsite was pretty structured, and the tech talks were really cool. I met a bunch of hiring team folks and they seemed like genuinely good people to work with. We chatted about our backgrounds, what we've done, and looked at some really interesting opportunities both on the team and company side. Most of the time was me answering questions, technical and non-tech. But man, after that onsite, everything just stopped. Like, total radio silence for four business weeks. During that month, I actually got and accepted two other offers with better pay and benefits from a direct competitor and a big tech company nearby. Then, a whole month after my onsite, Motorola Solutions finally gets in touch with an offer, but by then, I wasn't even interested anymore. A whole month of silence for a competitive AI/ML and distributed systems role is just too long, makes you feel like a second thought. The super slow decision-making really makes it feel like there's a hesitant, paralyzed, and bureaucratic culture inside. In this war for AI/ML talent, you gotta be fast and upfront. Even if internal approvals are slow, you HAVE to keep candidates updated weekly. Honestly, even though the pay was a bit lower, I would've taken this job if the process hadn't been so drawn out and I'd been kept in the loop. By the time they made an offer, I'd already gone with faster competitors who actually stayed in touch, offered better pay, and showed more respect for my time. Seriously, you guys need to check your compensation benchmarks (especially for AI/ML and distributed systems) and how fast you hire if you want to stay competitive.

Confirmed questions1 question
  • A key question involved tackling a design and implementation challenge.
Motorola Solutions logo
Motorola Solutions

Senior Software Engineer

Engineering · a year ago

Mid Difficult Positive experience Accept offer 2 rounds

I applied for the Motorola Solutions position via LinkedIn. Got an email to schedule an initial interview, all in English up to that point. My first interview was with the manager, we spoke for about 30 mins in Portuguese, he was Brazilian too. It went well, very respectful, and I felt I passed to the next step. A few days later, I got an email saying I passed to the second stage, which had 4 back-to-back interviews, totaling 2 hours. This second round was all in English, mostly with Americans, one after the other, 1-on-1, each 30 mins long. It included various questions and a live coding session. After a few days, I got an email saying I was approved and received the job offer letter.

Confirmed questions8 questions
  • Fiz um live coding em Java.
  • Me ofereceram a opção de usar JavaScript para o live coding, mas escolhi Java.
  • Perguntaram sobre minha experiência com segurança.
Motorola Solutions logo
Motorola Solutions

Software Engineer

Engineering · more than a year ago

Mid Average Negative experience No offer 9 rounds

This company has a really messed up hiring process, I was treated terribly. Applied on Linkedin and got a call a few days later. Recruiters were rude from the start. First interview was with a recruiter, they showed some slides and asked general career questions. Then an online test on Codility with 2 Leetcode style problems and logic questions. Did well and passed. Next, had 2 interviews with managers, 3 with engineers, and 2 more with senior engineers. Around 8 or 9 people interviewed me in total. They were really secretive about what to expect in interviews. Almost everyone asked the same questions, like about my Java experience or Azure knowledge. Some interviewers didn't even know why they were interviewing me. They don't do live coding usually, but one interviewer decided to do it anyway. Two weeks after what I thought was the last interview, they scheduled another one. Finally, a manager told me they liked me and would make an offer. But then the recruiter asked me to do something illegal and uncomfortable. When I refused, they rescinded the offer.

Confirmed questions2 questions
  • Tell me about your experience with Java.
  • What's your understanding of Azure?

Motorola Solutions Software Engineer Interview Questions

Quoted word for word from Motorola Solutions interview reports.

Given a positive integer and a power k, how many numbers, when raised to the power k, end with the same unit digit as the given integer?

Read reports

What's the way to figure out if a binary tree is a proper Binary Search Tree?

Read reports

Regarding arrays of integers, how would you write a function to push all zeros to the end, keeping the order of the others the same?

Read reports

What does string immutability mean? Given s1="hello" and s2="world", if s1 = s1+s2, what would be the value of s2 and can you explain the memory allocation for this operation?

Read reports

Can you find out a perfect square number within the range of 1 to 100000?

Read report

Can you tell me how to count the items in a list without using a for-loop?

Read report

How would you find the unique number that appears only once in an array that has duplicate numbers?

Read report

What separates a process from a thread? And in what scenarios is using multi-threading preferable to using multiple processes?

Read report

Regarding searching a list of consecutive values for a missing value in O(log(n)) time, how would you approach that?

Read report

Formats, difficulty and experience

Across all 233 Motorola Solutions interview reports.

Interview formats

Technical 44.4%
Behavioral 33.3%
Coding 17.1%
Presentation 1.7%
Other 1.7%

Interview difficulty

Easy 17.2%
Average 67.4%
Difficult 15.5%

Candidate experience

Positive 72%
Neutral 14.7%
Negative 13.4%