By FDE Interview Prep, a SourceStrongAI company

In this post11 sections
  1. The short answer
  2. Travel and time on site
  3. One customer, many capabilities: where the switching comes from
  4. Ambiguity and pain tolerance
  5. When the job is not what was advertised
  6. What no one measures
  7. Questions that show whether a team is sustainable
  8. How to talk about workload in the interview
  9. Questions people ask
  10. Keep reading
  11. More from the blog

You have an interview coming up, or an offer on the table, and one question keeps coming back: will this job wear me down? Being a forward deployed engineer can be stressful, and the people who have done it point to four sources: travel, living inside one customer’s problems while answering to your own company, ambiguity, and a job that turns out different from the one advertised. If you are still working out what the job is, start with what a forward deployed engineer is.

We found no published burnout or attrition data for FDEs, so everything below is what named people have said, with who said it and when.

The short answer

The strain in FDE work is real, but it is not the same strain on every team. What the accounts describe:

  • Travel. Planes, hotels and customer offices, in amounts that vary by employer, team and project.
  • Switching. You carry one customer’s whole problem: data, code, meetings and politics, often in the same day.
  • Ambiguity. The brief is loose, the data rarely matches what the customer described, and you decide what to build.
  • Mismatch. Some engineers took FDE roles and found a different job from the one they expected.

In our reading of these accounts, what decides whether the strain is manageable is largely how the team is run: how many customers each engineer carries, who schedules the travel, and who says no. Those are things you can ask about before you accept an offer. The last two sections of this post give you the questions, and the words to use when an interviewer turns the topic around on you.

Travel and time on site

One former FDE’s description of the job is not flattering. As reported by The Wall Street Journal in March 2026, Hex founder Barry McCardel, a Palantir FDE for about five years, described it like this: “It means spending a lot of time on planes, sleeping in three-star hotels, somewhere in middle America, and working out of a dimly lit windowless conference room where there’s not enough charging ports.” Source 1The Hottest Job in Tech Isn’t Very Glamorous (WSJ, republished)PublisherThe Wall Street Journal via IT Executives CouncilSource typenews report

LeadDev quoted, in July 2026, Piotr Kraus, an ex-Palantir FDE who now consults for an FDE advisory firm, as saying that constant travel makes the role susceptible to burnout earlier than other roles. Source 2The rise of the forward-deployed engineer (FDE)PublisherLeadDevSource typenews report That is his view, not a measured rate.

How much travel is involved depends on when and where you look:

  • Palantir, in one former FDE’s memory. In an October 2024 essay, Nabeel S. Qureshi wrote that when he joined Palantir in 2015, the norm was for FDEs to “go onsite” to the customer’s offices and work from there 3-4 days per week, “which meant a ton of travel.” Source 3Reflections on PalantirPublisherNabeel S. Qureshi (Substack)Source typecandidate’s personal write-up That is one person’s memory of an earlier era, not FDE work today.
  • Palantir, by team. On Blind in February 2023, a Palantir-tagged user who described themselves as a new-grad FDE wrote that travel “depends on your team”: some teams travel every other week, some sit in one place, and some make occasional on-site visits. Source 4palantir forward deployed software engineerPublisherBlindSource typecandidate report on Blind Another Palantir-tagged user on Blind replied that they travel about once every 4-6 weeks and that it was “pretty optional”. Source 4palantir forward deployed software engineerPublisherBlindSource typecandidate report on Blind
  • OpenAI. The Engineering Leadership newsletter reported, in August 2026, that OpenAI generally tells new FDE joiners to expect around 50% of their time on site, and that Colin Jarvis, who leads forward deployed engineering at OpenAI, said this varies by project, with some people in the UAE and Japan on site around 80% of the time. Source 5Inside OpenAI's Forward Deployed Engineer RolePublisherEngineering Leadership (Gregor Ojstersek)Source typenews reportSource 6The Future of Forward Deployed Engineering | OpenAI, Ramp, Nominal, DatalandPublisherSouth Park Commons (YouTube)Source typerecorded talk or interview

