Over the past month, the FDE (Forward Deployed Engineer) role has been everywhere: OpenAI poured $4 billion into a dedicated deployment company, Anthropic embedded engineers directly inside financial giant FIS, and Google Cloud is racing to hire hundreds.
In China, things are even more direct. ByteDance posted FDE roles for its Doubao product at 35,000 to 70,000 RMB per month (roughly $4,800 to $9,600) with 15 months of pay. Job listings at Ant Digital Technologies and Zhipu now carry the FDE label too.
LinkedIn says FDE headcount has grown 42x in two years — three times faster than AI engineering roles.
So why the sudden feeding frenzy? Because models are good enough now. The next challenge is making money with them, in real businesses. AI companies have sunk enormous cost into model R&D, and the models themselves are ready. What comes next is plugging them into enterprises, solving actual problems, and generating returns. When people talk about enterprise AI transformation, the ones actually doing the work — wiring it up in the field — are FDEs.
But read the job descriptions, and all you get is a list of required skills and a vague sense of what the role involves. After the headlines, you still don’t know what this job looks like day to day, or how to break in.
So this article skips the conceptual framing and goes straight to practitioners who’ve done the work:
- A detailed retrospective from an engineer who spent eight years at Palantir
- Two interviews with OpenAI’s head of FDE
- A video self-portrait from an engineer who left Google to become an FDE
- A founder running all over Shenzhen
- An anonymous long-form post from someone who spent two years embedded in the power industry
- And the unfiltered complaints on Reddit, Blind, and Xiaohongshu
From a practitioner’s perspective, five questions:
- What does an FDE do every day?
- How is it different in China vs. overseas?
- Who’s suited for it, and what skills do you need?
- How do you transition into FDE?
- Why is it the role closest to entrepreneurship?
FDE Overseas: Grueling, Fast, and On-Site
Four or Five Iteration Loops Per Week
Nobody lays out the day-to-day more clearly than Nabeel Qureshi. He spent nearly eight years as an FDE at Palantir, wrote a widely circulated retrospective in 2024, then filled in the details on a podcast.
His week looked like this: Monday, walk into the client’s office for a meeting; Monday night, build the thing. Tuesday, show it to the client, collect feedback; Tuesday night, revise. Wednesday, show it again; Wednesday night, revise again. He’d run four or five cycles like that in a single week. “Six weeks later, you have something the client is willing to pay $20 million for.”
You Work at the Client’s Office, Almost All the Time
Nabeel’s first major project was Airbus.
He moved to Toulouse, France for a year, working four days a week right next to the A350 final assembly line.
What he built, in his own words, was “airplane-building task management software”: work orders, missing parts, and quality issues pulled together into one interface where you could check things off and see progress at a glance.
Later, on a project for the National Institutes of Health, he had his own badge and sat side by side with civil servants, biologists, and clinicians every day.
The travel intensity was absurd.
“Get a call, book a flight for the next morning, show up in some random city” — that was routine at Palantir. The culture was “get on the plane first, ask questions later.”
Many FDEs became United Airlines top-tier frequent flyers, clocking over a hundred thousand kilometers a year.
You Don’t Code That Much — Most of Your Time Goes to Communication and Requirements
In Palantir’s official 2015 recruiting video, FDEs themselves put the number at: on an ideal day, 40% to 50% coding, 20% handling assorted technical issues, and the rest spent digging through data to figure out what the problem actually is.
Gergely Orosz, the veteran engineer behind The Pragmatic Engineer, offered a more cynical breakdown: the real composition of the job is about 25% coding, 50% integration and data pipeline work, 25% meetings and calming down clients.
Anu, an engineer who left Google to become an FDE, put it even more bluntly in her self-reported video: “Some days, communication is 80% of the job.”
At Google, she had uninterrupted blocks of coding time, and a product manager shielded her from clients. Now, “you’re the person sitting in the same room as the client.”
Another FDE, handling ten clients solo at a startup, wrote a weekly journal entry that began: “By the time I looked up, it was 6 p.m. and I hadn’t written a single line of code. This happens more often than I expected.”
The Unsexy Side of FDE
Excel and Data Permission Hell
The least filtered section of Nabeel’s retrospective is about data: “Data scattered across formats that are impossible to analyze directly — PDFs, notebooks, Excel files. God, so much Excel.”
What was worse was the process of getting the data. “The client buys an 8- to 12-week pilot, and we spend the entire 8 to 12 weeks just getting data access. In the final week, we scramble to cobble together something that can be demoed.” What blocks the project isn’t the tech — it’s the internal silos on the client side.
Debugging Live in Front of the Client
Anu described a moment: something broke during a live demo, and she debugged it on the spot, thinking “this would be so embarrassing if I can’t fix it — they paid for this.” This is the biggest difference between FDE and a normal engineering role: there’s no “fix it in the next iteration” option. Today’s problem gets solved today.
A Reddit commenter had an even more vivid version: he went hiking with a Palantir friend, and the friend opened his work laptop to fix a bug at the summit.
This Line of Work Eats Pain
Palantir president Shyam Sankar has an internal catchphrase, relayed by a former FDE-turned-investor on a podcast: the FDE’s job is to “eat pain and excrete product.”
A former Palantir FDE who later led FDE recruiting said one of their core screening criteria was “grit — a willingness to suffer”: “Being an FDE is painful. These people have to genuinely believe they can pull off the impossible.”
Her own memory: spending weeks in a small German town with two colleagues, going to the client’s factory floor every day. “What you see on site and what’s in the contract — those are two completely different things.”
A Day in the Life of a Chinese FDE: Running Across Shenzhen, Asking Questions During Water Breaks
One Chinese FDE’s Schedule
The most concrete picture of daily life in China comes from Lawted (a pseudonym from a media interview), based in Shenzhen. A former big-tech programmer, he got into Harvard but decided to defer — choosing to do FDE work as a founder instead. His reasoning: the next year or two is the best window to get into traditional-enterprise AI transformation.
His day:
- Morning: visit different companies to research whether their workflows are suitable for AI
- Afternoon: embed on-site and observe, catching staff during their water breaks to ask questions
- Evening: organize the day’s findings and build systems
“I used to just sit in the office and wait for people to hand me requirements. Now I’m running all over Shenzhen, finding companies, finding bosses.”
His entry point was classic: a logistics company reached out. Out of their 40 to 50 employees, 20 to 30 spent every day manually pulling tracking numbers and addresses out of PDFs from clients and typing them into Excel.
He used AI coding tools to build a demo. What used to take a person several minutes per PDF, the AI parsed in seconds. The client signed a letter of intent on the spot.
Two Years of Field Lessons
A power-industry practitioner on Zhihu wrote up the complete journey of three enterprise AI projects — the most grounded, no-bullshit firsthand account of AI on-site delivery on the Chinese internet. A few verbatim quotes:
“After three enterprise AI projects, I discovered a brutal fact: 90% of clients have no idea what they want. You ask ‘what do you want to do with AI,’ and nine out of ten say ‘something like ChatGPT.’”
A smart Q&A system took six months from requirements to launch, with three mid-stream changes to the requirements.
The client’s scanned PDFs had no text layer — just extracting the text took three weeks. “The client didn’t understand why it was so slow: isn’t it just uploading a file?”
He got smarter over time: “During demos, I’d deliberately show some wrong answers. Let the client see that AI isn’t magic. The biggest enemy of enterprise AI adoption isn’t technology — it’s expectation management.”
The most deflating part came after launch: in a unit of over 600 people, fewer than 10 used the system daily.
Later, when he embedded the AI into the OA approval workflow so it pushed results automatically, usage shot up 5x. His iron rule for pricing: data cleaning is at least 30% of the total cost, and operations at least 20%. These two line items are non-negotiable.
He also described the uniquely Chinese delivery environment: the client’s internal network isn’t connected to the internet. Drivers, CUDA, model weights — tens of gigabytes — all have to be downloaded in advance and carried into the server room on a hard drive.
Salary and the Bar to Entry in China
Lai Juncheng (pseudonym), who handles FDE recruiting at a Shanghai AI company, gave the most honest numbers: at his company, junior FDEs make 20,000 to 30,000 RMB monthly ($2,700 to $4,100). Senior roles are annual-package-based, 400,000 RMB and up. Million-RMB annual packages do exist, but they’re concentrated at the very top — not the industry average.
For reference at big tech: ByteDance’s Doubao FDE roles are listed at 35,000 to 70,000 RMB monthly, 15 months of pay. At the top end, that’s about 1.05 million RMB a year ($144,000).
His definition of the role is refreshingly stripped-down: in a software company, the FDE is “the majordomo who handles everything except coding and admin.”
He himself came up through implementation engineer, pre-sales, product manager, and project manager — and folded them all into one role.
When hiring, he looks for two things: learning ability and the capacity to see through to the essence of a problem. He doesn’t filter by major: “People on our team who studied design or niche foreign languages have all done outstanding work.”
Beware of Becoming On-Site Outsourcing
To understand the Chinese FDE’s predicament, you first need to read an on-site account from 2021. Note: this was traditional IT on-site outsourcing from before the AI wave — not FDE — but it’s the pitfall Chinese FDEs fear sliding into most.
The engineer wrote: at the client site, you had to avoid the senior leadership at the cafeteria, because one leader’s exact words were “how come the migrant workers are allowed to eat here too.”
Everyone in the client’s IT department, from the director down to the contract workers, wanted to offload some of their own work onto the on-site staff.
The office was on the fourth floor. The water dispenser was on the first floor. There was an electric kettle on the fourth floor — but it was for client employees only. He eventually took a 50% pay cut just to escape the on-site role.
Today, people doing AI deployment on Xiaohongshu are still arguing about the exact same thing.
One post title is a straight-up accusation: “Aren’t 99% of FDEs just outsourced labor and paid hand-holding?”
Doing consulting for clients, building custom workflows, teaching clients how to use AI — “let’s be honest, it’s just repackaging the same old thing in a fancier new term.”
China vs. Global: Side by Side
The Trap for Chinese FDEs
Put the firsthand accounts from both sides next to each other, and the differences jump out.
Here’s the overseas benchmark: OpenAI’s FDEs built a customer service system for fintech company Klarna, then distilled the solution into an internal framework. They open-sourced it, and it eventually became OpenAI’s official Agents SDK — now the standard tool every FDE uses.
There’s an even better example: a 2,000-person Japanese sales team wanted a slide-generation assistant. The initial slide layouts the model produced were atrocious. The FDE tested 50 different approaches, packaged up the best samples, and handed them to the model training team. Three months later, a new model version shipped, and “the slides suddenly got good.”
Meanwhile, here’s the self-deprecating take from Chinese practitioners:
“We don’t call this new paradigm FDE. We call it: pre-sales + account manager + implementation + tech support + dedicated hand-holding + temporary product manager.”
“Overseas, they’re just now hyping the idea of using demos to find direction. We’ve already demo’d ourselves bald.”
That’s the dividing line: does the road you paved at the client site eventually become part of your company’s product?
Overseas, FDE output feeds back into the product and the model. In China, most on-site output stays with that one client — and starts decaying the moment you leave.
There’s another layer of difference, hidden in where trust comes from.
A practitioner who’s done AI deployment on both sides wrote on Xiaohongshu: in the US, trust is contract-based. Sign the contract, and core data is opened to you. In China, trust is relationship-based. “You have to get drunk together first” — build personal rapport before you can get access to anything real.
So for the same on-site work, Chinese FDEs have one extra layer of labor: infiltrating the organization, building personal connections, punching through silos.
The Salary Gap
Overseas: LinkedIn data shows FDE headcount grew 42x in two years.
On comp: Anu, who jumped from Google, said she didn’t take a pay cut. “FDE total comp is often higher at the same level — $200,000 is easy to hit.”
A tech recruiter with 18 years in the game said two FDE roles she’s filling for the same hedge fund client are both at $350,000, and the client is willing to wait six months for the right person.
China: the title just landed. ByteDance, Ant Group, and Zhipu are using “FDE” directly in their job posts. There isn’t even an agreed-upon Chinese translation yet — three different terms are in circulation.
The growth is in AI transformation for traditional enterprises. Lawted’s math: “It used to take a year or two and cost millions of RMB to build an enterprise management system. Now with AI-assisted coding, we can deliver a custom system in two months.”
The government has stepped in too: Shanghai ran the country’s first FDE training program — one month of theory, two months of on-site practice — and is planning to tie it to intermediate professional certifications.
Common Misconceptions About FDE
Five common misconceptions, each fact-checked with practitioner quotes.
Misconception 1: FDEs are just pre-sales or product managers who can talk tech.
Yasha (pseudonym), who spent eight years as a PM in the US, then moved to development, then to FDE, put it in absolute terms: “An FDE cannot be a people-person product manager who just relays requirements back to programmers. That’s too slow and too lossy. You have to have real technical depth — make judgments yourself, solve problems on the spot yourself.”
Misconception 2: FDE is a promotion from engineering.
Anu made a point of correcting this: FDE is not a level above engineer. It’s a completely different job, a different growth curve — a lateral move to a different track. Her performance reviews also shifted from “code quality” to “client outcomes.”
Misconception 3: FDEs mostly write code.
See the time breakdowns above: coding takes 25% to 50% of the time. Some days, communication takes 80%.
Misconception 4: FDEs have to be on-site every day.
The counterexample is Ramp: their FDE team visits clients “once a quarter at most — everything is over video calls,” with one person serving five or six clients simultaneously.
Being on-site is a means. Staying close to the client to solve problems — that’s the definition.
Misconception 5: China’s on-site delivery equals FDE.
Two differences: whether the output feeds back into the product, and whether you charge by outcomes or by headcount-days.
If you bill by person-day, whatever you call it, it’s outsourcing.
Who’s Cut Out for It — and Who Isn’t
The Right Fit: Common Threads
The person who built Ramp’s FDE team has a line: “The FDE team is the team that wants to say yes to the client. A lot of engineers won’t admit it, but deep down they want to say no — they want to keep building their own thing.”
OpenAI FDE lead Colin Jarvis offered this standard: “A relentless pursuit of value is the hallmark of a good FDE. The best FDEs are willing to rip apart what they just built and start over, because the client needs something different.”
Anu’s self-deprecating version: “Someone like me, who’s borderline ADHD — this job actually works to your advantage.” People who switch context instantly and enjoy doing eight different things in a day thrive here.
The Wrong Fit: A Checklist
The FDE handling ten clients solo wrote the most brutal account in his weekly journal: “If you need long uninterrupted stretches to produce anything, this role will destroy you.” “If you just want to build things and not talk to people, this is not your role.”
A former Palantir training lead who transformed over 250 engineers into FDEs has a list of people to steer away:
- People allergic to ambiguous requirements
- People who want to go deep on technical specialization
- People who can’t handle client emotions
- And people who don’t know how to set boundaries
That last type will burn themselves down to nothing.
Know the Risks Before You Switch
One: skill atrophy. A self-identified former Palantir person on Reddit wrote: “On a bad project, all you do is drag-and-drop and configuration. Your technical skills atrophy beyond recognition.”
Another assessment is even harsher: do five years of FDE and then interview for a standard engineering role at a big tech company — you’ll likely get down-leveled.
Two: getting chained to a client.
It sounds like a good problem: you’re so good the client can’t live without you. But the founder of Dataland (ex-Palantir) pointed out the trap in a roundtable: “The client getting addicted to the FDE is even worse than your company getting addicted to the services revenue. You try to pull the person out, the client terminates your contract.”
Zoom into the individual level: you build the system, you’re supposed to move on to the next project. But the client only trusts you, and demands that you stay. The company can’t afford to lose the account, so you stay parked at that one client.
Slowly, you go from “engineer exploring new problems” to “that one client’s dedicated ops person” — handling the same system’s day-to-day issues, not growing, with only one client on your resume.
In China, it gets weirder: clients trust through personal relationships, which means they trust you, not your company. The contract is billed by the day — every day you stay on-site, the company collects another day’s fee.
The client won’t release you. The company doesn’t want to swap you out. You can’t leave. Eventually, you become exactly what you feared: on-site outsourced labor.
Opportunity: How to Get In
Learn From Successful Transitions
Line up the real transition paths from the firsthand accounts:
- Eight years as a product manager, then development, then FDE — now being recruited at $400,000 a year (Yasha, US)
- Google engineer who made a lateral jump to FDE — four or five months later, confident enough to record a comparison video, no comp drop (Anu)
- Product design consultancy background, joined Palantir as an FDE (new hire from an official interview, four months in)
- Implementation engineer, pre-sales, product manager, project manager — all rolled into FDE, now runs recruiting (Lai Juncheng, Shanghai)
- Big-tech programmer who got an AI transformation request from a logistics company and jumped straight into founding a startup (Lawted, Shenzhen)
Two common threads.
One: nobody starts fresh out of school. Yasha said: “A new grad can’t do this. You typically need a few years of PM or development experience first. That’s also why starting pay isn’t low — first year, around $200,000-plus.”
Two: everyone straddles tech and business. Whatever you’re missing, you fill in.
What You’re Missing and How to Fill It
The former Palantir training lead laid out a transition roadmap:
- Month one: sit in on client calls, shadow the implementation team, and specifically document the gap between “what the client says the problem is” and “the real root cause”
- Month two: take end-to-end ownership of one client issue
- Month three: go to a client site and ship a small fix within the same week
- After that: write a weekly “what I learned from the client this week” note
The skill list is surprisingly basic:
- Solid SQL
- Can read logs on a Linux command line
- Comfortable with Docker
- Python: can handle spreadsheets, make API calls; has a gut feel for dirty-data pitfalls like time zones, encodings, and null values
No cutting-edge model techniques required.
What the Interview Actually Tests
Palantir has a signature “decomposition interview”:
They give you a vague requirement — something like “design a system that lets users share their interests” or “design a system for assigning cases to analysts based on expertise and availability.”
This is not the standard system design interview. One candidate ran through the textbook capacity-estimation-and-scalability template and was cut off mid-sentence by the interviewer, told to go back to “how the feature itself should be designed.”
OpenAI’s process is even more direct: a roughly five-hour take-home assignment. Build something with their API, submit the code, plus a video of yourself explaining it.
The reasoning is clear: FDEs present to clients every day, so they test exactly that.
Ramp adds one extra round beyond the standard engineering interview — testing whether you can actually communicate.
The Role Closest to Entrepreneurship
Let’s close with the most overlooked point in this whole thread.
Everyone is talking about enterprise AI transformation. A lot of people talk about it. Very few actually go down and do it. FDEs are the ones who do: turning “transformation” from a buzzword into a quality inspection system on a production line, an agent in a customer service backend, an anti-money-laundering flow inside a bank.
This position has a byproduct that might be worth more than the paycheck: you live inside your clients’ real pain points every day. Other people guess what the market needs to start a company. Your market needs walk up to you every morning.
Bob McGrew, a Palantir veteran who later became OpenAI’s Chief Research Officer, put it most directly:
FDE training is, precisely, training to become a founder. At a New York FDE roundtable with four panelists, two were Palantir alumni who had gone on to start their own companies. One of them said it outright: “FDE is the best training ground for future founders.”
The data backs it up. Nabeel’s retrospective includes this stat: every Y Combinator batch has more former Palantir founders than former Google founders, even though Google has 50 times more employees than Palantir.
Yasha explained why: “FDEs have seen too many successes and too many failures. If you have FDE experience, you know exactly what the market is missing and what product you should build.”
Lawted in Shenzhen just flipped the sequence entirely: he entered FDE work directly as a founder. That first logistics client became his company’s starting point.
How Long Does This Role Last?
Box CEO Aaron Levie said: “If I were doing college career counseling right now, the first thing I’d do is make sure students know this role exists and how to get an offer.”
Lai Juncheng, who runs FDE recruiting, was more level-headed: “Think of product managers when mobile internet took off ten years ago — white-hot for five to ten years, then gradually cooled down. But during that wave, you got outsized individuals like Zhang Xiaolong and Zhang Yiming emerging.”
Honestly, how long the role lasts doesn’t matter that much.
Enterprise AI transformation as a problem has unlimited runway, and it only gets bigger.
Someone who’s seen the real pain points and real problems of 100 companies — wherever the next opportunity is, they’ll have a sharper edge and a higher probability of seizing it.