The job in one line
A growth engineer is the person who makes growth measurable. They instrument the product so every meaningful action becomes an event, keep a tracking plan that names those events consistently, and fix the funnel leaks the data exposes. On the eight roles they sit next to the Growth PM: the PM decides what to test, the engineer makes the test measurable. Their code serves experiments, not the product roadmap.
What they actually ship
Most of the work is plumbing the rest of the team never sees. The PostHog team frames a growth engineer as someone who writes code to move business metrics rather than to build features — A/B test scaffolding, funnel fixes, the tracking that tells you whether anything worked.
- Map a funnel — signup, activation, upgrade — and instrument each step so drop-off is visible.
- Add the missing event. The classic example is a `subscription_started` that nobody wired up, so revenue is invisible to the funnel.
- Audit the tracking plan: kill duplicate events, fix inconsistent names, document what each property means.
- Build the internal tools and integrations — webhooks, syncs, dashboards — that let other roles act on the data.
The tracking plan is the deliverable
Everything downstream depends on clean events. Amplitude calls the event taxonomy the foundation of good analytics: a consistent naming convention, agreed properties, one source of truth. Segment describes the tracking plan as a living document of what you track and why. Get this right and profiles, segments, and journeys all read from the same trustworthy stream. Get it wrong and every report quietly lies.
Why the role is a multiplier
A growth engineer rarely owns a metric of their own. Their output is the team's ability to move metrics at all. When the Performance Marketer wants a high-LTV segment synced to an ad platform, or the Data Analyst needs a cohort report that isn't built on guesswork, the engineer is why that data exists and is trustworthy. Instrument once, and every role reads the same events. That multiplier is what makes the role part of an AI growth team, not a nice-to-have.
Growth engineer vs. product engineer
Both write code; the question they answer differs. A product engineer asks whether the feature works. A growth engineer asks whether the feature moves the number — and instruments the product so you can tell. They ship faster and scrappier, because a tracking fix that ships next quarter is a tracking fix that taught you nothing.
How fromHello runs this role
fromHello runs the growth engineer as one of eight AI agents inside an AI growth team. The agent maps your funnel, proposes the events you are missing, and drafts the tracking plan — then you approve, edit, or send it back. Nothing ships on its own; the agent proposes and you stay in the loop. If you are weighing it against a tool you would still have to operate yourself, fromHello vs Customer.io sizes the difference between renting the platform and getting the team that runs it.