Phone Interview - This was with the Lead Developer on the team. As others have mentioned, the STAR methodology is used heavily.
Very few technical questions, and those asked were fairly basic:
In-Person Interview - Received an invite for an in-person interview shortly after the phone interview.
Before meeting with the interviewers, I was greeted by an HR person who took myself and another applicant to a conference room to watch an intro video about GM. Not sure what it was about the HR person, but he wore me out after listening to him for 15-20 minutes. The video was pretty much a sales pitch for working at GM.
After the video, I was taken into a small room and interviewed 1-on-1 with a hiring manager. Again, behavioral questions were asked, very few tech questions. The hiring manager didn't seem interested right from the start; it made me think he was going through the motions and already had a candidate selected.
Second interview was with another hiring manager. He asked very similar questions to the first interviewer and also asked about my experience using certain JavaScript frameworks: Durandal, Node, JQuery, etc.
All-in-all, it was a fairly comfortable experience. Didn't feel like I was being "grilled", as is the technique for many other companies hiring developers.
Tell me about a project where part or all of the project had to be reworked or scrapped.
The following metrics were computed from 1 interview experience for the General Motors .NET Software Developer - Sales and Marketing role in Phoenix, Arizona.
General Motors's interview process for their .NET Software Developer - Sales and Marketing roles in Phoenix, Arizona is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for General Motors's .NET Software Developer - Sales and Marketing interview process in Phoenix, Arizona.