McKinsey · Primly Community

McKinsey software engineer interview process, full loop: what actually happens

quietquit_quincy · 6 replies

Finished my loop at McKinsey's tech division (QuantumBlack side) about six weeks ago. Got the offer, am joining in August. Writing this up because I could barely find anything useful before I went in.

Here's the structure I went through for a Senior SWE role: Recruiter screen (30 min) Technical phone screen with a hiring manager (45 min, mix of coding and design) Two technical onsite rounds (one coding, one system design) One behavioral/values round A final conversation with a partner-level person

The total timeline was about 7 weeks from first recruiter email to written offer. They gave me a deadline extension without drama, which I appreciated.

The coding rounds leaned medium LeetCode difficulty. I got one graph traversal problem and one string manipulation problem. Both were pretty standard but they cared a lot about code quality, not just correctness. I was asked to walk through edge cases without being prompted, and the interviewer was clearly noting whether I tested my own code.

The system design round was closer to what you'd see at a typical big-tech L5 interview. I was asked to design a data pipeline that could ingest sensor data at scale. The interviewer had a consulting background but was technically sharp. They pushed on tradeoffs at every layer: storage, compute, consistency model. Felt less "whiteboard theater" than some FAANG loops I've done.

The behavioral was lighter than I expected given this is McKinsey. They asked about a time I had to influence without authority and a time I changed my mind based on data. Very STAR-method friendly. Not a case interview at all, which threw me because I'd half-prepped for one.

Comp: my offer for Senior SWE in NYC was roughly in line with market for that level. Not FAANG-ceiling but solidly above median consulting tech roles. Happy to share more in comments if helpful.

The vibe throughout was collegial, not gotcha. Interviewers were prepped, had clearly read my resume. One thing I wish I'd done: research QuantumBlack specifically, not just McKinsey broadly. The hiring team is pretty proud of the research/AI reputation and it came up.

6 replies

market_realist

Thanks for writing this up. Seven weeks total is faster than I expected from MBB. Did the recruiter give you a heads up on timeline at the start, or did you have to ask?

backend_bekah

They gave me a rough estimate upfront (6-8 weeks) and it held. I did ask after the onsite for a status update and they responded same day. Communication was better than most places I've interviewed.

consultant_cam

Worth noting that the structure varies a bit between McKinsey offices and tracks. The core tech teams (QuantumBlack, Lilli, the internal platform groups) run a more SWE-standard loop. If you're applying to a tech role embedded in a consulting practice, you might still get some case-adjacent elements. Ask the recruiter early which track you're actually interviewing for.

visa_vik

Do they sponsor H1B for the SWE roles? That's my main blocker with MBB positions. Hard to find a clear answer.

backend_bekah

They do sponsor for QuantumBlack roles. My recruiter confirmed it early when I asked directly. I'd just ask the recruiter on your first call rather than waiting.

ml_mike

The 'influence without authority' question is basically a QuantumBlack signature. I heard the same thing from two different people who went through loops there in the past year.