McKinsey Software Engineer Interview Questions & Rounds
How the McKinsey software engineer interview works: HackerRank OA, code pair, technical, PEI and case rounds, with questions from real candidate experiences.
On this page
How to Crack McKinsey: The Software Engineer Interview, From Real Experiences
Last updated November 20, 2026 · 26 min read · For interns, new grads, experienced SDE 1 and L4 hires, senior and staff engineers
Built by the Codinzhub team. This guide is built from McKinsey & Company software engineer interview experiences that candidates shared, including posts and OA questions on Codinzhub. The process changes by year, level, office and unit, so treat this as a map, not a promise.
The 30-second version. Campus candidates in India and off-campus new grads start with an online assessment, on HackerRank in all 6 reports that name a platform. On campus it is usually 2 coding questions, sometimes with SQL or MCQs. Off campus, the 2023 test mixed SQL, a REST API task, front-end JavaScript and one DSA problem. Next, in a code pair round, a McKinsey engineer watches you solve one problem: usually DP, strings or arrays on campus, practical tasks for experienced hires. Then a technical interview covers projects, SQL, fundamentals and some design. Campus drives finish with the India hub CTO, a manager or HR. Other tracks add a Personal Experience Interview and a problem-solving case, and one engineer was rejected there. The habit that matters most: explain your approach and get a yes before you type, then be ready to justify every line.
What this guide is, and what it is not
This guide is built from 28 candidate experiences of McKinsey & Company's software engineer interviews, from 2020 to 2026, with most from 2022 and 2023. It covers interns, new grads, experienced SDE 1 and L4 hires, and a few senior and staff engineers. The India reports are campus drives; most off-campus reports do not state a location.
It is:
- A map of the process, stage by stage, as candidates described it
- The question patterns that keep coming back, and the follow-ups to expect
- A six-week plan and practice problems matched to those patterns
It is not:
- A list of leaked questions or a promise of what you will be asked
- An official description of McKinsey's process
- An offer rate. Outcomes in candidate posts are self-reported and are not a statistical sample.
Important things to know before you start
These are the McKinsey-specific facts that change how you prepare.
The code pair is a conversation. A McKinsey engineer sits with you, on HackerRank in 2022 and 2024 campus reports. Several reports (5 of 12) say you explain the approach, or why each line exists, and code only after the interviewer agrees. Practise solving out loud with someone watching.
The online test is not only DSA. Several OA reports (9 of 19), mostly off-campus and experienced-hire tests, included JavaScript or React, REST API calls or Flask, and several (8 of 19) included SQL. In two 2023 reports the HackerRank JavaScript test harness failed although the code ran locally.
Engineers get a case and a Personal Experience Interview too. A problem-solving case appears in most reports that describe the later rounds (5 of 8). One 2025 SDE 1 who took it lightly was rejected there.
AI tools. McKinsey's interviewing page says AI may not be used during assessments unless it is explicitly permitted, and may not be used to generate answers in real time during an interview.
Round-by-round breakdown
Candidates described five stages: application, shortlisting, a HackerRank online assessment, an interview loop built around a code pair round, and a final decision.
Stage 1: Application, where candidates applied
The data has two channels: campus drives in India and online applications. The other 9 records do not say how the candidate applied, and none mentions a referral.
| Channel | What candidates said |
|---|---|
| Online application | 13 of 28 records. Off-campus new grads and interns (2022 to 2023) got a test invite after applying. Experienced applicants heard from a recruiter the next day (2021 senior) or within a week (2025 SDE 1). |
| Campus drive | 6 of 28 records, all in India, 2021 to 2026, for titles such as Junior Software Developer, Software Engineer and Software Associate intern. Two drives (2022, 2024) hired for an internship plus a full-time role. |
What helped. One 2022 campus candidate advised focusing on DSA, competitive programming and "especially hackathons". That drive's HR round asked about hackathons and contest ranks.
Stage 2: Shortlisting, how candidates moved forward
On campus, the online assessment was the first filter. Off campus, candidates got a test invite or a recruiter call before any interview.
- Campus test cut (India). About 400 students were eligible for the 2024 coding test. In two August 2022 drives, about 300 students reached the code pair and 40 to 45 the technical interview. One sent about 15 to the CTO round; the other required solving every OA question. Another 2022 drive kept 20 after its coding test and opened with an aptitude and critical-thinking game. A 2021 intern drive kept 31.
- Off-campus test invite (2022 to 2023). The test came soon after applying, and two commenters said the resume screen came after it.
- Recruiter or HR call (experienced). A 2025 SDE 1 got an HR call within a week. A 2021 senior engineer got a recruiter call the next day, then phone interviews with two architects.
What candidates noticed. In one 2022 drive, the McKinsey team briefed shortlisted students after every round on what the next round would expect.
Stage 3: Online assessment
Campus and new-grad candidates started with an online assessment (OA), a timed test taken before any interview. So did the 2025 SDE 1 and a 2025 senior backend applicant. The 2021 senior and staff reports do not mention an OA, and no record describes a separate phone screen.
Online assessment
How it works. Several reports (6 of 19) name HackerRank, and none names another platform. Each of the 6 India campus OA reports describes 2 coding questions, sometimes with 2 SQL queries (2021, 2022) or MCQs on DBMS, OS and networking (2022). The October 2026 IIT Roorkee test was 2 coding questions plus 20 MCQs, one labelled ML. The 2023 off-campus new-grad test had 4 parts; one candidate called it easy to medium, another called its DSA part LeetCode hard. A 2025 SDE 1 got a React task and a Flask task. No record states a time limit.
At a glance
- Length: Not reported (one 2023 candidate finished the 4-part test in 45 minutes)
- Questions: 2 coding questions on India campus drives, sometimes plus 2 SQL queries or MCQs; 4 mixed parts in the 2023 off-campus test
- What was asked: DSA (DP, graphs, union-find, intervals, strings), SQL (8 of 19 reports), and web tasks (9 of 19): JavaScript or React, REST API calls, Flask
- Most common: Call a REST API and process the returned data (4 reports, all off-campus, 2022 to 2023)
| Question | What it tests | Level |
|---|---|---|
| Call a REST API and process the returned data | HTTP requests and JSON handling | New grad / SWE |
| Vanilla JavaScript: render 20 buttons numbered 1 to 20 | DOM creation and event wiring | New grad |
| SQL: customers with more than 3 failed campaign events | Joins, GROUP BY with HAVING | New grad |
| React task built around component state | React state handling | SDE 1 (experienced) |
| Get the groups: friendships formed by queries, report the number of groups | Union-find | New grad |
| 0/1 knapsack variant that returns the maximum quantity instead of value | 0/1 knapsack DP | New grad |
| Merge overlapping intervals | Sorting intervals, then merging | Intern |
The 4 India campus OAs from 2022 and 2024 were DSA only, or DSA plus SQL or MCQs. The web-heavy mix came from off-campus and experienced-hire tests. In two 2023 reports, the HackerRank JavaScript test file failed although the code ran locally. Partial scores could be enough: a 2022 candidate passed 12 of 15 tests on one question and was shortlisted. A full score could also fail: two candidates were rejected after solving everything.
OA questions shared on Codinzhub.
| Question | Drive | Topic |
|---|---|---|
| Sort dates chronologically | IIT Roorkee, October 2026 | Not reported |
| Smart shuffle playlist of N songs | IIT Roorkee, October 2026 | Not reported |
| ML question set around an e-commerce company | IIT Roorkee, October 2026 | Not reported |
See all McKinsey OA questions in the question bank.
Stage 4: The interview loop
On India campus drives the loop was a code pair round (sometimes two), a technical interview, then a final round with the India hub CTO (2022), a manager (2024) or HR. Elsewhere, the code pair led to a Personal Experience Interview (PEI), McKinsey's story-based behavioral interview, with a problem-solving case that some candidates call the PSS round. Senior candidates described architect-led rounds. Round lengths are rarely reported.
How a code pair round runs. Campus reports from 2022 and 2024 describe this sequence:
- A McKinsey engineer sits with you for the whole round, in campus labs or on HackerRank.
- You explain the approach, and in one 2022 drive you also wrote pseudo-code. Coding starts after the interviewer approves it.
- You code, run the tests and discuss time complexity.
- If tests fail, you can ask for feedback. One 2022 candidate was told base cases were missing, fixed them, and was asked to add comments.
Code pair round
At a glance
- Length: Not reported (one 2022 candidate had about 40 minutes for one DP problem)
- Questions: 1 problem in 4 campus reports; 2 problems chosen by the interviewer in the 2024 drive
- What was asked: DSA on campus (DP, strings, arrays); practical tasks for experienced and web roles (SQL, a REST call, front end plus back end plus database)
- Most common: No single repeated question
The code pair was the first interview after the OA in most reports (8 of 12). Several (5 of 12) describe the rule: explain first, code after approval. A 2025 SDE 1 and a 2022 new grad said the pair round mirrored the OA, and the 2025 interviewer asked why specific lines were there. One 2022 candidate coded only a brute force, explained it, and still advanced. Experienced rounds were practical: a 2025 McKinsey Digital round combined front end, back end and database, and a 2021 staff round was an SQL query plus a Java REST call.
| Question | Follow-up | Level |
|---|---|---|
| Two bus lines with a switching cost: minimum time to reach each city | Pseudo-code first, then the recursion tree and its complexity, then DP, then comments | New grad |
| Minimum number of jumps to reach the end of an array | Not reported | New grad |
| Longest palindromic substring | Not reported | Intern |
| String DP that also uses graph ideas and permutations | Not reported | New grad |
| SQL query that produces a required output | Not reported | Staff |
| Java: open an HTTP connection, make a REST call, process the results | Not reported | Staff |
Technical interview
At a glance
- Length: About 45 minutes (one 2022 campus report); the project discussion alone took about 30 minutes in two other reports
- Questions: A resume and project discussion plus 1 or 2 DSA or SQL questions
- What was asked: Projects, OOP, DBMS and SQL, OS, DSA classics and a design question
- Most common: No single repeated question; a project deep dive came up in most rounds (8 of 10)
The round opens with your resume, and interviewers went deep on one project. Several reports include SQL (4 of 10); one 2021 intern drew a project's tables and then queried them. Several include design (6 of 10): a high-level design, a vending machine class design, a URL shortener, API design or a "tech architect" round. ML projects drew ML questions in 2 reports.
| Question | What it tests | Level |
|---|---|---|
| Search in a rotated sorted array, from brute force to optimal | Modified binary search | New grad |
| Draw your project's database tables, then query them in SQL | Schema design and SQL | Intern |
| Reverse a linked list, then reduce the extra space | In-place pointer reversal | Intern |
| Explain merge sort on a whiteboard with an example | Divide-and-conquer sorting | New grad |
| Houses joined by pipes: place tanks and taps, report diameters | Graph traversal along pipe chains | SWE |
| Design a simple URL shortener | Requirements, storage and collisions | SWE |
Final technical round with a senior leader (campus)
At a glance
- Length: Not reported
- Questions: Many short fundamentals questions, plus a few behavioral ones
- What was asked: OOP, DBMS theory, OS, graph algorithms, projects, career goals and situational questions
- Most common: No single repeated question; OOP and DBMS fundamentals came up in both reports
In 2022 the CTO of the McKinsey India hub asked the candidate to rate themselves in OOP, OS, DBMS, networks, DSA and algorithm design, then questioned from those ratings. In 2024 a manager began with behavioral questions, then moved to fundamentals.
| Question | What it tests | Level |
|---|---|---|
| Rate yourself in OOP, OS, DBMS, CN, DSA and DAA | Self-assessment that steers the questions | New grad |
| Multiple inheritance and the diamond problem, then polymorphism | OOP fundamentals | New grad |
| DBMS anomalies, minimal cover and functional dependencies | Normalisation theory | New grad |
| Spanning trees: explain MSTs with Prim's and Kruskal's algorithms | Graph algorithms | New grad |
| OS: processes, multithreading, semaphores and mutex locks | Operating-system concurrency | New grad |
| Situational questions on leadership and teamwork | Leadership and teamwork | New grad |
Personal Experience Interview, case and HR rounds
At a glance
- Length: Not reported
- Questions: Not reported
- Themes: Conflict, ownership of a past problem, motivation, achievements, and a business-style case with simple arithmetic
A problem-solving case appears in most reports that describe the later rounds (5 of 8), and a PEI or competency-story round in several (4 of 8). A 2025 SDE 1 did not expect a case inside the PEI round, took it lightly, and was rejected. In a 2026 QuantumBlack (AI by McKinsey) process, pair programming led to a virtual case plus a PEI. One report posted in 2026 disagrees: its "PSS Round 1" was coding on arrays and hash maps, a URL shortener design and behavioral questions, with no business case. Campus drives used HR rounds instead.
Reported questions.
- Tell me about a disagreement with a colleague and how you resolved it (2 reports)
- Case: high-end vs ordinary tablet launch, then cost and break-even maths
- PEI deep dive into one past issue and the conversations you had
- Real examples of learning, teamwork, feedback, entrepreneurial drive, structured thinking
- Tell me about a challenging project
- As a mechanical engineer, why software development?
See all behavioral questions in the question bank.
Stage 5: Final round and offer
Decision. No record describes a hiring committee or team matching. On campus, the decision followed the final CTO, manager or HR round, and selections were small: 10 internship plus full-time offers in one 2022 drive, 3 of 20 in another, and 2 of 39 in a 2021 intern drive. Off campus, a 2025 SDE 1 still had a final round after the PEI, and a 2025 senior backend applicant was told to expect 5 rounds after the OA.
Timing. No record gives an end-to-end timeline. One 2022 new grad got a pair programming scheduling email about a week after submitting availability.
Offer. Compensation is not reported in the data.
The Codinzhub Next-Round Playbook
Candidates who moved forward explained their thinking out loud, knew their projects in detail, and did not treat the case as a formality.
To get past the online assessment
- Know which test you face: 2 DSA questions on India campuses, or a mix of SQL, REST API and JavaScript or React tasks off campus.
- Attempt every part, including the web parts. One 2022 candidate who skipped a colour change in the JavaScript task was rejected.
- If the HackerRank harness fails while your code runs locally, read the provided test file first. In one 2023 report its import line was wrong.
To get past the code pair round
- Say your approach and wait for a yes. Several reports (5 of 12) describe approval before coding.
- Offer the obvious recursion, state its cost, then improve it. One 2022 interviewer asked for exactly that path.
- Be ready to defend each line, as a 2025 interviewer asked.
To get past the technical interview
- Know one project down to its schema and algorithms. Most rounds (8 of 10) began with a project deep dive.
- Give every approach, from brute force to optimal. One 2022 candidate did this and was called back within 5 minutes.
To get past the final campus round
- Rate yourself honestly. The 2022 CTO questioned from the self-ratings, down to minimal cover and MSTs.
To get past the PEI and case round
- Bring real stories and expect "why" after each one. A 2025 SDE 1 said the round expected deep dives.
- Practise one business case with simple maths out loud, such as a manufacturing cost and a break-even count.
How the loop differs by level
Each level in the data has a technical check. What changes is its content: campus loops lean on DSA and CS fundamentals, while experienced loops lean on practical web, SQL and design work.
| Level | What candidates describe |
|---|---|
| Intern | Based on 2 reports. A 2021 campus drive: an OA with 2 coding questions and 2 SQL queries, a code pair (longest palindromic substring), a technical round, then a PEI plus case round, with managerial and HR rounds after it. A 2022 off-campus intern test had JavaScript, SQL and one DSA problem. No system design was reported. |
| New grad and campus full-time | 11 records. On campus: the OA, 1 or 2 code pair rounds, a technical interview, then the CTO, a manager or HR. Examples are the two bus lines DP, the rotated sorted array and MSTs. Design was light, with one high-level design question in 2022. Off-campus new grads (2022 to 2023) had the 4-part OA, then a pair round that mirrored it. |
| SDE 1 with experience, L4 | Based on 2 reports. A 2025 SDE 1 had a React and Flask OA, a technical round on projects, databases and system design, pair programming, then a PEI round with a case, with a final round still to come. A 2022 L4 full-stack candidate reached a case-based PSS round after 2 rounds. |
| Senior (SSE, SDE 2, senior backend) | Based on 3 reports. A 2021 senior engineer had architect phone interviews on the resume, API design and Node.js. A 2025 SDE 2 had a code pair and a tech architect round scheduled. A 2025 senior backend applicant was told there would be 5 rounds after the OA. No question titles were reported. |
| Staff | Based on 1 report from 2021, an architect role at a McKinsey software unit. A hiring manager round came first, then a pair programming round with one SQL query and a Java REST call, and no DSA. Design was not reported. |
Most-asked topics
These counts cover the 16 reports that named at least one technical question; bare mentions such as "an SQL query" are left out. The surprise is how practical the questions are: web tasks and SQL top the list, ahead of any single DSA topic.
| Topic | What it means | Seen in | Reported examples |
|---|---|---|---|
| Web tasks (front end, REST APIs) | Building a small UI or calling an HTTP API | 8 of 16 reports | Call a REST API and process the data; render 20 buttons |
| SQL and database fundamentals | Queries, normal forms, keys and anomalies | 6 of 16 reports | Customers with more than 3 failed events; query your project's tables |
| Linked lists, sorting, binary search | Classic data-structure basics | 5 of 16 reports | Rotated sorted array; reverse a linked list; merge intervals |
| Strings and arrays | Scanning and transforming sequences | 5 of 16 reports | Longest palindromic substring; minimum jumps to the end |
| Dynamic programming | Answers built from stored subproblems | 4 of 16 reports | Two bus lines with a switching cost; knapsack variant |
| Graphs | Reachability, groups, cheapest routes, MSTs | 3 of 16 reports | Get the groups; houses joined by pipes |
| OOP and class design | Classes, inheritance, OOP pillars | 3 of 16 reports | Vending machine design; the diamond problem |
| OS and concurrency | Processes, threads and locks | 2 of 16 reports | Semaphores and mutex locks |
The question patterns that keep coming back
Most McKinsey questions fall into six patterns. Spot the pattern under the story, because the code pair interviewer asks for your approach before you type.
1. Practical web tasks: front end and REST APIs
This is the most McKinsey-specific pattern and the most widespread (8 of 16 reports). Off-campus and experienced tests asked for something small and working: JavaScript buttons, a React component with state, a Flask task, or an API call. How to choose: if a framework is named, hold state its standard way. To fetch data, send the request, check the status, parse the JSON and handle a failed response before shaping the output. The most repeated OA question, calling a REST API, came up in 4 reports.
Reported examples. Call a REST API and process the returned data; render 20 buttons numbered 1 to 20; React task built around component state; Java: open an HTTP connection, make a REST call, process the results.
2. SQL and database fundamentals
SQL showed up in the OA, the code pair, the technical interview and the final round (6 of 16 reports). How to choose: "for each X with more than N" means GROUP BY plus HAVING, and a required name format means string functions in the SELECT. When the interviewer points at your own project, draw the tables and keys first, then query.
Reported examples. Customers with more than 3 failed campaign events; names of students with an even score, in uppercase; draw your project's database tables, then query them; DBMS anomalies, minimal cover and functional dependencies.
3. Linked lists, sorting and binary search
These were classic campus technical questions (5 of 16 reports), asked from brute force to optimal. How to choose: a rotated sorted array still allows binary search, because at least one half of each split is sorted. Overlapping ranges mean sort by start, then merge. To cut extra space on a list, reverse pointers in place instead of using a stack.
Reported examples. Search in a rotated sorted array; reverse a linked list, then reduce the extra space; merge overlapping intervals; explain merge sort on a whiteboard.
4. Dynamic programming in the code pair
DP was the main campus code pair topic (4 of 16 reports), dressed as bus lines, jumps or a knapsack. How to choose: if step i depends on a few earlier answers plus a small state (which line you are on, capacity left), write that recurrence, then memoise or tabulate it. Two parallel tracks with a switching cost means one DP value per track at each position.
Reported examples. Two bus lines with a switching cost; 0/1 knapsack variant returning the maximum quantity; ways to cover N metres with jumps of 1 to 5; longest palindromic substring.
5. Graphs: groups, routes and spanning trees
Graphs are less common (3 of 16 reports) but appear in the OA, the technical interview and the CTO round. How to choose: merging friends into groups is union-find. Shortest time with weights is Dijkstra, and without weights it is BFS. "Connect everything at least cost" is a minimum spanning tree, built with Prim's or Kruskal's.
Reported examples. Get the groups; move a product to the final node in the shortest time; houses joined by pipes; MSTs with Prim's and Kruskal's.
6. OOP, OS and class design
The final campus round and some technical rounds tested fundamentals by name (OOP in 3 reports, OS and concurrency in 2). How to choose: for "design X", list the nouns, give each one responsibility, and use inheritance only for a true "is-a" relationship. For OS, know when a mutex is enough and when you need a counting semaphore.
Reported examples. Design a vending machine; the diamond problem, then polymorphism; processes, multithreading, semaphores and mutex locks.
Preparing for the Personal Experience Interview and case round
The Personal Experience Interview (PEI) and the problem-solving case caught engineers in this data off guard (see Stage 4). McKinsey's interviewing page says most client-facing roles include personal experience and problem-solving interviews, and asks candidates to bring two examples for each of four areas. Treat this round as scored: a 2025 SDE 1 was rejected after taking the case lightly.
Build your story bank. Prepare six to eight real stories, each under two minutes, that you can defend line by line. Cover the themes candidates were asked about:
| Theme | Reported prompt (paraphrased) | Follow-up to expect |
|---|---|---|
| Conflict | A disagreement with a colleague or teammate, and how you resolved it | Not reported |
| Ownership of a problem | A deep dive into one past issue and the conversations you had | Not reported |
| Hard projects | A challenging project | Why you made each decision |
| Pressure | How you handled tight deadlines | Not reported |
| Competencies | Examples of learning, teamwork, confidence, feedback, entrepreneurial drive, structured thinking | A real example for each |
| Motivation | Hackathons and contest ranks; why software after mechanical engineering | Not reported |
Structure each story. Situation in one line, then what you did and why, the result, and what you would change. Use real experiences and say "I".
Expect depth. A 2025 SDE 1 said the PEI expected deep dives into issues and conversations, and in one 2026 "PSS" round the interviewer kept asking "why". For the case, lay out the factors before you calculate. The 2021 intern case moved from launch factors to a manufacturing cost and a break-even unit count.
A six-week plan
The plan follows the patterns above, most common first, and ends with mocks that feel like the code pair and the case. Plan on two to three focused hours a day.
- Week 1: Practical web tasks. Small UI pieces in plain JavaScript (lists, buttons, a style change on click) and a function that calls a REST API and transforms the JSON. Habit: run every task against a test file, not only in the browser.
- Week 2: SQL and databases. Joins across 3 tables,
GROUP BYwithHAVING, string functions, normal forms, keys and functional dependencies. Habit: draw your own project's schema and write 3 queries on it. - Week 3: Linked lists, sorting, binary search, strings and arrays. Rotated-array search, in-place list reversal, merging intervals, palindromic substrings, jump problems. Habit: brute force first, then improve, and state the space cost.
- Week 4: Dynamic programming. Knapsack variants, two-state DP and counting DP. Habit: draw the recursion tree, then convert it to a table.
- Week 5: Graphs, OOP and OS. Union-find, BFS and Dijkstra, MSTs, one class design (a vending machine), and threads, semaphores and mutexes.
- Week 6: Mocks. Do 4 code pair mocks with someone watching: explain, get a "yes", then justify lines when asked. Add 2 short business cases and rehearse PEI stories out loud.
India campus candidates can go lighter on week 1 and heavier on weeks 3 to 5, since their OAs were DSA-based. Experienced candidates should add a URL shortener and API design discussion in week 5.
Only two weeks? Spend 3 days on web tasks, 2 on SQL, 3 on arrays, linked lists and binary search, 2 on DP, 1 on graphs and OOP, and 3 on code pair mocks, the case and PEI stories.
Practice problems that match these experiences
These are well-known practice problems that match the patterns above. They are not claims about McKinsey's question bank unless a row says the problem was asked as-is.
| # | Practice problem | Pattern | Seen in these experiences as |
|---|---|---|---|
| 1 | Merge Intervals | Sorting, then merging ranges | Asked as-is in one 2021 intern OA |
| 2 | Search in Rotated Sorted Array | Modified binary search | Asked as-is in one 2022 technical interview |
| 3 | Reverse Linked List | In-place pointer reversal | Asked as-is in one 2021 technical interview, with a space follow-up |
| 4 | Convert Binary Number in a Linked List to Integer | Linked-list traversal with bit arithmetic | Asked as-is in one undated full-stack OA |
| 5 | Longest Palindromic Substring | Expand around centre or string DP | Asked as-is in one 2021 code pair round |
| 6 | Water Connection Problem | Walking pipe chains in a graph | Asked as-is (houses, tanks and taps) in one undated technical interview |
| 7 | Assembly Line Scheduling | Two-state DP with a switching cost | Two bus lines with a switching cost (2022 code pair) |
| 8 | Jump Game - Minimum Jumps to Reach End | Greedy reach or DP | A very similar problem in one 2022 code pair round |
| 9 | 0/1 Knapsack Problem | 0/1 knapsack DP | Knapsack variant returning maximum quantity (2022 OA) |
| 10 | Climbing Stairs | Counting DP | Ways to cover N metres with jumps of 1 to 5 |
| 11 | Number of Provinces | Union-find or DFS on groups | Get the groups (2022 OA) |
| 12 | Min Cost to Connect All Points | Minimum spanning tree (Prim's or Kruskal's) | MSTs in the 2022 CTO round |
Web and SQL tasks have no single matching problem, so build small ones yourself. For the URL-shortener prompt, start with Encode and Decode TinyURL. For merge sort, use Sort an Array.
How to handle a question you have never seen
Code pair and technical rounds are usually one story-wrapped problem plus follow-ups, so a repeatable method beats memorised solutions.
- Repeat the problem and one example. In a code pair, the interviewer sits next to you, so agree on the input and output before anything else.
- Say the brute force and its complexity. Campus interviewers approved the approach before any code, and one 2022 interviewer asked for the exponential recursion first.
- Name the bottleneck. Repeated lookups suggest a hash map. Repeated subproblems suggest DP. Merging groups suggests union-find. A sorted-but-rotated array still allows binary search.
- Say when you are stuck. One 2022 candidate could not finish a string DP, coded the brute force, explained the approach, and still got the next round.
- Code in small pieces while talking. Name helpers clearly and be ready to explain any line. A 2025 interviewer asked why specific lines were written the way they were.
- Run the tests and fix the failing case. The campus code pair ran against test cases. When one candidate passed 10 of 15, they asked for feedback, found the missing base cases, fixed them and then added comments.
Why candidates were rejected
Eight reports end in a rejection, and only two give a reason, both the candidate's own reflection. Treat this as thin evidence. Where no reason was given, the list shows the stage that filtered the candidate.
- Not taking the case seriously. A 2025 SDE 1 said the PEI round included a case study they did not expect for an engineering role, so they took it lightly. They were rejected there.
- Leaving part of the web task unfinished. A 2022 off-campus candidate finished everything except a colour change in the JavaScript task and was rejected. Another commenter said resumes are screened after the OA, so that one part may not be the cause.
- Rejected after a full solve, no reason given. Two off-campus candidates (2022 and 2023) solved every OA question and were still rejected.
- Stopped after a later round, no reason given. One 2022 campus candidate was not shortlisted after the technical interview. Another reached the final HR round and was not selected (3 of 20 were selected). A 2021 intern was not selected after the PEI and case round (2 of 39 were selected).
In this data, a full OA score alone did not decide the outcome, while a clear explanation of a brute force once did.
Selected vs. rejected: do this, not that
A few habits repeated in reports that moved forward; the rejected reports show what skipping them can cost.
| Do this | Not that | What the reports show |
|---|---|---|
| Explain before you type: state the approach and wait for approval | Coding silently: typing before the interviewer agrees | Several code pair reports (5 of 12) describe approval first. One 2022 candidate advanced with a brute force and a clear explanation. |
| Justify every line: know why each line exists | Replaying a memorised OA answer: code you cannot defend | Two reports say the pair round mirrored the OA. The 2025 interviewer asked for the rationale behind specific lines. |
| Prepare for a case: a short business problem plus PEI stories | Treating the case as optional for engineers | A case appears in most later-round reports (5 of 8). One 2025 SDE 1 who took it lightly was rejected there. |
| Know your projects to the schema | A resume you cannot go deep on | Most technical rounds (8 of 10) had a project deep dive. One intern had to draw a project's tables and query them. |
| Practise web basics if you apply off campus | Preparing DSA only | Several OA reports (9 of 19) had web parts. A 2022 candidate who left a JavaScript sub-task unfinished was rejected. |
If you remember only five things
- The process. An online assessment (HackerRank where named) comes first, then a code pair round, a technical interview, and either a final CTO, manager or HR round (campus) or a PEI plus case round.
- The code pair format. A McKinsey engineer watches you solve one problem (two in the 2024 campus drive), and you explain before you code.
- The core habit. Say the approach, wait for approval, and be ready to justify every line.
- The core topics. Practical web tasks and SQL top the list, followed by linked lists, sorting and binary search, strings and arrays, and DP.
- The round engineers underestimate. Prepare for the Personal Experience Interview and a business-style case, which appear in most later-round reports.
FAQ
Does every track have an online assessment?
Usually, yes: 19 of the 28 reports describe one, including campus, new-grad and 2025 experienced reports. The 2021 senior and staff reports describe recruiter calls, a hiring manager round and architect interviews without mentioning one.
Is the online test DSA or web development?
It depends on the track. India campus OAs had 2 DSA questions, sometimes with SQL or MCQs. The 2023 off-campus new-grad test had 4 parts: SQL, a DSA problem, a REST API task and front-end JavaScript.
Do I need dynamic programming?
Yes, for campus code pair rounds. DP appears in 4 of 16 reports with named technical questions. Off-campus web tests that listed their parts had one DSA problem.
Is system design asked?
Lightly. Several technical-round reports (6 of 10) had some design: a high-level design, a class design, a URL shortener, or API design with an architect.
Do software engineers really get a case interview?
Yes, in most reports that describe the later rounds (5 of 8). One 2026 report described its "PSS" round as coding plus design instead of a business case, so ask your recruiter which version you will get.
How long does it take?
Not reported end to end. The reported waits were short: a recruiter call the next day or within a week of applying.
About this guide
The Codinzhub team researched and wrote this guide from 28 McKinsey & Company software engineer interview experiences, from 2020 to 2026, including experiences and OA questions shared on Codinzhub. We kept only what candidates described. The questions are our own short summaries, and the practice links are similar problems unless a row says the problem was asked as-is. If you went through the McKinsey software engineer interview recently, share your experience on Codinzhub and we will update this guide.
Disclaimer. McKinsey's process changes by role, year, office and unit (for example McKinsey Digital or QuantumBlack). Use this guide to build a foundation, and confirm the current format with your recruiter.
Search the question bank
The questions from each round above, with practice links for similar problems. Log in to search every question we collected for this role, including questions shared on Codinzhub.
Showing 20 of 98 questions
Sort dates chronologically
A Mckinsey online assessment question shared on Codinzhub (IIT Roorkee, October 2026).
Smart shuffle playlist of N songs
A Mckinsey online assessment question shared on Codinzhub (IIT Roorkee, October 2026).
ML question set around an e-commerce company
A Mckinsey online assessment question shared on Codinzhub (IIT Roorkee, October 2026).
15
A Mckinsey online assessment question shared on Codinzhub (IIT Roorkee on-campus OA. The full statement is on Codinzhub. Sorting Online assessment Not reported 2026 Coding Codinzhub (exact).
16
A Mckinsey online assessment question shared on Codinzhub (IIT Roorkee OA: you are given a playlist containing N songs. The… Not reported Online assessment Not reported 2026 Coding Codinzhub (exact).
17
A Mckinsey online assessment question shared on Codinzhub (IIT Roorkee OA (2 coding + 20 MCQ pattern).
Call a REST API and process the returned data
Level: New grad / SWE.
Vanilla JavaScript: render 20 buttons numbered 1 to 20
Level: New grad.
SQL: customers with more than 3 failed campaign events
Level: New grad.
React task built around component state
Level: SDE 1 (experienced).
Get the groups: friendships formed by queries, report the number of groups
Level: New grad.
0/1 knapsack variant that returns the maximum quantity instead of value
Level: New grad.
Merge overlapping intervals
Level: Intern.
Two bus lines with a switching cost: minimum time to reach each city
Level: New grad.
Minimum number of jumps to reach the end of an array
Level: New grad.
Longest palindromic substring
Level: Intern.
String DP that also uses graph ideas and permutations
Level: New grad.
SQL query that produces a required output
Level: Staff.
Java: open an HTTP connection, make a REST call, process the results
Level: Staff.
Search in a rotated sorted array, from brute force to optimal
Level: New grad.
Keep preparing on Codinzhub
- McKinsey interview questions and experiences — OA questions and interview experiences candidates shared for McKinsey.
- Browse McKinsey online assessment questions — filter the Codinzhub question bank by company.
- Amazon Software Engineer interview guide — the Amazon process, rounds and question patterns.
- Google Software Engineer interview guide — the Google process, rounds and question patterns.
- Adobe Software Engineer interview guide — the Adobe process, rounds and question patterns.
- All company interview guides — every guide on the Codinzhub blog.
Keep track of what you’ve learned.