What does a Growth Engineer actually do?
A Growth Engineer is a full-stack engineer whose work product is measured in lift on a target metric (signups, activation, revenue), not features shipped. They're embedded in growth or marketing, not in the core product engineering org, and they ship at marketing's tempo (days to weeks) rather than product's (weeks to months).
The role exists because growth experiments need engineering output the core product team can't prioritize. Landing pages, signup flows, A/B test infrastructure, lifecycle automation, integration plumbing, marketing-site CMS work. A good growth engineer ships 3-5 things per week; a great one knows which 2 of those will actually move the needle.
The "GTM Engineer" title (popularized by AI / dev-tools companies in 2024-25) is functionally identical. Same role, same skills, slightly more prestige. OpenAI, Anthropic, Vercel pay top-of-market for it.
Core responsibilities
- Ship landing pages: fast, tested, instrumented. Often dozens per quarter for paid campaigns and product launches.
- Build the experimentation platform: feature flags, A/B framework, analytics events. Or at least integrate one (Statsig, GrowthBook, LaunchDarkly).
- Signup + onboarding flows: a high-impact surface for any product with a free tier.
- Marketing site engineering: Next.js, Astro, or whichever JAMstack the company picked. Plus CMS plumbing (Sanity, Contentful, payload).
- Integration plumbing: connecting marketing tools (HubSpot, Customer.io, Segment) to the product. Often the most leveraged work the team needs.
- Performance engineering: Core Web Vitals, image optimization, lazy loading. SEO depends on this and the SEO team can't do it.
- Lifecycle automation: partnering with Lifecycle Marketing on triggered emails, push, and in-app messages.
Skills that matter
- Strong TypeScript + React: the modal stack at growth-stage tech companies. If you can also do Next.js or Astro deeply, you're hireable everywhere.
- SQL + product analytics: to know what to ship and how it's performing. dbt basics if the company has a data warehouse.
- A/B test infrastructure: having shipped one is a strong signal in interviews.
- API design: most growth integrations are gluing 3rd-party systems. Knowing what good API design looks like keeps you sane.
- Marketing-side empathy: the rare quality that separates strong growth engineers from frustrated ones. You need to think like a marketer, not just take requirements from one.
- Pragmatism: growth engineering is iteration-heavy and ship-fast. People who need 3 weeks to architect a thing don't last.
Salary in the US (2026 benchmarks)
| Level | Base salary (USD) | Notes |
|---|---|---|
| Junior (2-4 yrs) | $130K to $170K | Usually transitioning from product eng |
| Mid (5-7 yrs) | $160K to $215K | Owns the growth eng stack |
| Senior IC (8+ yrs) | $200K to $280K | Multiple-experiments-deep, often staff level |
| GTM Engineer (top AI / dev-tools) | $240K to $350K | OpenAI, Anthropic, Vercel pay top of market |
Total comp at hyper-growth companies often reaches $400K-$600K with equity. The role is rare and high-leverage, so salary keeps creeping up.
Career trajectory
- Staff Growth Engineer: IC track, usually owning the experimentation platform itself.
- Engineering Manager (Growth): managing 3-6 growth engineers at growth-stage companies.
- Head of Growth: rare but real. Strong growth engineers with channel instincts can step into the leadership track.
- Technical co-founder: a common path among the strongest practitioners. Growth engineers ship the kind of full-stack output that early-stage companies need.
How to break into the role
- Start as a full-stack product engineer for 2-4 years. Build muscle on shipping software end-to-end.
- Volunteer for the marketing-site or onboarding work. It's usually unowned and the bar to deliver value is low.
- Ship a public side project that involves marketing instrumentation: landing page, A/B framework, analytics dashboard. Public proof of work is a hiring shortcut.
- Read the canon: Reforge growth engineering material, Vercel + Linear blog posts, Stripe and Notion engineering blogs.