How to Present a Case Study During a Marketing Interview

You get 45 minutes with a hiring manager, and someone on the panel slides a printout across the table: "Walk us through a campaign you're proud of." Most candidates start at the beginning of the project. They narrate the timeline. They list the deliverables. And by minute twelve, the interviewer is nodding politely while secretly wondering what you actually decided.

Presenting a case study during a marketing interview is not storytelling. It is decision archaeology. The interviewer doesn't care what your campaign looked like on a slide deck. They care how your brain moved from a messy problem to a defensible choice. If you can show that mechanism clearly, you're hired. If you recite a project plan, you're not.

I've sat on both sides of that table, and I've watched plenty of strong marketers lose offers to weaker candidates who simply told their story better. Here's how to be the second person.

Why the case study decides the interview more than your CV

Resumes are compression. Everyone's CV says "led a team of six" and "grew pipeline." The case study is the only moment in the process where the interviewer sees the raw material of how you think, and it's the part candidates under-prepare most.

When I interviewed for a senior growth role a couple of years ago, I spent three evenings polishing my slides. I spent zero evenings rehearsing what I'd actually say. The presentation landed flat because I read the deck instead of thinking out loud. I didn't get the job. A colleague who applied for a similar role two months later spent her prep time the opposite way—no slides, just a whiteboard and a story she could tell in her sleep. She got an offer.

What interviewers are actually listening for

Three signals, and almost nothing else:

• Judgment under constraint. Did you make a choice, or did you just execute a brief someone handed you?
• Ownership of the outcome. Can you distinguish what you did from what your team did? Vague "we" language reads as borrowed credit.
• Reflection. Would you do it differently? Candidates who can't name a single mistake sound like they're reciting a highlight reel.

The rest—the charts, the pretty fonts, the animated timeline—is decoration. Useful, not decisive.

How to present a case study during an interview

Open at the point of tension. Not "Our campaign ran from March to September," but "We had a conversion rate stuck at 1.8% and a board that wanted it doubled in one quarter." That single sentence does three things at once: it sets stakes, signals scarcity, and invites the interviewer to lean in.

The opening 90 seconds

Give the setting in three beats:

1. The business situation, in one sentence. "A B2B SaaS company selling to mid-market operations teams."
2. The problem, with a number attached. "Trial-to-paid conversion sat at 1.8% while the benchmark for our segment hovered near 3%."
3. Your mandate. "I was brought in to rebuild the trial experience inside one quarter, with no engineering headcount."

Ninety seconds. That's the whole introduction. Do not explain your org chart. Do not describe your team's history. The interviewer needs the terrain, not the weather report.

The body: hypothesis first, then evidence

Here's where most presentations go wrong. They walk through every tactic in chronological order. Better approach: state the hypothesis you formed, then show how you tested it.

In the SaaS example above, the hypothesis was that trial users never reached the "aha" moment before the sales rep called, so outreach felt premature. The intervention wasn't a new email sequence—it was a reordered onboarding flow that pushed users to a specific dashboard action within ten minutes of signup. Conversion climbed from 1.8% to 2.9% over eleven weeks.

Notice what that story contains: a diagnosis, a bet, a mechanism, and a result. Four elements, no filler. If your presentation has the mechanism missing—the "why this should have worked"—the interviewer will suspect you got lucky.

The close and the recommendation

End on what you'd advise going forward, not what happened next. "If I were running this again, I'd invest in the same onboarding reorder but build the telemetry first—we spent two weeks guessing before we had data." That sentence tells the interviewer you're still thinking about it, which is the entire point.

How to prepare a case study for an interview

Preparation starts with a filter question: which of your projects actually demonstrates judgment? Not the biggest one. Not the most recent one. The one where your decision changed the outcome in a way you can defend.

Pick the right project, then cut it in half

I keep two or three case studies in a mental drawer, each tuned to a different kind of role: growth, brand, product marketing. When a company asks, I pick the one closest to their actual problem, not the most impressive one. A campaign with a $400K budget and modest results is a worse fit for a scrappy startup than a scrappy experiment that tripled signups on a shoestring.

