Growth Marketer
Structured interview questions for Growth Marketer, with what a strong answer surfaces for each one.
BehavioralExperimentation rigor Describe the last experiment that clearly failed. What was the hypothesis, what did you measure, and what did you change afterwards?
What a strong answer surfacesThe ability to frame an experiment as a hypothesis test and not as a personal success. A clear up-front hypothesis with a measurable success criterion, a clean stop criterion, concrete learnings. Bonus: the candidate describes how the learning fed into the next experiment or the roadmap. Anyone who cannot name a failed experiment rarely has real experimentation practice and tends toward confirmation bias in the analysis.
BehavioralAnalytical thinking Tell me about the last time you ran a data analysis that disproved a prior assumption held by management. What did you find, and how did you communicate it?
What a strong answer surfacesThe ability to work with data independently (SQL, spreadsheet, analytics tool) and to communicate an uncomfortable result without a defensive posture. Bonus: the candidate describes making the analysis reproducible (a notebook, a documented query, a shared dashboard) and how the finding was turned into a decision. Anyone who only exports data from the marketing tool and presents it without validation is too weak for this position.
BehavioralAcquisition-channel expertise Describe the last time you built a new acquisition channel from scratch. Which channel, what period, how did you validate it?
What a strong answer surfacesA structured approach: a small test budget, a clear validation criterion (CAC below a threshold, sufficient volume, a scalable cost-per-mille curve), a defined stop criterion. Bonus: the candidate describes a channel that only worked after 4 to 8 weeks of iteration (shows patience and the ability to iterate), or a channel they shut down after a clear validation failure. Anyone who names only successful channel launches or scales channels with no CAC comparison shows a weakness in validation discipline.
SituationalFunnel vision You take over a growth post at a B2B SaaS SMB with 40 employees, 3 M€ ARR, a 14-day trial with 8 % trial-to-paid. Management wants to lift trial-to-paid to 14 %. What do you do in the first 30 days?
What a strong answer surfacesAudit before action: a funnel diagnosis (signup-to-activation, activation-to-power-use, trial-to-paid), qualitative interviews with 5 to 10 converted and 5 to 10 non-converted trial users, identifying the two or three bottlenecks with the highest leverage. Only then hypotheses, only then experiments. Candidates who jump straight to we build a better onboarding show an execution bias with no diagnosis. Bonus: the candidate questions the base assumption (is 14 % realistic for our segment? What benchmark data exists?).
SituationalAcquisition-channel expertise You have a budget of €8,000 per month for paid acquisition. Current channels: Google Ads (CAC €320, stable volume), LinkedIn Ads (CAC €480, growing volume). A new channel is proposed by the team (Reddit Ads, untested). How do you allocate the next quarter?
What a strong answer surfacesRisk allocation instead of a single bet: roughly 70 to 80 % on validated channels (Google plus LinkedIn) in proportion to current CAC efficiency, 15 to 25 % as a test budget on the new channel with a clearly defined validation criterion and a stop criterion after 4 to 6 weeks. Bonus: the candidate asks about pipeline conversion per channel (the same CAC does not mean the same LTV) and proposes validating lead quality per channel with sales. Anyone who bets everything on one channel or splits the budget evenly across three shows a lack of allocation discipline.
SituationalExperimentation rigor An experiment on the pricing page shows an 18 % conversion lift after 2 weeks, against a planned 4-week sample. Management wants to roll it out immediately. How do you react?
What a strong answer surfacesStatistical cleanliness: the candidate refuses an early stop if statistical significance and the minimum sample (a sample-size calculation up front) are not reached. They explain the risk of peeking bias and propose a middle path (let the test run to the planned end, prepare the rollout plan in parallel). Bonus: mentions a segment-specific analysis (does the effect hold across all plans? Across all sources?). Anyone who agrees to roll out immediately with no query has no statistical reflex and produces false conclusions in the medium term.
TechnicalExperimentation rigor How do you prioritize a list of 30 possible experiments? Describe your framework concretely and compute an example out loud.
What a strong answer surfacesA structured methodology: ICE (Impact, Confidence, Ease) or PIE (Potential, Importance, Ease) or similar, with example values. Bonus: the candidate names the weakness of the framework (Confidence is subjective without data, Impact estimates tend toward optimism) and describes a correction mechanism (a post-mortem after each experiment, calibration tracking of their own estimates). Anyone who only names the framework without being able to compute an example has not applied the framework operationally.
TechnicalTool and data competence Describe your ideal growth stack for a B2B SaaS SMB with 50 employees and 5 M€ ARR. Justify each tool and name the two or three connections that break first.
What a strong answer surfacesA lean, coherent stack: a CRM (HubSpot or Salesforce), product analytics (Amplitude, Mixpanel or PostHog), web analytics (GA4 or Plausible), lifecycle automation (Customer.io, HubSpot or Braze), an experimentation tool (VWO, Optimizely or feature-flag-based), an SEO tool (Ahrefs or Semrush), a data warehouse (BigQuery or Snowflake), reverse ETL for activation data (Hightouch or Census) where relevant. Bonus: the candidate identifies the fragile connections (a product event to the CRM, attribution across multiple devices) and names concrete pitfalls.
TechnicalTool and data competence Which SQL or spreadsheet analysis do you do most often yourself, without asking an analytics team? Describe a concrete recent analysis with the data source, question and result.
What a strong answer surfacesOperational data autonomy: the candidate describes a concrete cohort analysis, funnel drop-off analysis or channel-attribution evaluation that they did themselves, ideally in SQL or a structured notebook. Bonus: mentions a validation loop (the result cross-checked with the product team or sales) before it was communicated. Anyone who can only work in pixel-analytics tools (the GA4, Mixpanel UI) without ever having written a raw-data query hits limits fast at an SMB, because the analytics team usually does not even exist.
ValuesProduct mindset Tell me about a situation where you worked closely with the product team on a feature meant to improve the funnel. How was the collaboration?
What a strong answer surfacesA partnership posture with product rather than a demanding stance. The candidate describes shared hypotheses, jointly defined success criteria, a shared review process. Bonus: mentions a feature that the product team implemented against the growth person's initial wish (shows that they understand the product logic and do not do pure optimizing without product understanding). Anyone who describes the product team as the-team-that-blocks-my-requests starts at an SMB with the wrong posture.
ValuesCross-functional collaboration How do you take difficult feedback from sales or the customer-success team that exposes a gap in your growth work (e.g. lead quality, onboarding friction)?
What a strong answer surfacesA learning posture: the candidate describes not just hearing the feedback, but integrating it and changing the practice. Bonus: shared what they learned with the rest of the team or documented a new process (a shared MQL definition, an onboarding-review cadence). Anyone who describes explaining their own logic instead of accepting the observation shows a coachability weakness that becomes a bottleneck in a cross-functional role like growth.
ValuesCross-functional collaboration Describe the marketing or growth team where you felt most comfortable. What defined the culture?
What a strong answer surfacesReflective clarity about their own ideal environment. The answer should be specific enough that they either fit your culture or not (speed, data focus, autonomy, collaboration, learning cadence). Bonus: the candidate names something that was missing in previous teams and would be a deal-breaker. Anyone who feels comfortable everywhere rarely has clear preferences and tends toward a fast re-resignation when reality does not fit.
CasePosture and motivation Why are you applying to us specifically and not to one of our competitors who are looking for similar profiles?
What a strong answer surfacesConcrete research into the product, market and stage of the company. The candidate names two or three specific aspects (market positioning, growth phase, product architecture, team) that attract them. Bonus: the candidate also identifies a difficulty or risk of the position (an early stage with no data maturity, a small ICP, strong competition) and explains why it is still the right choice. Anyone who answers with generic responses (I love growth, the mission speaks to me) has not prepared specifically and will move again after 6 to 12 months when the next logo beckons.
CasePosture and motivation What do you specifically want to learn in this role that you cannot learn in your current position?
What a strong answer surfacesSpecific learning goals beyond more responsibility: a concrete stack (a data warehouse, reverse ETL), a concrete funnel phase (retention mechanics, pricing tests), a concrete market (DACH specifics, international expansion). Bonus: the candidate describes an attempt to learn the desired thing in the current job, and why it was not possible there (shows an active learning posture, not pure move motivation). Anyone who cannot name specific learning goals is usually only looking for a salary increase or a better logo.
CasePosture and motivation In 18 months, what would be the best possible result of your work with us, and how would it be measured?
What a strong answer surfacesA concrete, measurable vision anchored in the company's business goals: quantified ARR or pipeline contributions, improved funnel metrics, an established experimentation cadence, raised data maturity. Bonus: the candidate names both output metrics (what was generated) and system metrics (which processes, which tools, which team posture established). Anyone who answers only very generically (I want to have an impact) has no clear career vision or has not engaged with the specific position.
Evaluation playbook
The Growth Marketer role reveals itself across five evaluation stages. The hands-on exercise (stage 4) is central: without it, it is hard to tell who really designs and prioritizes experiments from profiles who only repeat playbooks from their last job.
Stage 1: CV review
Look for: consistent tenure (at least 18 months in previous growth positions), company context (an SMB or scale-up between 10 and 300 employees, not exclusively a corporation or agency), a stack covered across several levers (paid, SEO, lifecycle, onboarding, pricing tests). Negative: 100 % paid specialization with no funnel view, or conversely pure brand or content profiles who call themselves growth without ever having measured a conversion path. Save the named growth curves (I grew ARR by X %) for the interview; those numbers are usually worthless without context on the starting point, market and team.
Stage 2: Phone screen (30 min)
Three questions only: (1) Describe your last quarter: which two or three experiments, what result, (2) Which funnel lever did you have the measurably biggest impact on? Give the number, period and context, (3) Why a move now? A clear narrative versus an unfocused one. Outcome: go/no-go in a 5-minute debrief, no more.
Stage 3: Structured interview (90 min)
Work through the 15 questions below, alternating behavioral, situational, technical, culture-fit and motivation. On the technical question about experiment prioritization (ICE or PIE), ask the candidate to compute out loud. At least two interviewers (ideally management or the Head of Marketing plus someone from product or data), independent scoring before the debrief.
Stage 4: Hands-on exercise (90 min, see work sample)
An experiment roadmap on a concrete funnel bottleneck (signup-to-activation or trial-to-paid). The candidate receives a funnel dashboard with numbers, formulates 3 hypotheses, prioritizes by ICE score, describes the test setup and defines success criteria. A 30-min presentation with 30 min of Q&A. This stage weighs heavily in the final decision. Candidates who list tactics with no prioritization framework or choose vanity metrics as success criteria are eliminated here.
Stage 5: References (structured check)
Call two references: a former direct manager (ideally the Head of Marketing or management) and a former peer from product, data or sales. Ask both the same 4 questions: What is she/he strongest at? Which experiment did they push through against expectations and how? Would you hire them again tomorrow, why or why not? A concrete example of how the person handled a failed experiment? The fourth question delivers the most signal on the experimentation posture.
How to recognize a great hire
| Trait | Below bar | On bar | Above bar |
|---|---|---|---|
| Analytical thinking | Reads dashboards passively without formulating hypotheses. Accepts the first number with no validation. Cannot compute CAC, LTV or funnel conversion without a spreadsheet. | Formulates testable hypotheses from data. Validates numbers across two sources before communicating them. Computes marketing math (CAC, payback, average order value) out loud, operationally. | Builds data models independently (SQL, spreadsheet, notebook) to investigate open questions. Spots biases (selection bias, survivorship bias) in marketing data and corrects the analysis accordingly. Can defend an uncomfortable analysis before management with numbers. |
| Experimentation rigor | Starts experiments with no up-front hypothesis or success criterion. Stops tests early on positive signals (peeking). Attributes success to the experiment without checking external factors (seasonality, parallel releases). | Documents the hypothesis, success criterion, minimum sample and stop criterion before each experiment. Runs the test to statistical significance. Runs a post-mortem after each experiment that captures the learning independently of the outcome. | Establishes a repeatable experimentation system: a prioritized backlog (ICE or PIE), central documentation, a shared calibration of their own estimates, a segment-specific evaluation. Can transfer the system to new employees and coaches others in the experimentation craft. |
| Acquisition-channel expertise | Knows only one or two channels in depth. Scales with no CAC comparison between channels. Does not question single-channel dependency as a risk. | Actively pilots three to five channels with a clear CAC and LTV comparison per channel. Validates new channels with a test budget before scaling. Spots saturation signals (rising CAC at constant volume) and reallocates. | Builds new channels systematically from zero: a validation protocol, a stop criterion, a scaling plan. Understands the mechanics of each channel in depth (bidding strategies, audience logic, creative iterations) and can speak with specialists as an equal without falling into the specialist bias. |
| Funnel vision | Optimizes one funnel phase in isolation (acquisition or activation) without checking the effect on the downstream phases. Measures output metrics (clicks, signups) rather than outcome metrics (activation, retention). | Thinks end to end: knows where the biggest funnel bottleneck sits and allocates effort accordingly. Understands the link between funnel phases (improved activation affects trial-to-paid and retention). Identifies bottlenecks before an output drop. | Steers the funnel as a system: coordinates with product, sales and customer success, anticipates cadence breaks before the revenue effect, establishes shared funnel metrics across functions. Spots structural limits (market TAM, an ICP bottleneck) beyond funnel mechanics. |
| Product mindset | Treats the product as an immutable variable. Writes more copy, builds more landing pages, instead of addressing structural product frictions. Sees the product team as a service provider rather than a partner. | Proposes product improvements with a hypothesis and data basis. Understands the product roadmap and proposes growth experiments that harmonize with it. Accepts product-driven prioritization. | Is perceived by the product team as a co-owner of relevant product surfaces (onboarding, activation, pricing). Formulates product hypotheses with the same depth as product managers. Participates in the roadmap discussion, not just the growth roadmap. |
| Cross-functional collaboration and coachability | Defends their own function with no dialogue with sales, product or customer success. A defensive posture toward feedback. No shared vocabulary across functions. | Shared definitions (MQL, activation, power user) with the adjacent teams. A regular cadence (weekly 30 min with sales, monthly with product). Accepts qualitative feedback and integrates it. | Establishes shared dashboards, shared rituals and a shared language across functions. Spots weak signals from other functions before escalation. Coaches their own environment in data competence and an experimentation mindset without falling into the role of a teacher. |
30 / 60 / 90 day success plan
By day 30
- A complete funnel audit: signup, activation, trial-to-paid, retention by month 1 / 3 / 6, CAC and payback per active channel
- A 1:1 with each key stakeholder (management, Head of Marketing, sales leadership, product, customer success) to clarify expectations and friction points
- Identification of the two or three funnel bottlenecks with the highest leverage, documented with a data argument and first hypotheses
- Qualitative interviews with 5 to 10 activated users and 5 to 10 non-activated trial users to validate the bottleneck hypotheses
By day 60
- A prioritized experiment backlog for the quarter with an ICE score, shared with management and product
- First funnel experiment on the top bottleneck started, with a documented hypothesis, sample calculation and stop criterion
- A shared growth dashboard established with sales and product: funnel conversions, channel CAC, activation cohorts, retention curves
- A steering cadence set: weekly 30 min with product, monthly 60-min growth review with management
By day 90
- First significant improvement on the top bottleneck demonstrated (e.g. plus 2 to 4 percentage points of funnel conversion on the target stage) or a clearly documented learning on failure
- A growth plan for the next quarter written: quantified funnel goals, an experiment backlog, budget per channel, dependencies on product and sales
- Two to three acquisition channels actively piloted or scaled, each with a clear CAC and LTV comparison
- An established experimentation cadence: at least 2 completed funnel experiments per month with a documented post-mortem