Deloitte Data Analyst interview typically runs 4 rounds: recruiter call, communication test, technical interview, and final interview. Timeline is about 3-8 weeks, with resume-heavy screening and live coding.
$75K
Avg. Base Comp
$125K
Avg. Total Comp
4-5
Typical Rounds
3-6 weeks
Process Length
We've seen a clear pattern in Deloitte's Data Analyst interviews: they care less about polished theory and more about whether you can defend the story on your resume. Multiple candidates reported deep follow-ups on past projects, from the models they chose to the tools they listed, and the pressure came from the specificity of those questions. If you mention NLP, ML, Excel, or Python, expect the conversation to stay anchored there until the interviewer is satisfied that you actually used those tools and understand the tradeoffs behind them.
A recurring theme is that Deloitte is testing for practical communication under scrutiny. One candidate described an early recorded response that felt like a short self-introduction and communication check, while another noted a communication test before the technical discussion. That emphasis carries into the technical conversation itself: candidates were asked to explain why they chose SBert over BERT, how they evaluated whether a model met the objective, and even to connect their work to broader domain knowledge like healthcare. The non-obvious make-or-break factor here is not just getting the right answer, but showing that your answer is grounded in real experience and that you can move comfortably from resume bullet to technical detail without losing the thread.
Synthetized from 2 candidates reports 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.
My interview process started with a digital interview after I had applied, and it came about two weeks later. That first step was recorded, and I was told it could be recorded twice, with the responses reviewed by teams rather than AI. The main prompt was pretty open-ended: I had to talk about something outside of my resume, so it felt more like a short self-introduction and communication check than a technical screen.
After that, I moved into a technical round that was centered on my past projects and the details on my CV. The interviewer pushed for a deep explanation of the work I had done before, and I quickly realized they expected me to know my resume very well. There were also SQL questions mixed in, along with situational and case-based questions. In my case, the SQL portion included standard problem-solving topics like joins, group by, and subqueries, plus questions about handling large datasets and optimizing queries. I was also asked some basic Python and pandas questions, along with data cleaning concepts and the difference between INNER JOIN and LEFT JOIN.
What stood out to me was that the interview was not just about coding or SQL in isolation. They also asked about general healthcare topics, what I did in college, and even specifics from my CV such as Excel and other tools listed there. The overall difficulty was moderate, but it felt tougher because the interviewer expected strong command of both the technical basics and the story behind my past work. If you couldn’t explain your projects clearly or answer follow-up questions confidently, it seemed like that would hurt your chances quickly.
I didn’t get an offer from this process. My main takeaway is to know every line of your resume and be ready to explain your projects in depth, not just at a high level. For prep, I’d focus on SQL fundamentals, especially joins and subqueries, and make sure you can discuss your past work and any tools you listed on your CV without hesitation.
Prep tip from this candidate
Know every line of your resume and be ready to explain your past projects in depth, because the technical round leaned heavily on CV details plus follow-up questions. Also review SQL joins, group by, subqueries, and basic pandas/data cleaning so you can answer the technical add-ons confidently.
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 | |
|---|---|
| Raining in Seattle | |
| Bagging vs Boosting | |
| Using R Squared | |
| Hurdles In Data Projects | |
| Missing Housing Data | |
| Find Duplicate Numbers in a List | |
| Assumptions of Linear Regression | |
| FAQ Matching | |
| Classification and Regression | |
| Bias vs. Variance Tradeoff | |
| Swap Variables | |
| Data Preparation for Imbalanced Data | |
| Multicollinearity in Regression | |
| String Palindromes | |
| Youtube Recommendations | |
| Simple Explanations | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Data Cleaning Experiences | |
| Linear vs Logistic Regression | |
| Experiment Validity | |
| Revenue Retention | |
| Sort Strings | |
| Spam Classifier | |
| Overfit Avoidance | |
| Slow SQL Query | |
| Algorithm Reliability | |
| Stakeholder Communication | |
| Xgboost vs Random Forest |
Synthesized from candidate reports. Individual experiences may vary.
After applying, candidates wait roughly two weeks before hearing back. Deloitte uses this stage to shortlist applicants for the next steps based on their resume and background.
A recruiter call covers basic introductory questions about your background, skills, and education. In some cases, candidates are also told whether they will need to complete an additional communication assessment before the technical round.
Shortlisted candidates may be asked to complete a Versant communication test before moving forward. The test is AI-evaluated, with quick rejection if you fail and no immediate response if you pass.
This virtual round focuses heavily on your resume, past projects, and technical fundamentals. Interviewers ask deep follow-ups on tools, models, and choices you made, along with SQL topics like joins, group by, subqueries, query optimization, and handling large datasets, plus Python, pandas, and data cleaning questions.
Candidates are asked to solve several live Python problems in a shared online compiler while being observed. Questions include array and string manipulation, finding duplicates, merging arrays, and identifying unique elements, with brief time to think before coding.