Then cut. Whatever length you think the story needs, halve it. The strongest presentations I've seen run eight minutes, not twenty. Interviewers allocate more time to probing your reasoning than to listening to your narrative, and you want the balance to favor questions.

Build a backup deck, but rehearse without it

Bring slides if the format calls for them. Prepare them so you can present if the tech fails, but rehearse the talk track as though the slides don't exist. If someone unplugged the projector mid-presentation, you should still be able to finish the story at the whiteboard.

Anticipate the probing questions

The interviewer will ask at least one of these. Have answers ready:

• "How do you know your change caused the lift and not seasonality?"
• "What did you try that didn't work?"
• "Who disagreed with you, and how did you handle it?"
• "What would you do with twice the budget?"
• "Where's the weak point in your evidence?"

The last question is the tell. Candidates who can name the weakness of their own case study without flinching are the ones who get offers. Everyone else gets a polite thank-you email.

How to do a case study in marketing

Two different exercises hide behind the same phrase, and conflating them is a common mistake. One is presenting a past project you already ran. The other is solving a case the interviewer hands you cold—a hypothetical market entry, a pricing problem, a competitive threat. They demand different muscles.

The two formats compared

Format	What it tests	Time budget	Biggest risk
Presenting your own case study	Judgment, ownership, reflection	8–12 min presentation, 10+ min Q&A	Narrating instead of deciding
Solving a case live	Structured thinking, prioritization, comfort with ambiguity	30–45 min dialogue	Jumping to tactics before framing the problem

For the live case, the work is in the framing. Before you suggest a single tactic, state the problem in your own words, name your assumption, and ask whether the interviewer agrees. That small move—checking the frame before solving—is what senior marketers do naturally and junior ones skip.

The framework I use for either format

I don't use a named consulting framework. I use a stripped version that fits on the back of a napkin:

1. What business outcome is at stake?
2. What's the constraint (budget, time, team, data)?
3. What did we believe, and why?
4. What did we do, and what moved?
5. What's the honest caveat?

Five lines. If you can't fill them, you don't understand the case yet. If you can fill them, you can present the case in any format, on any medium, to any panel.

How do you present a case study in a presentation?

Presentations live or die on structure and pacing. Aim for one idea per slide and roughly one to two minutes per slide. A ten-minute talk shouldn't have more than eight slides, and the first slide should already contain tension—not a title card with your name and the company logo.

The slide order that works

1. Situation and constraint (one number, one sentence)
2. The fork in the road (the decision you faced)
3. Your hypothesis
4. What you did, briefly
5. What moved (quantified)
6. What didn't move, and why
7. What you'd do next

Seven slides. Notice the order is deliberately non-chronological. The result comes before the failure, because you want the interviewer to be evaluating your judgment by the time they hear the caveat. Chronology is for documentaries. Interviews reward argument.

Presence matters as much as content

Slow down on the numbers. Pause after you say "conversion went from 1.8% to 2.9%" so it lands. Candidates speed through the result because they're nervous, and the interviewer misses the only quantitative moment in the whole talk. Also, keep your hands visible, avoid reading from the slide, and look at the person who asked the toughest question—not the friendliest face in the room.

One thing I learned the hard way

I once spent ten minutes on a beautiful slide explaining the market context, and the interviewer interrupted at minute eleven to ask "so what did you actually do?" That was the whole feedback loop. Since then, I never spend more than one slide on context, regardless of how fascinating I find the market. The interviewer is evaluating you, not the industry.

The honest verdict

The case study doesn't win the offer on the strength of results. It wins on the clarity of your reasoning and your willingness to name your own weaknesses. Strong candidates with modest numbers beat weak candidates with spectacular ones, because the interviewer is trying to predict what you'll do in their messy situation—not how pretty your last campaign looked.

So before your next interview, take your best project, strip out everything except the decisions, and practice telling it in eight minutes without slides. If the story holds, you're ready. If it collapses, you've just learned where your understanding is thin—which is worth more than any polished deck.