Most large corporations treat these categories of employment as different budget line items with different rules and limitations: (1) full-time employees, (2) individual contractors, and (3) large contractor "body-shops" or outsourcing providers. Many times in my career, I have seen layoff a few from (1) then way over spend on (2) or (3). The mid-level manager who makes the decision gets to "claim" that expenses were reduced in (1) and "win" at year-end reviews. Yes, I know: This is total non-sense, but I have seen it many, many times at mega-corps.

when i worked for an australian bank, one co-worker in a nearby team had been working on the the banks systems as a sysadmin for over a decade.

the bank would go through cycles of "we need to reduce our headcount and outsource everything" and then 4 years later "we need to reduce spend on contractors and retain more knowledge and expertise in house". he'd survived multiple waves of it, switching back and forth between being an employee or a contractor through some external agency, as management trends changed, while essentially doing the same job.

I've seen that in a large management consultancy company. Part of their risk management procedures (both for the company and in terms of some EU law) meant they couldn't keep contractors for longer than x years. They'd have to convert to employee or separate for 12 months.

Bit that doesn't really work in knowledge systems. Even with the best documentation people will build up knowledge that no one has, and their departure is costly.

Equally at the end of their contract a lot of time will need to be spend on a handover which slows down others even more.

So what happened? The contractor went via another middle man, which checked the correct boxes on the form, and everybody was happy.

> One pattern I saw repeatedly was a contractor being let go, only to return via a large outsourcing provider. The provider must have added a substantial markup despite supplying the same engineer back to the same team, without having incurred any procurement costs.

When I worked (well, was a contractor at) a very large company, they'd kicked out all their small contracting providers only to get the same people back via a single big one. I was told this was part of a vendor consolidation move, because maintaining their existing direct relationship with literally hundreds of thousands of vendors had a huge cost in itself.

I doubt they were dumb enough to think there was no markup, but going direct isn't free either. There ain't no such thing as a free lunch.

Now, was it a net good move? That's both above my pay grade and not my expertise. But from the fact it took me a month of billed time to buy a license of that same company's own product[1], I wouldn't have called it an efficient bureaucracy.

[1] all purchases of own-company product had to be done through the 99% internal billing discount program.

It's very possible that this occurred during the IR35 shake-up - HMRC moved the liability for unpaid income tax (in a situation where a contractor was determined to be a de-facto employee) from limited company contractors themselves onto the client (the bank, in this case).

Banks had a very low risk appetite and so had to let these people go. What was going on in a lot of places was that vital staff who had to be dumped were intermediated by outsourcing providers. These companies either then paid the staff a very high salary and sold them in as temp labour, or took on the risk themselves and hired them as contractors for the same purpose.

This all made sense, but for a lot of contractors at the time, it felt like the apocalypse. The net effect was that HMRC exchanged flexibility in the labour market for immediate tax take. This may not have been a sensible decision.

I have a friend who left BigCo and then rejoined it as a contractor, plus some additional employees that he manages now. He cynically says "My job is to convert OpEx to CapEx when the finance department tells some director they can't have more headcount."

> Senior management routinely seem baffled that they could announce redundancies or hiring freezes, yet technology costs would continue to rise.

I dont think they're baffled, they just trying to show they're attempting to keep costs under control.

> One pattern I saw repeatedly was a contractor being let go, only to return via a large outsourcing provider.

That's 'normal' in Canada and France.

I think I have a simpler answer: quarterly results.

Management just really needs to make the next earnings look like what it should look. Next quarter is next quarter's problem.

In my experience, it's probably due to differences in budget line items. Usually, regular labor costs and outsourcing costs are budgeted separately. Some teams may not have the authority to hire an additional full-time employee, but they do have the authority to use external contractors. On top of that, the internal political landscape differs as well. When it comes to office politics, increasing headcount in a particular department means increasing that department's influence. There are also additional benefits and administrative costs that come with hiring permanent staff. Moreover, standard contracts usually come with overhead for contract management personnel and procedural costs, and these are often handled by the vendor side. In other words, direct employment comes with long-term responsibilities for performance and benefits, but when you outsource, most of that liability shifts to the external vendor.

I've told this story before, but I worked for an ISP that was obsessed with things like CAPEX vs. OPEX and staffing vs. outsourcing (they always mixed those two for some reason, even if I'd say that buying consultants and salaries are both OPEX). In any case, it resulted in outsourcing 50% of development to a another company, at twice the cost, then keeping those consultants on for a decade. The saving, had they hired instead would have been massive. The reasoning was: Well we can fire the consultants in within two weeks... sure but you can fire staff within a month or two. Six months at the most. Right now you're just announcing that you suck at long term planning.

At one point they were convinced that the operations team was horrible inefficient and outsourcing would be cheaper (they'd already pulled operations back from IBM, because IBM is expensive and incompetent). Luckily someone decides to get some other consultants involved and actually measure the inefficiencies, before taking action, so the savings made from outsourcing the team (again) would be more clear. They didn't expect to be told that they had one of the speediest, leanest and most efficient operations teams in the country.

Same company handed out 20% raises one year and the next we were apparently almost broke. Then no on wanted to work there, because there were no prospects of a raise in the future, so they started hiring new people at MUCH higher starting salaries. They'd start people out on the salary levels you'd expect to reach after 5-8 years, so they would avoid having to budget in raises.

At some point companies just get top heavy with incompetent business types, who doesn't tend to stick around, at least not in the same role for to long. They forget the past and start their playbook, which always happens to be the reverse of what happened two years ago.

This doesn't seem to answer why an engineer is let go and gets rehired through an outsourcer.

The military is like this. Higher Headquarters decides to contract out maintenance and logistical support for $aircraft_fleet. Uniformed maintainers go home in Friday and show up Monday making a lot more money to do the same job but without risk of getting posted or deployed.

Contractor fees come out because of a different pot of money, so perverse incentives abound.

That's because the bankers didn't realize they're not in the banking business anymore - they're in the IT business (which has a focus on tracking money).

> Sometimes that means working around processes and incentives in ways that look very strange from the outside.

At my last performance review, at my last job (this is going back more than a decade now) one of my agreed KPIs was to take the lead on a 3-6 month project, making all the required technical decisions etc. and successfully delivering it on time and on budget.

I never got the opportunity, and quit that job six months later to start my own business, but still did contract work for them.

Got a social call a year later from my old boss (who also left, before I did) and got to tell them “so I hit my KPI, you’ll never believe what I had to do to make it happen…” :D

At the risk of injecting recent US politics into this, the shipyard I used to work at had five employees laid off under DOGE and replaced by the exact same individuals (there aren't actually that many naval architects in the US), now working as contractors at a higher base pay. I feel like there's a lot of that out there.