Glassdoor users rated their interview experience at Motorola Solutions as 100% positive with a difficulty rating score of 1 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Administrative Assistant and rated their interviews as the hardest, whereas interviews for Administrative Assistant and roles were rated as the easiest.
The hiring process at Motorola Solutions takes an average of 210 days when considering 1 user submitted interviews across all job titles. Candidates applying for Administrative Assistant had the quickest hiring process (on average 210 days), whereas Administrative Assistant roles had the slowest hiring process (on average 210 days).
1 problem solving question, wasnt hard was similar to leetcode medium problems, nothing too fancy. The same interview included behavioral questions and research related questions since the position was for grad students
Interview questions [1]
Question 1
Tree related question, cannot remember the exact problem
Thanks for sharing your positive experience! We’re glad to hear that you had a great chat with members from our recruiting and hiring teams. We strive to provide the best experience for candidates, and your review validates our time and effort spent creating a memorable experience.
I applied through an employee referral. I interviewed at Motorola Solutions (Chicago, IL)
Interview
Initially, there was a recruiter screen of 20 minutes followed by the final Hiring Manager call of 30-45 minutes, which consists of both technical + behavioral questions. No heavy leetcode style, just focused more on resume discussion
I applied online. The process took 3 weeks. I interviewed at Motorola Solutions (Bayan Lepas) in Sep 2022
Interview
Smooth and straight to the point.
Go through the CV and they will ask to elaborate more on specific points in CV
Few test on the technical skill such as linux cmd and log path for troubleshooting
Total interview take around 40 mins
Interview questions [1]
Question 1
If customer reported an Application is down on a linux server what would check to understand what went wrong and how to resolve the issue.