# Growth Engineering: What It Is and What Growth Engineers Do

Source: https://trymimetic.com/guides/growth-engineering

[Guides](/guides) / Revenue QA

# Growth engineering: what it is and what growth engineers do

Growth engineering is software work aimed at a business number instead of a feature list. A product engineer is handed "build saved carts". A growth engineer is handed "more first-time visitors should finish a purchase" and decides what to build, test or fix to get there.

The role grew out of the growth teams consumer tech companies set up in the late 2000s and 2010s, when it became clear that small changes to signup, onboarding and checkout often moved revenue more than big new features. It has since spread to ecommerce, SaaS and marketplaces, and to any company where the path from visitor to customer runs through software.

## What growth engineers own

The work clusters around the moments where people either keep going or leave:

- **Getting in.** Landing pages, signup and account creation, the first visit on a phone.
- **The first useful moment.** Onboarding, first purchase, the first time the product does what it promised.
- **Paying.** Pricing pages, paywalls, cart and checkout, payment methods, upsells.
- **Coming back.** Email and push triggers, subscriptions, saved state, reasons to return.
- **Bringing others.** Referrals, invites, sharing.

Under all of it sits the plumbing that makes the work measurable: event tracking, attribution, an experiment system, and analytics everyone trusts. On most teams the growth engineer owns that plumbing too, because without it nobody can tell whether a change helped.

## How the work runs

Growth engineering is a loop, not a roadmap:

1. **Find where people drop.** Read the funnel, session recordings and support tickets, broken down by device, browser, country and traffic source. The biggest losses often sit in one slice, like a payment button that fails in one in-app browser.
2. **Size it.** How many people hit this step, how many leave, and what that costs. A small fix on a busy step usually beats a big build on a quiet one.
3. **Change something.** Fix the break, or build the smallest version of a new idea.
4. **Measure it honestly.** Run an A/B test when traffic allows it. When it doesn't, compare before and after and say plainly that it isn't a test.
5. **Keep what worked, remove what didn't,** and write down why, so the next idea starts from evidence.

The habit that separates good growth engineers is step 4. A change that "felt like it worked" and a change that measurably worked look the same in a status update.

## Growth engineering vs related roles

| Role | Usually measured on | Typical work |
| --- | --- | --- |
| Product engineer | Shipping the roadmap | New features, platform work |
| Growth engineer | A business metric: conversion, activation, retention, revenue | Experiments, funnel fixes, tracking, pricing and checkout changes |
| Growth marketer | Acquisition cost, channel results | Campaigns, ads, email, landing pages |
| CRO specialist | Conversion rate | Research, test ideas, test analysis, often without writing production code |

In practice the lines blur. Small teams often have one person doing growth marketing and growth engineering. Large ones split the work across a growth product manager, a designer, analysts and several engineers.

## Growth engineering vs GTM engineering vs marketing engineering

Three newer titles get mixed up, and job posts use them loosely. The useful difference is what each one is pointed at:

|  | Growth engineer | GTM engineer | Marketing engineer |
| --- | --- | --- | --- |
| **Pointed at** | The product or store: turning visitors into customers who come back | The sales pipeline: finding and reaching the right accounts | The marketing surface: sites, landing pages, tracking, campaigns |
| **Typical work** | Experiments, onboarding, checkout and pricing changes, funnel fixes | Lead lists, data enrichment, outbound sequences, CRM workflows | Landing pages, site performance, tags and attribution, campaign tooling |
| **Common in** | Consumer apps, ecommerce, self-serve software | B2B companies with a sales team | Most companies with a marketing team |
| **Measured on** | Conversion, activation, retention, revenue | Pipeline and meetings booked | Leads, campaign results, site conversion |

GTM engineering grew fast with B2B outbound automation. Marketing engineering overlaps most with growth engineering on an online store, where the marketing site and the store are the same thing.

## Skills that matter

- **Full-stack range.** The work moves between the frontend, the backend, the analytics pipeline and third-party tools in the same week.
- **Measurement.** Event design, attribution, and enough statistics to know when a test result is noise: sample size, test length, and not stopping early because a number looks good.
- **Speed with care.** Many small changes shipped safely, behind flags or as tests, with an easy way back.
- **Judgment about what to try.** Picking the change with the best expected payoff, not the most interesting one.
- **Product and customer sense.** Knowing why people hesitate, not just where.

