Pros
Lots of vacation given on day 1
Cons
I worked in GMIT for 4 years. I no longer do. If you were family, I would advise you to avoid GMIT for several reasons: (1) There is no defined technical career plan if you don't want to become a Project Manager. GM likes to pretend (lie) that not having a defined technical career plan speaks to the various career opportunities that you will encounter at GM. In reality, out of my 4 years at GM, i saw a grand total of TWO people in my org (about 150 people) get promoted. The rest stayed in same position, switched teams, or left GM altogether. Many of the people in my org who I respected as brilliant engineers inevitably leave GM for greener pastures. (2) GM doesn't appreciate IT. They talk a lot about having a vision of GM as a tech company while simultaneously offering none of the perks of tech companies and certainly nowhere close to the salary (esp in Austin, a growing tech hub). Pay for coffee, pay for food at "lunch & learn" event, etc (3) Many of your colleagues in GMIT will be low-performers and you will often have to clean up after them. This is largely due to the complete absence of technical questions during the interview. It's all personality questions. So you end up working with people who are polite and incapable of innovation. (4) Many teams don't follow best practices for software development. Code review, continuous integration, blue-green deploy, unit testing, etc .... completely absent on many teams. Your skills will actually end up deteriorating if you're not careful (even as a college grad with a clean slate mind) . Imagine going to an interview for your next job and saying "we didn't write unit tests" - who would want to hire that engineer ? If you do end up working at GMIT, have your side projects that you work on at home so that you can actually solve interesting problems and have something to talk about in interviews.