The interview process began with a phone screening conducted by a recruiter, where general questions were asked. Eric informed me that the process would involve six rounds, including multiple LeetCode-style interviews repeated across three rounds.
The first round was an online coding assessment on Codility, featuring LeetCode-style questions. The second round was another easy LeetCode-style problem, also conducted via Codility. In the third round, I spoke with a technical interviewer who focused on my past experience and asked questions related to Java, Kafka, and general backend development.
The fourth round was again LeetCode-style coding, and it was unclear why the same type of assessment was being repeated. The fifth round involved a system design interview.
The final round was a behavioral interview with Engineering Manager Hussain. Unfortunately, it didn’t feel like a meaningful conversation, as he seemed more interested in wrapping up the interview quickly.
I felt useless after going through a six-hour interview.
LRU cache in system design.
Using a hashmap + doubly linked list in LeetCode.
The following metrics were computed from 16 interview experiences for the General Motors Senior Software Engineer role in United States.
General Motors's interview process for their Senior Software Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having good feelings for General Motors's Senior Software Engineer interview process in United States.