📣 You're prepping for the wrong case study

👋 Hey Friends!

So there I was, on a video call, being handed a product scenario I had never seen, with three people watching my face while I read it.

No prep. No take-home doc. No overnight to make it pretty.

Just me, a blank Google Doc, and the specific dread of realizing the thing they wanted to watch was not my answer.

It was me.

Thinking.

Live.

In front of them.

😱

That is when it clicked. I had been calling two completely different interviews by the same name. And so has almost everyone I mentor.

The scenario: a gaming payments startup building the kind of checkout that keeps players from ever leaving the game. I was dropped into an integration for a new partner. Six weeks to build. Eight to launch. A two-week buffer as the emergency hatch. My team on one side, the partner's engineers on the other.

Then, halfway through, they moved the ground. Two higher-priority partners, both near go-live dates, both frustrated, and only two engineers to cover all three. July holidays eating into capacity.

Then, just as code freeze was about to start, forty bugs.

There was no right answer. They knew that. I knew that.

They weren't checking whether I landed on the "right" fix. They were watching how I moved when the floor shifted. Whether I froze or narrated my way through it. Whether I could tell a glass ball from a rubber one with three people staring.

One asks whether you can reason out loud while uncomfortable and half-sure. The other asks whether you actually believe what you built — enough to defend it when someone smart tries to take it apart.

Now compare that live case to a take-home I did for another company a few months later. They handed me a test portal and 48 hours. Go find the gaps in the onboarding flow.

No one watching. No ground moving. Just me, the product, and two days to build something I could stand behind in a room the following week.

Completely different job. Completely different prep.

And most people , including people I mentor, mix them up constantly.

Here is how you prep each one, because they are not interchangeable.

1. Live case: Prep your process, not your answers.

You can't memorize your way through this. You can only have a spine to fall back on when your brain goes blank.

Mine: clarify first. Context, user, problems, solutions, measure. Every time, in that order. I say it out loud at the start — "Before I solve this, who am I actually solving for?" — and it buys me three seconds of composure and signals to the panel that I don't just react, I orient.

Then I narrate my tradeoffs as I make them. Not because I'm performing, but because narrating slows down the panic and makes your thinking legible. Being wrong out loud and catching it reads better than a polished answer with no visible thinking. They're not buying your conclusion. They're buying the person who arrived at it.

The thing most candidates get wrong in a live case: they go quiet when they're unsure. Silence feels safe. It isn't. Silence reads as stuck. Narrating uncertainty — "I'm weighing X against Y, and here's why I'm leaning toward X right now, though I might update that" — reads as confidence.

2. Take-home: The artifact is bait. The defense is the test.

This one tricks even experienced PMs.

You get 48 hours and immediately think: I need to make something beautiful. You spend 30 hours on the deck, 10 hours tweaking the visuals, 8 hours second-guessing your findings.

That's the trap.

The presentation doesn't get you the job. Surviving the questions about it does.

Here's what I do now: Build the visual fast. Lovable or Codex will get you a clickable walkthrough in an afternoon, and a working prototype lands harder than 40 polished slides, every time. Then spend your real time on the three questions they'll use to attack your findings:

Write them down. Answer them before they can ask. Walk into that defense room knowing exactly where your blind spots are and how you'd talk around them. That's what conviction looks like.

3. Find out which one it is. Before you prep a single thing.

This is the step almost nobody takes, and it costs people the role.

Prepping conviction for a live case makes you rigid, you walk in with an answer when they want to watch you find one. Prepping improv for a take-home makes you look like you didn't care enough to do the work.

So before you open a single Notion doc or practice framework, send one message to the recruiter:

"Quick question, is the case live in the room, or do I build something and present it?"

That's it. One sentence. You'll get the answer in under an hour in most cases, and it completely changes how you spend the next week.

TThey already know the scenario is fake. The six weeks, the partner, the code freeze — all made up. None of that is the point.

The point is a quieter question running underneath the whole thing: When this gets hard, and it will, do I want this person in the room with me?

That's the whole job. The interview is just the first time they get to watch you do it.

P.S. If the case study round is the wall costing you the offer, that's exactly what I work through in my free 1:1 sessions. Bring me the scenario that scared you. We'll prep together.

P.P.S. If you're still working toward landing a remote role in the first place, Remote Rebellion is the community, newsletter, and course I'd point you to. Built specifically to help people land remote jobs. Worth bookmarking.