The spread is the point. “FDE” does not tell you how many nights you will spend away. The posting and the team do. How much forward deployed engineers travel goes through what postings state, and our lesson on travel, location and on-site time shows how to read the travel line before you apply.

One customer, many capabilities: where the switching comes from

Palantir’s blog draws the line between its two engineering roles in a phrase: a Dev’s focus is “one capability, many customers,” while a Delta’s (its FDE) is “one customer, many capabilities.” Source 7Dev versus Delta: Demystifying engineering roles at PalantirPublisherPalantir BlogSource typecompany blogSource 8A Day in the Life of a Palantir Forward Deployed Software EngineerPublisherPalantir BlogSource typecompany blog

That phrase explains most of the context switching. A product engineer goes deep on one part of the system. An FDE carries everything one customer needs. Here is an illustrative day, ours rather than any one team’s:

  • Morning: a data pipeline broke overnight, and the customer’s operations lead noticed before you did.
  • Midday: a steering meeting where an executive asks why the project is not finished.
  • Afternoon: a request to your own product team for a feature the customer needs, which that team has not planned.
  • Evening: the fix for the pipeline, written in the customer’s environment, with the customer’s tools.

In our view, the hardest part is the last two items together. You work for the customer, but your own company sets your priorities, and the two do not always agree. Our lesson on what FDEs do shows why the customer’s problem, not a component you own, sets your scope.

The load gets worse when a team takes on too much. Deep Engineering quoted, in August 2026, DataGOL COO Ritika Singh as saying: “Spread across every deal, the role burns out fast.” Source 9Forward Deployed Engineer Jobs Are Out There. Hiring Is Harder Than The Postings SuggestPublisherDeep EngineeringSource typenews report She was talking about how a company allocates its FDEs across sales deals, not about travel.

The opposite approach exists. Jarvis said on a South Park Commons panel in May 2026 that OpenAI’s FDE unit works only about 10 engagements at a time and has to say no more often than yes. Source 6The Future of Forward Deployed Engineering | OpenAI, Ramp, Nominal, DatalandPublisherSouth Park Commons (YouTube)Source typerecorded talk or interview That figure is for the whole team, not for one engineer. What matters to you is the habit behind it: someone decides which customers get FDE time, and turns the rest down.

Ambiguity and pain tolerance

The second source of strain is not knowing what “done” looks like. Jarvis told The Pragmatic Engineer in August 2025 that FDEs work in a lot of ambiguity: what customers describe in scoping often does not match the data and the systems, so the team moves fast and re-scopes to the most useful thing it can do. Source 10What are Forward Deployed Engineers, and why are they so in demand? (Gergely Orosz)PublisherThe Pragmatic EngineerSource typenews report

Palantir’s Chief Architect, Akshay Krishnaswamy, went further on a16z Deep Dives in January 2026: he said he is not sure you can know whether someone will be a good FDE until you put them in the field. Source 11How Palantir Scaled: Why the Best Software Is Built Backwards (YouTube auto-generated English captions)Publishera16z Deep Dives, YouTubeSource typerecorded talk or interview He named the ability to work from loose declarative instructions, and agreed with the host that pain tolerance is “a big one”. Source 11How Palantir Scaled: Why the Best Software Is Built Backwards (YouTube auto-generated English captions)Publishera16z Deep Dives, YouTubeSource typerecorded talk or interview

What pain tolerance means in practice is our reading, not a definition any employer publishes. It looks like this:

  • You can keep working when the data is wrong, the access request is stuck, and the deadline has not moved.
  • You can hear a frustrated customer out without taking it personally or promising what you cannot deliver.
  • You can pick a plan from a vague brief and change it without treating the change as failure.

Pain tolerance is not the same as working without limits. In our view, the useful kind includes being able to say “not this week” to a customer and still keep their trust. The best way to find out how you handle a loose brief is to try one. Our free AI practice case gives you a vague customer ask and scores how you scope it. It needs a sign-in.

