Skip to content
Interview Questions

McKinsey Interview Experience 2026

How McKinsey India campus hiring usually runs across consulting / BA tracks (Solve, case + PEI) and Junior Software Developer / QuantumBlack tracks (HackerRank, code-pair, fundamentals). Synthesized from public 2022-2024 write-ups with prep notes added - treat this as a prep map, not a script.

Round-wise process at a glance

Consulting / Business Analyst (campus)

Round Typical format What clears you
Resume screen CV + academics Spikes, leadership, crisp formatting
McKinsey Solve ~65 min Redrock + Sea Wolf (typical) Methodical exploration; integrity rules
Buddy / workshop (some campuses) Non-evaluative coaching at McKinsey; case intro Use feedback; do not treat as optional
Interview rounds 2+ sessions; case + PEI each (~45-60 min) MECE structure, mental math, deep PEI story
Final / partner Open-ended case; harder PEI probes Business judgment + personal role clarity

JSD / SDE (campus software track)

Round Typical format What clears you
Online coding (HackerRank) 2 problems; arrays / strings; easy-medium Both problems with solid test coverage
Code-pair 1 Employee present; 2 medium DSA; explain then code Clear approach + working code + complexity
Code-pair / technical 2 1 array problem + SQL + projects Project ownership; SQL comfort
Manager / final Behavioural + OOP / DBMS / OS / DSA Fundamentals depth + leadership stories

Consulting interview experience 1 - Summer BA / consulting intern, campus 2024

Consulting interview experience 1

Candidate profile: Undergraduate; Summer Intern Business Analyst; CDC campus process

Before interviews
  • Resume shortlist via CDC; buddy assigned from the firm (non-evaluative at McKinsey in many accounts)
  • Buddies clarify role expectations and case/PEI prep
  • Tip: Ask buddies for feedback on one PEI story and one case opening structure
Interview day - single deciding round (some UG intern drives)
  • CV deep dive on past experiences
  • Interviewer-led mini case / study discussion after resume
  • Brief behavioural conversation
  • Result: Offer reported in public campus write-up (UG intern expansion)
  • Tip: First-principles structure beats memorised frameworks that do not fit the prompt

Key takeaways: Even one round can combine CV, case, and fit - prepare all three, not only cases.

Takeaways

  • What decided it: First-principles structure on a mini case after a sharp CV deep dive, not a memorised framework dump
  • Common fail: Case-only prep when the deciding round also grades PEI/fit and resume spikes
  • How to practise: One PEI story + one case opening with a buddy; CV bullets you can defend line-by-line

Consulting interview experience 2 - BA / intern, IIT campus Day-0 pattern

Consulting interview experience 2

Candidate profile: Strong resume; consulting primary; multiple Day-0 interviews

Steps 1-2 - Shortlist + buddy workshop
  • Resume screen ~7-10 days after CDC upload in one account
  • Case workshop plus buddy rounds before Day-0/Day-1 interviews
  • McKinsey buddies described as non-evaluative; still practise seriously
  • Tip: Use workshop language (MECE, hypothesis) in live cases
Step 3 - Two partner rounds (example)
  • Each ~45-60 minutes: case plus PEI-style personal questions
  • Cases may shift mid-interview; guesstimates appear when frameworks do not fit
  • PEI probes personal contribution, not team brochure
  • Result: Offer decision among stacked Day-0 schedules (McKinsey vs other MBB)
  • Tip: Keep mental math visible; partners grade communication as much as answer

Key takeaways: Partner rounds reward calm structure under ambiguity and crisp PEI depth.

Takeaways

  • What decided it: MECE structure when cases shift mid-interview, visible mental math, and PEI answers that name your contribution
  • Common fail: Brochure-style team stories; freezing when the case does not fit a memorised framework
  • How to practise: Two partner-style mocks with mid-case pivots; 90-second PEI with personal role clarity

Consulting interview experience 3 - Post-internship PPO path

Consulting interview experience 3

Candidate profile: MBA campus; summer intern at McKinsey; PPO pursuit

Internship loop (historical MBA account)
  • McKinsey problem-solving session before interviews
  • Multiple case + guesstimate interviews same day (~4-5 sessions, 45-60 min each)
  • Frameworks rarely fit cleanly - first principles emphasised
  • Tip: Basics and CV consistency matter as much as case volume
PPO decision factors
  • Ownership on workstreams, client communication, asking for help early
  • Oral and written communication plus delivering results under manager feedback
  • Result: PPO reported after successful internship
  • Tip: Treat each client meeting as PEI fodder with measurable impact

Key takeaways: Summer performance is extended PEI - document impact weekly during the internship.

Technical interview experience 4 - Junior Software Developer, on-campus 2024

Technical interview experience 1

Candidate profile: Final-year CS/IT student; Internship + Full Time JSD drive

Round 1 - HackerRank OA
  • ~400 students eligible in one 2024 account
  • 2 questions: array-related and string-related, easy to medium
  • Tip: Accuracy over exotic optimisations - clear both fully
Round 2 - Code-pair
  • McKinsey employee accompanies you on HackerRank
  • 2 medium problems: string manipulation, DP, or trees
  • Explain approach first; code only after interviewer approves; discuss time complexity
  • Follow-up technical questions after both problems pass
  • Tip: Think out loud; do not silently code
