“Growth engineer” is one of those titles that means different things at different companies. Here’s the version I’ve found works.

The unlock

Marketing teams have ideas they can’t ship. Product teams have a roadmap that doesn’t optimize for distribution. Engineering teams have backlog they’re already drowning in. A growth engineer sits at the intersection and ships the work that none of them would, because none of them own it cleanly.

The day-to-day

Most of my time goes to one of three things:

• Funnels — tightening the path between someone landing and someone paying
• Loops — building referral, content, and sharing flows that compound
• Tooling — internal dashboards, attribution, and experimentation infra

The percentages shift week to week, but the through-line is: you ship code that makes the business faster, not the product roadmap faster.

What it isn’t

It isn’t running ads. It isn’t writing copy. It isn’t a more technical PM title. If you’re hiring for any of those, you don’t want a growth engineer — you want the actual role.