An executive search firm says there are exactly 2,000 people in the United States qualified to do one of the hottest jobs in tech right now. Not 2,000 available. Two thousand, total, full stop. Demand for that job is projected to grow 2,100% by the end of the year. The job is called forward-deployed engineer, and two years into the AI boom that was supposed to shrink headcount everywhere, it’s one of the clearest signs that AI adoption is creating entirely new categories of work faster than it’s eliminating old ones.
Forward-deployed engineer jobs in 2026 didn’t exist as a mainstream hiring category eighteen months ago. Now Christian & Timbers, the executive search firm behind that 2,000-person estimate, says 70% of companies were planning to hire FDEs by the end of the second quarter — up from just 5% to 10% at the start of the year. That’s not incremental growth. That’s a category going from niche to nearly universal in six months, and it’s a useful reminder that “AI is coming for your job” and “AI is creating jobs nobody’s heard of yet” can both be true of the same technology at the same time.
What a forward-deployed engineer actually does
A forward-deployed engineer — FDE, in industry shorthand — is someone who embeds inside a client organization to actually get AI systems working: connecting models to messy internal data, untangling workflows, and making sure an AI pilot survives contact with a company’s real, duct-taped-together tech stack. Palantir popularized the role years ago, deploying engineers directly into client operations rather than shipping software and walking away.
The term has exploded because that’s turned out to be the hard part of AI adoption. Buying access to a frontier model is easy. Getting it to do something useful inside a Fortune 500 company’s decade-old CRM, three different data warehouses, and years of undocumented process is not. Christian & Timbers’ research — built on interviews with more than 250 C-suite hiring executives across 180 companies, a survey of 80 Fortune 500 executives, and conversations with over 300 FDEs and applied AI engineers between January and June 2026 — found that the largest consulting and services firms are reporting a need to grow their FDE headcount tenfold, building out teams of 20 to 100 people.
The talent pool hasn’t kept pace. The study puts the total number of FDEs on the market today at around 17,000, with a meaningful share already employed at Palantir. Of those, the firm estimates only about 2,000 have the specific mix of technical depth, industry knowledge, and hands-on deployment experience needed to reliably deliver what Christian & Timbers founder Jeff Christian calls “multiple tens of millions of dollars of ROI impact” — the kind of value that shows up as accelerated revenue or genuinely automated back-office work, not just a slide deck about AI strategy.
Why AI adoption is creating jobs, not just cutting them
The clearest illustration of this showed up this month in the launch of June, a startup that emerged from stealth on August 3 with $20 million in pre-seed funding led by Marc Benioff’s Time Ventures. June’s founder, former Salesforce executive Efrat Rapoport, put the paradox in plain terms: “AI, paradoxically, increases the demand for professional services.” Her point wasn’t abstract. It’s that most companies trying to deploy AI hit a wall of fragmented data, duplicate fields, and years of technical debt that no model can reason its way through on its own — so the industry’s default answer has been to hire more people to bridge that gap, not fewer.
That’s consistent with what’s happening at the top of the AI labor market more broadly. Days after June’s launch, Jeff Dean — one of Google’s longest-serving and most influential engineers — announced he was leaving to co-found Discovery Loop, a new venture aimed at using AI to accelerate scientific research, alongside several other senior Google AI researchers. Whatever you think about where AI research is headed, the pattern at the leading edge isn’t fewer specialized humans. It’s a scramble to hire and deploy more of them, in new roles that didn’t exist a product cycle ago.
Chris Taylor, CEO of Ode with Anthropic — a services firm built specifically around forward-deployed engineering — drew a useful distinction: “Many FDEs are well equipped to help you roll Claude Code out to your workforce. Very few are capable of building your flagship AI product feature.” In other words, this isn’t just one job. It’s a spectrum of new specialist roles, most of which are still being defined in real time, at companies that are hiring for them faster than job descriptions can keep up.
There’s independent evidence this shift is showing up in real usage patterns, not just hiring announcements. Anthropic’s own Economic Index — a research dataset tracking how people actually use Claude across occupations, released as a queryable connector in late July — is built specifically to answer questions like which jobs are absorbing the most AI-driven task change and how. It won’t tell you where the FDE jobs are, but it’s a sign that “which roles are AI adoption reshaping” is now something companies and researchers are trying to measure directly, rather than guess at from headlines. The forward-deployed engineer boom is the sharpest current example of that reshaping in action.
What this means if you’re not one of the 2,000 elite FDEs
Here’s the practical problem: a talent category growing 2,100% and topping out at 2,000 truly qualified people isn’t a job market you find by searching “forward deployed engineer” on a job board and waiting for a recruiter to call. Demand this concentrated and this new moves through networks first — consultancies staffing up teams of 20 to 100, enterprises building “internal FDE” functions to keep proprietary knowledge in-house, and AI labs’ own services arms (OpenAI’s Deployment Company, Anthropic’s Ode) all competing for the same tiny pool of people, often before a formal req ever gets written.
That dynamic isn’t unique to FDEs — it’s just an unusually visible version of how hiring actually works in a fast-moving, expertise-scarce category. Companies that are scrambling to fill roles they can barely define yet don’t post a polished job listing and wait. They ask around. They call people they’ve worked with. They reach out directly to engineers with relevant, adjacent experience — cloud migrations, enterprise integrations, applied ML — even if those people have never held the title “forward-deployed engineer” before, because the title itself is only a few quarters old.
If you have experience anywhere near this space — enterprise software implementation, data engineering, applied AI, technical consulting — waiting for an FDE-specific posting to appear is a slower path than it looks. The people making these hires are moving fast and asking their networks first, which means the fastest way into a role that didn’t exist a year ago is a direct message to someone doing the hiring, not a filtered job board search for a job title still being invented.
It’s also worth noticing which companies are hiring for this and why. Christian says enterprises across insurance, fintech, healthcare, and gaming — not just tech-native companies — are seeking out FDEs, often preferring to build internal teams rather than bring in outside consultants, specifically to protect proprietary business processes from the AI labs and consultancies they’re paying. That’s a useful signal if you’re deciding where to point your outreach: the demand isn’t concentrated in Silicon Valley AI startups, it’s spread across ordinary large employers quietly building a function that didn’t exist in their org chart a year ago. A regional insurer or a mid-size healthcare system building its first internal AI deployment function is often easier to reach directly than a frontier lab drowning in inbound interest.
The direct-outreach case
Christian’s own warning is worth taking seriously too: this window may not stay open forever. He told TechCrunch that within two years, agents could be automating other agents rather than humans doing the automating, and that the FDE role itself might eventually “go away” as the deployment problem gets solved by better tooling. For now, though, demand for the people who solve it manually is outrunning supply by an order most job categories never see.
That combination — a role expanding at 2,100% with almost no applicable job-board history — is close to a textbook case for reaching out directly instead of waiting for the listing to catch up. There isn’t yet a deep archive of “forward deployed engineer” postings to search, and even where postings exist, the firms hiring fastest are explicitly building internal teams and going through referral networks to avoid losing proprietary process knowledge to outside consultancies. Applying blind into that kind of hiring motion means competing for the small fraction of roles that make it to a public listing at all, weeks after the actual hiring conversation started.
Emerging categories like this are exactly where identifying the right person — a team lead building out an internal AI deployment function, a hiring manager at one of the services firms racing to staff up — and reaching them directly pays off before the role is fully defined, let alone posted. angld.AI is built for that moment: paste in a company name or a job description, even a rough one, and it identifies the person actually making the hiring call, pulls together relevant background, and drafts a personalized outreach message in under a minute — so you’re one of the people a hiring manager hears from directly, not one of a thousand applicants to a listing that hasn’t been written yet.
