Deloitte Quantitative Analyst interview typically runs 2 rounds: senior manager technical interviews. The process is highly CV-driven, with interviewers pressing candidates to defend every listed skill in depth.
$164K
Avg. Base Comp
$285K
Avg. Total Comp
2
Typical Rounds
1-2 weeks
Process Length
We've seen Deloitte's quantitative interviews operate less like a structured assessment and more like a forensic review of your background. The candidate here described a first round that stayed close to their CV before escalating sharply — the follow-up went skill by skill through their resume, pressing on option pricing, Monte Carlo simulation, and risk measures in real depth. That escalation pattern is telling: Deloitte senior managers appear to use the first conversation to identify where to probe hardest in the second. Anything you list as a competency becomes fair game for a detailed technical cross-examination.
A recurring theme in this experience is the emphasis on practical modeling judgment rather than definitional knowledge. The mining-company valuation question — how do you value a business with no terminal value, projected all the way to end of reserves, and how do you forecast cash cost — is not a question you can answer with a framework you memorized. It requires understanding the actual economics of the asset. Similarly, the Monte Carlo question about simulation count and scaling behavior was designed to separate candidates who have run simulations from those who have only read about them. These are the moments where surface-level preparation collapses.
The unexpected coding prompt at the end of an otherwise finance-heavy interview is worth flagging too. It suggests Deloitte wants to confirm analytical range, not just domain expertise. The clearest lesson from this account: the candidate's own assessment was that overstating experience on the CV was the decisive mistake. When interviewers are this methodical, any gap between what's written and what you can actually defend tends to surface quickly.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Deloitte process.
I went through 2 rounds with senior managers, and the whole thing was pretty technical from the start. The first round felt manageable because they spent a lot of time digging into the details of my background and the work I’d listed on my CV. There was a theoretical question at the end on linear regressions, but it was more of a quick check than a full grilling. The second round was much tougher and felt like they were going line by line through my Skills section. That’s where they pushed on option pricing, Monte Carlo simulation, and risk measures, and they clearly wanted more than textbook definitions. One question that stood out was how many simulations you need for a Monte Carlo simulation to work, and how it scales as you increase the number of runs. They also asked a coding question at the end: write code to find the day of the week for a given future date, which was a bit unexpected in an otherwise finance-heavy interview.
There was also a valuation case that was very specific and practical. They asked about the right method to value a mining company when there’s no terminal value and the business has to be projected all the way to the end of reserves. I also got asked how I would forecast cash cost, which made it clear they were testing whether I understood the mechanics behind the model, not just the high-level theory. I was a bit thrown off by how detailed they got, and I think they were not impressed that I’d stretched some parts of my resume. In the end I was rejected, so I’d say the main takeaway is to be very honest about what’s on your CV and be ready to defend every technical bullet point with real depth.
Prep tip from this candidate
Be ready to defend valuation assumptions for resource companies, especially how to model a mining business without a terminal value and how to forecast cash costs. Also review Monte Carlo basics beyond the definition — they asked about simulation count, scaling, and then finished with a small coding problem on date logic.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Deloitte
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Bagging vs Boosting | |
| Raining in Seattle | |
| Maximum Profit | |
| Hurdles In Data Projects | |
| Missing Housing Data | |
| Size of Joins | |
| Assumptions of Linear Regression | |
| Duplicate Rows | |
| Using R Squared | |
| Cyclic Detection | |
| Precision and Recall | |
| Find Duplicate Numbers in a List | |
| Data Preparation for Imbalanced Data | |
| FAQ Matching | |
| Classification and Regression | |
| Impossibly Iterative Fibonacci | |
| Slow SQL Query | |
| Swap Variables | |
| Blob Indexing | |
| Yelp-like System | |
| Bias vs. Variance Tradeoff | |
| Subway Machine Learning Model | |
| Multicollinearity in Regression | |
| String Palindromes | |
| Seller Type Modeling | |
| Digital Classroom System Design | |
| Client Solution Pushback | |
| Youtube Recommendations |
Synthesized from candidate reports. Individual experiences may vary.
A senior manager conducts a detailed walkthrough of the candidate's CV, probing the specifics of prior roles and projects listed on the resume. The round concludes with a theoretical question on linear regression as a quick knowledge check of quantitative fundamentals.
A more rigorous session where the interviewer goes line by line through the candidate's Skills section, pushing hard on topics such as option pricing, Monte Carlo simulation convergence and scaling, and risk measures — expecting depth well beyond textbook definitions.
Candidates are given a practical valuation case, such as determining the correct method to value a mining company with no terminal value that must be projected to end of reserves, and are asked to explain how they would forecast cash costs at a detailed, model-mechanics level.
An unexpected coding question is posed at the end of the second round, such as writing code to determine the day of the week for any given future date, testing basic programming ability within an otherwise finance-heavy interview context.