Product Engineer & Growth
Growth roles go to whoever can find, with data, the exact place users fall out of the funnel - and then close it.
How to read this page - source, method & limits
Where this comes from
A self-reported, first-person account of one real role, authored by the person who held it. There are no automated data sources, scores, or predictions on this page - every statement is a human claim. Each role is checked by an “honesty lint” before it ships: it must name the part of its success you cannot copy (the unfair advantage) alongside the part you can, plus at least one fake wall and one concrete first step.
How it's meant to be used
Intended: as one honest worked example of how a hard-looking role was reached, to copy the replicable lever and the first move. Not intended: as a checklist, a guarantee, or a claim that this is the only way in. It is a sample size of one.
Assumptions & limitations
Written in hindsight, so it can over-credit what happened to work and under-count luck and timing. It's also survivorship-biased - you're reading the paths that worked. Treat the prerequisites as “what mattered here,” not “what is required everywhere.”
If an AI coach discusses this role
A local coach can talk through this page using a hidden brief. It is instructed to separate the replicable lever from the unfair advantage and to never promise the role or any outcome. Verify anything time-sensitive (deadlines, named programs, contacts) yourself - those drift.
What it really is
Owning product analytics and growth for an AI grant-funding platform: designing the Mixpanel event architecture, watching thousands of session recordings, and finding the onboarding and payment bottlenecks.
What you actually needed
- Can instrument a product and read the funnel data honestly
- Patience to watch real sessions and spot where people get stuck
- Will turn findings into shipped changes, not just decks
Fake walls (looked required, weren't)
- A formal growth or data-science title, or a marketing background - the lever was analytical and product instinct
The proof-of-work
A Mixpanel event architecture and a stack of identified, evidenced conversion bottlenecks the founders could act on.
The move
Worked directly with founders, instrumented the product, and showed measurable activation/retention insight.
⚖️ The unfair advantage (named honestly)
A network that put him in direct contact with the founders of a funded startup.
The replicable lever underneath it
The lever is the analytical method, which is public and free: instrument any product (even your own), watch the funnel, and write up where users drop. That artifact is what gets you the seat.
The climb
- 1
If you're you've never instrumented a product
set up analytics on any app and map one funnel
→ leaves behind: a funnel and a drop-off write-up
- 2
If you're you can read a funnel
find a startup and offer a real teardown of their activation
→ leaves behind: an evidenced list of bottlenecks
- 3
If you're founders trust your read
own analytics and ship the fixes
→ leaves behind: a product/growth role with measurable wins
🌱 Do this week
Add event tracking to any small app, map its funnel, and write one page on where users drop and why.
Ask the coach
Dig into how this role actually gets reached: the proof-of-work, the move, and what to do if you don't have the unfair advantage.
I'll answer honestly about how this role gets reached. I will not promise an outcome, and I'll always separate the part you can copy from the part you can't. Tap a question or ask your own:
Runs on your own machine. No outcome is promised; this is guidance, not a guarantee.
No outcome is promised. This is the lever and the move, told honestly - the rest is the work.