Growth Engineer CV Guide: Where Engineering Meets Product and Marketing

Growth engineering is one of the most genuinely misunderstood roles in tech. It sits between software engineering, product management, and marketing analytics, draws from all three, and often ends up being evaluated by hiring teams who are not quite sure what they are looking for. That ambiguity is both the challenge and the opportunity when writing your CV. Done right, your application can make a recruiter's job easier by articulating the role clearly and demonstrating that you fit it precisely. Done wrong, it reads as either "developer who does some marketing tasks" or "marketer who can write basic code" — neither of which lands.

This guide is about writing a growth engineering CV that positions you correctly, proves your impact, and makes you immediately legible to the teams most likely to hire you.

Understanding What Hiring Teams Actually Want

Before writing a single word of your CV, it is worth being clear about what a growth engineering role actually requires and how it varies across companies. At a startup series A or B, a growth engineer is often a generalist: someone who can build experiments end to end, instrument event tracking, write SQL queries to analyse results, and ship frontend changes that improve funnel conversion. The emphasis is on speed, breadth, and comfort with ambiguity.

At a larger company, growth engineering roles tend to be more specialized. You might own experimentation infrastructure, work exclusively on acquisition funnel optimization, or focus on activation and retention with dedicated data engineering support. The skills that matter in this context — statistical rigour, platform knowledge, experiment design — are more specific than the generalist startup version.

Your CV needs to reflect which type of role you are applying for. A growth engineer CV written for Series A startup roles and one written for a growth platform team at a large consumer tech company should emphasize different things. The underlying experience might be the same, but the framing, the metrics highlighted, and the language used need to match the context.

The Structure: What Sections to Include

A growth engineering CV works best with a structure that mirrors the role's hybrid nature. Here is a layout that works consistently:

Professional summary — 3–4 sentences that establish your positioning clearly. Not "experienced software engineer with growth experience" and not "growth marketer with technical skills." Something like: "Growth engineer with five years of experience owning the full experimentation lifecycle — from hypothesis through implementation to statistical analysis. Comfortable writing production-level TypeScript and Python, designing and analysing A/B tests, and translating data insights into shipping decisions."

Core skills — a single section that spans technical and analytical competencies. This is one of the few contexts where listing skills explicitly is genuinely useful, because growth engineering spans so many tools and disciplines. Include: languages (JavaScript, Python, SQL), experimentation platforms (Optimizely, LaunchDarkly, internal frameworks), analytics tools (Mixpanel, Amplitude, Segment, Looker), and any specific areas of growth expertise (SEO, referral loops, onboarding optimization).

Work experience — see below for how to write this section specifically.

Projects or experiments — for engineers who have run notable experiments with measurable impact, a dedicated section listing two or three high-signal examples can be more effective than trying to weave everything into job descriptions.

Education — brief, at the bottom. A computer science degree is common but not required; many strong growth engineers have backgrounds in economics, statistics, or even physics.

Writing Work Experience That Proves Hybrid Impact

The work experience section is where most growth engineering CVs fall short. The risk is writing bullet points that are either purely technical ("built internal experimentation framework in Node.js") or purely outcome-focused without the mechanism ("improved conversion rate by 18%"). Both are incomplete. The best growth engineering bullets connect the engineering work to the business outcome through the analytical layer.

Here is what that looks like in practice:

Weak: "Ran A/B tests on onboarding flow"

Stronger: "Designed and implemented eight onboarding experiments over six months using LaunchDarkly, increasing trial-to-paid conversion by 14% and reducing time-to-first-value from four days to under two"

Weak: "Built internal analytics tooling"

Stronger: "Built a lightweight event replay tool in Python that cut experiment debugging time by 60% and enabled the team to run 3x more experiments per quarter"

Weak: "Worked with marketing team on SEO improvements"

Stronger: "Implemented programmatic landing page generation targeting 400+ long-tail keywords, resulting in 35% growth in organic trial signups within 90 days"

The formula is: what you built + the mechanism + the measurable outcome. All three components need to be present. Hiring teams want to see that you understand which lever you pulled, how you pulled it, and what moved as a result.

Technical Skills: How Deep Is Deep Enough?

One of the most common questions from growth engineers writing their CV is how technical to make it. The honest answer is: deep enough to be credible, but not so specialized that you look like a backend engineer who wandered into growth by accident.

