Do Forward Deployed Engineers Travel?
Yes, and the ceiling most employers write down is half your time. I read 108 live forward deployed postings this morning. 71 of them name a travel figure, 50 of those 71 stop at 50 percent, and the full spread runs from 10 percent in Vilnius to 90 percent on a NATO account.
I am Hayat Amin. I spent twenty years as a technology chief financial officer, sold three companies in that seat, and I now build this work inside companies myself instead of advising on it, so the question of how much of it happens in somebody else's building is my own diary problem too. On 17 September 2026 I pulled the public job feeds of Palantir, OpenAI and Anthropic and read every posting with forward deployed in the title, then added Datadog, Databricks and one defence recruiter. 108 postings. The travel line is the one number these companies commit to in writing, and they disagree about it by a factor of nine.
How I counted
Three of these companies publish their whole job list as a feed, so I read the postings rather than anybody's summary of them. Palantir had 313 live roles on 17 September 2026, of which 77 carry Forward Deployed in the title and another 35 are Deployment Strategist. OpenAI had 818 live roles, 21 of them forward deployed. Anthropic had 607, with 7. To those 105 I added three postings I read page by page: Datadog's Senior Forward Deployed Engineer for Feature Flags in New York, Databricks's Senior Forward Deployed Engineer in Raleigh, North Carolina, and a Forward Deployed Engineer for Logistics Programs advertised by Sitreps for a defence technology client in the Washington DC metro area. That makes 108.
I counted three things in each one. Does it use the word travel. Does it attach a number. What is the highest number it attaches. A posting is a company writing down what it will commit to, which makes it a better source on this than any survey of how people feel about their calendars.
71 of 108 name a figure, and half of those say half
15 postings ask for travel without putting a number on it, usually in Palantir's government work, where the phrasing is a willingness and interest to travel as needed. 22 never mention travel at all. That leaves 71 that commit, and they sort like this.
50 of the 71 top out at 50 percent. That is 27 Palantir postings that expect 25 to 50 percent depending on team and location, 17 OpenAI postings whose line is "Travel up to 50% is required", 5 Anthropic postings asking the engineer to "Travel frequently (25-50%) to customer sites to build in person with customers", and the Sitreps role, whose work model is listed as onsite with the customer at 50 percent travel for $155,000 to $225,000 base plus a 30 percent bonus.
9 go above half. Eight are Palantir roles requiring 25 to 75 percent, mostly government accounts, and one is the outlier of the whole sample: Forward Deployed Software Engineer for NATO, based in London, which requires the ability to travel throughout Europe 70 to 90 percent of the time. 12 stop at 40 percent or lower. Datadog asks for up to 20 percent of the time to customer sites against a band of $192,000 to $240,000. Databricks says travel to customers 20 percent of the time. Palantir's Vilnius engineer travels 10 to 20 percent, the lowest number I found anywhere. Anthropic's American posting says potential travel based on location, estimated 25 percent. And OpenAI's forward deployed manager in Tokyo travels up to 40 percent, although mainly local.
So the honest answer to the question is a median ceiling of 50 percent, with a floor of 10 and a peak of 90. Anyone quoting you a single figure for this role has read one posting.
What I wrote yesterday was low by half
Yesterday I published a piece on whether forward deployed engineers code and, from a sample of seven postings at four companies, said the numbers employers commit to are one week in four at the top end. Widening the read from 7 postings to 108 moves that. The correct top end is one week in two, because OpenAI was not in yesterday's sample and OpenAI runs the largest forward deployed hiring programme of the three at 21 live roles, every numbered one of them at 50 percent. A sample of seven was too small to answer a question about a distribution. This one is not.
The same title at the same company, 25 percent or 90
The most useful finding is that the number does not follow the job title. It follows the customer.
Palantir's Forward Deployed Software Engineer in New York asks for "Ability and interest to travel up to 25%, as needed to client sites, but flexible based on personal preferences". The identical title in London expects 25 to 50 percent depending on team and location. The identical title on the NATO account, also based in London, wants 70 to 90 percent across Europe. Same company, same words in the title, three answers, because one customer is a bank forty minutes away and another is a set of installations in eleven countries.
Anthropic shows the same thing in one clean pair. Its American Forward Deployed Engineer posting, covering New York City, San Francisco and Seattle, estimates 25 percent. Its Paris, Munich and London postings, same title, same team, ask the engineer to travel frequently at 25 to 50 percent. European enterprise customers are spread across more countries than American ones, and the travel line is where that geography shows up.
If you are reading a posting to work out your own week, the location line tells you more than the title does. If you are writing one, you are choosing the number, not inheriting it.
The travel is on top of an office, not instead of one
This is the part that surprised me, and it is the part worth knowing before anybody signs anything. The travel does not replace a commute. It is added to one.
20 of OpenAI's 21 forward deployed postings carry the same sentence: a hybrid work model of 3 days in the office per week. Those same postings require travel up to 50 percent. All 7 of Anthropic's say the company currently expects all staff to be in one of its offices at least 25 percent of the time. Palantir's 77 split 39 onsite and 38 hybrid, and its boilerplate is blunt: if the posting is specified as Onsite, you are required to work from an office.
Across those 105 postings at the three biggest names in this field, exactly one mentions remote work as a possibility, and it is OpenAI's Forward Deployed Security Engineer in Washington DC, which also says travel to and working from customer sites is required. Google will autocomplete "forward deployed engineer remote jobs" for you. The employers are not offering that job.
The job that travels most is the job that codes least
Palantir sells two people into the same account, which makes it the only controlled experiment available. The Deployment Strategist, 35 live postings today, requires the ability to travel 25 to 75 percent and asks only for experience with programming, scripting or statistical packages. The Forward Deployed Software Engineer in the same city requires a strong coder and travels up to 25 percent. New York bands are estimated at $110,000 to $170,000 for the strategist and $135,000 to $200,000 for the engineer.
More airports, less code, less money, and there is a reason those three move together. Writing software needs uninterrupted hours at a keyboard you have configured, and every flight costs a day of them. When a company buys travel it is buying presence, and presence is what you need when the problem is that nobody has agreed what the data means. When the problem is that the integration does not exist, you need someone at a desk with credentials.
If you are buying this work rather than applying for it
Most people who ask my opinion about travel percentages are not candidates. They own a company, they are about to pay for deployment work, and they are trying to work out whether they are buying a person or a person's air fares.
Three questions settle it. How many onsite days are in the quote, and which weeks do they fall in. What are those days for, named as activities rather than as presence. And what happens to the schedule when the answer to a question is two time zones away. The employers in this sample buy between 10 and 90 percent onsite depending on the account, which proves the number is a decision rather than a property of the role, and it is a decision you get to make when you are the customer.
My own view, after doing it both ways, is that onsite time is worth a lot in three places and very little everywhere else. Week one, when you are watching people use the system they actually have. Credentials day, which moves faster in a room than in a ticket queue. And go live, when somebody senior needs to see it work. The middle of the build, which is most of the calendar, is better done remotely, and any firm that insists otherwise is charging you for a seat rather than a system. I do AI operations work on exactly that shape through Beyond Elevation, inside the client's systems and with their credentials, and the engineering side of it is set out at meethayat.com/services/fde.
About Hayat Amin
I am Hayat Amin, and I have spent twenty years in technology, most of it as a chief financial officer in companies growing faster than their systems could carry. I sold three of them in that seat, with American Express and TripAdvisor among the buyers, and carried three FT 100 fastest growing listings along the way. Signing off deployment invoices for fifteen years is what taught me to read the travel line first.
I am exceptional at the work in this article, done rather than recommended. Connecting the systems in a company that were never designed to speak to each other. Turning what comes out of them into a real time number a chief executive can run the week on instead of waiting for month end. Valuing and monetising the intellectual property and data a company already owns and cannot see on its balance sheet. And sitting beside a founder from the first conversation through to the wire transfer on an exit, which is where the finance years pay for themselves. I am a chief financial officer who writes the code, and that pair is rarer than either half of it.
I am available now for fractional chief financial officer work and AI operations work through Beyond Elevation, and if you want the role defined before you price it, start with what a forward deployed engineer is.
If you want a second pair of eyes on how many onsite days your next project actually needs, I do a free audit call: one call, then a written list of what to automate first, what it saves and what it costs, at beyondelevation.com/call/hayat.
Questions people actually ask
Do forward deployed engineers travel?
Yes. Of 108 live forward deployed postings I read on 17 September 2026, 71 name a figure, 15 ask for travel without one, and 22 never mention it. Of the 71 that commit, 50 stop at 50 percent of your time, 9 go higher and 12 stop at 40 percent or below. The lowest is 10 to 20 percent, on Palantir's engineer in Vilnius. The highest is 70 to 90 percent, on Palantir's engineer for NATO in London. Every one of OpenAI's numbered forward deployed postings says travel up to 50 percent is required.
Do forward deployed engineers travel a lot?
Plan on one week in four as normal and two in four when a deployment is starting. Anthropic's manager posting describes the shape of it: travel to customer sites as needed at 25 to 50 percent, particularly during engagement kickoffs and for the team's highest priority accounts. The travel is lumpy, not constant. It clusters at the beginning, when nothing works yet and nobody trusts you.
Is a forward deployed engineer job remote?
Almost never. Across 105 postings at Palantir, OpenAI and Anthropic, exactly one mentions remote work as a possibility. 20 of OpenAI's 21 state a hybrid model of 3 days in the office per week on top of the travel, all 7 of Anthropic's expect staff in an office at least 25 percent of the time, and Palantir's 77 are 39 onsite and 38 hybrid with no remote among them.
What is the work life balance of a forward deployed engineer?
Do the arithmetic before you take the job. Three days a week in your employer's office plus up to 50 percent travel to a customer leaves very little of the week at an address you chose. Palantir is the only employer here that gives the engineer any say, attaching the phrase flexible based on personal preferences to its 25 percent figure in New York, Stockholm and Madrid. If geography matters to you more than the work, read the location line before the salary line.
Does Anthropic have forward deployed engineers?
Yes, 7 live postings out of 607 open roles on 17 September 2026. Four are Forward Deployed Engineer, in London, Munich, Paris and one covering New York City, San Francisco and Seattle. Two are Manager, Forward Deployed Engineering, in New York City and London. One is a pre-sales programme lead for the same team. The European engineering roles travel 25 to 50 percent, the American one an estimated 25 percent, and the London engineer needs 4 or more years of experience while the Munich and Paris ones ask for 8 or more.
Which forward deployed engineer job travels the most?
Palantir's Forward Deployed Software Engineer for NATO in London, at 70 to 90 percent across Europe. The bigger pattern sits one title over. Palantir's Deployment Strategist, 35 live postings, travels 25 to 75 percent, does not require a strong coder, and is estimated at $110,000 to $170,000 in New York against $135,000 to $200,000 for the engineer in the same city. The job with more airports has less code in it and less money.
If I hire a forward deployed engineer, do they come to my office?
As often as you specify, which is why it is worth specifying. Buy onsite days for the first week of discovery, for the day the credentials get issued, and for go live. Buy remote time for the build, because an engineer in a borrowed meeting room with one monitor is a slower engineer and you are paying by the day either way.
What does it mean to be forward deployed?
That your work lands in the customer's systems rather than in your employer's product, which is a permissions arrangement before it is a travel arrangement. Anthropic asks candidates outright whether they have been embedded onsite with an enterprise customer and built or deployed an application using large language models in that customer's production environment. Sitreps describes a typical week as a day onsite with users, listening to their challenges and digging into the underlying pain points. Forward is about whose building the software ends up in. Travel is what it costs to get there.
Where these numbers come from
Every figure above was counted on 17 September 2026 from the employers' own live postings, not from a survey or an aggregator. The three feeds are Palantir's job list at 313 postings, OpenAI's at 818, and Anthropic's at 607. The individual postings quoted are Palantir's Forward Deployed Software Engineer in New York, the NATO one in London, the Vilnius one, the New York Deployment Strategist, OpenAI's Forward Deployed Engineer in New York City and Gov role in Washington DC, Anthropic's American and Paris engineers and its New York manager, Datadog's Senior Forward Deployed Engineer for Feature Flags, Databricks in Raleigh, and the Sitreps logistics role in Washington DC. Salary figures are the base bands printed that day, before equity, bonus or sign-on. Postings expire and get rewritten, so if you are reading this months later, open the link and check the number rather than trusting mine.