What is a Growth Engineer?

Growth Engineers write code to help the company grow. We don't build the core product, and we usually sit within GTM rather than traditional engineering. The role is new - only really emerging in the last year, but it's becoming common fast because it gives GTM teams a new kind of leverage.

There's still confusion about what a Growth Engineer actually does, which is fair. Most of us are generalists with entrepreneurial backgrounds, comfortable moving across different parts of the business. And unlike sales, marketing, or product engineering, our work rarely maps to one clean metric.

Traditionally, marketing, sales, and product-growth teams couldn't build hacky growth projects or quick experiments, and often worked with engineering for every small experiment or funnel tweak.

A Growth Engineer removes that bottleneck by taking an idea all the way from insight → code → experiment → measurement. That means wearing a mix of hats: engineering, product, design, analytics, and distribution. Not to replace either team, but to connect them and move faster than a normal process allows.

I might be:

• BuildingTechnical demos that help users instantly understand the product, like these.
• Shipping experiments across different distribution channels
• Automating workflows and building tools that make the GTM team faster
• Running SEO and AEO experiments
• Filming DevRel-style contentt
• Taking early demo calls to understand where users get stuck and what they care about
• Shipping growth hacks like the YC Unicorn Predictor

This role allows me to combine building and selling. I get to write code, launch experiments, talk to users, and see instantly whether something I built actually mattered. It feels like being a founder again.