Growth Engineer
Growth engineers sit at the intersection of product, data, and engineering, designing experiments that move north-star metrics. Their daily English covers writing experiment briefs, presenting statistical results to product managers, and communicating funnel findings across functions. This path builds the precise vocabulary needed to run, document, and discuss growth experiments with confidence.
Topics covered
- A/B testing & experimentation
- Funnel analysis
- Activation & retention
- Product-led growth
- Statistical significance
- Experiment documentation
Vocabulary spotlight
4 terms every Growth Engineer should know in English:
The single primary metric that best captures the core value a product delivers to users
"Our north-star metric shifted from signups to weekly active users after the PLG pivot."
A segment of users deliberately excluded from an experiment to serve as a control baseline
"We kept a 10% holdout group to measure the long-term effect of the onboarding change."
The point in a conversion funnel where users stop progressing to the next step
"The biggest funnel drop-off is between the pricing page and checkout — 68% abandon there."
To roll out the winning variant of an A/B test to 100% of users after a statistically significant result
"We achieved 95% confidence on day 14, so we shipped the winner to production."
📚 Vocabulary Reference
Key terms organised by category for Growth Engineers:
Experimentation
Funnel & Conversion
Product-Led Growth
Data & Analysis
Recommended exercises
Real-world scenarios you'll practise
- Writing an experiment brief for a new onboarding A/B test and presenting it in a cross-functional review.
- Reporting statistically significant results to a product manager — explaining p-values and confidence intervals in plain English.
- Running a retro on a failed experiment — communicating learnings without blame and proposing next steps.
- Presenting a funnel analysis to stakeholders, highlighting the highest-impact drop-off point and the recommended fix.
Recommended reading
Frequently Asked Questions
What English skills do Growth Engineers most need to improve?+
Growth Engineers most commonly need to improve: technical vocabulary (the correct English terms for domain concepts), collocation accuracy (using the right verb for each action), written communication (bug reports, PR descriptions, technical docs), and spoken communication for standups, code reviews, and stakeholder meetings.
How long does the Growth Engineer learning path take?+
The Growth Engineer learning path contains 20–40 hours of material studied comprehensively. Most learners focus on the highest-priority modules first and return to the rest over time. Spending 30 minutes per day for 4–6 weeks produces noticeable improvement in workplace English.
What vocabulary should a Growth Engineer prioritise first?+
Start with the vocabulary that appears most in your daily work — terms you read in documentation, use in commit messages, and hear in meetings. The Growth Engineer path begins with the most frequent vocabulary clusters before moving to advanced communication patterns.
Are there interview exercises for Growth Engineer roles?+
Yes. The Growth Engineer path includes role-specific interview question modules with model answers and key phrases — the actual questions interviewers ask and the vocabulary needed to answer them fluently. There is also a dedicated Interview Practice hub for general interview skills.
Does this path include pronunciation help?+
Yes. The path links to pronunciation exercises for the technical terms most commonly mispronounced in this domain. The Pronunciation hub includes drills for acronyms, silent letters, word stress, and minimal pairs — all in IT context.
What are the most common English mistakes Growth Engineers make?+
The most common mistakes: incorrect collocations (using the wrong verb with a technical noun), false friends from L1, tense errors when narrating past incidents or walkthroughs, and using overly formal or overly casual register in written communication.
How do I improve my English for code reviews?+
Learn the standard code review collocations: approve a PR, request changes, leave a nit, address feedback, block a merge, resolve a conversation. Use hedging language for suggestions: "This might be cleaner as…", "Have you considered…?". The Collocations section includes a dedicated Code Review set.
Can I use this path alongside my daily work?+
Yes — the path is designed for working professionals. Each exercise set takes 10–15 minutes. The most effective approach is to study a vocabulary module before a meeting or task where you'll use that vocabulary, then practise immediately after. Context-linked practice produces much faster retention.
Is the content free?+
Yes, completely free. No registration required, no payment, no time limit. All vocabulary modules, exercises, glossary entries, and learning path guides are open access.
How do I track my progress through this path?+
Progress is tracked in your browser's local storage — completed exercise sets are marked with a checkmark when you return. No account is needed. You can bookmark specific modules and use the exercises overview to see which sets you've completed.