3 ms·
Many of these were transitions from other firms. For example, I am part of this 8000, and I, along with many peers, were hired from HP to (at first) do the sam
by c0nsumer 12y ago
Many of these were transitions from other firms.
For example, I am part of this 8000, and I, along with many peers, were hired from HP to (at first) do the same job as before, but for GM. We had previously been contractors or part of HP Enterprise Services with GM as our customer. So, for a good number of these it wasn't a bunch of jobs being created but a simple insourcing shift.
It's been roughly two years since my transition over to a direct job and I've been happy with the choice to take the offer. There's nifty things happening here, way more flexibility and opportunity than before, and GM's a good company to work for.
ADDENDUM: I wouldn't consider myself a programmer; I'm more of a systems engineer / troubleshooter / sysadmin who writes small utility things as-needed.
- smackfu 12y ago"Insourcing" doesn't sound like it would be very simple since I don't see what incentive HP has to let the people go to GM.
- csours 12y agoSimple for the employees changing employers; whatever GM did to facilitate the transfer has not been made public.
- domdip 12y agoProbably preferable to layoffs (cheaper, no bad press) if a major project is shutting down and they have nowhere to put them. Also, could have been wrapped up in all sorts of other agreements about termination of contract. This was probably a major deal for both companies.
- c0nsumer 12y agoWith all of the recent layoffs that HP has had, I'm glad I'm no longer there. Working directly for GM feels considerably more secure than HP ever did. As others have said, I suspect it was an easy way to shed a bunch of employees without having to pay severance.