Thread regarding General Motors layoffs

Stay away from GM IT

I wouldn't recommend joining GM IT. I had 10+ years in software engineering in a different industry with very basic web experience, hoping to strengthen those skills and grow my career with GM. The hiring manager and the leads enjoyed interviewing with me and decided to hire me. I even received a decent relocation package to Michigan. Six months after my starting date, my team was merged with another team and my hiring manager was "relieved" of his managerial role, which was given to the manager of the other team (this was a hint of things to come). One year after this transition, my hiring manager, who remained on the team mostly to maintain morale, joined the business team as a business analyst (yes, quite an odd transition for a senior IT software manager). A month or so later, I was let go (1.5 year into my GM career). The company-wide layoff was announced three months later. I was duped into coming to Michigan only to have the rug pulled out from under me. I'd think they'd demote me (was 6A) or cut my pay if it's indeed a lack of web experience, but to cut loose an experienced software personnel just like that tells you how much they value IT talents. Years of Ciera, S10, Sonoma, and Silverado ends with me; No more GM ever again.

Good advice, @Yhd4nsK-7poq.

by
| 1483 views | | 6 replies (last ) | Reply
Post ID: @OP+YpSs8R9

6 replies (most recent on top)

Stay away from GM period. The company has black balled itself !

by
| | Reply
Post ID: @6qpl+YpSs8R9

Great insight guys!!

Gracias

by
| | Reply
Post ID: @3nhb+YpSs8R9

In Austin, maybe 80% of the engineers were in their 20s and pretty inexperienced.

The older people were managers who weren't very technical, so they couldn't guide anyone even if they wanted to. And they usually only cared about schedule, not quality or anything else.

Just deliver something on the date the manager promised, no matter what it was or how buggy.

by
| | Reply
Post ID: @2whr+YpSs8R9

2eow-- spot on. That was exactly my experience in Austin.

In 95% of the groups, the technical bar was very low. Everything was about politics.

Heck, the people in the Austin office only showed up between 10 and 4, with 2 hours off for lunch.

The whole office was empty before and after.

You'd think management would care. You'd be wrong.

by
| | Reply
Post ID: @2tql+YpSs8R9

TLDR; Even as a new college hire, you can do so much better than GMIT. The world is your oyster if you can code, don't settle for a sh-- company.

I worked in GMIT for 4 years. I no longer do. If you were family, I would advise you to avoid GMIT for a 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.

(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.

by
| | Reply
Post ID: @2eow+YpSs8R9

Right on. Losing customers one at a time.

by
| | Reply
Post ID: @xsj+YpSs8R9

Post a reply

: