Хабр USA All articles
Industry Trends

The $180K Flight Ticket: Why Some Startups Are Ditching Relocation for Distributed-First Hiring

Хабр USA
The $180K Flight Ticket: Why Some Startups Are Ditching Relocation for Distributed-First Hiring

Ask any startup founder what it costs to hire a senior engineer and you'll get a number. Ask what it costs to relocate one, and you'll usually get a shrug. That shrug is expensive.

We spoke with a dozen CTOs, two immigration attorneys, and a handful of relocated engineers to piece together the real ledger behind the great relocation wave of 2022–2024 — and why a quiet reversal is underway.

The Sticker Price Nobody Budgets For

The base salary is the easy part. A senior backend engineer relocating from, say, Tbilisi or Belgrade to the Bay Area commands $160K–$200K — often a 3–4x jump over their previous compensation. But the salary is maybe half the story.

Visa sponsorship and legal fees typically run $15K–$30K per candidate, sometimes more when premium processing or RFE responses are involved. Relocation packages — flights, shipping, temporary housing, a landing buffer — add another $20K–$50K. Then comes the silent killer: payroll taxes and benefits priced for the US market. An engineer whose fully-loaded cost in Eastern Europe might have been $70K becomes a $280K line item in California.

"We did it for three engineers and burned roughly $700K in year one above what a distributed model would have cost," one Series B CTO told us, asking not to be named because his board hasn't formally signed off on the shift. "And two of the three were asking about moving to Austin within eight months anyway."

The Retention Problem Nobody Puts in the Deck

Immigration attorney Mara Feldman (a fictionalized composite of several practitioners we interviewed) describes a pattern she calls the "two-year itch": engineers who relocate under sponsorship are effectively locked in, but once permanent residency timelines clarify, mobility spikes.

"The visa is retention until it isn't," she says. "Companies discover that the same engineer they paid to bring over is now interviewing elsewhere, and their new employer simply restarts the sponsorship clock."

There's also a quieter attrition factor: culture shock, spousal employment gaps, and the sheer cost of Bay Area family life push some relocated engineers back toward remote roles — sometimes with the same company, sometimes not.

The Distributed-First Counter-Move

The alternative isn't outsourcing in the 2010s sense — body shops, timezone misery, code tossed over the wall. The new model, which several of our interviewees call "distributed-first," treats Eastern European hubs as co-equal engineering centers from day one.

The economics are blunt. A principal engineer in Warsaw or Yerevan at $90K–$120K fully loaded, working from a modern coworking setup with overlapping hours to CET and partial overlap to ET, delivers senior-level output at 40–60% of the relocated cost. No visa lottery. No relocation churn. No $3,000/month apartment subsidy.

One fintech CTO in New York put it simply: "I can hire two staff engineers in Belgrade for the cost of relocating one to Manhattan, and they don't leave when their green card clears."

Where Relocation Still Wins

To be fair, distributed-first isn't a universal answer. Early-stage teams building culture from scratch often benefit from co-location. Roles requiring deep physical or regulatory proximity — defense-adjacent work, some healthcare systems, anything with hardware — genuinely need people on US soil. And security-conscious sectors sometimes prefer the legal simplicity of onshore employment.

There's also the human side. Some engineers want to relocate, for opportunity, for family, for the experience itself. Companies that treat relocation as an employee benefit rather than a staffing tactic report far better outcomes.

The Takeaway

The relocation wave was driven partly by genuine urgency — the 2022 exodus of Russian-speaking engineers was real, and companies that moved fast won talent. But urgency is a bad budgeting framework.

The startups quietly winning this cycle are the ones running honest math: not what does the hire cost, but what does the model cost over three years — including churn, visas, taxes, and the option value of not putting all your people in one expensive zip code.

The engineers, for their part, have figured this out too. Many of the best ones now ask a pointed question in interviews: "Why do I need to move to do this job?" Increasingly, the strongest answer a startup can give is: you don't.

All Articles

Related Articles

Three A.M. Heroes: The Invisible Fixes That Kept American Software From Falling Over

Three A.M. Heroes: The Invisible Fixes That Kept American Software From Falling Over

Yandex Was the Best Company You Weren't Watching. Its Unraveling Is a Masterclass in Fragility.

Yandex Was the Best Company You Weren't Watching. Its Unraveling Is a Masterclass in Fragility.

How Well-Funded Startups Keep Building Expensive Houses of Cards — And Why Eastern European Engineers See It Coming

How Well-Funded Startups Keep Building Expensive Houses of Cards — And Why Eastern European Engineers See It Coming