On this page
Last updated November 1, 2026. Figures come from Legion's /jobs page, read on that date. The feed changes every day, so the page always shows the current list.
A growth engineer is a software engineer judged on a business number, not on features shipped. A product engineer is asked "does it work?" A growth engineer is asked "did it move sign-ups, activation, revenue or meetings, and how do we know?" Our growth roles guide puts the role next to six other growth titles. This post covers the job itself: what you build, what it pays, who hires it and how to get in.
Read the job posts before you read the definitions
Definitions of this role vary, and job posts show what companies pay for. Here is what the 34 growth engineer postings in the feed showed on November 1, 2026.
The title covers two jobs. Most postings describe the classic role: experiments inside a software product. Seven of the 34 titles point outside the product instead. They name outbound, GTM, data automation, martech, SEO or audience growth. That second kind is close to what a GTM engineer does, which is why the two titles now overlap.
A growth leader usually hires it. For 19 of the 34 postings, the likely hiring manager had "growth" in their title: a head, director or VP of growth, or a head of growth engineering. Six more named a founder or CEO. The other nine went to engineering, product, marketing or sales leaders. So expect to work for the person who owns the growth number, or for the founder when nobody else does yet.
Know what the role pays
Nine of the 34 postings listed a salary, and all nine were in the US. Each row below is one company's posted range.
| Posted range | Location |
|---|---|
| $160K to $280K | United States, remote |
| $150K to $230K | San Francisco or New York |
| $140K to $220K | New York |
| $150K to $220K | San Francisco |
| $150K to $200K | United States, remote |
| $165K to $185K | United States |
| $140K to $180K | New York |
| $80K to $150K | San Francisco Bay Area (founding role) |
| $120K to $140K | Austin |
The median bottom of these ranges was $150K and the median top was $200K. The highest top was $280K. The lowest bottom, $80K, was a founding role.
The other 25 postings listed no salary, and 17 of those were outside the US. Nine rows are a small sample, so treat them as a snapshot of postings from October 12 to 31, 2026, not as a market average. The /jobs page shows salary, posted date and the likely hiring manager for every role it tracks.
Build experiments inside the product
This is the classic growth engineer job. The work follows a loop, and each step has a reason.
Find the stage that leaks the most, because one fix there beats five fixes anywhere else
Read the numbers by stage: visits, sign-ups, activated users, paying customers, retained customers. Pick the stage where the most people drop out. That is the only stage you work on until it improves.
Instrument the stage before you change it, because a test you cannot measure teaches nothing
Add the events you need, check that they fire, and record a baseline for at least a week. Skip this and you get the worst outcome: the change shipped, and nobody can say whether it worked.
Ship the smallest change that could move the number, because speed of learning beats polish
Typical builds are a shorter sign-up form, a new onboarding checklist, a pricing page variant, a referral prompt after the first success moment, or a lifecycle email triggered by what a user did. Put each behind a feature flag so you can switch it off.
Write down what each test taught, because the next quarter should not repeat it
One paragraph per experiment: what you changed, what you expected, what happened, what you will do next. That log is also your portfolio.
Build the outbound machine outside the product
The other kind of growth engineer builds systems that find and reach buyers. If you have read job posts for GTM engineers, this will look familiar. The way I put it: the job is to find signals that tell you how a buyer sees their world, so the message can match it.
Here is how I build a target market, from my guide to finding every company and contact in a market.
Collect ten times the companies you need, because cutting is cheaper than finding
If I need 1,000 usable companies, I start with at least 10,000. Then I cut with cheap rules first, such as regex on names and domains, before I pay for AI.
Decide on companies before you buy contacts, because company decisions are cheap and contact enrichment is not
In my current workflow, qualifying a company from its homepage costs about $6 per 10,000 companies. Contact enrichment is not that cheap, so I only pay to find people inside companies that have already qualified.
Store the reason for every decision, because you will have to defend the list later
Every company in or out of the list gets a literal reason. When a campaign underperforms, the reasons tell you whether the list or the message was wrong.
Give the whole workflow to an agent, because the steps repeat every week
Once the steps are written down, Claude Code can run them end to end and return the files, the counts and the open questions for a person to check. Every task I repeat becomes a skill this way. In the Legion pipeline, the run stops for a person's approval before launch, before paid people-finding and before spend over the limit.
Become a growth engineer by shipping, not by collecting certificates
A growth engineer role is an engineering role judged on a number, so you need two things to show: code you can ship and proof that you moved a number. Here is the order to follow.
Pick a side first, because the two kinds of role want different portfolios
If you like product code, aim for experiments inside a product: frontend, analytics events, A/B tests and feature flags. If you like data and APIs, aim for the outbound side: lists, enrichment, scripts and automation.
Learn the minimum stack for that side, because you need to ship alone
For the product side: one frontend framework, SQL, one product analytics tool and a feature flag system. For the outbound side: one scripting language, SQL, a few data APIs and an AI coding agent such as Claude Code.
Ship one measured experiment end to end, because a result beats a resume line
Pick a real product, your own or an open-source one, or a real market for the outbound side. Run one experiment from baseline to result and write it up with the number before and after.
Give the tool away, because it shows the work and brings people to you
I build CLIs, scrapers and workflows and give them away in public. The more I give away, the more opportunities come back. A public repo with a write-up does the same for a growth engineer job hunt.
Apply where a growth leader is hiring, because they know what the work is worth
In the feed, the likely hiring manager is listed for each role. Roles that report to a head or VP of growth usually have the clearest number to own, and that makes your experiment write-up easy to compare against the job.
Start with one experiment this week
Do not try to learn the whole field first. Pick one number, one stage and one change. Measure it for a week, ship the change, and write down what happened.
On the outbound side, the same rule holds. Take 50 companies from your current list and write down exactly why each one belongs or does not. Every decision you cannot explain becomes the next rule to fix. Then scale what holds up.
FAQ
What is a growth engineer?
A growth engineer is a software engineer who owns a growth number, such as sign-ups, activation, revenue or booked meetings, and ships code and experiments to move it. The role sits between engineering and growth, and is judged on results, not on features shipped.
What does a growth engineer do?
Most growth engineers build experiments inside a product: sign-up and onboarding changes, pricing tests, referral features and lifecycle emails, each instrumented so the result can be trusted. Some build outside the product instead: target lists, enrichment, outbound and the automation that connects them.
What is a growth engineer's salary?
Nine US growth engineer postings in Legion's jobs feed listed a salary on November 1, 2026. The median posted range was $150K to $200K. The ranges started between $80K and $165K and topped out between $140K and $280K. Check the /jobs page for current postings.
What is the difference between a growth engineer and a GTM engineer?
A growth engineer usually builds inside the product to move sign-ups, activation and revenue. A GTM engineer builds outside it: the lists, enrichment, outbound and automation that find and reach buyers. Seven of 34 growth engineer titles in the feed named outbound, GTM, automation, martech, SEO or audience work, so the two roles now overlap. The growth roles guide compares them side by side.
Do you need to code to be a growth engineer?
Yes. Every growth engineer role is an engineering role. You need enough code to ship a change to production or to automate a workflow across APIs. If you do not want to code, look at growth marketing manager or growth strategist roles instead.
Who does a growth engineer report to?
Usually a growth leader. In the feed, 19 of 34 growth engineer postings named a likely hiring manager with "growth" in the title, and six more named a founder or CEO.
How do I become a growth engineer?
Pick a side (product experiments or outbound systems), learn the minimum stack for it, then ship one measured experiment end to end and publish the write-up. A result with a number before and after is the strongest thing you can show.
Ready to put these ideas to work? Explore Legion and build your marketing agents.