When the job is not what was advertised

Some of the strain comes from a mismatch between the title and the work. The Pragmatic Engineer reported, in March 2026, that Gergely Orosz had talked with two engineers who took FDE roles and were disappointed. Source 12Is the FDE role becoming less desirable?PublisherThe Pragmatic EngineerSource typecandidate’s personal write-up The Pragmatic Engineer also quoted a developer who took an FDE role and quit four weeks later; the article does not say whether that developer is one of the two. Source 12Is the FDE role becoming less desirable?PublisherThe Pragmatic EngineerSource typecandidate’s personal write-up The developer said:

“The company wanted to use me more on the engagement lead side, and nothing on software development. It’s not what I signed up for, and I didn’t like the vibe and culture.”

In The Pragmatic Engineer’s account, the developer also said the role had an IT-services mindset. Source 12Is the FDE role becoming less desirable?PublisherThe Pragmatic EngineerSource typecandidate’s personal write-up The shape is worth knowing: the developer’s complaint was not hours or travel, it was doing a different job from the one they signed up for.

The reputation has a history too. As reported by The Wall Street Journal in March 2026, the FDE job has historically been seen as demanding, undesirable and less prestigious than product-focused engineering roles. Source 1The Hottest Job in Tech Isn’t Very Glamorous (WSJ, republished)PublisherThe Wall Street Journal via IT Executives CouncilSource typenews report If you worry about that side of it, whether FDE is a step down from software engineering takes the question on directly.

The fix is to find out before you sign what share of the work is writing code. Ask to hear about the last thing an engineer on the team shipped.

What no one measures

Here is what the evidence does not contain: we found no employer, survey or study that publishes burnout rates, attrition or average working hours for FDEs. Anyone who tells you FDEs burn out faster, or last a set number of years, is guessing.

What exists are single voices at single companies, some of them years old. They point in both directions, and they tell you what to ask about, not what to expect:

  • Long hours, said openly. In his October 2024 essay about his years at Palantir from 2015 on, Nabeel S. Qureshi wrote that the company was “loud about the fact that people worked long hours, were paid lower than market, and had to travel a lot.” Source 3Reflections on PalantirPublisherNabeel S. Qureshi (Substack)Source typecandidate’s personal write-up
  • One crunch week in two years. A Hacker News commenter who said they spent two years as an FDE at Palantir wrote, in April 2017, that they averaged “maybe 50h a week” and remembered only one crunch week, when they chose to work more than 80 hours. Source 13Hacker News comment by Anderkent on 'Palantir No Longer Works With The NSA'PublisherHacker NewsSource typecandidate comment on Hacker News
  • A warning from a neighboring role. One reviewer on Blind, a current Sierra software engineer rather than an FDE, wrote in September 2026 that work-life balance is tough, “especially for customer facing roles”, and that without boundaries you’ll burn out. Source 14Sierra AI company pagePublisherBlindSource typecandidate report on Blind
  • An employer’s own promise. AWS’s security postings for its forward deployed engineering team describe the team’s culture as “people-first, anti-burnout, bold, and engineering-excellence-driven.” Source 15Security Engineer, Forward Deployed Engineering - Job ID: 10552897PublisherAmazon.jobsSource typecompany job posting That is what AWS says about itself, and a good reason to ask its engineers what it looks like in practice.

Questions that show whether a team is sustainable

These questions are ours, built from the strains above. Ask them of the engineers on the panel, not only the recruiter, because they see the weeks most clearly.

  • “How many customers is each engineer working with right now?” A good answer is a number and a reason. A worrying one is “whatever comes in.”
  • “Who decides when someone goes on site, and how far ahead do you know?” A good answer names a person and a planning rhythm. A worrying one is “the customer calls and we go.”
  • “What happened after the last long on-site stretch?” Listen for recovery time, a lighter week or a rotation. Silence is an answer too.
  • “When a customer asks for something outside the engagement, who says no?” You want a person with the authority to do it, and a recent example.
  • “What did the last engineer who left this team go on to do?” Moves into product, leadership or a founding role suggest the work built careers. Nobody being able to say is worth a follow-up.
  • “How much of last month was writing code?” This is the question that might have warned the developer who quit after four weeks.

