Deloitte Software Engineer interviews commonly combine an assessment or screening with resume-driven technical discussion, coding, and behavioral or manager conversations.
$128K
Avg. Base Comp
$168K
Avg. Total Comp
3 rounds
Typical Rounds
1-3 weeks
Process Length
Deloitte Software Engineer candidates describe several tracks, especially campus hiring, so the sequence and technical depth vary. The most consistent theme is a resume- and project-driven technical conversation: candidates were asked to explain what they personally built, the technologies they used, implementation decisions, and challenges. Prepare a concise walkthrough that distinguishes your contribution and connects it to a clear result.
Early stages may include aptitude, verbal or logical-reasoning questions, programming fundamentals, and coding. Reported coding tasks ranged from reversing an array and finding its largest value to easy-to-medium data-structures-and-algorithms problems. Practice narrating the approach, complexity, and tradeoffs rather than silently coding.
Technical content reflects the role track. Java-oriented interviews covered OOP, collections, streams, multithreading, Spring Boot, REST APIs, microservices, and database design. Other candidates reported Python fundamentals or machine-learning concepts and an open-ended pricing case. Review the technologies on your own resume deeply instead of treating every reported topic as a universal requirement.
Behavioral and manager conversations tested motivation, teamwork, communication, challenges, career goals, client interaction, and fit. Some campus processes also included a group discussion or JAM-style stage. Prepare specific examples, know why the role interests you, and be ready to move between technical details and clear discussion of your experience.
Synthesized from 94 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 first technical round was easier than I expected: it focused on my project work and basic Salesforce concepts rather than difficult coding. After an initial phone call with the HR recruiter, I spoke with a technical interviewer who asked me to walk through my experience and explain items such as record types, objects and fields, and the difference between profiles/permissions and roles. I was also asked about defect priority versus severity.
The second technical round was with a manager and was much more scenario-driven. The questions centered on how I would handle a Service Cloud situation, so I found it more useful to explain my reasoning and how the platform features fit the business need than to give memorized definitions. The overall process was straightforward and conversational, with the manager probing practical knowledge instead of trying to catch me out. After the technical discussions, there was a salary-negotiation round. I received and accepted the offer.
For preparation, I would make sure you can clearly explain your own Salesforce project work, including the objects, fields, permissions, and roles involved. Also review Service Cloud scenarios and be ready to distinguish defect priority from severity with a practical example.
Prep tip from this candidate
Be ready to explain your Salesforce project work in detail, especially objects, fields, permissions versus roles, and Service Cloud scenarios. Review defect priority versus severity with a practical example.
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 | |
| Find Duplicate Numbers in a List | |
| Hurdles In Data Projects | |
| Portfolio Platform Architecture | |
| Duplicate Rows | |
| FAQ Matching | |
| Skyscanner Partner ETL | |
| Slow SQL Query | |
| Yelp-like System | |
| Data Pipelines and Aggregation | |
| Swap Variables | |
| 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 | |
| Youtube Recommendations |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report online assessments with aptitude, reasoning, verbal or English questions, programming fundamentals, and coding. Reported coding difficulty ranges from simple implementation tasks to medium problems, while some experienced candidates instead began with recruiter screens.
Technical interviewers often asked candidates to walk through projects, technology choices, implementation decisions, deployment, and challenges. Be ready to distinguish what you personally built and explain why you chose a particular approach.
Candidates report Java, SQL, OOP, Spring Boot, REST APIs, Python, cloud, Salesforce, or core CS questions alongside live or assessment-solution coding. The exact stack varies, but clear reasoning and practical examples recur.
Candidates in some processes report a group discussion, case-study discussion, or live case. Topics ranged from a business scenario to communicating a viewpoint; this stage may occur before or alongside later interviews.
Candidates report conversations about why Deloitte, career goals, teamwork, challenges, location flexibility, and communication. Some technical processes also included a manager discussion that stayed focused on projects and practical scenarios.
