Forward deployed engineer posts paid a median $200,000 base in the job posts we tracked between 3 May and 5 October 2026, against $150,000 for GTM engineers, and they're hiring for different work: getting a product running inside a customer's systems, versus building the pipeline that finds those customers. If your problem is customers who bought and never got set up, you want the first. If it's not enough qualified pipeline, you want the second.
Both titles have "engineer" in them and both sit near revenue, which is presumably why they get compared. Across 82 forward deployed engineer posts and 98 GTM engineer posts in that window, the overlap mostly stops at the word "build".
The tools barely overlap
The cleanest way to see it is the stack. Clay was named in 61% of the GTM engineer posts, HubSpot in 55%, Salesforce in 43% and n8n in 34%. Those are pipeline tools. They're where leads get enriched, scored, routed and sent.
In the forward deployed posts, the most common tool we picked up was Python, at 11%. SQL was 5%, n8n 4% and Salesforce 2%. Clay and HubSpot didn't register at all.
Our tool shares only count a post when the term shows up in its title, summary or extracted stack, so they're floors, and for engineering languages I suspect a low one. Bloomberry's analysis of 1,000 forward deployed engineer posts found Python in 66% of them, TypeScript in 35% and AWS in 32%. Put that next to ours and one job lives in a software engineering stack and the other lives in your CRM.
The work points in opposite directions
GTM engineer posts are about your own pipeline. Building came up in 89% of them, automation in 78% and pipeline in 69%. Outbound was in 57% and enrichment in 44%. Whatever gets built, your sales team is the one using it.
The forward deployed posts lean on integrations, at 51%, and AI agents or LLMs, at 33%. Pipeline showed up in 17%. Outbound and enrichment didn't register at all. That work is aimed at someone else's company, the one that just bought your product and needs it wired into their data.
Bloomberry's numbers back that up from the other side. In its sample, 55% of posts mentioned working directly with customers and 68% required travel. None of the roles carried a quota. Bitscale's comparison frames it as vendor versus seller. In its version the forward deployed engineer works for the software company and stays until the deployment runs in production, while the GTM engineer works for the selling company and builds its pipeline system. Bitscale sells GTM engineering as a service, so weigh its "which one do you need" section with that in mind, but the split it draws matches what the posts say.
One overlap is real. AI agents or LLMs came up in 28% of GTM engineer posts too, so both jobs are picking up agent work. They're pointing it at different problems.
Pay: a third more, before equity
The salary samples are small, so take this as directional. Eighteen of the 82 forward deployed posts printed a range. Their median midpoint was $200,000, with the middle half between $185,000 and $225,000. For GTM engineers it was 23 of 98 posts, a $150,000 median, and a middle half of $115,000 to $175,000.
Even the bottom of the forward deployed middle half sits above the top of the GTM one. Bloomberry, with a much bigger sample, landed on a median base of $173,816 and found equity mentioned in 70% of posts. Putting Bloomberry's median next to our GTM median, the base gap is somewhere between $24,000 and $50,000. We don't have equity data for the GTM posts, so I can't tell you how total pay compares.
Neither salary is the cost of the seat. The BLS says private employers in June 2026 spent $54.06 an hour on wages and $24.82 on benefits for management and professional staff, which is about 46% on top of pay. At the medians from our posts, that's roughly $292,000 a year for a forward deployed engineer and $219,000 for a GTM engineer. Call it $24,000 and $18,000 a month. The full GTM engineer cost breakdown goes through agencies and freelancers too.
How to tell which one you need
Ask who the work is for. If a customer has signed and your product needs custom integration, data plumbing or agent setup on their side before it does anything useful, that's a forward deployed engineer. If your own team needs more qualified pipeline, cleaner routing or outbound that doesn't fall over, that's a GTM engineer.
A few signs you're about to post the wrong ad. You want someone to "own GTM" but the real pain is churn from customers who never got set up properly. That's a deployment problem, and a GTM engineer won't fix it. Or you've seen forward deployed engineers in the news and want one, but your product is configured in an afternoon. Then what you probably need is a good implementation person, or nobody.
There's some overlap at the edges. Two of the forward deployed posts we tracked had "GTM" in the title itself, and Bloomberry put 14% of the roles in its sample inside GTM or sales teams. My read is that those hybrid posts mostly want a sales engineer who can code.
We don't place forward deployed engineers
We don't, and I wouldn't try to hire one remotely from another time zone anyway. The job is customer-facing, Bloomberry found travel in 68% of posts, and 60% of them asked for three to five years of experience. If your deployments need someone in the customer's office, pay the $292,000 and hire close to your customers.
GTM engineering is different. Building came up in 89% of those posts, and the systems live in your own tools rather than a customer's. We place GTM engineers from the Philippines and Latin America full-time on your team, in your tools, from $4,000 a month all-in, with a free replacement if the fit is wrong. This breakdown of 98 GTM engineer posts shows what the job involves week to week.
Before you write either ad, write down the first thing this person will build and who will use it. A customer means a forward deployed engineer, and your own sales team means a GTM engineer.