Deloitte Business Analyst interviews typically combine an HR/motivational screen, one or more case-study or scenario rounds, and light technical checks such as SQL joins or OOP basics, with some campus tracks starting with an online aptitude test; reported timelines run up to about six weeks.
$97K
Avg. Base Comp
$120K
Avg. Total Comp
2-5 rounds
Typical Rounds
4-6 weeks
Process Length
Deloitte's Business Analyst interviews don't follow one fixed script, but the reported loops share a recognizable shape: an initial screen, a conversational HR round about motivation and background, and at least one case or scenario exercise, often finishing with a manager, senior leader, or partner. Some campus-track candidates start with an online aptitude test covering logical, quantitative, and English reasoning. One test also included two coding questions, the second at medium difficulty, so time management matters.
The case-study round is where preparation pays off most. Formats range widely:
One interview also asked the candidate to watch a video and propose a project plan based on it, which rewards quickly synthesizing information and thinking on your feet.
Technical depth is generally light. Expect a SQL question on joins, or a request to explain object-oriented programming with an example on more technology-focused tracks. Behavioral questions carry real weight. Prepare a sharp answer to why Deloitte rather than another Big Four firm, plus specific stories about teamwork, friction, weaknesses, a time you took a stand, and a project issue you handled. Timing varies: one candidate waited about two weeks after the final round, while others describe five to six weeks end-to-end with stretches of silence. Plan on patience and a professional follow-up after about a week without news.
Synthesized from 37 candidate 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.
The process was surprisingly varied depending on which stage I entered. I started with an online psychometric test, which felt like a filter more than anything—pattern recognition and personality assessment. After that came a job simulation exercise that gave me a realistic feel for what the role might involve. Then I moved into the assessment centre, where I was asked to prepare a short presentation on a topic they gave me in advance. The topics weren't overly technical; mine was about problem-solving in a business context, and they provided guidance beforehand so you're not completely in the dark. The presentation lasted maybe 20 minutes, followed by a one-on-one interview with a director. During the interview, they dug into behavioral territory—they asked me to describe a time I'd come up with a creative solution to a problem, which was pretty open-ended. They seemed interested in how I think and approach challenges rather than textbook knowledge. Throughout, I also did case study exercises based on real-life scenarios, like ERP and CRM situations, where you had to think through the business implications. The whole thing felt less like a grilling and more like they were genuinely trying to see if I'd fit. For fresh graduates, there wasn't much emphasis on deep technical knowledge—just the basics around your academic background and communication skills. A manager interview came up as well where they talked through your career pathway and why you wanted this role. The timeline was quick: application one day, screening call the next week, and onboarding discussion within a couple of weeks after that. It all moved fairly smoothly.
Prep tip from this candidate
Be ready to discuss a time you solved a problem creatively, and don't worry too much about technical depth—they care more about how you think and communicate your ideas. Prepare to articulate your interest in audit and Deloitte specifically.
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 | |
|---|---|
| Bagging vs Boosting | |
| Size of Joins | |
| Cyclic Detection | |
| Precision and Recall | |
| Hurdles In Data Projects | |
| Assumptions of Linear Regression | |
| Duplicate Rows | |
| Using R Squared | |
| Classification and Regression | |
| Slow SQL Query | |
| Swap Variables | |
| Data Pipelines and Aggregation | |
| User Event Data Pipeline | |
| Multicollinearity in Regression | |
| String Palindromes | |
| Seller Type Modeling | |
| Open Source Reporting Pipeline | |
| Impossibly Iterative Fibonacci | |
| Yelp-like System | |
| Scalable Data Pipelines | |
| Youtube Recommendations | |
| Digital Classroom System Design | |
| Client Solution Pushback | |
| Simple Explanations | |
| Why Do You Want to Work With Us | |
| Justify a Neural Network | |
| Merchant Acquisition | |
| Your Strengths and Weaknesses | |
| Data Cleaning Experiences |
Synthesized from candidate reports. Individual experiences may vary.
Some candidates, particularly on campus tracks, report an online aptitude test covering logical and quantitative reasoning. In one case it also had an English section plus two coding questions, one easy and one medium. Others start directly with an online or HR interview instead.
Candidates describe an HR conversation covering academic background, work experience, five-year goals, and why Deloitte over other firms. One candidate's HR interview lasted about 30 minutes and felt conversational and low-pressure, but a clear, consistent story about career direction still matters.
Many candidates report at least one case-style round. Formats range from a guesstimate discussed alongside HR questions, to a 30-minute case analysis, to a detailed IT and cloud strategy case solved independently and then presented to interviewers and other candidates. One candidate was asked to discuss a video and propose a project plan based on it.
Technical questions appear in some loops but are generally light. One candidate was asked a SQL question on joins. Another had a technical interview asking them to explain object-oriented programming with an example and discuss their coding knowledge. A third discussed foundational technology knowledge and the phases of an IT transformation project.
A closing round with a manager, senior leader, or partner is common, covering background, career trajectory, and potential. In one loop the partner round was a second, more probing case interview, alongside questions on teamwork, weaknesses, and a time the candidate took a stand.
Reported timelines range from a few weeks to about six weeks end-to-end. One candidate heard back about two weeks after the final round, while another described communication going quiet for stretches. A professional follow-up after about a week of silence is reasonable.
