Part of the guide: Nearshore Software Development: A Field Guide
A note on this archive: an earlier version of this site was lost in a migration, with no surviving backup. This piece is a good-faith recreation of our writing from this period, not a recovered original; its date reflects the period it represents. See about this archive.
Over the past year, wave after wave of layoffs swept through tech — hundreds of thousands of roles, at companies that had spent a decade only ever growing. I won't pretend to have a tidy theory of why it all happened. But I do spend my days in the market it reshaped, and I want to push back on the conclusion a lot of people jumped to.
The lazy read is: "great — senior talent is cheap and easy to get now." It's wrong, and acting on it will cost you.
A flood of résumés is not a flood of the right people
It's true that a lot of genuinely good engineers became available who weren't before. It's also true that the number of applicants for any given opening went up enormously. Those two facts are not the same thing, and confusing them is expensive.
When a role draws four hundred applicants instead of forty, your problem isn't supply anymore — it's signal. The best people in that pile are still in demand, still fielding offers, still gone within a week. What grew is the haystack, not the number of needles. We've made this point before in tighter markets, and it's only more true now: vetting is the whole game. A downturn doesn't lower the bar for finding senior people; it raises the cost of getting it wrong, because now you're sifting.
The work didn't stop
On the other side of the table, something quieter happened. Companies froze full-time headcount — the budget conversations got serious, "do more with less" went from a slogan to a mandate — but the roadmaps didn't shrink to match. The features still had to ship. The on-call still had to be covered.
That gap, between frozen hiring and unfrozen work, is exactly where flexible capacity earns its keep. When you can't add a permanent employee but you still have to deliver, engaging a senior developer on a contract basis turns a fixed cost you can't get approved into a variable one you can. You bring on the capability when you need it, and you're not carrying it when you don't.
And to be clear about the distinction, because it matters: that isn't a laid-off employee by another name. It's a genuinely different relationship — independent, scoped, flexible — and an honest answer to a real constraint, not a loophole.
Why this favored nearshore, specifically
Put those two pressures together — be more careful about who you bring on, and turn fixed costs into variable ones — and you get a market that rewards exactly the model we'd already been building toward.
Senior developers across the Americas fit both pressures at once. They're flexible capacity without full-time overhead, and they're in your time zone, so the careful integration good work requires can actually happen. The cost discipline of the moment makes them attractive; the seniority and the overlap are what keep the work good. It's the combination again — not the lowest rate, but the right person, reachable when you need them.
Quality still wins — especially now
The temptation in a downturn is to let "cheaper" quietly become the only thing that matters. I'd resist it. The companies that come out of a hard stretch in good shape are usually the ones that stayed disciplined about who does the work, not just what it costs. We don't win by being the cheapest, and we don't think you should buy that way either.
A market full of available people is not a market full of easy answers. It just means the judgment about who you actually bring on matters more than it did when everyone was hiring at once. Spend that judgment well.