McKinsey’s Problem Solving Test eliminates roughly 65–70% of candidates before case interviews even begin. The pass rate hovers around 30–35%, with a threshold of approximately 70% correct answers (18 out of 26 questions). Yet in our experience working with hundreds of candidates, most who fail the PST do not lack intelligence — they lack a structured preparation plan.
This guide provides a complete 4-week preparation framework that builds the three core skills the PST tests: data interpretation, mental math, and logical reasoning. Whether your office administers the written PST or the gamified Solve assessment, this plan equips you with the analytical foundations that both formats demand.
Understanding the PST Format
The McKinsey Problem Solving Test is a 60-minute paper-based assessment with 26 multiple-choice questions. Unlike academic exams that test memorized knowledge, the PST measures your ability to process business information under time pressure — the same cognitive skills that define effective consulting.
Test Structure and Timing
Each PST consists of three business scenarios (sometimes called “cases” or “passages”), each followed by 8–10 questions. The scenarios present a company situation with supporting data exhibits — charts, tables, financial statements, or market data. Questions require you to extract information, perform calculations, or draw logical conclusions from the presented data.
| Component | Detail |
|---|---|
| Duration | 60 minutes total |
| Questions | 26 multiple-choice (4 options each) |
| Scenarios | 3 business cases with data exhibits |
| Calculator | Not permitted |
| Scoring | Correct answers only — no penalty for guessing |
| Threshold | ~70% (approximately 18/26 correct) |
| Format | Paper-based, pencil and paper only |
The time pressure is severe: 138 seconds per question on average. In practice, some questions require only 45 seconds (straightforward data lookup) while others demand 3+ minutes (multi-step calculations or complex logical deductions). Effective time management is not optional — it is a core competency being tested.
The Six Question Types
The PST tests three skills through six question formats. Understanding the distribution helps you allocate preparation time efficiently:
pie title PST Question Type Distribution
"Reading Facts" : 38
"Reading Implications" : 15
"Fact-Based Conclusions" : 18
"Formulae" : 12
"Best Conclusion" : 10
"Brain Teasers" : 7
| Question Type | Skill Tested | Difficulty | Time Target | Strategy |
|---|---|---|---|---|
| Reading Facts | Data interpretation | Low–Medium | 60–90 sec | Scan exhibit first, locate data point, verify units |
| Reading Implications | Data interpretation + Logic | Medium | 90–120 sec | Identify what the data implies vs. what it states |
| Fact-Based Conclusions | Logical reasoning | High | 120–180 sec | Eliminate options that require assumptions beyond the data |
| Formulae | Mental math | Medium | 90–150 sec | Simplify first, estimate, then calculate precisely |
| Best Conclusion | Logic + Judgment | High | 120–180 sec | Distinguish “most supported” from “possibly true” |
| Brain Teasers | Logic + Creativity | Variable | 60–180 sec | Recognize the pattern type, apply systematic elimination |
Reading Facts questions account for approximately 38% of the PST, making them your highest-return investment. A candidate who masters this single type and struggles with everything else can still pass if their accuracy on Reading Facts approaches 100%.
Start with a Diagnostic
Before designing your study plan, take one full-length practice test under timed conditions (60 minutes, 26 questions, no calculator). Score it and categorize every mistake into one of four buckets:
| Error Type | What It Reveals | Example | Typical Fix |
|---|---|---|---|
| Comprehension | Misread the question or data exhibit | Confused revenue with profit in a chart | Slow down on question parsing; underline key terms |
| Calculation | Math error or lost zeroes | Computed 15% of 4,200 correctly as 630 but wrote 6,300 | Develop zero-tracking notation; estimate first |
| Logic | Drew an unsupported conclusion from data | Treated a plausible inference as proven fact | Practice distinguishing “proven” from “possible” |
| Time | Ran out of time or rushed correct approach | Knew the method but could not finish in 2 minutes | Build speed through daily drills; skip-and-return strategy |
Based on our analysis of over 800 candidate error patterns, time management and logic errors account for approximately 60% of all PST failures. Comprehension and calculation errors make up the remaining 40%. Your diagnostic tells you where to concentrate effort.
Diagnostic Scoring Benchmarks
Your diagnostic score predicts how much preparation you need:
| Diagnostic Score | Readiness Level | Recommended Timeline |
|---|---|---|
| 75%+ (20+ correct) | Near-ready | 2 weeks of targeted practice |
| 60–74% (16–19 correct) | Foundation exists | Full 4-week plan |
| 45–59% (12–15 correct) | Significant gaps | 5–6 weeks; extend skill-building phase |
| Below 45% (< 12 correct) | Fundamental rebuild | 8 weeks; consider additional resources |
Do not be discouraged by a low diagnostic score. The PST tests trainable skills — unlike IQ tests that measure fixed cognitive capacity, PST performance responds dramatically to deliberate practice. In our experience, candidates who follow a structured plan typically improve by 15–25 percentage points within four weeks.
The 4-Week PST Preparation Roadmap
This plan assumes 60–90 minutes of daily practice. Adjust the timeline if you have more or less time available, but preserve the sequence — each phase builds on the previous one.
flowchart LR
A["Week 1\nFoundation\n& Format"] --> B["Week 2\nTargeted\nSkill Building"]
B --> C["Week 3\nIntegration\n& Speed"]
C --> D["Week 4\nSimulation\n& Polish"]
style A fill:#e8f4fd,stroke:#2196F3
style B fill:#e8f4fd,stroke:#2196F3
style C fill:#fff3e0,stroke:#FF9800
style D fill:#e8f5e9,stroke:#4CAF50
Week 1: Foundation and Format Mastery
Objective: Understand the test structure, identify your weaknesses, and build baseline familiarity with all six question types.
Daily schedule (75 minutes):
- 15 min: Mental math warm-up (percentages, divisions, growth rates)
- 30 min: Practice 15 questions from one specific question type
- 20 min: Review every mistake using the 4-bucket error framework
- 10 min: Summarize the day’s patterns in a study log
Week 1 milestones:
- Complete diagnostic test (day 1)
- Work through all six question types at least once
- Identify your top 2 weakest question types
- Establish a mental math baseline (can you calculate 17% of 3,400 in under 15 seconds?)
Critical insight: Many candidates skip Week 1 because they feel “ready to practice.” This is a trap. Understanding the format — how exhibits are structured, what language signals a Fact-Based Conclusion vs. a Best Conclusion question, how distractors are designed — gives you a 10–15 second speed advantage on every question. Over 26 questions, that compounds to 4–6 minutes of extra time.
Week 2: Targeted Skill Building
Objective: Develop the specific skills your diagnostic revealed as weak. Build calculation speed to eliminate time pressure as a failure mode.
Daily schedule (90 minutes):
- 15 min: Mental math drills (see mental math guide for structured sequence)
- 40 min: 20 questions weighted 70% toward your weakest types, 30% toward maintenance of strong types
- 25 min: Deep error review — for each mistake, write a one-sentence “rule” that would have prevented it
- 10 min: Speed drill — 5 questions with a 1-minute hard cap each
Week 2 milestones:
- Score 65%+ on timed practice sets in your weak areas
- Complete mental math drills without paper for basic operations
- Accumulate 10+ “rules” from error analysis (these become your pre-test mental checklist)
- Reduce average time per question to under 150 seconds
The rules library: As you review errors, you will notice patterns — recurring traps you fall into. Document these as crisp rules:
| Rule # | Trigger | Rule |
|---|---|---|
| 1 | “Which of the following is true?” | This is a Fact-Based Conclusion — I need PROOF, not plausibility |
| 2 | Multi-year data with “growth rate” | Check if they want CAGR or simple growth — read the question twice |
| 3 | Table with percentages | Verify: percentage of WHAT? Total? Category? Previous year? |
| 4 | “Approximately” in the answer | This signals I should estimate first, not calculate exactly |
| 5 | Large numbers with many zeroes | Write out the number with clear digit grouping before calculating |
By the end of Week 2, you should have 10–15 personalized rules that address your specific error patterns.
Week 3: Integration and Speed
Objective: Combine individual skills into full-test performance. Build the stamina and speed to maintain accuracy across 60 continuous minutes.
Daily schedule (90 minutes):
- 10 min: Mental math warm-up (now emphasizing speed over accuracy growth)
- 50 min: Full 26-question practice set under strict 55-minute time limit
- 30 min: Comprehensive review — score, time analysis, error categorization
Week 3 milestones:
- Complete full tests within 55 minutes (5-minute buffer for review)
- Score 70%+ on at least 2 of 4 practice tests
- No single error type exceeds 40% of your total mistakes
- Implement and refine the two-pass strategy (see below)
The two-pass strategy: In Week 3, introduce the approach that top scorers use on test day:
- First pass (40 minutes): Move through all 26 questions sequentially. Answer everything you can solve within 100 seconds. If a question requires extended calculation or complex reasoning, mark it and move on.
- Second pass (15 minutes): Return to marked questions with the confidence that you have already secured your “easy” points. Invest remaining time on the hardest questions.
- Final sweep (5 minutes): Check that all questions have an answer — never leave blanks, since there is no penalty for guessing.
This strategy prevents the common failure mode of spending 5 minutes on question #4 and then rushing through questions 20–26.
Week 4: Simulation and Polish
Objective: Replicate test-day conditions as closely as possible. Eliminate any remaining inconsistencies in performance. Build confidence through consistent scores above threshold.
Daily schedule (75 minutes):
- Day 1–2: Full simulated test (strict timing, unfamiliar questions, desk environment)
- Day 3: Review both tests comprehensively; update rules library
- Day 4: Targeted drill on any remaining weak spots identified in simulation
- Day 5: Final simulated test + light review
- Day 6–7: Rest and mental preparation (light mental math only)
Week 4 milestones:
- Score 75%+ consistently (at least 3 of 4 simulated tests)
- Complete tests within 55 minutes without feeling rushed
- Experience zero “surprise” question types — every format feels familiar
- Establish a test-day routine (see below)
Simulation realism checklist:
- Unfamiliar question set (not questions you have seen before)
- 60-minute strict timer with no pauses
- No calculator, no phone, no digital devices
- Seated at a desk with only pencil and paper
- Morning session (9 AM) to match typical test timing
- Complete the full 26 questions without breaks
Three Core Skills and How to Build Them
Data Interpretation
Roughly half of all PST questions require extracting or comparing data from exhibits — charts, tables, and text passages. The skill is not reading the data; it is reading it fast and selectively.
The exhibit pre-scan technique: Before reading any question, spend 15 seconds scanning the exhibit:
- What type of visualization is this? (bar chart, line graph, table, text)
- What are the axis labels and units? (millions, thousands, percentages, years)
- What is the scale? (are differences large or small?)
- Are there any footnotes or special conditions?
This 15-second investment saves time on every subsequent question for that exhibit because you already understand the data structure.
Common data interpretation traps:
| Trap | How It Appears | How to Avoid |
|---|---|---|
| Unit mismatch | Revenue in billions, costs in millions | Always check units before comparing numbers |
| Index confusion | “Indexed to 2019 = 100” means 120 is 20% growth, not 120 units | Look for “index” or “base year” language |
| Cumulative vs. incremental | Bar chart shows cumulative total, not yearly additions | Check axis title: “cumulative” vs. “annual” |
| Percentage base confusion | “40% of revenue” vs. “40% of costs” — same number, different meaning | Identify the denominator before calculating |
| Correlation vs. causation | Two trends move together in a chart | Data shows correlation only; causation requires additional evidence |
Training method: Practice reading the question stem first, identifying the exact data point needed, then scanning the exhibit. Time yourself: target under 30 seconds to locate any single data point in a standard exhibit. Work through exhibits from profitability cases and financial analysis cases in our case library to build fluency with common business data formats.
Mental Math
The PST forbids calculators, and approximately 25% of questions require calculations — percentages, growth rates, ratios, or multi-step arithmetic. In our experience, candidates who practice mental math daily for two weeks improve their PST score by an average of 3–4 questions.
The estimation-and-adjustment technique for large numbers:
- Simplify: Remove zeroes (6,700,000 → 6.7)
- Round: Make numbers friendly (6.7 → 7)
- Calculate: Perform the easy computation
- Adjust: Correct for rounding direction and restore zeroes
Essential mental math shortcuts:
| Operation | Shortcut | Example |
|---|---|---|
| Multiply by 15% | Divide by 10, then add half | 15% of 840 = 84 + 42 = 126 |
| Divide by 7 | Divide by 7 ≈ multiply by 0.143 (≈ 1/7) | 490 ÷ 7 = 70 |
| Compound growth | For small rates: multiply rate × years | 3% for 4 years ≈ 12% total (actual: 12.55%) |
| Percentages of percentages | Multiply the percentages | 30% of 40% = 12% |
| Quick division by 8 | Halve three times | 720 ÷ 8 = 360 → 180 → 90 |
| Multiply by 25 | Divide by 4, then multiply by 100 | 48 × 25 = 48/4 × 100 = 1200 |
Daily drill sequence (15 minutes):
- Minutes 1–3: Percentage calculations (random % of random 3-digit numbers)
- Minutes 4–6: Division (2-3 digit numbers divided by single digits)
- Minutes 7–9: Growth rate calculations (Year 1 value → Year 2 value, compute % change)
- Minutes 10–12: Multi-step problems (revenue = price × volume, then compute margin)
- Minutes 13–15: Estimation challenges (approximate answers to complex calculations)
Our mental math guide provides a structured drill sequence with progressive difficulty levels.
Logical Reasoning
Fact-based Conclusion questions are the hardest type on the PST — they require you to distinguish what is proven by data from what is merely plausible. This is the same analytical rigor tested in McKinsey case interviews.
The proof standard framework: For every answer option, ask:
- Can I point to a specific data point that PROVES this? → Potentially correct
- Does this seem reasonable but lacks direct data support? → ELIMINATE — this is a distractor
- Does this require an assumption about something not shown? → ELIMINATE
- Does this contradict any data point? → ELIMINATE
Common logical reasoning traps:
| Trap Type | Example | Why Candidates Fall for It |
|---|---|---|
| Plausible but unproven | “Company A has higher revenue, so it is more profitable” | Sounds logical, but revenue ≠ profit without cost data |
| Necessary vs. sufficient | “Sales increased, so the new campaign worked” | Sales could have increased for other reasons |
| Scope creep | Data shows Q1 results; answer generalizes to “annual trend” | Q1 alone cannot prove annual direction |
| Relative vs. absolute | “Market share increased” but actual revenue decreased | Both can be true simultaneously if market shrinks faster |
Training method: For every practice question, write down the specific data points that support your answer. If you cannot point to concrete evidence in the exhibit, your answer relies on assumption. Practice applying the hypothesis-driven approach to each scenario: form a hypothesis from the question stem, then test it against the data.
Practice Methodology: Quality Over Volume
Completing hundreds of practice questions without reviewing your mistakes is the most common preparation error we observe. Effective PST preparation follows a deliberate practice cycle:
flowchart TD
A[Practice Set\n15-26 questions] --> B[Score & Time\nRecord per-question time]
B --> C[Error Analysis\nCategorize each mistake]
C --> D{Pattern?}
D -->|Same error type recurring| E[Targeted Drill\nFocus on that skill]
D -->|Diverse errors| F[Review Fundamentals\nSlow down and rebuild]
E --> G[Update Rules Library\nAdd prevention rule]
F --> G
G --> A
Track three metrics for every practice session:
- Accuracy — percentage correct (target: 75%+ by week 3)
- Speed — average seconds per question (target: under 130 seconds)
- Error distribution — which of the four error buckets each mistake falls into
When you notice the same error type appearing across multiple sessions, that is your highest-leverage improvement area. Spending 30 focused minutes on your weakest skill type yields more progress than two hours of random practice.
The Progress Tracking Matrix
Maintain a simple spreadsheet or table tracking your performance trajectory:
| Week | Test # | Score | Time Used | Comprehension Errors | Calculation Errors | Logic Errors | Time Errors |
|---|---|---|---|---|---|---|---|
| 1 | Diagnostic | 58% | 60 min | 3 | 2 | 4 | 2 |
| 2 | Practice 1 | 62% | 58 min | 2 | 2 | 3 | 2 |
| 2 | Practice 2 | 65% | 56 min | 1 | 3 | 2 | 2 |
| 3 | Practice 3 | 73% | 54 min | 1 | 1 | 2 | 1 |
| 3 | Practice 4 | 69% | 53 min | 2 | 1 | 2 | 1 |
| 4 | Simulation 1 | 77% | 52 min | 0 | 1 | 2 | 0 |
This trajectory — starting around 58% and reaching 77% by week 4 — is realistic for candidates who follow the full plan with daily consistency. The most dramatic improvement typically occurs between weeks 2 and 3, when targeted skill-building starts integrating into full-test performance.
Diminishing Returns and When to Stop
Practice follows a logarithmic improvement curve. The first 20 hours of structured preparation yields roughly 15 percentage points of improvement. The next 20 hours yields approximately 5–8 points. Beyond 50 hours of total preparation, returns diminish significantly.
If you are scoring 75%+ consistently across multiple simulated tests, additional practice has minimal marginal value. Shift your energy to case interview preparation — the PST is a gate, not the destination. Our McKinsey case interview guide covers the next stage.
PST vs. Solve: Adapting Your Preparation
Some McKinsey offices — particularly in Asia, the Middle East, and parts of Europe — still administer the written PST. Others have transitioned to the gamified Solve assessment, which includes mini-games like Ecosystem Building and Redrock Study.
| Dimension | PST | Solve |
|---|---|---|
| Format | Paper-based, multiple-choice | Digital, gamified mini-games |
| Duration | 60 minutes fixed | 60–70 minutes (varies by game version) |
| What’s scored | Correct answers only | Decision-making process + outcomes |
| Calculator | Not allowed | Not applicable (no direct calculation) |
| Preparation overlap | Data interpretation, logic, mental math | Same core skills + systems thinking |
| Unique preparation | Speed reading, elimination strategy | Ecological reasoning, pattern recognition |
| Retake policy | Typically once per recruitment cycle | Same — one attempt per cycle |
| Result communication | Pass/fail (no score shared) | Pass/fail (no score shared) |
The core analytical skills — data interpretation, structured reasoning, and mental math — transfer directly between both formats. If you are unsure which format your office uses, prepare for the PST first: it builds a stronger quantitative foundation, and every PST skill is tested in Solve as well.
How to Find Out Which Format Your Office Uses
- Check your email invitation — it will mention either “Problem Solving Test” or “Digital Assessment” / “Solve”
- Ask your recruiter directly — they can confirm the format
- Check with recent applicants from the same office
- Note: Some offices switched mid-cycle in recent years, so past information may be outdated
Test-Day Strategy and Execution
The Night Before
- Review your rules library (the personalized error-prevention rules from weeks 2–3)
- Lay out your test-day supplies: multiple sharpened pencils, eraser, watch (no smart watches)
- Set two alarms for the morning
- Sleep 7–8 hours — cognitive processing speed drops measurably with sleep deprivation
- Do NOT take a full practice test the night before — light mental math review at most
Morning of the Test
- Eat a protein-rich breakfast (avoid sugar crashes mid-test)
- Arrive 15 minutes early
- Do 5 minutes of mental math warm-up in the waiting area
- Mentally rehearse your two-pass strategy
During the Test: Minute-by-Minute Strategy
| Time Block | Minutes | Action |
|---|---|---|
| Start | 0:00–1:00 | Scan all three scenarios; note which looks shortest/easiest |
| First pass | 1:00–40:00 | Work through questions sequentially; mark any taking >2 min |
| Check | 40:00–41:00 | Count answered vs. marked; assess remaining time budget |
| Second pass | 41:00–55:00 | Return to marked questions with full attention |
| Final sweep | 55:00–60:00 | Ensure every question has an answer; guess on any blanks |
Answer Elimination Technique
When uncertain, systematic elimination dramatically improves your odds:
- 4 options remaining: 25% chance of guessing correctly
- Eliminate 1: 33% chance
- Eliminate 2: 50% chance
- Eliminate 3: Certain answer
For Fact-Based Conclusion questions, you can almost always eliminate 1–2 options quickly by identifying answers that require information not present in the data. This means even your “guesses” on hard questions should have 33–50% accuracy rather than 25%.
Advanced PST Techniques
The Question-Stem-First Method
For Reading Facts and Formulae questions, reading the question stem BEFORE reading the passage or exhibit saves significant time:
- Read the question stem to understand what you are looking for
- Identify the type of data needed (number, trend, comparison, calculation)
- Scan the exhibit with a targeted search rather than reading everything
- Locate the answer and verify it matches one of the four options
This technique reverses the natural reading order (passage → question) and can save 15–25 seconds per question. Over the full test, this compounds to 4–6 minutes of additional buffer.
Handling Multi-Step Calculations
Some PST questions require 3–4 sequential calculations. These questions test your ability to stay organized under pressure. Use this structured approach:
- Decompose: Break the problem into discrete steps before calculating anything
- Estimate: Approximate the final answer magnitude to guide your expectations
- Calculate step by step: Write each intermediate result clearly (use margins of your test booklet)
- Verify: Check that your final answer is in the right ballpark (matches your estimate)
Example: “What is Company X’s profit margin if revenue is $4.2M, COGS is 60% of revenue, and operating expenses are $840K?”
- Step 1: COGS = 60% × $4.2M = $2.52M
- Step 2: Operating profit = $4.2M – $2.52M – $0.84M = $0.84M
- Step 3: Profit margin = $0.84M / $4.2M = 20%
- Estimate check: Revenue of ~$4M, costs of ~$3.4M → profit ~$0.6–0.8M → margin ~15–20%. Answer checks out.
Dealing with Information Overload
PST exhibits often contain more data than any single question requires. This is deliberate — it tests your ability to filter relevant from irrelevant information. Signs that you are reading too much data:
- You spent more than 30 seconds on an exhibit without identifying what you need
- You feel like you need to “understand everything” before answering
- You are reading footnotes or axis labels that the question does not reference
Discipline yourself: read the question first, identify the single data point or comparison needed, find it, answer, move on.
Five Preparation Mistakes That Derail Candidates
Starting with mock tests instead of skill building — Taking full tests before mastering the fundamentals produces discouraging scores and masks which skills need work. Build skills in weeks 1–2, then integrate with full tests.
Ignoring mental math — Candidates who rely on written long-form calculations consistently run out of time. Ten minutes of daily mental math practice is non-negotiable.
Treating all question types equally — Reading Facts accounts for roughly 38% of the PST. Mastering this single type first guarantees the highest return on preparation time.
Skipping error analysis — Finishing a practice set and checking the score without reviewing why each mistake occurred means repeating the same errors. Use the 4-bucket error framework after every session.
Cramming the night before — The PST tests cognitive processing speed, not memorized knowledge. Rest and mental clarity on test day matter more than one extra practice session.
Additional Mistakes We Observe Frequently
Practicing only easy questions — If you are scoring 90%+ on practice sets, the questions are too easy. Increase difficulty or add stricter time constraints.
Not simulating test conditions — Practicing at your desk with coffee, music, and breaks does not prepare you for the silent, timed, no-breaks reality of the test center.
Over-relying on a single resource — Different PST practice providers have slightly different question styles. Expose yourself to at least 2–3 different sources to avoid becoming pattern-dependent.
Ignoring the two-pass strategy — Many candidates finish their first pass with only 5 minutes remaining because they spent too long on hard questions early. The two-pass approach prevents this.
Preparing in isolation — Discussing PST questions with other candidates helps identify blind spots in your reasoning. Your logic errors are often invisible to you but obvious to others.
Building Your Preparation Resource Stack
Recommended Practice Sources
The PST preparation ecosystem has limited high-quality resources compared to GMAT or GRE preparation. Here is how to prioritize:
| Resource Type | Purpose | When to Use |
|---|---|---|
| Official McKinsey practice tests | Format familiarity, authentic difficulty | Week 1 (diagnostic) and Week 4 (final simulation) |
| Case interview data exhibits | Data interpretation practice | Weeks 1–3 (extract exhibits from real cases) |
| GMAT data sufficiency questions | Logical reasoning under time pressure | Weeks 2–3 (closest analog to Fact-Based Conclusions) |
| Mental math apps/drills | Calculation speed | Daily, all 4 weeks |
| Business news data | Real-world exhibit reading | Supplementary, whenever available |
Work through data-heavy cases in our case library to build fluency with the exact type of business data exhibits the PST uses. Cases tagged with market sizing are particularly useful for mental math practice, while profitability cases mirror the financial exhibit formats common on the PST.
Creating Your Own Practice Questions
Once you exhaust available practice resources (a common problem given the limited PST material), you can generate additional practice by:
- Taking any business data exhibit (from a case, news article, or annual report)
- Writing 3–4 questions about it:
- One Reading Facts question (“What was X’s revenue in 2024?”)
- One Formulae question (“What is the compound annual growth rate from 2020 to 2024?”)
- One Fact-Based Conclusion question (“Which of the following MUST be true based on the data?”)
- One Reading Implications question (“What does the data suggest about X’s competitive position?”)
- Having a study partner attempt your questions and vice versa
This exercise deepens your understanding of question design and makes you better at recognizing trap answers.
From PST to Case Interviews: The Continuity
Passing the PST is not the end — it is the beginning of case interview preparation. The good news: PST preparation builds a foundation that transfers directly to case performance.
flowchart TD
A[PST Skills] --> B[Case Interview Application]
A1[Data Interpretation] --> B1[Chart/Exhibit Analysis in Cases]
A2[Mental Math] --> B2[Back-of-Envelope Calculations]
A3[Logical Reasoning] --> B3[Hypothesis Testing & Synthesis]
A4[Time Management] --> B4[Structured Case Pacing]
A1 --- A
A2 --- A
A3 --- A
A4 --- A
B1 --- B
B2 --- B
B3 --- B
B4 --- B
| PST Skill | Case Interview Application | How It Transfers |
|---|---|---|
| Data interpretation | Exhibit analysis during cases | Same skill, applied in real-time conversation |
| Mental math | Back-of-envelope calculations | Identical calculations, now verbalized to interviewer |
| Logical reasoning | Hypothesis testing and synthesis | Same proof standard, now driving case direction |
| Time management | Structured case pacing | Same discipline, applied across 30-minute case |
| Error awareness | Self-correction during cases | Catching your own logic errors before interviewer does |
Candidates who prepare thoroughly for the PST typically perform 20–30% better in their first case interview practice than those who skipped PST preparation or barely passed through luck. The quantitative confidence built during PST prep eliminates “math anxiety” that undermines many case performances.
Key Takeaways
- Take a diagnostic test first to identify your weakest skills — do not prepare blindly
- The PST has six question types; Reading Facts (38% of questions) delivers the highest return on preparation time
- Follow a phased 4-week plan: foundation, skill building, integration, simulation
- Data interpretation, mental math, and logical reasoning are the three skills the PST evaluates — build each deliberately
- Track accuracy, speed, and error distribution for every practice session to guide your focus
- Build a personalized rules library from your errors — these become your test-day mental checklist
- The two-pass strategy prevents time catastrophes: solve easy questions first, return to hard ones
- The estimation-and-adjustment mental math method eliminates calculator dependency
- Simulate test-day conditions in Week 4 — unfamiliar questions, strict timing, no breaks
- PST preparation transfers directly to both Solve and case interviews, making the investment doubly valuable
Build Your PST Skills with Real Cases
Strengthen your data interpretation by working through McKinsey-style cases from our case library — each case includes the kind of exhibits and analytical reasoning the PST demands. For a deep-dive on question-type-specific strategies, see our PST question-type strategy guide. If your office uses the gamified format, our Solve assessment guide covers the specific preparation differences. And when you are ready to test your analytical skills in a case context, try our AI Mock Interview for real-time feedback on your structured problem-solving approach.