Academic snapshot
Marks: Top academic bar (often 8+ / IIT-NIT bias on campus lists)
Degree: Full-time relevant degree per JD
Backlogs: None active preferred
Year: Final-year and recent grads
McKinsey & Company is a global management consultancy founded in 1926, known for extremely selective analyst hiring. In India, McKinsey recruits from top campuses for roles across strategy, operations, and digital transformation. India offices sit in Mumbai, Gurugram, Bengaluru, and Chennai.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus (target schools) | Batch PPT, campus JD academic filters | Solve + case + PEI bar |
| Careers portal / referral | Resume screen volume; networking matters more | Still expect Solve + cases |
| Internship → full-time | Conversion may shorten stages | You still defend cases and PEI stories |
Off-campus does not mean “easier cases.” It often means heavier resume competition before you ever open Solve. If your CGPA sits below your campus’s printed bar, spend energy on casing and networking, not on hunting a mythical lower cutoff blog post.
Top academic bar is the honest phrase candidates use. McKinsey does not always publish one universal India CGPA number. Many campus lists behave like high floors (students often cite 8+ with IIT/NIT bias on target lists); strong Solve and case performance still decide advancement after screening.
Degrees: Full-time engineering, commerce, economics, and related degrees appear in India recruiting. Read your drive notice for branch/degree filters.
Gaps and backlogs: Active backlogs are a usual blocker. A short gap needs a clean skills story. Integrity issues in PEI end loops fast.
What helps the resume screen: Leadership roles with metrics, internships with ownership language, competitions or research with outcomes, and clear bullets - not buzzword salad. Certificates are secondary. See certifications after case fundamentals are solid.
Academic snapshot
Marks: Top academic bar (often 8+ / IIT-NIT bias on campus lists)
Degree: Full-time relevant degree per JD
Backlogs: None active preferred
Year: Final-year and recent grads
Skills & focus
Primary: Case interviews
Secondary: PEI STAR stories
First filter: McKinsey Solve / PST variants
Differentiator: Structured problem-solving + clear communication
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | Top academic bar / high campus floor (often 8+) | No single public India number - verify JD |
| Degree | Full-time relevant degree | Engineering + non-engineering both appear |
| Year | Final year + recent grads | Internship conversion paths exist |
| Backlogs | No active backlogs preferred | Clear before paperwork |
| Skills gate | Solve + cases + PEI stories | Coding is not the BA default |
When a campus JD prints a number, treat it as a shortlisting filter. Once you are in the funnel, Solve performance, case structures, math accuracy, and PEI stories decide advancement. A 0.2 CGPA difference rarely saves a weak case.
| Signal | What it usually means | What to do |
|---|---|---|
| Printed high CGPA on campus JD | Hard filter for that drive | Confirm with placement cell |
| No printed number (off-campus) | Resume + Solve decide | Strengthen leadership bullets |
| Borderline academics | Need stronger Solve/cases/PEI | Extra peer casing hours |
| Below 8 on many target lists | Often filtered before Solve | Focus on drives where you qualify |
| Band | Rough feel | Reality check |
|---|---|---|
| Below printed floor | Low on-campus | May still compete off-campus with exceptional profile |
| At printed floor | Eligible; Solve decides | Cases + PEI must be strong |
| Comfortably above | Stronger resume-screen odds | Still not an offer by itself |
| Top of class + leadership metrics | Best practical combination | Offer still requires Solve + cases |
Download 2026 Mckinsey placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
McKinsey does not publish one permanent official “coding paper.” “Previous year papers” on this site are pattern trainers for Solve/PST-style filters, case structure practice, and PEI prep - not leaked live cases or live Solve keys.
| Round (typical) | What to practice |
|---|---|
| McKinsey Solve / PST variants | Timed problem-solving, game mechanics, numerical stamina |
| Case interviews | Structuring, math, synthesis, recommendation clarity |
| Personal Experience Interview | STAR ownership, leadership, personal impact, collaboration |
| Final / HR | Why McKinsey?, location, travel willingness, logistics |
| Theme you saw in a set | What to drill next | Why McKinsey asks it |
|---|---|---|
| Profitability drop | Revenue vs cost tree + 2 drivers deep | Core case muscle |
| Market entry | Market size → competition → capabilities → risks | Classic strategy prompt |
| Pricing | Value vs cost-plus vs competitive | Client recommendation clarity |
| Growth | Organic vs inorganic levers | Structured optionality |
| Exhibit math | % change, CAGR intuition, weighted averages | Speed under pressure |
| PEI leadership | STAR with conflict + metric | Personal Experience Interview |
2025 PDFs often drill “profit decline for a retailer.” Own the profit tree - revenue (price × volume) and cost (fixed vs variable) - then drill a related problem in another industry. That transfers; memorising the story text does not.
McKinsey hires freshers through campus placement cells (often target schools), the careers portal, referrals, and internship conversion. After resume screen, the shape is consulting-style: McKinsey Solve, cases, Personal Experience Interview, then HR.
Campus recruitment
Through college placement cells - PPT, then Solve and interview days.
Online applications
Apply on mckinsey.com careers for early-career / Business Analyst-style roles; follow the invite for Solve format.
Referrals
Employee referrals improve visibility. You still need to clear Solve and cases.
Placement cell or recruiter checks academics against the drive bar, degree, backlogs, and year of passing. Leadership bullets and internship impact help when volumes are high. This is a gate - Solve and cases are the real filter.
Resume bullets that travel well into PEI:
Vague bullets like “worked on a team project” force you to invent stories under pressure.
McKinsey Solve is the modern digital assessment that replaced the classic Problem Solving Test on many paths. Candidate reports describe game-based ecosystems (often called plant / ecosystem and redrock-style games) that reward calm, structured decisions under time.
| Component (typical) | What it checks | Prep move |
|---|---|---|
| Solve games | Problem-solving under time | Practice mechanics; stay calm |
| Numerical comfort | Quick % and ratio work | Daily mental math |
| Older PST-style (legacy notes) | Reading + quantitative reasoning | Timed reading + calculation |
Pass bar in practice: Finish cleanly without panic clicks. Students who treat Solve as “just a game” and ignore tutorial rules lose easy points.
Student tip: Read every on-screen instruction twice in practice. Speed without accuracy is a silent fail mode.
Deeper notes: McKinsey Online Assessment.
Often multiple cases across interview days. Structure:
Student tip: Speak in headlines. “I’d look at revenue and cost; on revenue I’d start with volume because…” beats dumping a memorised 12-box framework.
Worked mini-outline - profitability drop:
Worked mini-outline - market entry:
Behavioural deep dive on resume stories: leadership without authority, personal impact, entrepreneurial drive, inclusive collaboration. Use STAR with numbers. McKinsey PEI is not a soft HR chat - empty leadership claims fail.
Expect follow-ups like “What would you do differently?” and “Who disagreed with you?” Have a second layer ready.
Why McKinsey (problem-solving culture, not “MBB brand”), location among Mumbai / Bengaluru / Gurugram / Chennai, travel comfort, joining vs exams. Know the ₹20-35 LPA fresher band so CTC talk is grounded.
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | McKinsey Solve / PST | Timed | Problem-solving under pressure |
| 2 | Case interviews | 30-60 min each | Structure, math, synthesis |
| 3 | PEI | 30-45 min | Leadership & impact stories |
| 4 | HR / offer | 20-40 min | Fit, location, logistics |
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT then Solve window |
| Solve → interview invite | Days to weeks | Batch logistics vary |
| Case + PEI loop | Often clustered interview days | Multiple conversations |
| Offer / paperwork | After finals | Written offer wins |
| End to end | Often 2-6 weeks | Off-campus can stretch |
| Case type | Focus | Prep move this week |
|---|---|---|
| Profitability | Revenue vs cost trees | One peer case + math drill |
| Market entry | Size, competition, fit, risks | One written structure |
| Pricing | Value / competitive / cost | Exhibit % practice |
| Growth | Organic vs inorganic | Headline recommendation practice |
| PEI | STAR with metrics | Two stories spoken aloud |
If your friends are preparing for product companies, do not copy their calendar blindly:
Tech affiliate or digital JDs can reintroduce coding - read the notification before you abandon DSA entirely.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a McKinsey invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for McKinsey sits around ₹20-35 LPA (candidate-reported - confirm the letter). Languages students mention most often: C, Go. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): McKinsey eligibility for freshers 2026 is candidate-reported and drive-specific. Business Analyst / consulting tracks usually expect a top academic bar (often 8+ CGPA with IIT-NIT bias on many campus lists), a relevant full-time degree, and no active backlogs. Case skill, McKinsey Solve performance, and PEI stories matter more than a marginal CGPA difference once you clear screening. Always verify the official career.
What you are training for: McKinsey fresher consulting loops commonly run: Application / resume screen → McKinsey Solve (or PST-style variants on older cycles) → Case interview rounds → Personal Experience Interview (PEI) → HR / offer. Campus and off-campus timelines vary; many candidates report multi-week processes.
Short version of the prep split: Treat McKinsey like MBB consulting hiring, not a coding company. Split time roughly: 35% McKinsey Solve practice, 40% case drills, 15% PEI STAR stories, 10% fit and industry awareness. Peer casing beats solo reading.
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the McKinsey previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most McKinsey drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at McKinsey usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why McKinsey?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a McKinsey-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the McKinsey story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed McKinsey papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many McKinsey papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in McKinsey-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed McKinsey paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why McKinsey. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For McKinsey, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three McKinsey mistakes, you are collecting content, not preparing.
Sit one more mixed McKinsey set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on role (Business Analyst vs other early-career tracks), location (Mumbai, Bengaluru, Gurugram, Chennai), hiring year, and written components.
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Fresher consulting / BA-style | ₹20-35 LPA | Primary band for this hub |
| Tech / digital affiliates | May differ | Follow that JD’s offer letter |
| Lateral / experienced | Higher bands | Outside fresher default |
Confirm base, bonus, and benefits on the written offer. Do not treat blog midpoints as guarantees.
Policies vary by office and year. Candidates commonly care about:
Office culture stories differ by city - ask your interviewer what staffing looks like for first-year BAs rather than guessing from LinkedIn posts.
Know the ₹20-35 LPA fresher context, ask how the package splits (fixed vs variable), and clarify joining date vs final exams. One calm clarifying question beats aggressive negotiation with no market anchor. If bonus language is unclear, ask for the written breakup rather than debating midpoints from Telegram groups.
When McKinsey interviewers push on PEI, they want:
“I improved the process” without numbers is a soft reject signal even if your case was fine.
Referrals and coffee chats help resume visibility; they do not replace casing. If someone offers a referral, still prepare as if the Solve and case bars are unchanged - because they are.
Typical consulting path: Application screen → McKinsey Solve (or PST-style variants) → Case interviews → Personal Experience Interview (PEI) → HR/offer. Confirm round names on your invite.
Most fresher BA-style loops report about four major stages (Solve → case → PEI → HR), with multiple case conversations inside the case stage. Count the mailer, not a random blog.
Yes. Free McKinsey placement papers PDF and 2024-2026 style practice sets are on this site - pattern trainers for Solve and case prep, not leaked live cases. Start with the 2026 PDF or the paper archive.
Candidate-reported formats are timed digital games (ecosystem / plant and redrock-style) that test problem-solving under time. Exact games vary by year - verify your invite. Practice mechanics, stay calm, and keep numerical comfort warm.
Commonly reported: a top academic bar on campus lists (often 8+ with IIT-NIT bias), relevant full-time degree, no active backlogs preferred. McKinsey does not publish one universal cutoff - your drive notice overrides this page.
Candidate-reported fresher CTC often lands around ₹20-35 LPA (as of August 2026), varying by role and location (Mumbai, Bengaluru, Gurugram, Chennai). The written offer letter is the only number that matters.
Common India hubs: Mumbai, Bengaluru, Gurugram, Chennai. Staffing can involve travel. HR usually checks preference and joining logistics. Be honest early.
Split time roughly 35% Solve, 40% cases, 15% PEI STAR, 10% fit. Peer case 3× weekly. Details: preparation guide.
Classic BA recruiting is Solve-, case-, and PEI-led. Tech affiliate JDs may differ. Read your notification before spending months on DSA.
The Personal Experience Interview is a behavioural deep dive on resume impact: leadership, personal impact, entrepreneurial drive, inclusive collaboration. Use STAR with metrics. It pairs with cases - you need both.
All three use cases. McKinsey is known for McKinsey Solve as a distinctive first filter and a structured PEI. Prep cases for all; customise “Why this firm?” with real reasons, not brand ranking. See also BCG and Bain.
Profitability, market entry, pricing, and growth cover most fresher volume. Practice exhibit math and a crisp recommendation every time.
Treat Solve as a real reject stage, case out loud with a peer three times a week, keep a math/structure error log, and rehearse two PEI leadership stories until they sound natural. Reading frameworks alone does not make you case-ready.
Start with McKinsey interview experience on this site, then cross-check reputable case-prep write-ups for India recruiting. Use them as maps, not scripts.
Case and PEI bars are the same skill set. What changes is logistics and staffing stories in HR - have an honest office preference and travel comfort answer. Do not invent office stereotypes.
Profile patterns that got selected: Strong academics on target campuses, leadership bullets with metrics, internship or project impact, steady peer casing rather than last-week panic. Off-campus selects often had sharper networking plus equally sharp cases.
McKinsey Solve gate: Timed filter. Calm mechanics mattered. Students who treated it as “just a game” and skipped tutorials struggled.
Case rounds: Profitability and market-entry dominated practice notes. Interviewers pushed on math units and whether the recommendation matched the analysis.
PEI: “Tell me about a time you led without authority” and personal-impact stories with real outcomes. Empty leadership claims failed.
Takeaway candidates repeated: clean Solve run + clean structures + honest math + two strong PEI stories beat a perfect resume with weak casing.
What hurt other candidates: dumping frameworks without prioritising; silent math; stories with no numbers; “Why McKinsey?” answers that could fit any logo; ignoring Solve until the night before.
Do not binge 20 new frameworks. Deepen structures you already use.
Prompt: A mid-size retailer sees profit down 12% YoY. What would you look at?
Speak this in under four minutes. That transfer skill matters more than memorising a retail case PDF.
| Story type | Prompt you should answer | Metric to include |
|---|---|---|
| Leadership | Led a project end-to-end | Time saved / users / ₹ impact |
| Personal impact | Changed an outcome for someone else | What changed because of you |
| Entrepreneurial drive | Started or fixed something without a brief | Scope you invented |
| Inclusive collaboration | Made room for quieter voices | How the team outcome improved |
| Failure | Missed a goal | What you changed next time |
If a story has no number, it is not ready for McKinsey PEI.
More narratives: McKinsey interview experience.