One vague answer is not a reason to walk away. A pattern of them is. Questions to ask at the end of an FDE interview has more, grouped by interviewer, with good and worrying answers for each.

How to talk about workload in the interview

The interviewer may raise the topic first. Our question bank has the forms it takes: how you have handled a sustained period of heavy load, the fastest-moving environment you have worked in, and what travel you can commit to. Each question page shows its framework free.

Our framework for the heavy-load question has five parts:

  1. The load, made concrete. What was happening, for whom, and for how long.
  2. The habits that held. What kept you steady and organized.
  3. The boundary, and the time you defended it. What you said no to, and to whom.
  4. What didn’t work. One honest miss.
  5. The warning sign you watch for now. How you catch it earlier next time.

The full framework is free on the question page. Here is a fictional answer that follows it, short enough to say in under a minute:

“For six weeks I carried two customers: a data migration and a customer’s compliance audit, with on-site time at one of them. I batched each customer to fixed days and kept a one-page note per customer that I reread before every call. In week one I told the audit lead that the reporting work would slip if we tried both, and we moved it. What didn’t work: I kept answering messages at night, and by week four my code reviews got sloppy. My lead noticed before I did. Now my warning sign is skipped reviews, and I raise it the same week.”

Common mistakes, and the fix for each:

  • “I thrive under pressure.” It says nothing. Tell one specific week instead.
  • “I never burn out.” It sounds like you have not had a hard stretch yet, or will not notice one. Say what you do to stay steady.
  • Promising unlimited travel. If you say yes to everything in the screen, you will have agreed to it. Give the limit you can keep, and say what would make more possible. For example: “I can be on site two weeks a month. Beyond that, I’d want to know a few weeks ahead.” The travel question has a free model answer.
  • Complaining about a past employer. Describe the load and your choices, not whose fault it was.

In our view, asking about sustainability need not make you look soft if you frame it around the work, as someone who wants to stay effective over a long engagement: “I want to do this well for years, so I’d like to know how the team handles on-site stretches.”

The strain in this job is easier to carry when you know what it is before you start. The later modules, including the lesson on what hiring leaders say they look for, come with Pro, which starts with a 7-day free trial. But the place to begin costs nothing. Our first module covers what FDEs do, how the role differs from its neighbors, who hires them and how to read a posting, so you can judge whether the work suits you before you spend weeks preparing. Start with The FDE role, decoded. It’s free, and the travel lesson takes under ten minutes.

GlossaryForward deployed engineerA software engineer who builds and ships production systems inside a customer’s problem and environment, accountable to that customer’s outcome.More on Forward deployed engineer

Questions people ask

Is being a forward deployed engineer stressful, according to press reports?

It can be, and the accounts point to travel and ambiguity. As reported by The Wall Street Journal, Hex founder Barry McCardel, a former Palantir FDE, described the job as a lot of time on planes and in hotels. We found no published burnout or attrition data for FDEs.Source 1The Hottest Job in Tech Isn’t Very Glamorous (WSJ, republished)PublisherThe Wall Street Journal via IT Executives CouncilSource typenews report

Do FDEs burn out faster than software engineers, according to press reports?

We found no study that measures it. Piotr Kraus, an ex-Palantir FDE and a consultant at an FDE advisory firm, told LeadDev that constant travel makes the role susceptible to burnout earlier than others. That is his view, not a measured rate.Source 2The rise of the forward-deployed engineer (FDE)PublisherLeadDevSource typenews report

How can I tell whether an FDE team is sustainable before I join?

Ask how many customers each FDE carries at once, how travel is scheduled and who decides it, what happens after a long on-site stretch, and where FDEs go when they leave the team. Specific answers are a good sign; vague ones are worth a follow-up.

Keep reading

Guides

Lessons

Questions

More in The FDE role, page 2