Round 3 - Second technical / code-pair
  • 1 medium array coding question
  • Medium SQL query
  • Resume deep dive - especially projects
  • Tip: Know every project decision; demos help if allowed
Round 4 - Manager (tech + HR)
  • Behavioural: career goals, leadership, teamwork scenarios
  • OOP: abstraction, encapsulation, polymorphism
  • DBMS: normal forms, primary keys
  • DSA: conceptual trade-offs across structures
  • OS: multithreading, process, semaphores, mutex locks
  • Result: Cleared on successful tracks
  • Tip: Rate yourself honestly if asked - they probe whatever you rate high

Key takeaways: Code-pair is a collaboration test. Narrating approach is as important as AC.

Technical interview experience 5 - SDE / JSD, earlier campus pattern

Technical interview experience 2

Candidate profile: Campus SDE candidate; INT+FTE path

Code-pair batch (labs)
  • One shared 2022 pattern: DP question in a supervised code-pair batch
  • ~300 into this stage in that account
  • Tip: Optimise only after a correct brute force is agreed
Technical interview (~45 min)
  • Resume projects; OOP
  • Whiteboard: merge sort with example; linked lists; hash maps
  • Medium SQL; high-level design for a stated problem
  • DSA: search in a rotated sorted array - brute to optimal
  • ~40-45 students at this stage in one funnel
  • Tip: Always give complexity for each approach
Final with CTO / hub lead
  • Self-rate OOP, OS, DBMS, CN, DSA, DAA
  • Diamond problem / multiple inheritance; polymorphism
  • DBMS anomalies, minimal cover, functional dependencies
  • Spanning trees / MST (Prim, Kruskal) when asked
  • ML follow-ups if projects are ML-heavy
  • One account: ~15 at final, 10 selected for INT+FTE
  • Result: Offer received on that track
  • Tip: After each round McKinsey sometimes briefs what they want next - listen and adjust

Key takeaways: Fundamentals with depth beat a long list of half-known buzzwords. Own your resume end-to-end.

HR interview experience

HR interview experience

Candidate profile: Candidate who reached the manager round

Behavioural portion (manager round)
  • Career goals and why McKinsey technology / this hub
  • Situational leadership and teamwork prompts
  • Web / product questions when relevant to your stack
  • General conversation on how delivery works inside the firm
  • Final result: Combined with technical score for offer decision

Key takeaways: PEI-style stories help even on software tracks - prepare 2-3 STAR examples on ownership and conflict.

Sample answers for high-frequency questions

Use these as frames, not scripts.

Technical

Q. Explain approach before coding in a code-pair - what do they want?
A. Restate the problem, give brute force, then optimise with complexity, confirm edge cases, then implement. Interviewers often redirect the approach - treat that as collaboration, not failure.

Q. OOP: abstraction vs encapsulation?
A. Abstraction hides complexity behind a clean interface; encapsulation bundles state with methods and controls access. Example: a payment API abstracts gateway details; private balance fields encapsulate account state.

Q. OS: process vs thread; why mutex / semaphore?
A. Process: independent address space. Thread: shared memory inside a process. Mutex: exclusive lock for one critical section. Semaphore: counting resource permits. Mention deadlock risk when locks are nested wrongly.

Q. Find an element in a rotated sorted array.
A. Modified binary search: decide which half is sorted, then decide whether the target lies in the sorted half. O(log n) time, O(1) space. Start from linear scan only if clarifying.

Behavioural

Q. Career goals?
A. Near-term: ship reliable software in a collaborative environment. Medium-term: own a service end-to-end. Tie one concrete skill you want to grow to McKinsey Digital / hub work - not a generic FAANG script.

Common questions checklist

OA / code-pair

  • Arrays, strings, hashing, DP, trees
  • Explain → code → complexity
  • SQL joins / aggregations

Fundamentals

  • OOP pillars; diamond problem
  • DBMS NF, keys, anomalies
  • OS threads, sync primitives
  • Project and API troubleshooting if on resume

Tips from successful candidates

Coding tips

  • Practise explaining before typing
  • Pass both OA problems fully
  • Discuss trade-offs, not only the final code

Fundamentals tips

  • Revise OOP, DBMS, OS the week before
  • Be ready to self-rate subjects
  • Defend every resume bullet

Behavioural tips

  • 2-3 STAR ownership stories
  • Ask a thoughtful question at the end
  • Listen to post-round briefings

McKinsey hub

HR interview questions

Placement papers

Preparation guide

Sources

Round-wise notes synthesize public campus and careers write-ups across consulting and JSD tracks, then add prep takeaways and outcome context. Confirm which track your drive is hiring for. Citation inputs:

HR interview

Behavioural prompts usually sit inside the manager round. Use the dedicated HR page for STAR frames.

Similar companies

Bain · BCG · Deloitte · Accenture

Ready to prepare? Drill code-pair etiquette and CS fundamentals together - McKinsey software panels test both.

Pro tip: In shared reports, OA and code-pair do the heavy filtering. Fundamentals depth decides the final manager round.