the cause behind the roles · endgame engineering

The new roles are bottlenecks with job titles.

When AI commoditizes the labor, a job title stops naming the labor and starts naming the boundary it dissolves. Every hot role that’s crystallized in the last few years maps to a specific cell of the bottleneck taxonomy, and where a cell is expensive and durable but still unnamed, the taxonomy predicts the role before the market does.

Emerging roles mapped onto the bottleneck taxonomy grid, showing coverage gradient F1 Don't understand F2 Can't work with F3 Can't align G1 Technologists G2 C-level G3 Business units G4 Customers G5 Marketplace FDE PM frontier high coverage (FDE) one seam (PM / translator) the G2 executive cells: priced, but no clean title yet

These roles aren’t emerging because the technical work got harder. They’re emerging because AI collapsed the cost of the technical work, and when the doing gets cheap, the scarce value moves to the boundary-crossing.

Every one of these titles is the market pricing a specific bottleneck cell. The technical skill is table stakes; the bottleneck it removes is the job. That’s a testable claim, and it runs both directions. It explains the roles that have already crystallized, since every one maps to a hot and persistent cell, and it predicts where the next ones appear: wherever a bottleneck cell is both expensive and durable, a role will form to remove it.

When AI commoditizes the labor, a job title stops naming the labor and starts naming the boundary it dissolves.
role → cell

Every hot title maps to a cell.

Notation is (Group, Failure): who the model is about, and how it fails. G1 technologists · G2 C-level · G3 business units · G4 customers.

Forward Deployed Engineer

The cleanest example. It removes the customer and technologist bottleneck at all three failure levels at once. The FDE embeds inside the customer’s organization, and the first thing they build isn’t code; it’s a customer-specific ontology, grounding the system in the customer’s own nouns and verbs. That’s the modeling cell. Because they’re embedded rather than handing a spec over a wall, the model never gets stuck, because translation is removed by presence. Because they ship and stay accountable for production code, the build aligns to the model. Then they route what they learn back to the platform: MAIT’s Improve→Transform loop wearing a job title. The tell that this is bottleneck-removal and not engineering: OpenAI created the role to fix a specific gap, customers stuck bridging trial to production, and the honest analysis says the models aren’t the problem, the deployment is.

Prices: (G4,F1) + (G4,F2) + (G4/G1,F3)

bottleneck-removal role

The builder & the AI Product Manager

Marc Andreessen’s “builder” merges product manager, designer, and engineer into one person, and the reason given is explicitly the elimination of the communication bottleneck between those three functions. That’s a pure translation play inside the product org. The AI Product Manager is described in the same language: a “translator” coordinating engineers, designers, and legal, sitting on the seam between what the model can do and what actually ships.

Prices: (G1,F2) + (G4,F2)

bottleneck-removal role

The Analytics Translator

McKinsey’s analytics translator bridges data science and the business. Practitioners are candid that it’s a skill set rather than a job title, which is exactly what you’d predict for a role that is nothing but bottleneck-removal with no technical deliverable of its own. It exists to move a model across the line to the group that owns the decision.

Prices: (G1,F2) + (G3,F2)

bottleneck-removal role

Design Engineers & Product Engineers

The builder’s narrower cousins. They remove the design-to-engineering translation tax, the friction where an intent understood by one function fails to survive the handoff to the next. A single, expensive seam, closed.

Prices: (G1,F2) internal seam

bottleneck-removal role

Solutions & Deployment Engineers

The FDE’s lighter-weight relatives, customer-embedded but a step down in coverage precisely because they don’t own production code. They clear the customer translation cell but leave customer alignment partly open. That gap is the point: the gradient of coverage is itself a taxonomy prediction.

Prices: (G4,F2) · (G4,F3) partly open

bottleneck-removal role
the coverage gradient

The more cells a role closes, the more it’s worth, and the harder it is to hire.

That gradient is itself a prediction of the taxonomy. Coverage isn’t a résumé line; it’s the number of gates a role opens between capability and outcome.

wide coverage → scarce

The Forward Deployed Engineer spans a whole block: model, translate, and align the customer, plus the technology alignment behind it. That’s why its compensation runs where it does.

a single seam → common

The AI PM, the analytics translator, and the design engineer each sit on one translation seam. Valuable, learnable, and more plentiful. One gate, not a block.

partial coverage → the tell

The solutions engineer clears customer translation but leaves customer alignment open, because they don’t own production code. The open cell is exactly where the value leaks.

The frontier: the roles the taxonomy says are coming

The executive cells, meaning how a specific executive decides and getting the model across the line to them, are the obvious next frontier. The “AI translator to the C-suite” doesn’t have a clean title yet, but the taxonomy says it’s coming, because the cell is both expensive and durable. When a bottleneck is priced but unnamed, a role is forming to remove it.

the evidence · earnings calls, july 2026

The vendors described the role before the market named it.

This page claims a title now names the boundary it dissolves rather than the labor it performs. In July 2026 four CEOs described exactly that reorganization on their own earnings calls, in the language of headcount and contract terms.

peer-reviewedsurvey researchcompany filingsmarket dataearnings call
Microsoftearnings callFY26 Q4 · Jul 29, 2026

6,000 people hired to remove one bottleneck

Microsoft announced Frontier Company, embedding 6,000 industry and engineering experts with customers to co-design and continuously improve AI systems. Nadella called it the largest outcome-driven engineering organization in the industry. It ran quietly for a year first, across 330 projects with 164 customers.

