Candidates describe Deloitte software engineer interviews as project-heavy, with Java, SQL and OOP fundamentals, light coding, and manager, HR or director conversations. Rounds and format vary by team.
$112K
Avg. Base Comp
$138K
Avg. Total Comp
3-5 rounds
Typical Rounds
3 weeks
Process Length
Candidates describe the Deloitte software engineer interview as a deep dive into your own projects, backed by Java, SQL and OOP fundamentals, rather than a heavy algorithm screen. Many accounts open with a self-introduction and move straight to the resume: which module you owned, the stack behind it, the architecture and the challenges you hit. Follow-ups tend to ask why you made each choice, so vague answers get pushed on.
On the technical side, Java and object-oriented concepts such as polymorphism come up repeatedly, along with SQL. Spring Boot and JVM questions appear in some reports, and one candidate's first round was almost entirely Spring Boot with no coding at all. Others mention AWS basics, JavaScript, React or Node.js, and one candidate was asked about Java design patterns and core principles.
Coding is usually short: a single LeetCode-style problem, easy array or string exercises, a stock-profit question, or two simple Python DSA problems. Some candidates begin with an online assessment of aptitude, logical reasoning and basic coding, and one was asked to explain their submitted solution in the technical interview.
Later rounds are conversational: manager, HR or director discussions about teamwork, ownership and why Deloitte. One candidate was handed a case study during the interview, and another described a partner conversation of about 1 hour 20 minutes with heavy probing. Outcomes are mixed, with both offers and rejections, and formats vary by team, so confirm the structure with your recruiter.
Synthesized from 162 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.
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 | |
| Swap Variables | |
| Yelp-like System | |
| Data Pipelines and Aggregation | |
| User Event Data Pipeline | |
| Subway Machine Learning Model | |
| Seller Type Modeling | |
| String Palindromes | |
| Digital Classroom System Design | |
| Impossibly Iterative Fibonacci | |
| Blob Indexing | |
| Text Editor With OOP | |
| Scalable Data Pipelines | |
| Open Source Reporting Pipeline |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates report starting with an online assessment. One described math, English grammar, logical reasoning and a few simple coding questions, and another aptitude plus coding. That same first candidate was later asked to walk through the submitted OA solution in the technical interview, so keep your reasoning clear.
Some candidates report a short recruiter or HR call early on, covering background, experience and teamwork. Others place HR at the end of the process, so the order appears to vary by team. Expect basic questions such as why Deloitte and, in one report, whether you are comfortable with the location.
Technical rounds often begin with an introduction and a project walkthrough covering stack, architecture and challenges. Questions then move into Java and OOP, SQL, Spring Boot, AWS or JavaScript basics. Coding is typically brief, such as one easy-to-medium problem or an array or string exercise. One candidate's first round was all Java and Spring Boot with no coding.
Later rounds are reported as more conversational. Topics include teamwork, communication, ownership and, for one candidate, moving into consulting. One candidate received a case study from a lead during the interview, and another had a director round. Interviewer style varies, and one candidate described a long, probing partner conversation.
