How to use this kit

#What's in the kit

PMInterviewKit is a text-first course organized around the round types you met in the round types and how they differ. It has eleven modules:

Alongside the lessons sits the question bank, which you can filter by type: Product sense, Metrics, Estimation, Strategy, Behavioral, Technical and AI.

#One method per module

Each module teaches one method for its round and uses it the same way in every worked answer. This is deliberate. In an interview you won't have time to choose between three frameworks. You need one approach you've used so often that it runs on its own, leaving your attention free for the actual problem.

So when you start a module, learn its method in the first lesson, then watch it applied again and again in the worked answers. By the end, the steps should feel boring. Boring is good. Boring means automatic.

You'll notice the methods don't carry famous acronyms. Interviewers hear the popular ones constantly, and an answer that recites one tends to sound memorized. The kit's methods are plain-language steps you can adapt to any prompt.

#The four kinds of lesson

• Method lessons explain one step and show it on an example. Read these carefully once.
• Worked answers and cases show a full answer, start to finish, with the candidate's clarifying questions, assumptions, structure and summary, plus notes on what a weaker answer would have done.
• Common traps lessons list the mistakes that sink candidates in that round and how to recover mid-interview.
• Practice lessons in module 9 turn reading into skill: rubric, scripts, drills and a mock plan.

#How to read a worked answer

Worked answers are the most valuable part of the kit, and the easiest to waste.

If you read a strong answer straight through, it will feel obvious. You'll nod along and think "yes, I'd have done that." You probably wouldn't have, and you won't find out until an interviewer is watching. This is the illusion of competence, and it's the main way people over-prepare on paper and under-prepare in practice.

Read worked answers like this instead:

1. Read only the prompt. Stop there.
2. Attempt it yourself, out loud, for five to ten minutes. Even a rough attempt counts. At minimum, say your clarifying questions, the user or structure you'd choose and your main recommendation.
3. Now read the worked answer. Compare it step by step with what you said.
4. Write down one difference that matters: a step you skipped, a choice you didn't defend, a trade-off you missed.
5. Use that difference deliberately in your next practice question.

Key idea Always attempt before you read. Five minutes of struggling with a prompt makes the worked answer far more useful.

#The practice loop

Every module feeds the same loop:

1. Learn the method from the module's lessons.
2. Attempt a question from the question bank, timed and out loud, ideally recorded.
3. Grade your recording with the self-grading rubric, quoting what you actually said as evidence for each score.
4. Drill your lowest dimension using drills by weakness.
5. Repeat with a new question, and every week or so, with a partner using the mock interview scripts.

The loop matters more than the order you read modules in. Someone who reads half the kit and practices thirty questions will usually interview better than someone who reads every word and practices five.

#Where to start, by situation

• Interview within a week: follow the 7-day plan in study plans exactly.
• A month or more: follow the 30-day plan.
• No date yet: start with modules 1, 2 and 4 in that order, practicing as you go, then fill in the rest. They cover the rounds that appear in most PM loops.
• Applying to an associate PM program: add associate PM programs early, since those processes often differ from experienced-hire loops.
• Targeting an AI-heavy role: read what AI product rounds test in week one, so you know what to listen for as you work through the other modules.
• Just got a recruiter email: read the recruiter screen today.

#What this kit is not

A few honest limits:

• It isn't insider information. Company processes change, and the kit doesn't claim to know any company's private rubric. Where module 8 describes specific companies, it relies on what they publish or describes patterns generally. Always check the company's own careers pages and what your recruiter tells you.
• It isn't a script to memorize. Interviewers spot memorized answers quickly. The worked answers show reasoning to learn from, not lines to repeat.
• It isn't a guarantee. Interviews involve judgment calls and some luck. What the kit can do is make sure your preparation is focused, your method is solid and your practice measures the right things.

Try it Before moving on, decide which plan you're following and write today's date and your interview date (or "none yet") at the top of a new practice log. Add one line: the round type you feel least ready for. That's where you'll look first when you grade.

#Recap

• The kit has eleven modules, one per round type plus foundations, company playbooks, practice and offers, and a question bank filterable by type.
• Each module teaches one method and uses it in every worked answer, so it becomes automatic.
• Always attempt a prompt before reading its worked answer, then write down one difference that matters.
• Run the loop: learn, attempt, grade with the rubric, drill your weakest dimension, repeat.
• The kit isn't insider information or a script; check company sources and practice out loud.