The median US GTM engineer earns:
$159,000Most land between $135K and $190K (the middle 50%), and the full range runs from about $65K to $410K. That comes from 509 US job postings that disclosed a salary, pulled from our live board of GTM engineer roles, April to July 2026. Only about a quarter of postings state pay at all, so this is the disclosed slice, not a survey.
The numbers, US disclosed (n=509):
- Median: $159K
- Middle 50% (P25 to P75): $135K to $190K
- By level: mid $155K, senior $175K, staff $219K
- Founding GTM engineer: ~$195K, usually plus equity
- SF / New York: $170K median
- Fully remote: $147.5K median
By seniority #
The level ladder is clean and the jumps are real.
| Level | Median (US) | What changes |
|---|---|---|
| Mid | $155K | Builds and runs the systems |
| Senior | $175K | Owns the architecture, sets the patterns |
| Staff | $219K | Sets strategy across the revenue org |
| Founding | ~$195K + equity | First GTM hire, builds from zero |
The founding-engineer number sits above senior and near staff, which fits: it is the first GTM hire at an early-stage company, usually carrying equity, and the risk-and-scope premium shows up in cash too.
The founding GTM engineer is the architect of the revenue engine, and that is why the number sits where it does. Think of it like Waymo: someone has to build the system that runs agentic and algorithmic first, with humans in the passenger seat as the loop that feeds and corrects the autonomous engine. Whoever builds that foundation is what the company scales on. Expect a good share of these founding engineers to be running revenue as CRO in a few years.
Where you work still moves the number #
Two location findings, one expected and one not:
- San Francisco and New York pay a premium: $170K median, about $11K over the national number.
- Fully remote roles pay less, not more: $147.5K median versus $160K for roles tied to an office. A roughly $12K remote discount, even for a job that is almost entirely buildable from a laptop.
The remote number is worth sitting with. This is a role you can do almost entirely from a laptop, and it still pays a discount when it is remote. Whether that is the market lagging or location genuinely mattering less than it looks, it is a real gap in the current data.
What actually moves you from $135K to $190K #
The spread is not about who writes better code. It is the shift from builder to revenue architect.
At the bottom of the band, you build the engine. At the top, you build it and you get it adopted. You have the business acumen to make the reps actually use what you shipped, so the impact lands company-wide instead of dying as a clever workflow nobody runs. Building without enablement is a waste of time. The premium is not paid for the engine, it is paid for the adoption.
Base, or base plus variable? #
Almost all of these numbers are base or total cash, and the profile rarely carries an individual variable the way a sales rep does. We think that is a missed opportunity. A GTM engineer whose systems visibly move conversion or coverage should share in the outcome, with a small variable tied to metrics they actually control, not a percent of “assisted revenue.” It is uncommon for this profile today, but it is the right direction. The full comp-design argument is in our GTM engineer guide.
How we got these numbers #
We read every GTM engineer job posting on our live board and pulled the disclosed salary from each. 509 US postings stated pay; we trimmed obvious parsing errors (below $40K or above $500K) and took the midpoint of each stated range. It is disclosed pay from real 2026 postings, refreshed weekly, not a self-reported survey. The honest caveat: only about a quarter of employers post a number, so the disclosed slice may skew slightly toward companies confident about paying well.
See every open GTM engineer role with its salary where disclosed, refreshed weekly: browse the board.