You can get ready for a product manager interview in 30 days if you practice out loud every day and test yourself weekly. The plan below spends 22 days on skills (product design, metrics, strategy, behavioral, estimation, AI) and 8 days on mock interviews and review, with a full mock at the end of every week. AllthingsPM gives you what each day needs in one place: 4,122 real questions from 260 companies, each with an answer guide, and a scored AI mock interview that asks follow-ups, free once a day.
AllthingsPM is an AI PM course and PM interview prep platform. Below is the full schedule first, then how to run each week, with worked examples from our question bank.
What does a 30-day PM interview study plan look like?
Plan on about two hours a day. Aced's own study plan says most candidates need "four to eight weeks of consistent practice, at a couple of hours a day plus more on weekends" [1], so 30 days is the fast end. It works if you already have some product experience and you skip passive reading in favour of answering questions out loud.
| Day | Focus | What you do | Where on AllthingsPM |
|---|---|---|---|
| 1 | Diagnostic | One full mock, no prep. Save the scorecard. | Mock interview |
| 2 | Target | Read your target JD and company hub, shortlist 20 questions | Company hubs, Jobs |
| 3 | Behavioral | Write 6 to 8 stories: decision, stakes, number | Behavioral guide |
| 4 | Behavioral | Map each story to 3 prompts, say two out loud | Question bank |
| 5 | Product design | Learn one framework end to end | Design guide |
| 6 | Product design | Answer 2 design questions out loud, timed | Question bank |
| 7 | Product design | Design mock, read feedback | Mock interview |
| 8 | Metrics | North star, inputs and counter metrics | Metrics tree template |
| 9 | Metrics | Root cause: "metric X dropped 10%" | Metrics questions |
| 10 | Metrics | Experiments and trade-offs | Question bank |
| 11 | Metrics | Metrics mock | Mock interview |
| 12 | Estimation | Learn the tree method, do 3 sizing questions | Guesstimate answers |
| 13 | Estimation | Estimation mock | Mock interview |
| 14 | Review | Full mock, compare with Day 1 | Mock interview |
| 15 | Strategy | Market entry and "should we build this?" | Question bank |
| 16 | Strategy | Competition and monetization | Question bank |
| 17 | Strategy | Strategy mock | Mock interview |
| 18 | AI and technical | How AI products are specced and measured | AI PM course |
| 19 | AI and technical | AI question mock | Mock interview |
| 20 | Product design | Second pass on your weakest design habit | Question bank |
| 21 | Review | Full mock loop | Mock interview |
| 22 | Behavioral | Company values (for example Amazon's principles) | Company hubs |
| 23 | Product design | Target company's design questions | Company hubs |
| 24 | Metrics | Target company's metrics questions | Company hubs |
| 25 | Strategy | Target company's strategy questions | Company hubs |
| 26 | Behavioral | "Tell me about yourself" and "why us" | Resume review against a JD |
| 27 | Review | Mock built from your real JD | JD mock |
| 28 | Review | Fix the two lowest scores from Day 27 | Question bank |
| 29 | Review | Final full mock | JD mock |
| 30 | Rest | Light review of stories and one framework, sleep | None |
The shape follows the loops you will face. Meta's loop covers product sense, analytical thinking, and leadership and drive [5]. Google's covers product design, strategy, analytical, technical and leadership rounds [6]. Every week of this plan touches at least three of those.
The plan deliberately overweights behavioral and metrics compared with the bank. Both appear in almost every loop, and both are where prepared candidates pull ahead fastest, because stories and metric trees are reusable across companies.
How AllthingsPM does this. Every row in the table maps to a page you can open today. The question bank filters by type and company, and any question starts a mock interview with one click, so you never spend a study day hunting for material.
Why does the plan start with a mock instead of reading?
Day 1 is a cold mock because you need a baseline. A scorecard from Day 1 tells you which of the six question types to protect time for, and it gives you something to beat on Day 14.
In Roediger and Karpicke's 2006 experiments, students who took recall tests retained more a week later than students who restudied the same material, even though the restudy group felt more confident [4].
Day 2 is about your target. Read the job description line by line and open the company's hub. If you are interviewing at an AI company, the jobs catalog has live PM job descriptions you can read side by side with your own.
How AllthingsPM does this. Run your Day 1 mock on AllthingsPM's mock interview in voice if your interview is on video. The feedback scores structure and depth, and the transcript shows where you rambled. On Day 2, paste your JD into the JD mock once just to see which questions it generates; that list becomes your shortlist.
What should you do in week 1 (days 1 to 7)?
Week 1 builds the two things you will reuse all month: a story bank and a product design framework.
Days 3 and 4: stories. Write six to eight stories from your work. Each needs a decision you made, what was at stake, and a number that shows the result. Then map each story to several prompts. Common ones in our bank include Tell me about a time when you used data to influence or persuade people, tagged to 8 companies, and Tell me about a time you had conflict with a team member or a manager. One strong story can answer three or four prompts.
Days 5 to 7: product design. Product design is 36% of the AllthingsPM bank, the biggest single type. Learn one structure (clarify the goal, pick one user, pick one pain point, propose a focused solution, name a metric) and use it until it is automatic. The CIRCLES method is a good starting point if you have none.
A worked example: Design a library for the future, tagged to 8 companies in our bank. A strong answer does not list ten features. It picks one user, say a parent with a young child who visits on weekends, names one pain point (finding age-appropriate books fast), proposes one solution, and closes with a success metric such as repeat weekend visits.
How AllthingsPM does this. Each question page in the question bank has an answer guide that shows this structure applied to that question. Read one guide, close it, then answer a different question in a mock interview where the AI interviewer asks the follow-ups a real one would.
What should you do in week 2 (days 8 to 14)?
Week 2 is analytics: metrics, root cause, experiments and estimation. Metrics is 18% of our bank overall and 26% of Meta's questions, and Google carries the highest estimation share of the big five at 17%.
Days 8 to 11: metrics. Build a metrics tree: one north star, the input metrics that drive it, and one counter metric that keeps it honest. Then practice the classic diagnosis question: "metric X dropped 10% last week, what happened?" Separate internal causes (a release, a tracking bug) from external ones (seasonality, a competitor) before you guess. Our metrics tree template and counter metrics guide cover both.
A worked example from an AI company: What metrics would tell you whether Perplexity is winning against Google Search?. Start with the user outcome (did people get an answer they trusted?), pick a north star, and add a counter metric, because a rising query count can also mean users had to ask twice.
Days 12 and 13: estimation. Learn to build a tree from a population down to the number asked, state each assumption, and sanity-check the result. Three questions on Day 12, one mock on Day 13, is enough for most loops. Our guesstimate questions with worked answers walk through the method.
Day 14: review. Run a full mock and put its scorecard next to Day 1. Pick the two lowest-scoring habits and write them on a card you read before every practice session.
How AllthingsPM does this. Filter the question bank to metrics or estimation and to your target company. Every metrics question can start a scored mock interview, and the interviewer follows up on your counter metric, which is where most candidates slip.
What should you do in week 3 (days 15 to 21)?
Week 3 covers strategy and AI. Strategy is 23% of our bank and leads the question mix at most AI labs: 35% of Anthropic's questions and 29% of OpenAI's.
Days 15 to 17: strategy. Practice three shapes: market entry, competition and monetization. For each, name the goal, the options, your pick and the risk you are accepting. A worked example: How would you monetize ChatGPT?. Segment users first (consumers, professionals, developers, enterprises), then match a model to each, and end on the metric that would tell you it is working.
Days 18 and 19: AI and technical. Even non-AI roles now ask how you would launch or measure an AI feature. A useful question is How would you design an experiment to evaluate a generative AI feature when outputs are non-deterministic?. You need to talk about evals, guardrails and success metrics in plain language.
Days 20 and 21. Revisit your weakest design habit from Day 14, then run a full mock loop on Day 21.
How AllthingsPM does this. The AI PM course chapter The AI PRD covers naming risks, guardrails and success metrics before you build, which is exactly what AI interview questions probe. Read one lesson on Day 18, then answer an AI question in a mock interview on Day 19.
What should you do in week 4 (days 22 to 30)?
Week 4 is your target company. Averages stop helping here, because loops differ sharply. In the AllthingsPM bank, Amazon is 35% behavioral, Microsoft is 59% product design, Meta is 26% metrics, and Anthropic and OpenAI lead with strategy.
Day 22: values. If you are interviewing at Amazon, learn its 16 Leadership Principles, which Amazon publishes on its jobs site [3], and tag each of your stories to two or three of them. Other companies publish values too; read them and do the same.
Days 23 to 25: the target's questions. Open your company's hub, for example Google, Meta, Amazon or Anthropic, and answer its most common questions of each type out loud.
Day 26: your pitch. Rehearse "tell me about yourself" and "why this company" against your resume. Interviewers pull on anything your resume claims, so make sure every bullet has a story behind it.
Days 27 to 29: the real rehearsal. Run a mock built from the actual job description on Day 27, fix the two weakest answers on Day 28, and run a final full mock on Day 29.
Day 30: rest. Read your story cards and one framework, then stop. Sleep is worth more than a last mock.
How AllthingsPM does this. The JD mock builds an interview from the exact job description you paste, so Days 27 and 29 rehearse your real loop, not a generic one. On Day 26, run resume review against a JD to see which claims an interviewer is likely to probe.
How do you adjust the plan if you have less or more time?
Two weeks. Aced suggests a compressed plan that puts product sense, analytics and behavioral first, then strategy and technical, ending with mocks [1]. In this plan's terms, keep Days 1 to 7, Days 8 to 11, and Days 27 to 29, and drop estimation unless your target is Google.
Six to eight weeks. Double the skill days and add a second mock each week. Aced's eight-week version gives product sense two weeks, analytical and execution two weeks, then a week each for strategy, behavioral, technical and AI, and mocks [1].
Twelve weeks. Lewis Lin's widely shared 12-week plan, written by an experienced PM targeting Google and Facebook, adds weeks of technical and system design study before product work [2].
How AllthingsPM does this. Whatever length you pick, the free tier gives you one JD mock a day, and Pro ($20 a month or $120 a year) removes the limit, so the plan scales without new tools. See pricing for the current plans.
What mistakes break a 30-day plan?
- Reading instead of speaking. Rereading feels like progress; answering out loud is what changes your performance [4].
- Skipping the weekly mock. Without Days 7, 14, 21 and 29 you have no signal on whether you improved.
- Preparing for the average company. A Microsoft loop and an Amazon loop need different weeks 4.
- No numbers in stories. A behavioral story without a result number is easy for an interviewer to discount.
Why AllthingsPM is the better choice for a 30-day PM interview plan
A 30-day plan needs three things every day: a real question, a model of a good answer, and a way to test yourself out loud. AllthingsPM puts all three in one account. The question bank holds 4,122 real questions from 260 companies, each with its own answer guide. The mock interview asks any of them back to you in text or voice, follows up, and scores you. The JD mock turns your actual job description into an interview for the final week, and the AI PM course, built from 604 real PM job postings, covers the AI questions that now show up in most loops.
Other options have real strengths. Aced (formerly Exponent) publishes solid study plans and has a large peer community [1], and paid coaches give human calibration before a big loop. Those are useful additions. For the daily work a 30-day plan runs on, AllthingsPM is the most complete single tool we found: questions, answer guides, company hubs, JD-based mocks, resume review and a course, with a free daily mock and unlimited practice at $20 a month.
Start with the Day 1 diagnostic: run a free mock interview and keep the scorecard.
Frequently asked questions
Is 30 days enough to prepare for a PM interview?
Yes, for most candidates with some product experience, if you study about two hours a day and practice out loud. Aced says most candidates take four to eight weeks at that pace [1], so 30 days is the fast end and leaves no room for passive reading.
What is the best way to prepare for a PM interview?
The best way is AllthingsPM: practice real questions from your target company with answer guides, then run scored mock interviews, including one built from your actual job description. Add a human mock or a coach late in the process for calibration.
How many hours a day should I study for a PM interview?
About two hours on weekdays and more on weekends, which matches Aced's guidance [1]. One focused hour of answering out loud beats three hours of reading.
How many mock interviews should I do in 30 days?
This plan has eight mock and review days, including full mocks on Days 1, 14, 21, 27 and 29. More helps if each mock is followed by fixing a specific weakness.
Which question types should I prioritize?
Match your target company. In the AllthingsPM bank, product design is 36% of all questions, but Amazon is 35% behavioral and Meta is 26% metrics. Open your company hub to see its mix.
Do I need to prepare for AI questions if the role is not an AI PM role?
It is worth two days. AI features are showing up in most products, and questions about evaluating non-deterministic outputs appear across several companies in our bank.
Start your 30-day plan today
Day 1 takes one hour: a cold mock and a saved scorecard. Start a free mock interview on AllthingsPM, then open the question bank for Day 2.
Sources
- Aced (formerly Exponent), "Product Manager Interview Prep (2026 Study Plan)": https://www.tryexponent.com/blog/the-ultimate-pm-interview-study-plan
- Lewis C. Lin, "12 Week PM Interview Prep Plan (Featured on Blind)": https://www.lewis-lin.com/posts/12-week-pm-interview-prep-plan/
- Amazon, "Leadership Principles": https://www.amazon.jobs/content/en/our-workplace/leadership-principles
- Roediger, H. L. and Karpicke, J. D. (2006), "Test-Enhanced Learning: Taking Memory Tests Improves Long-Term Retention", Psychological Science: https://journals.sagepub.com/doi/10.1111/j.1467-9280.2006.01693.x
- IGotAnOffer, "Meta Product Manager Interview (questions, process, prep)": https://igotanoffer.com/blogs/product-manager/facebook-product-manager-interview
- Aced (formerly Exponent), "Google Product Manager (PM) Interview Guide": https://www.tryexponent.com/guides/google-product-manager-interview
- AllthingsPM question bank, 4,122 questions across 260 companies, September 2026: https://allthingspm.app/question-bank