The technical bar for growth engineering is typically full-stack competence with a frontend bias. You need to be able to ship UI changes, instrument events, write backend logic for referral or sharing features, and query data independently. If you need a separate data engineer to write every SQL query, or if you require a frontend engineer to implement every experiment, that is a constraint that hiring teams will notice.

What you do not need, and should not overemphasize, is deep systems programming, infrastructure engineering, or highly specialized backend work. If your CV reads as "senior systems engineer who also runs A/B tests," the growth role you are applying for may not even shortlist you — they will assume you are overqualified for the engineering work and underinterested in the broader mandate.

Be honest about your technical level and calibrate your CV accordingly. Growth engineering hiring managers are good at detecting people who are overselling their depth.

Metrics and How to Present Them

Growth engineering is a metrics-first discipline, and your CV should reflect that. Every significant project should have at least one number attached to it. The relevant metrics depend on which part of the funnel you have worked on:

• Acquisition: organic traffic growth, CAC reduction, channel conversion rates, signup volume
• Activation: time-to-first-value, feature adoption rates, onboarding completion rates
• Retention: D7/D30 retention, churn reduction, engagement frequency
• Monetisation: trial-to-paid conversion, ARPU changes, upsell rates
• Experimentation: number of experiments run, win rate, velocity improvements

If you do not have clean metrics for every bullet, use ratios and relative improvements where absolute numbers are confidential. "Reduced drop-off at the pricing step by 22%" communicates clearly without revealing absolute volumes. "Improved email activation sequence open rate from 18% to 31%" gives a baseline and a result without disclosing anything sensitive.

What to avoid: vague outcome language like "significantly improved" or "contributed to growth." These read as signalling that you either do not have numbers or do not understand why numbers matter. In a growth role, both are disqualifying signals.

Experimentation Depth: Showing You Understand the Science

Strong growth engineering CVs distinguish themselves by demonstrating that the candidate understands statistical validity, not just experiment execution. There is a meaningful difference between "ran A/B tests" and "designed experiments with 80% power at a 5% significance threshold, segmented by cohort to avoid novelty effect contamination."

If you have experience with:

• Minimum detectable effect calculations
• Multi-armed bandit algorithms
• Bayesian vs frequentist experiment analysis
• Handling peeking problems and sequential testing
• Experiment interaction effects in overlapping tests

...include it. Even a brief mention in your summary or skills section signals to an experienced growth leader that you understand experimentation as a discipline, not just a tool.

Positioning for Different Company Stages

Your CV should read differently depending on whether you are targeting an early-stage startup, a growth-stage company, or a large platform team.

Early stage (Seed–Series A): Emphasize breadth, speed, and comfort with ambiguity. Use examples that show you have shipped experiments with minimal support, made judgment calls with incomplete data, and worn multiple hats. The hiring manager here wants someone who can move fast and own things end to end.

Growth stage (Series B–D): Emphasize scaled impact, cross-functional collaboration, and the ability to both do the work and build systems around it. Examples that show you have built infrastructure others can use, or run experiments that involved product, data, and marketing alignment, land well here.

Large platform team: Emphasize technical depth, platform thinking, and statistical rigour. Show that you can work within a large codebase, contribute to shared tooling, and bring analytical credibility to experiment design.

Using NextCV to Tailor Your Application

Growth engineers applying to multiple roles face a specific challenge: the role description varies enormously from company to company, even when the title is the same. A growth engineer at a B2B SaaS company is doing something quite different from one at a consumer app or a marketplace. Tailoring your CV to each specific role is therefore especially important — and especially time-consuming if done manually.

NextCV makes it practical to generate a version of your CV matched to each role's specific requirements, so the experiment examples you surface, the metrics you lead with, and the framing of your background all resonate with the specific team's priorities. Given that a well-matched CV is the single most important variable in whether you make it to a screen, it is worth investing in the tailoring.

The Cover Letter: Where to Tell the Story Your CV Cannot

Growth engineering CVs benefit significantly from a strong cover letter — not because hiring managers always read them, but because the ones who do are disproportionately likely to be senior growth leaders who want to understand how you think, not just what you have done. Your cover letter is where you can explain your growth philosophy, discuss an experiment that failed and what you learned, or articulate why you are excited about the specific company's growth challenges. That analytical voice is one of the most compelling signals in a growth engineering application.

Write your cover letter last, after your CV is finalized. Use it to say things the CV format cannot accommodate: the reasoning behind decisions, the context around a pivotal experiment, the genuine reason you want to work on this specific problem. The combination of a metrics-dense CV and a thoughtful cover letter is nearly impossible to ignore.