Candidates describe Deloitte software engineer interviews as project-focused conversations with Java, OOP and SQL fundamentals, short coding questions, and behavioral or fit discussions, with reported totals of three or four rounds.
$98K
Avg. Base Comp
$120K
Avg. Total Comp
3-4 rounds
Typical Rounds
3 weeks
Process Length
Candidates who interviewed for Deloitte software engineer roles describe a process built around your resume and projects more than around hard algorithm puzzles. One candidate who accepted an offer was asked which module they had worked on and what exactly they did there. Another, who did not get an offer, faced interviewers pressing on the architecture, features, challenges and implementation details of resume projects. A third was asked to walk through the approach behind their online assessment solution before a live coding problem.
The technical questions reported are mostly fundamentals. Java, OOP and SQL come up repeatedly. Individual candidates also mention AWS basics, Python list versus tuple, HTML and JavaScript, database design, or theoretical Python and data structure questions. Coding prompts are described as short, such as reversing a string, an easy array question, or a single easy-to-medium LeetCode-style problem. Reported round counts run from three to four. A typical sequence is an assessment or recruiter step, one or two technical interviews, and a manager, HR or director conversation.
Fit questions are straightforward:
Experiences are not uniform. One candidate was handed a case study by a lead during the interview. Another had a technical interview switch from the described format to a live screen share. A couple of reports mention slow or missing follow-up. The safest preparation is to be able to explain every line of your resume and answer fundamentals quickly.
Synthesized from 158 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.
My process started with an online assessment on Codility, which I completed before anything else. The first real round was a 30-minute technical screening, followed by a 45-minute system design interview. The design round was the longer of the two, so I'd plan your energy accordingly. The final stage was a second round split into two 30-minute parts: a behavioral interview and a leadership interview. Since both were short, I'd recommend having concise stories ready that show ownership of your work and how you've led or influenced others. I did not receive an offer, but the process was clearly structured, and the Codility assessment was the first filter I had to get through.
Prep tip from this candidate
Expect Java, Spring Boot, and distributed systems topics, along with DSA problems built on strings and Java streams. Prepare short, structured behavioral and leadership stories, since the final round was split into two 30-minute interviews.
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 | |
| Raining in Seattle | |
| Maximum Profit | |
| Bagging vs Boosting | |
| Size of Joins | |
| Real-Time Transaction Streaming | |
| Normalize Grades | |
| Cyclic Detection | |
| Skyscanner Partner ETL | |
| Precision and Recall | |
| Find Duplicate Numbers in a List | |
| Hurdles In Data Projects | |
| Portfolio Platform Architecture | |
| Duplicate Rows | |
| FAQ Matching | |
| Slow SQL Query | |
| Data Pipelines and Aggregation | |
| Swap Variables | |
| Yelp-like System | |
| User Event Data Pipeline | |
| Subway Machine Learning Model | |
| Seller Type Modeling | |
| String Palindromes | |
| Digital Classroom System Design | |
| Blob Indexing | |
| Impossibly Iterative Fibonacci | |
| Text Editor With OOP | |
| Scalable Data Pipelines | |
| Open Source Reporting Pipeline |
Synthesized from candidate reports. Individual experiences may vary.
Some candidates began with an online assessment. One described computer-based math, English grammar, logical reasoning and a few simple coding questions, and was later asked to walk through the submitted solution in the technical interview. Another received an assessment by email before an HR conversation, and one reported a behavioral multiple-choice test.
Candidates describe an early recruiter or HR step. One had a short recruiter call before the technical interview, and another had an HR conversation about their background, experience and teamwork. Why Deloitte and long-term goals are common fit questions, so prepare concise answers on motivation.
Technical rounds were centered on the resume. Candidates were asked about modules worked on, tech stack, architecture and challenges, plus Java, OOP and SQL. Others reported AWS basics, Python list versus tuple, HTML and JavaScript, database design, or theoretical Python and data structure questions. Coding was short: reversing a string, an easy array question, or an easy-to-medium LeetCode-style problem. One technical round lasted about 30 minutes, and one used a live screen share.
Final stages differed by candidate. Reports include a manager round, a case study given live by a lead, a director round, and a final round with HR and an engineering manager on fit and location. One candidate had a final HR round about salary. Be ready to think aloud on an unfamiliar problem.
