Real, anonymous reports from people who interviewed for Software Engineer at General Motors (GM), newest first and distilled into what to expect across the loop.
I started with a recruiter touchpoint, then after a couple follow-ups I ended up in a structured sequence of rounds. The first part was the technical coding segment with a 45-minute slot, and once I cleared that, I moved into another 45-minute round focused on debugging. After that, there was a final 45-minute domain/depth discussion that felt more like a hiring-manager conversation, where the tone shifted from pure implementation to explaining my experience and how I approach problems.
I went through a pretty standard multi-round loop. After recruiter contact and scheduling, I took an online assessment that mixed one easy and multiple progressively harder LeetCode-style questions. The next round was behavioral, around 40 minutes, with classic prompts and a focus on telling stories with structure.
The interview process typically follows a structured multi-round format, starting with a recruiter touchpoint, followed by a coding assessment, and concluding with behavioral and technical interviews. Candidates often experience noticeable gaps between rounds, allowing time for preparation.
Candidates encounter a coding assessment early in the process, often featuring LeetCode-style questions that test fundamental programming skills. The assessment serves as a critical gatekeeper, determining progression to subsequent interview rounds.
Behavioral interviews are prevalent, focusing on candidates' past experiences and problem-solving approaches, often using the STAR method. These rounds assess fit and communication skills, with interviewers looking for clear storytelling and reflections on past work.
Technical interviews often emphasize core concepts such as object-oriented programming and system design, with candidates expected to articulate their thought processes clearly. The difficulty level varies, but candidates should be prepared for in-depth discussions on their technical expertise.
Candidates report varying levels of communication from interviewers, with some experiencing a lack of responsiveness post-interview. Engaging discussions and clear expectations during interviews can enhance the overall experience, while poor communication can lead to frustration.
The overall interview experience is generally described as organized and fair, with candidates often receiving offers after demonstrating both technical and behavioral competencies. However, some candidates noted inconsistencies in outcomes and communication, impacting their perceptions of the process.