Not for everyone
Not for everyone
Good salary, medical insurance, and cool benefits.
Work-life balance is very bad.
Building in JS frameworks is not used anywhere, which causes programs to lose their edge with "living" frameworks. Professionally, this is a cemetery for developers.
Mid- to low-level management have no idea what code is all about or how to deal with workers.
There is a lot of politics in mid- to low-level management.
Additional Ratings
Was this helpful?
General Motors Interview Questions
General Motors Interview Experiences
Software Engineer
Seamless process. First round was the technical test, which consisted of two LeetCode questions (easy). Then, the recruiter asked about why this company. The last one was with the hiring manager. I didn't make it through the recruiter.
Software Engineer
I first applied through Handshake. Then they made me do a coding assessment through HireVue, which had three questions and a time limit of three hours (from what I remember). A month later, they conducted a behavioral interview through Microsoft Team
Software Engineer
The interview process was straightforward. I had a phone screen with a recruiter to go over my resume. Then, a 2-hour technical interview with questions from what became my day-to-day tasks. These questions were algorithm questions, e.g., "how will y
Software Engineer
United StatesOctober 1, 2020Seamless process. First round was the technical test, which consisted of two LeetCode questions (easy). Then, the recruiter asked about why this company. The last one was with the hiring manager. I didn't make it through the recruiter.
Software Engineer
Los Angeles, California, United StatesSeptember 1, 2022I first applied through Handshake. Then they made me do a coding assessment through HireVue, which had three questions and a time limit of three hours (from what I remember). A month later, they conducted a behavioral interview through Microsoft Team
Software Engineer
Toronto, Ontario, CanadaSeptember 1, 2021The interview process was straightforward. I had a phone screen with a recruiter to go over my resume. Then, a 2-hour technical interview with questions from what became my day-to-day tasks. These questions were algorithm questions, e.g., "how will y
