FDE Follows the Customer, Not the Code: Why the Map Went Bicoastal

Palantir invented the Forward Deployed Engineer in the Valley. Two decades later, the role it created is nearly as common in Manhattan as it is in San Francisco. That is not a coronation — SF still leads on every way you can slice the data — but it is the surprise worth explaining. Almost every other engineering discipline clusters tighter around San Francisco each year. FDE is the one that’s spreading out. The map went bicoastal, and it went that way for a reason that’s baked into what the job actually is.

What the board actually shows

Start with the honest snapshot, because the temptation here is to overclaim. On the fde.directory board, open US listings, August 2026: San Francisco appears in 42% of postings and New York in 32%. That’s any-mention — a role that lists “San Francisco / New York” counts for both. Narrow to listings that name a single metro and pit the two coasts head to head, and SF takes 56% to New York’s 44%. Look only at the first-listed, primary city and the gap widens again: SF 32%, NYC 22%. The rest of the Bay — Palo Alto, Mountain View, Menlo Park, and the other Valley towns — adds another 8% or so, with Boston, DC, Austin, and Seattle trailing as minor nodes.

Read those three cuts together and the story tells itself. San Francisco leads everywhere. It is still the plurality city and, when a company forces a single choice, still the default. But New York isn’t a second city on this board; it’s the co-capital. On the any-mention cut, the two are ten points apart, not thirty. For a role born in Palo Alto, drawing even-ish with the Bay from Manhattan is the anomaly that demands a mechanism.

The mechanism: gravity is the customer, not the talent pool

Here’s the contrarian core. Every other engineering role tracks engineer supply. Where do the model researchers, the infra teams, the platform engineers cluster? Wherever the labs and the other engineers already are — which is the Bay. Talent attracts talent; the density compounds. That gravity has only strengthened as the frontier-model boom concentrated the hardest technical work in a few square miles of San Francisco.

FDE breaks the pattern because an FDE’s job is not to sit next to the model. It’s to sit next to the customer — to embed in the customer’s systems, the customer’s data mess, and often the customer’s building. The role’s center of gravity is therefore customer HQ density, not engineer supply. And customer HQ density has a different map. The large enterprises that buy and deploy AI at scale — banks, insurers, asset managers, media and publishing houses, law firms, retailers, pharma — are not headquartered in San Francisco. They’re headquartered in New York.

The numbers behind that are stark. New York City proper is home to 43 Fortune 500 headquarters, and the broader metro area leads every US region with roughly 49 — more than any other city in the country. That is the buyer base an enterprise FDE deploys into. San Francisco is where the models get built; New York is where they get bought. When the seat has to be near the deployment, the deployment is disproportionately in Manhattan.

Why New York specifically — and why now

Two things happened at once. The obvious one: as the FDE model scaled past frontier labs and into the Fortune 500, the seats followed the buyers into New York’s enterprise core. The less obvious one: the builders came too. The frontier labs are now opening and expanding New York seats of their own. Anthropic leased a 16-story Manhattan building in Hudson Square and said it plans to more than double its NYC headcount to over 1,000 by the end of 2026, up from fewer than 500 at the start of the year. OpenAI has its SoHo office; Palantir, Google, and a long tail of AI companies are adding space — AI firms signed roughly 845,000 square feet of Manhattan office leases in 2025 alone.

So both sides of the FDE equation now list New York. The buyers were always there; now the builders are planting flags a few blocks away. That’s what pulls a market from “second city” to “co-capital,” and it’s why the near-parity shows up on our board rather than staying a real-estate story.

There’s a directional hint that New York’s share is still climbing — among postings dated July 2026 or later, New York’s any-mention share ticks up versus older listings. I’d treat that as early and unconfirmed: the older sample is thin, and one board is not a proven multi-quarter trend. It’s a signal we’re tracking, not a number to bank on.

What it means if you’re the candidate

The practical read is clean. If you want to build the models — to be near the research, the training infrastructure, the frontier — San Francisco is still the center of the universe, and that isn’t close. If you want to deploy AI into large enterprises — to own the last mile inside a bank or an insurer or a media giant — New York is now a first-class FDE market, not a consolation posting. For the first time, an ambitious FDE can build a serious career on either coast without treating one as a step down.

A few smaller nodes are worth watching: Washington, DC for government and defense deployments, and Austin as an emerging node, each showing up in the low single digits. Neither is close to the two coasts yet, but they’re the places to watch if the customer-gravity thesis holds and the map keeps spreading toward wherever the buyers are.

None of this dislodges San Francisco. It’s still the build capital and still the plurality on every cut we ran. The point is narrower and, I think, more interesting: FDE is the rare engineering role whose geography is dictated by who’s buying the technology, not who’s building it — and once you internalize that, a bicoastal map isn’t a surprise at all. It’s the prediction.

For a primer on the role itself, see what a Forward Deployed Engineer actually does; for what these seats pay on either coast, the 2026 salary guide. Want the New York and San Francisco openings as they post? Browse the board or subscribe for the weekly.

— A. George