Deloitte Software Engineer interviews commonly combine project deep dives, core engineering fundamentals, brief coding or assessments, and fit-focused conversations. Reported processes range from two to five rounds.
$115K
Avg. Base Comp
$160K
Avg. Total Comp
2-5 rounds
Typical Rounds
3 weeks
Process Length
Deloitte Software Engineer candidates most consistently report interviews that test whether they can explain real engineering work clearly, then move between fundamentals, practical coding, and communication. Your project walkthrough is central preparation. Be ready to describe the architecture, your module ownership, implementation choices, debugging approach, trade-offs, and the business value of work on your resume. Follow-up questions may probe APIs, authentication, databases, cloud services, Java or JavaScript concepts, and how you would improve a design.
Technical formats vary by team. Reports include online assessments, live or verbal coding, easy-to-medium array and string prompts, SQL, OOP, core Java, Python, AWS, and frontend or backend framework questions. Some candidates also encountered system-design discussions, CRUD API design, case exercises, or a practical AI project. Practice stating assumptions, edge cases, complexity, and trade-offs aloud rather than relying on a silent solution.
Later conversations often cover teamwork, ownership, conflict resolution, motivation, and why Deloitte. Prepare concise examples that show how you contributed on a project and handled challenges with others. The evidence is varied across teams, so expect the technical stack and exact sequence to differ.
Synthesized from 18 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 | |
| Cyclic Detection | |
| Hurdles In Data Projects | |
| Find Duplicate Numbers in a List | |
| Portfolio Platform Architecture | |
| Duplicate Rows | |
| Slow SQL Query | |
| Yelp-like System | |
| Swap Variables | |
| Subway Machine Learning Model | |
| Seller Type Modeling | |
| String Palindromes | |
| Digital Classroom System Design | |
| Impossibly Iterative Fibonacci | |
| Blob Indexing | |
| Text Editor With OOP | |
| Youtube Recommendations | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Justify a Neural Network | |
| Your Strengths and Weaknesses | |
| Simple Explanations | |
| Game Feature Home | |
| Closest SAT Scores | |
| Rolling Bank Transactions |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial online assessment or recruiter conversation in some processes. Assessments may combine logical reasoning, English or communication checks, basic coding, and technology multiple-choice questions; recruiter calls may cover background, role fit, and experience.
Candidates frequently report technical interviews centered on projects, architecture, module ownership, implementation choices, debugging, APIs, databases, and the technologies listed on their resume. Expect follow-up questions that ask for concrete reasoning rather than short definitions.
Reported exercises range from straightforward array, string, SQL, and OOP questions to a live LeetCode-style problem, CRUD API design, or system-design discussion. Some candidates were asked to explain complexity, edge cases, authentication, validation, and trade-offs.
Candidates report final conversations with a manager, director, partner, or HR interviewer. These may cover teamwork, leadership, conflict resolution, motivation, location or compensation, and examples of project ownership; technical follow-ups can still appear.