The Career Out of the Seat: Draw the Exits, Not Just the Ladder

The one piece of forward deployed engineer news I found this week came from Seattle, and it was about founders.

On October 6 Todd Bishop at GeekWire reported that Foundations, a startup community with more than 300 founders, launched a service that hires those founders out to businesses to plan, build, and implement AI systems. It's priced per project. The service is called Foundations Design and Engineering, and Bishop notes the initials are a play on the job this series is about. Aviel Ginzburg, the co-founder: "I think the world of traditional consulting and startups is just absolutely going to merge."

Otherwise it was quiet. No new headcounts, no new academy. After last week I'll take it, and I'm not going to dress up a quiet week as a busy one. I'll use it to write the part the Foundations story points at.

Founders are walking into the seat for paid work. That isn't only a Seattle thing. Boaz Francis, who heads forward deployed engineering at Wonderful, told an Insight Partners panel in July that between one in six and one in seven of his new hires are ex-founders. His reason, as Santosh Iyer and Samma Hafeez wrote it up: "Those same people who can make a company out of nothing," he said, "will do well as an FDE."

The traffic the other way is old. Concept VC's count of Palantir alumni (undated, no byline, built on getPIN's data) found over 111 companies and $11.6 billion in capital raised by 2024, with "Forward Deployed Engineer being the most common background that founders had."

So the seat has one door that swings both ways. What it mostly lacks is any other door with a sign on it.

Rupanjana Bhattacharjee wrote the plainest version in August: "The career ladder is genuinely unsettled." Her warning is that you can do two years of strong work and then find "the promotion criteria were never defined, or were defined after the fact." And the way onward, she writes, "is frequently sideways into solutions architecture, product, or founding-engineer roles."

This is part 8 of The FDE Transition. Part 7 was the scorecard. This part is the career out of the seat: what an FDE becomes, and what the company owes them in writing before they start.

The short version

The FDE seat is a tour of duty, and most companies are trying to fix its retention problem by drawing a ladder inside it: senior, staff, architect. A ladder inside the seat works only if each rung is defined by what the product absorbed, never by how big the account got or how long the engineer has been on site. The exits matter more than the rungs. I count three, and I'd write them into the offer: into product, as the person who answers the handback packets you used to send; up, running the function without a bookings number; and out, to found a company on the problem you saw at three customers. Staff FDE is a real fourth choice when it means owning a class of customer and the hours-per-deployment line for it. The failure has a name, from Miku Jha at ServiceNow: "the permanent glue between the customer and the product." If your best FDE has been on the same account for a year with no next seat named, you're making glue.

A ladder inside the seat, and the rule for it

The Insight Partners panel is the best public look at what companies are doing about this. Bhaskar Roy, chief of AI products at Workato, has built a career ladder that climbs to an "architect" FDE. Miku Jha, who runs applied AI forward deployed engineering at ServiceNow, calibrates FDE pay to the top of the engineering ladder. Both are sensible. Neither says what an FDE is supposed to become.

Jha is the one who names the risk. The fastest way to lose an FDE, she warned, is to make them "the permanent glue between the customer and the product," or a "customer-facing coder" who goes from project to project. Her fix is to keep the work "intellectually compounding," and on her team's scorecard a productized asset counts as much as the customer outcome.

That's the generalization rate from part 7, used for retention. I think she's right, and I'd push it into the ladder itself.

Here's why. Bhattacharjee describes the engineer who gets so good at one customer that they're assigned it again, and then: "When you leave, much of what you learned leaves with you." Now promote that person for it. A senior title awarded for being irreplaceable at one account is a raise for being stuck. The company has paid extra to keep its best field knowledge in one head, at one site.

So if you draw the ladder, define the rungs by what left the site. An FDE lands deployments. A senior FDE lands them and the handback packets get written decisions. A staff FDE owns a class of customer, and FDE hours per deployment for that class fall. Every rung is a line on the scorecard you're already keeping. None of them is a count of years.

Three exits