Source: Microsoft FY26 Q4 earnings call, July 29, 2026.
what it confirms

The job description is bottleneck removal. Not a product team, not a support organization, not a consulting practice. People placed inside the customer to close the gap between capability and outcome, which is the definition this site works from.

Metaearnings callQ2 2026 · Jul 29, 2026

An agent took the task layer and the outcome still needed an owner

Movida, a Brazilian rental car company with roughly 400 locations, moved selection, pricing, and payment into a WhatsApp agent. Daily bookings rose 44% year over year in a one month window, and 85% of conversations finished without human involvement.

Source: Meta Q2 2026 earnings call, July 29, 2026.
what it confirms

Watch which number is which. The 85% is the task layer, and the agent took it. The 44% exists because someone chose the booking flow, defined what winning looked like, and removed what stood in the way. That second job is the one that didn't get automated.

Alphabetearnings callQ2 2026 · Jul 2026

The measurement arrived before the org chart did

Google reported that its ads support agents now autonomously resolve roughly 75% of support queries, and Pichai described a Chrome team compressing a two year timeline into about three months.

Source: Alphabet Q2 2026 earnings call, July 2026.
what it confirms

Each of those is a number attached to work somebody used to own outright. When the task gets measured and automated, the remaining question is who is accountable for the outcome. That question is what the new titles are answering.

Microsoftearnings callFY26 Q4 · Jul 29, 2026

The gap between buying and using collapsed

Microsoft said the interval between a customer buying M365 Copilot licenses and reaching high usage, defined as 80% monthly active users across their base, fell from months to days over the past year. Customers deploying to a majority of their information workers rose 75% sequentially.

Source: Microsoft FY26 Q4 earnings call, July 29, 2026.
what it confirms

Adoption latency is the cleanest proxy for how wide the boundary is. It is closing fastest where someone owns the crossing. If nobody in your organization owns it, you are not holding steady. You are falling behind a benchmark that keeps moving.

Sources: Alphabet Q2 2026, Microsoft FY26 Q4, Meta Q2 2026, and Amazon Q2 2026 earnings calls and releases, July 2026. Figures are as stated by company executives. Amazon reported after market close on July 30, so Amazon figures come from the release and initial call remarks rather than a full transcript.

the wider evidence · the labor market, measured

The pay data says the same thing the earnings calls do.

A thesis about how work is changing should show up in wages and postings before it shows up in job architecture. It does. Three independent datasets say the premium has moved to judgement, and that the roles closing the widest boundary are the hardest to fill.

peer-reviewedsurvey researchcompany filingsmarket dataearnings call
PwCsurvey research2026 · 1B+ job ads, 27 territories

The premium moved to judgement, not to tooling

PwC's 2026 Global AI Jobs Barometer analyzed more than one billion job advertisements across 27 territories. Jobs requiring AI skills grew 69% since 2019 against 9% for the total jobs market, and the average wage premium for AI skills reached 62%, up from 57% a year earlier. AI-exposed entry level roles are 7 times more likely to require traditionally senior skills such as judgement and leadership. Those roles grew 35% since 2019 while other entry level roles declined 10%.

Source: PwC 2026 Global AI Jobs Barometer, published June 2026.
what it confirms

The entry level finding is the one to sit with. Jobs most exposed to AI didn't disappear. They got harder, and what they now require is exactly the boundary work this page describes. The market repriced judgement before anyone wrote a job architecture for it.

Forward deployed engineer marketmarket data2025 to 2026

Postings grew faster than anyone can train the supply

Live Data Technologies reported forward deployed engineer postings growing more than 800% between January and September 2025, and over 1,100% year over year. Recruiting datasets put median base pay between roughly $173,000 and $200,000, with senior and frontier lab packages reported well above that. Palantir, which created the role, reported 85% revenue growth in Q1 2026 with US commercial revenue up 133%.

Sources: Live Data Technologies posting data as reported by recruiting analysts, 2025 to 2026; Palantir Q1 2026 results filed with the SEC. Compensation figures come from recruiting datasets rather than a single authoritative survey and vary widely by source, so treat them as directional.
what it confirms

Coverage explains the price. The FDE closes customer modeling, customer translation, and customer alignment in one seat, and the market pays for the block rather than for any one skill in it. Demand is scaling faster than the supply of people who can do all three.

IBM Institute for Business Valuesurvey research2026 · 2,000 CEOs

A whole executive seat appeared in twelve months

IBM's 2026 CEO Study surveyed 2,000 CEOs across 33 geographies and 21 industries. 76% of organizations reported having a Chief AI Officer in 2026, up from 26% a year earlier. Companies with one reported 5% higher return on AI investments. In the same study, 86% of CEOs said employees already have the skills to work with AI while only 25% of the workforce uses AI regularly, and 83% said AI success depends more on people adoption than on the technology.

Source: IBM Institute for Business Value, 2026 CEO Study.
what it confirms

The taxonomy predicts that a durable, expensive cell gets a title. This is that happening at the executive level inside a single year. The gap between 86% and 25% is the same prediction from the other direction: the cell is still open, which is why the title keeps moving.

Compensation reporting for emerging roles is uneven. Posting growth and headcount figures are better evidenced than salary bands, so the salary figures above are presented as ranges from recruiting datasets rather than as a single number.

the general case

The market is reinventing the capability set, one job posting at a time.

Each Valley role special-cases the same map. The outcomes engineer is the general case, and its six capabilities are how you build the removal skills for whichever cell you target.