General Motors (GM) Software Engineer interview experience

No offer

Medium

Positive

Mountain View, CAPosted Jun 2026 · Candidate report, summarized by Dataford

My loop landed on a pretty tight pattern: OA first, then I moved into three back-to-back interviews—technical, behavioral, and coding.

Across the interviews, the consistent theme was getting a strong sense of my resume, and I was asked a lot about my background and experience rather than only high-level “fit” questions.

One technical part pushed me to review a piece of code and fix it, which immediately made the process feel more hands-on than purely theory. The behavioral portion was anchored in classic STAR-style storytelling, and I had to connect my past project experience to how I’d handle challenges and collaborate.

The pace and structure made it easy to understand what was being evaluated at each step. I felt

Create a free Dataford account to unlock the full round-by-round breakdown, the questions asked and the outcome.

Read the full report Read the full report

Preparing for this interview?

General Motors (GM) Software Engineer interview guideThe full process, round by round, with the question bank Practice Software Engineer interview questionsReal questions from this role across companies All General Motors (GM) interview guidesEvery role we cover at this company