General Motors Software Engineer interview typically runs 3-4 rounds: HR screen, online assessment, technical interview, and behavioral or hiring manager round. The process usually takes about 2-4 weeks and is fairly structured, with some variation by team.
$104K
Avg. Base Comp
$140K
Avg. Total Comp
4-6
Typical Rounds
2-5 weeks
Process Length
We’ve seen General Motors lean less on flashy algorithmic difficulty and more on whether candidates can think like engineers who ship reliable products. Multiple candidates described a process that mixed coding with debugging, systems design, and broad software fundamentals, but the real signal was often how cleanly they reasoned under pressure. Even when the coding itself was only medium-level, interviewers seemed to watch for structured thinking, tradeoff awareness, and whether the candidate could explain not just the answer, but the path to it.
A recurring theme is that GM cares a lot about the person behind the resume. Our candidates report long stretches spent on internship work, project leadership, teamwork, and why they made certain decisions, with follow-up questions that pushed for specifics. In several experiences, the strongest conversations came from hands-on examples like test engineering, Formula Student, or past collaboration challenges. That tells us GM is looking for practical judgment and ownership, not just technical fluency. Candidates who could connect their experience to real engineering outcomes tended to fare better than those who stayed abstract.
We also see a clear preference for engineers who are comfortable with fundamentals in context. C++, OOP, memory management, and general software knowledge came up repeatedly, but rarely as isolated trivia; they were tied to how someone would build or maintain software in a real environment. The non-obvious trap here is assuming the interview will be purely technical because of the title. In practice, the people who stood out were the ones who could move naturally between code, design, and collaboration without sounding rehearsed.
Synthetized from 5 candidates 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 General Motors process.
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 General Motors
Design a data warehouse for a new online retailer
| Question | |
|---|---|
| Duplicate Rows | |
| Your Strengths and Weaknesses | |
| The Brackets Problem | |
| Target Indices | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Matrix Multiplication | |
| Search Timeout | |
| String Palindromes | |
| Why Do You Want to Work With Us | |
| Decreasing Tech Debt | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| String Shift | |
| Employee Salaries | |
| Random SQL Sample | |
| Closest SAT Scores | |
| Weighted Keys | |
| Prime to N | |
| Largest Salary by Department | |
| Upsell Transactions | |
| Monthly Customer Report | |
| First Touch Attribution | |
| Slacking Employees Salaries |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically apply through GM's internal portal or come in through a referral. HR/recruiting often reaches out quickly if the profile looks aligned, and the process then moves into an initial screening stage. This first conversation is usually a standard phone screen to confirm interest, background, and basic fit for the role. In some cases it is very light, focused on whether the candidate is a real person, interested in the job, and meets the basic requirements.
Most candidates complete an online coding assessment before moving forward. The OA commonly includes three coding problems, often in a LeetCode-style format with a mix of easy, medium, and medium-hard questions, or a dynamic programming problem on HackerRank. This round is typically a live video technical interview with one or more panelists. It may include verbal problem-solving, walking through how you would code a solution, and a broad discussion of your background and previous experience.
Candidates may face a live coding interview with two medium-difficulty questions, or a debugging exercise where they review a file and identify issues. The focus is on clean thinking under time pressure and practical problem-solving rather than especially tricky algorithms. The final conversation is often with the hiring manager and is more technical-behavioral than purely coding-focused. Interviewers spend a lot of time on resume deep-dives, teamwork, leadership growth, and STAR-style questions about handling challenges, ambiguity, and collaboration.
Some candidates report additional virtual rounds that are described as systems design or general software knowledge interviews. These tend to be broad and conversational, with emphasis on career background, domain knowledge, C++, OOP, memory management, and practical application design rather than deep formal design exercises.