Into product. This series started from the claim that the FDE is the Product Builder arriving from the services side. If that's true, the most natural next seat is the one on the receiving end of the handback: the named PM who reads the packet and owes a written answer in two weeks. Nobody is better placed to hold that job than someone who has sent packets into silence. Marcello Pedersen described Databricks rotating engineers between the FDE organization and the product team in both directions. Last week I argued with Paavany Jayanty's case for sending every PM on an FDE tour. This is the same road driven the other way, and I think it's the better direction, because the FDE arrives in product already knowing what three customers did with the thing.

I've hired a lot of product managers as a CPO. The hardest thing to learn in an interview is whether the person has really sat with customers or has read about them. A former FDE's deployments answer that before the interview starts. What they still have to learn is the editor's habit: saying no to a customer they like, for the sake of ten they've never met.

Up. Somebody has to run the function, and the org design chapter says who: the person whose job is to close the loop, with no bookings number. Nehal Vyas is honest about what the job is. "You think you'll be technical. You're not. You're an ops manager with an engineering title." Take that exit if you'd rather fix the system than the customer. The manager's product is the whole scorecard, all four numbers, and the hard one is hours per deployment, because making it fall means shrinking the thing you run.

Out. Concept VC's read of the Palantir founders: "It's no surprise that many FDEs went on to found companies addressing similar problems they saw firsthand." Vyas has the cold water: "Most FDEs don't become founders. Most become managers or stay as senior individual contributors." Both are true. The founder exit is the count of three with your own name on it. You saw the same problem at three customers, you sent the packet, and product said kill. Fine. That can be a company.

And as of this week the door plainly opens inward too. An FDE stint is now something a founder does between rounds, and something a hiring manager like Francis goes looking for.

Write the exit into the offer

A tour has an end. Almost no FDE offer says where.

I'd set the checkpoint by deployments, not months. After the third landed deployment, the FDE and their manager have one written conversation with four possible answers: another tour, staff, product, or manage. The manager has to bring a real opening for at least one of the last three. If there's never an opening, the ladder and the exits are decoration.

Pedersen's line about each engagement is that the job is "to work ourselves out of a job." That holds for the seat as much as for the engagement.

There's a clock on this. Anthropic's academy expects its first Claude Frontier Deployed Engineer badges in early 2027, and the announcement says nothing about what a badge holder does next. That's fair, it's a training program. But the 10,000 people it plans to train will ask their employers, and most employers have no answer yet.

Matthew Mayo at KDnuggets wrote the sentence I'd plan a career around: "The title may splinter or fade; the skill set it names will not." So plan around the skill, and treat the title as something you held for a while.

What this means in the seat, and at the top

If you're the FDE: keep your own record. Deployments landed, packets sent, decisions received, and what shipped for everyone because of you. It's the résumé for all three exits, and nobody else is keeping it.

If you run product: for your next PM opening, interview an FDE first.

If you run the company: ask how many FDEs moved into product in the last year. If the answer is none, your loop is made of documents and has no people in it.

One thing to try this week: list your FDEs. Next to each name write the account they've been on longest, how many months, and which exit they'd pick if you asked. Then ask. A year on one account and a blank in the last column is glue, and Jha already told you what happens to glue.

Sources: Todd Bishop, "AI founders for hire: Startup hub Foundations launches service to connect businesses with builders," GeekWire (October 6, 2026), with Aviel Ginzburg quoted · Santosh Iyer and Samma Hafeez, "How companies are building and scaling the FDE bench," Insight Partners (July 21, 2026), a panel with Miku Jha, Marcello Pedersen, Bhaskar Roy, and Boaz Francis · Rupanjana Bhattacharjee, "The Honest Case Against Becoming a Forward Deployed Engineer," Simpliaxis (August 22, 2026) · Nehal Vyas, "FDE Career Paths: Management, Product, Founder" (April 25, 2026) · Matthew Mayo, "Forward Deployed Engineer: AI's Hottest New Career, or Consulting With a Better Title?", KDnuggets (October 2, 2026) · Concept VC, "Behind The People: Palantir" (undated) · Anthropic, "Anthropic invests $100 million to train 10,000 engineers and tackle the enterprise AI talent gap" (October 2, 2026)

Part of the running argument on AI Product Management: once building is cheap, the scarce work is deciding what gets built for everyone, and the people who learned that in the field need a way into the room where it gets decided.

Related answer: What is the career path for a forward deployed engineer?