## Growth engineering on an online store

On an online store the loop is the same, and the places to look are well known:

- **Product pages:** price, shipping cost and delivery date visible on a phone without scrolling, reviews where people look for them, an add-to-cart button that clearly confirms it worked.
- **Cart and checkout:** no surprise costs at the last step, payment methods that work in every browser people actually use, including in-app browsers from social apps.
- **Tracking:** purchases counted once, consent banners that don't drop conversions, ad platforms receiving the real numbers.
- **Speed:** the first product image showing up quickly on a mid-range phone.
- **Search and navigation:** shoppers finding the product they typed, collections that don't dead-end.

Most of this is invisible in a top-line analytics report. Conversion rate looks normal while one browser can't check out, or a tracking change counts every sale twice. That's why the first job on a store is usually finding what's broken, not inventing new tests.

## People worth learning from

The best growth thinking is shared openly by people who have run growth at large companies. A good starting list:

- **Lenny Rachitsky.** [Lenny's Newsletter](https://www.lennysnewsletter.com) and the [Lenny's Podcast](https://www.youtube.com/@LennysPodcast) YouTube channel, long interviews with growth and product leaders. On X: [@lennysan](https://x.com/lennysan).
- **Andrew Chen.** Essays on growth loops and network effects at [andrewchen.com](https://andrewchen.com), and the book *The Cold Start Problem*. On X: [@andrewchen](https://x.com/andrewchen).
- **Elena Verna.** Practical writing on product-led growth and growth team structure at [elenaverna.com](https://www.elenaverna.com). On X: [@ElenaVerna](https://x.com/ElenaVerna).
- **Brian Balfour.** Growth frameworks and programs at [Reforge](https://www.reforge.com). On X: [@bbalfour](https://x.com/bbalfour).
- **Casey Winters.** Essays on marketplaces, retention and growth strategy at [caseyaccidental.com](https://caseyaccidental.com). On X: [@onecaseman](https://x.com/onecaseman).
- **Ronny Kohavi.** The standard reference on running trustworthy A/B tests, *Trustworthy Online Controlled Experiments* ([experimentguide.com](https://experimentguide.com)). On X: [@ronnyk](https://x.com/ronnyk).
- **Nikita Bier.** Consumer growth and viral launches, mostly shared on X: [@nikitabier](https://x.com/nikitabier).

If you read one thing on experiments, make it Kohavi's book. Most bad test calls come from the statistics mistakes it explains.

## Testing on Shopify

Shopify now has its own A/B testing, called Rollouts, for theme, checkout, catalog and discount changes. See our guide to [how Shopify Rollouts works](/guides/shopify-rollouts) for what it can and can't test, and what its results leave out.

## Where Mimetic fits

Mimetic does the repetitive part of growth engineering for online stores. It checks your site the way shoppers use it, across devices and browsers, finds what's costing sales, and turns each fix into a change your team can review before it goes live. Your engineers spend their time on the ideas worth testing, not on finding the breaks.

> [Check your store](/) to see what a growth engineer would fix first.

## Common questions

**What does a growth engineer do?**
Builds, tests and fixes the parts of a product or site that decide whether visitors become customers and keep coming back, and measures whether each change helped.

**What's the difference between a growth engineer and a GTM engineer?**
A growth engineer works on the product or store to turn visitors into customers. A GTM engineer works on the sales pipeline, building lead lists, enrichment and outbound workflows for a sales team.

**Is growth engineering the same as growth hacking?**
No. Growth hacking usually means clever acquisition tricks. Growth engineering is ongoing product and engineering work measured by experiments and business metrics.

**Do you need A/B testing to do growth engineering?**
It helps, but low-traffic sites can't test everything. Fixing clear breaks and measuring before and after, honestly labelled, is still growth engineering.

**What tools do growth engineers use?**
An analytics tool, an experiment system, a feature-flag system, session recordings, a tag manager, and the code itself. The tools matter less than measuring changes honestly.

Written by Coleman Hindes, founder, Mimetic.
Published 2026-11-18.

### See what is costing your store sales.

[Scan my site](/)
