Initial phone call with recruiter. There was no technical phone screening interview. I was asked to come in for an in-person technical interview directly.
The technical interview lasted about 2 hours, with 2 developers. They were chill and kept the interview casual and relaxed.
I was told to wait – there would be another behavioral interview if they decided to proceed. I had the behavioral interview soon after with 2 managers. I was asked something about handling conflict and dealing with ambiguity.
Since they work on porting the AOSP to work in an automotive setting, they had a lot of questions to ask about the theory of operating systems like heap vs stack, threads vs processes, deadlocks, mutex, and semaphores, etc.
Questions about the Java programming language itself, including intricacies about inheritance, the static keyword, threading in Java, etc.
The following metrics were computed from 1 interview experience for the General Motors Android Software Developer role in Oshawa, Ontario.
General Motors's interview process for their Android Software Developer roles in Oshawa, Ontario is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for General Motors's Android Software Developer interview process in Oshawa, Ontario.