How to Hire a Growth Manager

Product-led companies produce the strongest ones, because growth there is a real function with engineering attached rather than a rebranded acquisition team. Three backgrounds convert well: product managers who owned activation or onboarding, performance marketers who moved into lifecycle and in-product work, and analysts who got tired of recommending and started shipping. Be sceptical of the public growth persona built on conference talks and threads, and ask instead what they personally changed inside a product. Referrals from engineers and product managers are the best filter, since those people watched the work land. Ask every candidate for their experiment log. Set the funnel ownership out clearly in the [growth manager job description](/job-descriptions/growth-manager) so applicants know which stage is theirs.

Which part of the funnel they own, and what they get to work with. Acquisition, activation, retention, monetisation and referral are five different jobs, and someone excellent at onboarding may have never bought media in their life. Then state the resources honestly: engineering time, design support, data access, and whether they can ship without joining the product roadmap queue. A growth manager with no engineering capacity is an expensive suggestion box, and experienced candidates will ask about this in the first call. Say who arbitrates when growth work and roadmap work collide. Name the metric they will be judged on and confirm you can already measure it, because instrumentation gaps surface in week one otherwise.

Two exercises. First, a funnel with an obvious drop between signup and first meaningful action. Ask for one metric to move, three hypotheses ranked by expected impact against effort, what each needs to run, roughly how much traffic is required before the result means anything, and the decision rule agreed in advance. Second, hand them a test somebody else declared a winner: stopped early, judged on a metric that changed midway, run on a segment that was not the target. Strong candidates spot the early stop and the moved goalpost within minutes and say so plainly. Weak ones admire the lift. Both exercises take an hour and reveal far more than a discussion of tactics ever does.

Four. A screen on funnel ownership and what they personally shipped. A review of the funnel exercise with product and data people who can press on the reasoning. An engineering session on what they would build first, what instrumentation is missing and how they would keep the work small enough to ship weekly. Then a retention conversation, which is the stage that separates candidates, because most talk fluently about acquisition and go quiet on why users leave. Take a reference from an engineer who shipped their tests rather than only from their manager, and keep the [growth manager interview questions](/interview-questions/growth-manager) anchored to the exercise. Track panel scores and stage conversion the same way you would a funnel, using the numbers in your [recruitment metrics](/recruitment-metrics) reporting.

Expect a competitive search, because the profile is genuinely scarce and the title is attached to very different jobs at different companies. Candidates choose on two things: whether growth has real engineering capacity, and whether leadership tolerates experiments that fail. Show them the last five tests you ran, including the ones that did nothing. If almost everything you run appears to win, a good candidate will read that as a measurement problem and say so during the interview, which is a positive signal. Model the payback of the hire against the roles it unblocks, and if you use [AI recruiting tools](/ai-recruiting-tools) to source, keep a human reading the actual experiment write-ups.