Deloitte Software Engineer interview typically runs 3-4 rounds: recruiter screen, technical interview, manager round, and final HR/director round. It usually takes about 2-3 weeks and is highly resume-heavy, with strong emphasis on communication and project deep-dives.
$155K
Avg. Base Comp
$190K
Avg. Total Comp
3-6
Typical Rounds
2-4 weeks
Process Length
Our candidates consistently describe Deloitte as a process that looks simple on the surface but is really testing whether you can explain your own work with precision. Multiple people said the interviewers kept returning to resume projects, backend flow, API integration, architecture choices, and the exact module each candidate owned. When answers got vague, the follow-up questions got sharper. That tells us Deloitte is not just checking whether you’ve seen the stack before; they want to know if you can defend decisions, connect technical details to business context, and stay composed when the conversation turns into a deep dive.
A recurring theme is the company’s preference for practical fundamentals over flashy algorithms. We saw repeated mentions of SQL, Core Java, OOP, Spring, JavaScript, Python basics, and lightweight coding prompts like arrays or string reversal, alongside occasional system design or JVM questions. Even when the technical bar was moderate, candidates noted that speed and clarity mattered more than complexity. The strongest responses were the ones that showed clean reasoning, not memorized theory. In several experiences, the interviewer also shifted into consulting-style questions about teamwork, leadership, and why the candidate wanted Deloitte, which reinforces that communication is part of the technical evaluation here.
The non-obvious make-or-break factor is how well you can handle unpredictable probing. Some candidates described a calm, professional tone; others ran into unusually aggressive follow-ups or surprise case-style prompts given on the spot. That variation means preparation has to go beyond rehearsed answers. Our read is that Deloitte favors candidates who can stay structured under pressure, narrate tradeoffs clearly, and move fluidly between code, projects, and client-facing thinking without losing the thread.
Synthetized from 12 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 process started with a short recruiter call, and then I moved into a technical interview that was only about 30 minutes long. That round was pretty direct: I was asked a bunch of technical questions, including Java programming topics around OOPs, SQL, and a few resume-based project questions. The interviewer also threw in an easy-to-low-medium LeetCode-style problem, so it felt like they wanted to see both fundamentals and how I think through a coding question under time pressure. After that, I had a manager round and then a case study with a lead, which was the most unusual part of the process because the case was given to me during the interview itself, so I had to think on the spot rather than prepare in advance.
The conversation in the later rounds was more behavioral and project-focused. I was asked why I was looking to transition into consulting, and there were also questions about my strengths and how I could support them. In the technical discussion, the interviewer spent a lot of time on the projects listed on my resume, including the architecture, features, challenges, and implementation details, so it helped to be ready to explain not just what I built but why I made certain choices. Overall, the interviews were on the easier to medium side and the hospitality was good, but the process still felt selective. I didn’t get an offer, and there was no response after the technical round. My main takeaway is to be very comfortable defending every line on your resume, and to practice answering consulting-transition and project-deep-dive questions clearly and concisely.
Prep tip from this candidate
Be ready for a live case study handed to you during the interview, and practice explaining your resume projects in depth, especially architecture, implementation choices, and challenges. Also review Java OOPs, SQL, and a short easy-to-medium LeetCode problem since those came up together in the technical round.
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 | |
| Cyclic Detection | |
| Hurdles In Data Projects | |
| Find Duplicate Numbers in a List | |
| Yelp-like System | |
| Swap Variables | |
| Subway Machine Learning Model | |
| String Palindromes | |
| Seller Type Modeling | |
| Impossibly Iterative Fibonacci | |
| Text Editor With OOP | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Simple Explanations | |
| P-value to a Layman | |
| Sort Strings | |
| Slow SQL Query | |
| Stakeholder Communication | |
| Testing Constraints | |
| Creating Companies Table | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Customer Orders | |
| String Shift | |
| Comments Histogram |
Synthesized from candidate reports. Individual experiences may vary.
Many candidates begin with an online assessment sent by email or through the application portal. It typically includes aptitude or logical reasoning questions plus basic coding, and in some tracks also includes Java, SQL, React/JS, database MCQs, or simple language questions.
A recruiter or HR conversation usually follows and focuses on your background, experience, and motivation for Deloitte. Expect questions about teamwork, leadership, why Deloitte, and whether your experience matches the role or stack.
The first technical round is often resume-heavy and practical rather than highly algorithmic. Interviewers commonly ask about projects, backend flow, API integration, SQL, Java or Python fundamentals, OOP, debugging, and one easy-to-medium coding problem or live coding exercise.
This round goes deeper into your CV, project architecture, and how you think through technical tradeoffs. Candidates reported questions on Spring, JVM, system design basics, AWS, SQL joins and aggregates, and behavioral prompts about communication, conflict, and working in teams.
Some candidates receive an on-the-spot case or estimation exercise during the interview itself. Examples included market sizing, profitability diagnosis, or an unexpected business-style case given live, with the interviewer looking for structured thinking and clear communication.
The final round is with a director, senior consultant, lead, or partner and is often the most probing stage. It combines behavioral depth, project deep-dives, and follow-up questions that can get very detailed, along with occasional curveball estimation or personal questions.