Candidates describe Motional's Software Engineer interview as a recruiter screen, usually a hiring manager conversation, and technical rounds with medium-level coding, system design, and autonomous-vehicle topics.
$172K
Avg. Base Comp
$212K
Avg. Total Comp
4-5 rounds
Typical Rounds
Not reported
Process Length
Motional's Software Engineer interview, as candidates describe it, begins with a recruiter conversation and often a hiring manager screen before moving into technical rounds. Round counts vary: one candidate who received an offer reports four rounds, and another reports five.
Coding is described at LeetCode medium level. One offer recipient had three coding-style rounds in a virtual onsite, including one with the hiring manager that used an easier problem, and said the questions felt relevant to autonomous driving. That candidate's advice was to focus less on grinding random hard problems and more on clearly articulating your thinking, trade-offs, and why you chose one approach over another. Another offer recipient had a modified medium problem plus a short object detection and deep learning task.
System design shows up in several accounts, with different prompts. One candidate was asked to design a ring camera style product, which centered on architecture, edge cases, and real-world constraints. Another gave a high-level approach without implementation depth.
Domain depth depends on the team. One candidate faced motion planning, controls, and sensor calibration questions, and another was asked about verification and validation for autonomy. One candidate was asked about a project involving ambiguity and limited tooling, so have a story ready.
The hiring manager round differs by report. One offer recipient described a careful walk through their CV, while another candidate found the manager disengaged. One candidate waited more than a week for a recruiter follow-up.
Synthesized from 7 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Motional process.
Round 1: Introduction about my experience, core skills, and projects.
Round 2: C++ coding round What happened: STL and threads programming. Surprises: I was asked to implement smart pointers. Struggle: I managed to implement it.
Round 3: Design round covering the basics of ADAS, the camera pipeline, the vision stack, and how the ADAS feature function I was working on operates.
Round 4: HR
Questions asked: I was asked the difference between auto and decltype, and std::forward vs. forwarding references. I was asked to implement a customized thread-safe shared_pointer class. I was asked to explain how a red-black tree works and where it is used in the STL. They gave some use cases and asked how I would select the appropriate STL container.
I was asked to use multithreading (std::thread) concepts to solve the following problem: print zero, odd, and even numbers in a pattern using threads, for example 0102030405.
Coding question: sorting a binary linked list. I was given an unsorted singly linked list of binary values and asked to sort and print the list in place without using extra space.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Motional
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Top 3 Users | |
| Get Top N Frequent Words | |
| String Shift | |
| Find Bigrams | |
| Last Transaction | |
| Raining in Seattle | |
| Size of Joins | |
| Minimum Change | |
| First Touch Attribution | |
| Job Recommendation | |
| Nearest Common Ancestor | |
| Find the First Non-Repeating Character in a String | |
| Daily Retention Summary | |
| Find the Index with Equal Left and Right Sum | |
| Google Maps Improvement | |
| Delivery Estimate Model | |
| Type-ahead Search | |
| Detecting ECG Tachycardia Runs | |
| Friendship Timeline | |
| Type I and II Errors | |
| The Brackets Problem | |
| Third Purchase | |
| Level Of Rain Water In 2D Terrain | |
| Youtube Recommendations | |
| P-value to a Layman | |
| N-gram Dictionary |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe a relaxed recruiter conversation about their background, past projects, and what they want next. One was asked what they knew about Motional, and another was given an overview of the team's culture and technologies. Reports present this round as a fit and logistics check rather than a technical test.
Two candidates describe a manager round built around their resume. One offer recipient called it a careful CV deep dive that also touched on verification and validation for autonomy. Another candidate, who did not get an offer, found the manager disengaged. Be ready to explain your projects and how they apply to autonomous systems.
One candidate had a friendly phone screen on breadth of knowledge. A deeper round followed that covered a project involving ambiguity and limited tooling, plus motion planning and controls basics. Another had a modified medium LeetCode problem plus system design discussion.
One candidate reports two medium coding sessions, a system design round, and a domain round on calibration and sensor fundamentals. Another reports three coding rounds, one with the hiring manager on an easier problem, then a system design interview. A third describes four technical panels, including a ring camera style design prompt, with no separate behavioral round.
Final conversations differ by candidate. One offer recipient had a behavioral interview with the hiring manager and a culture-fit panel, plus a short object detection coding task. Another finished with a behavioral round with a team lead. Another candidate had no separate behavioral round at all.
