How Deloitte fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
Deloitte case study interviews are a critical component of the consulting recruitment process. Understanding the process helps you prepare effectively. Case Study Types: - Market Sizing: Estimate market size for a product or service - Profitability Analysis: Analyze revenue, costs, and profitability - Business Strategy: Develop strategies for growth, market entry, or…
Eligibility (from student reports): 6.0 CGPA in Class 10, Class 12, and every semester of graduation (the “60-60-60 rule”).
Fresher package ballpark (from student reports): Analyst: ₹6-9 LPA . Confirm on your offer letter.
How to use this page
Read the round table first, then the experiences. Practise the coding patterns with edge cases, and keep one clear story each for ownership, conflict, and a project failure.
Round
Duration
What they test
Online Aptitude Test
60-90 min
Quant, logical, verbal
Group Discussion (if conducted)
20-30 min
Current affairs / business topic
Technical Interview
30-45 min
SQL, OOPs, projects, basics
HR Interview
20-30 min
Communication, client readiness
Profile: B.Tech CSE, ~8.0 CGPA, tier-2 college, one internship, steady DSA practice
Online aptitude / written round
Sections matched what the college placement email promised, speed and accuracy mattered more than fancy tricks.
Shortlist usually followed within a week if you cleared the cutoff.
Technical interview
Coding: Simple array or string warm-up, expected approach: two pointers / hashing. They probed complexity and edge cases.
Follow-up: SQL joins and aggregations: GROUP BY, window functions.
Domain chat around SQL and OOPs . Plain explanations worked better than buzzwords.
Detailed project discussion: stack choice, hardest bug, and what you would rebuild.
HR / managerial
Why consulting?
A client-facing or communication example
Keep answers short, situation, what you did, result.
Result: Selected
What helped: Talking through the approach before coding, and connecting project work to Deloitte’s world (SQL).
Profile: B.Tech IT / ECE, ~7.2 CGPA, strong projects, average contest rating
What differed
Screening felt tighter on time; one question needed an optimised pass to stay competitive.
Later round leaned into case study : APIs, data choices, and failure modes at a fresher depth.
Warm-up: OOPs design for a small system (ATM / library), classes and relationships.
Mistakes that hurt other candidates
Coding before clarifying constraints
Treating HR as a formality
System-design jargon without a simple bottleneck story
Result: Selected after HR / managerial
Takeaway: At Deloitte, clear DSA plus a coherent story on SQL usually beats a high CGPA with weak explanation.
Simple array or string warm-up . Usually expects two pointers / hashing
SQL joins and aggregations . Usually expects GROUP BY, window functions
OOPs design for a small system (ATM / library) . Usually expects classes and relationships
Discussion on SQL and OOPs , bottlenecks, failure modes, simple APIs
Detailed project discussion, architecture, hardest bug, what you would change
Why consulting?
A client-facing or communication example
Willingness to travel
A time you influenced a decision
Clear the screening round first. Timed practice beats last-minute topic hopping.
For domain questions, explain SQL in plain language, inputs, outputs, what breaks at scale.
OOPs and SQL still open a lot of Deloitte panels. Do not skip fundamentals.
HR answers should be concrete. One story with a result beats five slogans.
If you do not know something, say so and outline how you would find out.
After technical rounds, Deloitte usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.
HR interview questions→
Common Deloitte HR questions, sample answer frames, and STAR tips.
EY · PwC · KPMG · McKinsey · BCG · Bain