to hire an app growth marketer, ask for numbers and decisions, not frameworks, then run a short paid test project with pass or fail criteria written before any spend. the ten questions below expose people who can present growth but have not run it, and the test project shows how the rest actually work inside an account.
The 10 questions that expose deck-only marketers
these ten questions work because a real operator answers each one with a number or a specific decision, while a deck-only marketer answers with a framework. listen for how fast the numbers come, whether the method behind them is clear, and whether they mention things they killed, not only things that won.
- “what was your CAC, and how did you calculate it?” good: a number, blended or channel, and what counted as a user. worrying: a cost per install presented as CAC.
- “what happened to retention while you scaled?” good: day 1 or day 30 before and after. worrying: they only tracked installs.
- “how many creatives did you test per month?” good: dozens, with a process. at ZuAI i ran 150+ a month. worrying: “a few really high quality ones.”
- “what did you kill last month, and why?” good: a specific ad or channel and the threshold that triggered it. worrying: nothing comes to mind.
- “what would you not do for us?” good: a clear line, like no paid spend until retention is measured. worrying: they will do anything you ask.
- “who actually does the work?” good: a named person, often the one talking to you. worrying: “the team.”
- “how will we know in 30 days if this is working?” good: a pass or fail metric written down now. worrying: “growth takes time.”
- “walk me through a creative brief you wrote.” good: concept, hook, audience insight, where the idea came from. worrying: a mood board.
- “when platform numbers and our analytics disagree, which do you trust?” good: blended numbers from your own analytics, and why. worrying: whatever the ad dashboard says.
- “can i talk to a founder you worked with?” good: yes, with a name. worrying: only unnamed testimonials.
How to structure a paid test project
a good test project is short, paid, capped and judged on criteria written before it starts. give the candidate one real question, such as whether a channel can produce retained users under a target cost, a fixed budget and window, and access to the numbers. then judge the process as much as the result.
a structure that works:
| part | what to set |
|---|---|
| question | one channel or one message to validate, not “grow the app” |
| window | two to four weeks |
| budget | a fixed ad budget you can afford to lose, plus a paid fee for their time |
| pass or fail | a written threshold, like cost per day 7 retained user under a target |
| reporting | weekly numbers and a written list of what was killed and why |
watch how they brief creative, how quickly they kill losers, and whether their reporting uses retained users. a failed test run well is a better hiring signal than a lucky win nobody can explain.
Red flags that cost founders the most
the red flags that cost the most are the ones that hide a lack of real results: reporting installs or clicks as outcomes, guaranteeing numbers for an app they have not seen, pushing one channel for every problem, recommending fake engagement, and never questioning your onboarding. any one of them is reason to keep looking.
- installs, impressions or clicks as results. none of them are users.
- guaranteed numbers. nobody can promise a CAC for an app they have not seen.
- one channel for everything. if every problem is solved by the channel they sell, they are selling a channel.
- fake engagement tactics. bought reviews, fake accounts, vote manipulation. these can get your app pulled from stores or your domain banned from Reddit.
- no opinion on the product. growth and product are connected. someone who never questions onboarding is doing half the job.
Proof you can actually check
the only proof worth weighing is proof you can verify: a named company, specific numbers, and the method behind them. a case study like that tells you more than any badge, directory ranking or logo wall, because you can test the story with the same ten questions above.
mine is the ZuAI breakdown, 10K to 2M users at $0.02 CAC, on the case studies page. for what each hiring option costs, see how much an app growth marketer costs, and for which kind of hire fits your stage, operator vs agency vs in-house. if you want to run these questions on me, start here.
want this applied to your app? get a free teardown: your funnel, your creative, and the one play i would run first.
Frequently asked questions
Who is the best app growth marketer?
the best app growth marketer for you is the one with a checkable result in an app like yours, at a stage like yours. ask for a specific number, like CAC or retention before and after, and how it was measured. a named case study with numbers beats a long client logo list every time.
What should I ask an app growth marketer in an interview?
ask what their CAC was and how they calculated it, what they killed last month, how many creatives they tested monthly, and what happened to retention while they scaled. operators answer with numbers and specific decisions. people who have not done the work answer with frameworks and slides.
Should I pay for a test project before hiring?
yes, and pay properly for it. a short, capped test project with written pass or fail criteria shows how someone actually works: how they brief creative, what they kill, how they report. unpaid spec work attracts the wrong people and tells you little about how they run a real account.