I've been hunting for solid, modern resources on growth engineering and… it's wild how little is out there.
There are plenty of "growth hacks," far too much generic marketing content, and plenty of engineering blogs. But there's a missing piece, the actual overlap. The glue between marketing, growth, and engineering. I literally found myself typing into ChatGPT: "any relevant podcast episodes out there on growth engineering?" while grasping for anything educational on the work I do every day.
The tech industry is evolving fast with the emergence of AI: agents, workflows, chats, all of it. And alongside it, the Growth Engineer is emerging too. Why? Because we're watching the old partition between "business" and "engineering" blur into something new: business impact, delivered through production-level software engineering.
That is why I'm starting GrowthEngineer.Tech.
So… what is growth engineering?
It's the work of rapid experimentation and the building of repeatable, measurable growth systems across product, marketing, analytics, lifecycle, and tooling, using engineering principles, without the trap of perfectionism.
And it's very often the role that exists when someone (or a small team) needs to be the glue between:
"We need to grow" and "we need to do it responsibly"
"Ship fast" and "measure correctly"
"Marketing wants X" and "the product actually needs Y"
"We have data" and "we can trust this data"
The best resource I found
I went deep looking for something recent and real about growth engineering, and the most relevant and current thing I could find was this single podcast episode on Spotify from 2023: Defining Growth Engineering with Alexey Komissarouk (yes, 3 years ago).
It's full of valuable insights that actually reflect the job:
what the role looks like in practice
how growth engineering interfaces with product + marketing + data
what you should measure vs. what people think you should measure
how to run experiments without fooling yourself
what it means to be "technical" in a growth context
If you're new to the space, it's a fantastic starting point. If you're already doing the work, it's rare for a piece of content to feel like, "Oh, you get it," and "I can actually learn something from you." Shoutout to Alexey Komissarouk, who feels like one of the only pioneers in the space.
Who I am (and who this is for)
I'm a Growth Engineer working in SaaS. My day-to-day is a mix of:
full-stack engineering
analytics + event instrumentation
funnel design + lifecycle
automation + GTM systems
experimentation frameworks
performance, reliability, and "don't break production"
…and then translating all of that into actual outcomes: activation, conversion, retention, revenue.
This newsletter/blog is for:
growth engineers
aspiring growth engineers
founders
early startup teams
builders wearing many hats
anyone who cares about measurable, compounding growth
Because in startups and high-velocity teams, growth engineering is basically inevitable. Someone has to:
move fast
measure honestly
iterate without drama
build systems that don't collapse under success
The core philosophy: impact > perfection
A big trap in this space is trying to build the "perfect" system before you ship anything.
But growth engineering is more like:
ship a version
instrument it
learn quickly
improve the loop
repeat forever
You still need technical professionalism: clean code, stable systems, proper tracking, good data hygiene, secure patterns, reliable pipelines, etc.
But you also need the ability to say:
"This is good enough to test. Let's learn."
Because the feedback loop is the whole point.
What you can expect here
My goal with GrowthEngineer.Tech is to build the resource I kept looking for.
Expect posts on:
tools I actually use (and why)
research worth reading (and what it means in practice)
opinions (with receipts)
strategies + best practices
"how I approach this" breakdowns
experiments: what worked, what didn't, and what I'd do differently
Mostly short, practical, and insightful.
If you're here early…
You're kind of proving the point: this space is growing, but the public playbook is still sparse.
So, let's build it.
If you're a growth engineer (or trying to become one) or just interested in the craft, do me (and all growth engineers looking for more resources) a favor and subscribe. And, if there's a topic you want covered, send it my way. I'm building this as a living resource.
We'll explore, experiment, test, and measure what growth engineering is together.