I was told that internally at Redhat if you’re assigned to a project and the project becomes unsupported by the company, you have a certain amount of time to be picked up by another team, after which, if you aren’t, you are let go.
I know that this is kinder than just firing someone outright if the project they were on failed, but the thought of it makes me feel uncomfortable.
This is more or less also how IBM operates. I know someone who had to interview for other teams at IBM because their other IBM project ended. After a while of trying to navigate the politics of it all they just gave up on IBM completely.
Sorry maybe I don't have my moral sensors tuned properly today but would you mind explaining what makes you feel uncomfortable about it?
Is it more because RedHat carries itself like a consultancy than other large enterprise businesses? Is it that the possibility of being let go after a large project that you performed a relatively specialized role on feels just about right for a consultancy, but not for a business that carries themselves like a long term player? I feel like I'd expect this behavior from Pivotal for example (not implying that they'd do that).
> Is it that the possibility of being let go after a large project that you performed a relatively specialized role on feels just about right for a consultancy, but not for a business that carries themselves like a long term player?
This. Someone there could hire me onto a project that fails for some reason out of my control, and then, because I’m older, I wouldn’t get picked up by another team.
I don’t know if project-pickup retention is still how they operate; it’s several-year-old anecdotal information from a past worker there before they were acquired by IBM.
I know that this is kinder than just firing someone outright if the project they were on failed, but the thought of it makes me feel uncomfortable.