Where to Find Growth Engineers
Growth engineers often come from these backgrounds:
- PLG companies: Dropbox, Slack, Notion alumni understand growth loops
- Former founders: They've had to wear all hats including growth
- Product engineers who got bored: They want to see impact on metrics
- Data-heavy backgrounds: Engineers with analytics experience
- Marketing engineers: Developers who worked closely with marketing
Interview Process for Growth Engineers
1. Initial screen (30 min)
Focus on growth mindset. Ask about experiments they've run, metrics they've moved, and how they think about prioritization.
2. Technical round (60 min)
Full-stack coding with a growth twist. Give them a problem like "improve this signup flow" where the solution involves both code and product thinking.
3. Growth case (45 min)
Present your actual funnel data. Ask them to identify opportunities, propose experiments, and estimate impact. Look for structured thinking.
4. Data round (30 min)
Give them a dataset and ask growth questions. Can they write SQL? Do they understand cohort analysis? Can they interpret A/B test results?
Key Interview Questions
Experimentation:
- • "Tell me about an experiment you ran. What was the hypothesis? What did you learn?"
- • "How do you decide what to test vs what to just ship?"
- • "How do you calculate sample sizes? When would you stop a test early?"
Growth thinking:
- • "How would you increase our signup rate by 20%?"
- • "What metrics would you track for activation? How would you move them?"
- • "Tell me about a growth loop you've built or improved."
Technical:
- • "How would you instrument this feature for analytics?"
- • "Walk me through building an A/B testing framework."
- • "How do you balance shipping speed with code quality?"
Red Flags in Growth Engineer Candidates
- No concrete examples: Can't point to specific experiments or metrics they moved
- Only talks tactics: No understanding of how tactics connect to strategy
- Afraid of failure: Growth requires embracing failed experiments
- Dark pattern enthusiasm: Wants to trick users rather than help them
- No curiosity: Doesn't ask about your funnels or growth model
- Siloed thinking: Doesn't see growth as cross-functional