head of growth — Core Skills
Use These Keywords
leadership, project management, cross-functional collaboration, stakeholder communication, data analysis
Avoid Generic Terms
responsible for, duties included, worked on, helped with
Acquisition, Retention and Funnel Terms. Role-targeted keyword map with ATS-safe placement strategies.
Head of Growth is three different jobs behind one title, so declare whether you ran performance marketing, product-led growth or growth analytics, name the metric you owned and how it was defined, and use that lane's vocabulary consistently.
Want to apply this to your own resume right now?
Analyze Role KeywordsHead of Growth postings fall into roughly three families that hire from different talent pools. The first is performance marketing leadership: paid search, paid social, app campaigns, affiliates, creative testing and budget allocation, usually reporting into marketing. The second is product-led growth: onboarding and activation, self-serve conversion, pricing and packaging experiments, in-product upsell and referral mechanics, usually reporting into product with a dedicated engineering squad attached. The third is growth analytics or growth engineering: event instrumentation, experiment infrastructure, growth modelling and the data layer everyone else depends on. A resume that never declares a lane matches all three weakly and wins none of them.
Reporting line and team composition tell a reader which one you were faster than any keyword can. Say who you reported to, whether engineers and designers sat on your team or had to be requested from elsewhere, whether you controlled a media budget and roughly how large it was, and whether you could ship product changes yourself. Where your career spans lanes, order the history so the relevant one dominates the first half of the page and compress the rest. If a posting is ambiguous, its metrics section resolves it: activation and conversion rates mean product growth, blended acquisition cost and payback mean performance marketing, and instrumentation language means the analytics variant.
The question behind every growth interview is whether you have ever owned a number rather than contributed to one. Name it, and then define it, because growth metrics are defined inconsistently across companies and an undefined number is treated as noise. Activation rate means nothing without the activation event behind it. Retention needs a cohort window and a statement of whether it is measured on logins, on a core action or on revenue. Acquisition cost needs to say whether it is blended or paid-only and whether salaries and tooling are inside it. Payback needs to say whether it is gross margin adjusted. Stating the definition also signals that you built the definition, which is usually the harder part.
Then give the mechanism, because a number without one reads as a coincidence. Growth work moves metrics through identifiable levers: removing steps from a signup flow, changing the default plan, adding a reactivation trigger, shifting budget between prospecting and retargeting, changing creative refresh cadence, introducing an annual billing incentive, or building a referral loop with a two-sided reward. Say which lever you pulled, what you expected to happen, and what actually happened, including the times the result was flat or negative. A candidate who reports a failed test with a clear read on why it failed is consistently more convincing than one whose every initiative apparently worked.
Measurement literacy has become the fastest way to distinguish a senior growth leader from a capable operator. Consent frameworks, mobile tracking restrictions and the erosion of third-party cookies have made platform-reported conversions unreliable as a measure of contribution, and every ad platform now reports more conversions than an incremental read would support. Senior candidates demonstrate that they know this. They name the consent management setup, the server-side tagging or conversions API implementation, the mobile measurement partner, and the modelled share of reported conversions. They also show at least one attempt at causal measurement, whether a geo holdout, a matched-market test, a read taken from a deliberate spend pause, or a lightweight media mix model.
The same scepticism applies inside the product. Self-reported attribution surveys, last-touch dashboards and correlational cohort comparisons all have well-known failure modes, and describing how you handled them is a stronger signal than any tool name. Say how you separated seasonality from effect, whether you ran holdout groups for lifecycle messaging, how you treated cannibalization between paid and organic traffic, and what you did when an incrementality result contradicted the platform numbers. This is where credibility is won on a growth resume, and it is almost always missing, which makes even two well-judged sentences disproportionately valuable to a reader who has seen a hundred of these.
Experiment counts are a weak signal. What an experienced interviewer looks for is design discipline: whether the hypothesis was falsifiable, how the primary metric and the guardrail metrics were chosen, whether sample size and minimum detectable effect were calculated before launch rather than rationalized afterwards, how long the test ran relative to the business cycle, whether repeated peeking was controlled through a fixed horizon or a sequential method, and how novelty effects and traffic contamination were handled. Describing a single experiment at that level of detail proves far more than a summary line about building a culture of experimentation, and it is the depth the interview will reach anyway.
Tooling belongs here too, named as products rather than categories. Give the product analytics platform and the event taxonomy behind it, the experimentation platform or feature flag system, the warehouse and transformation layer if experiment analysis ran there, the business intelligence tool, and the lifecycle messaging platform with the channels you actually used. Mention instrumentation work explicitly, because event schema design, identity resolution between anonymous and logged-in states, and agreeing a single reliable definition of an active user are the unglamorous foundations that make everything else measurable. Growth leaders who have done that work know it is a hiring differentiator, and the ones who have not usually cannot describe it.
| Signal | Why It Matters | Fix |
|---|---|---|
| The resume lists channels managed but never states a metric you owned. | Growth hires are made to move one specific number, so a channel list reads as an execution profile rather than an owner. | State the metric, its definition, the baseline and the mechanism you used to move it. |
| Every performance number on the page comes from an ad platform dashboard. | In-platform attribution overstates paid contribution under current consent and tracking constraints, and any experienced interviewer will probe it. | Add one incrementality read from a geo test, a holdout or a spend pause, even a small and imperfect one. |
| Experiment volume is quoted as the achievement. | A test count says nothing about statistical power, guardrails or whether anything was decided as a result. | Describe one experiment end to end, including the effect size you designed for and the decision it produced. |
Use These Keywords
leadership, project management, cross-functional collaboration, stakeholder communication, data analysis
Avoid Generic Terms
responsible for, duties included, worked on, helped with
Use These Keywords
SaaS, KPI tracking, process optimization, workflow automation, reporting
Avoid Generic Terms
various tools, software, systems, platforms
Follow this guided reading path to build topic depth and improve your ATS outcomes faster.
It is whichever the organization has decided, and the posting almost always reveals it if you read past the first paragraph. Check the reporting line first: a role reporting to a chief marketing officer is normally performance marketing leadership, one reporting to a chief product officer is product-led growth, and one reporting directly to a founder or chief executive can be either and usually means the function is being built from scratch. Then check the metrics section. Activation, trial conversion and onboarding language points to product. Blended acquisition cost, payback and channel mix points to marketing. Instrumentation and experiment platform language points to the analytics variant.
Use relative movement rather than absolute values, which is standard practice and rarely objected to. Percentage changes, ratios, indexed values and order-of-magnitude bands communicate the scale of what you did without disclosing anything commercially sensitive, and you can describe the size of the business in a range rather than exactly. What matters more than the number is the mechanism: a reader who understands what you changed, why you expected it to work, and how you knew it had worked will form a view of your ability regardless of whether the underlying figure is disclosed. Never substitute an invented number for a withheld one, because interview questions go straight there.
Use our tools to apply this guide and improve your next application.
Role-level keyword maps for FP&A, accounting, audit, and treasury resumes — with anti-patterns to avoid.
Stack-specific keyword strategy for SWE resumes with project-to-impact mapping that impresses both ATS and hiring managers.
Weak marketing bullets kill your ATS score and recruiter interest equally. See 20 real before/after rewrites that add impact, keywords, and measurable results.