It depends. If your role is "generic, replaceable developer" then you could risk outsourcing. If you're in a specific kind of project, or in a specialist position, it's less likely.

Then again I lost a position in a corp when the whole project was cancelled. The redundancy pay was sweet though.

> Then again I lost a position in a corp when the whole project was cancelled.

Sorry to hear that. As long as it wasn't canceled because they had trouble paying the bills or the teams were dysfunctional, that's usually pretty short-sighted of the corp.

Here's a bunch of people that we've already taken the cost of recruiting/training/onboarding who are familiar with our technology and processes. The right answer is to reassign them to other work in the organization.

It's an interesting situation from the other side as well. I got some resources to try to relocate to another team, but wasn't keen on it. One day you hear your team is important another that the whole project is finished - made me reluctant to try again. OTOH, in a big corpo the recruiting/onboarding costs are probably just ongoing / don't matter that much.

For sure. Large legacy corporations fire people far less than silicon valley companies fire+go out of business. And usually with larger lay off packages.

I knew people who had been working for large legacy corps who made 6 figures for over a decade while having the technical chops of a high schooler after their first AP programming class, and barely speaking English.(didn't know common words like bread, or meat)