Deloitte Interview Experience
Question Details
Getting placed at Deloitte was an enriching experience that involved an online coding + aptitude test and a single interview. Here's a detailed account of my journey.Prepa...
Full Details
Getting placed at Deloitte was an enriching experience that involved an online coding + aptitude test and a single interview. Here's a detailed account of my journey. Preparation Tip : I have only 2 platforms for my preparations : PrepStat & GFG. Selection Process Overview The selection process comprised: Online Coding + Aptitude Test One Interview (Focused on a programming language and projects) Online Coding + Aptitude Test Format The test was designed to assess both technical and problem-solving abilities: Online Test Aptitude Section : Prepared extensively using PrepStat, focusing on improving accuracy and time management for aptitude-based questions. Coding Section : Strengthened coding fundamentals with GeeksforGeeks (GFG), solving daily coding problems. Focused on efficiency and edge cases while practicing algorithms and data structures.
Interview Round The single interview was structured around two key aspects: 1. Programming Language The interviewer primarily focused on Java, asking about: Object-oriented programming principles. Practical applications of Java in problem-solving. 2. Projects I was asked to explain my projects, which included: React.js for creating dynamic user interfaces. JavaScript (JS) for implementing interactive functionalities. MySQL for database management. The interviewer delved into my approach to problem-solving and my understanding of integrating different technologies. Additional Topics Covered : Debugging and optimizing code snippets. Writing efficient SQL queries. Real-world application scenarios related to my projects. Leverage Resources: Used PrepStat for mock tests, aptitude preparation, and general interview readiness. Practiced coding and explored advanced concepts on GeeksforGeeks. Conclusion : The Deloitte interview process was a challenging yet rewarding experience that tested both technical expertise and problem-solving abilities. Thorough preparation using PrepStat for aptitude and GeeksforGeeks for coding ensured I was ready for each stage.
About This Question
This is a reported interview question from a deloitte interview for a eng manager role during the oa round reported in 2025.
It covers the following topics: Sql, Oop .
Difficulty rating: Hard
More Deloitte Interview Questions
About Deloitte Interview Reports
This question was reported by a candidate who interviewed at Deloitte. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Deloitte are the higher-signal extractions to take from this report.
For broader preparation context, the Deloitte interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Deloitte reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Deloitte Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Deloitte reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.