HR interview questions
Common Deloitte HR questions, sample answer frames, and STAR tips.
Deloitte Interview Experiences
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’s Analyst/technology fresher process typically runs 4 stages: an Online Aptitude Test, a Group Discussion where conducted, a Technical Interview (SQL, OOPs, projects), and an HR Interview. Deloitte’s separate consulting/strategy track can include case-study interviews - if you’re prepping for that track specifically, expect market-sizing, profitability, and business-strategy prompts instead.
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.
Round-wise process
Section titled “Round-wise process”| 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 |
Real interview experiences
Section titled “Real interview experiences”Experience 1: Analyst, on-campus 2023
Section titled “Experience 1: Analyst, on-campus 2023”Published GeeksforGeeks write-up. Five students from the drive received offers, this candidate among them.
Round 1: resume shortlisting - most applicants cleared this stage.
Round 2: online assessment
- Sections: verbal reasoning, aptitude, computer-science fundamentals, and two easy-to-medium coding questions.
- Each section had its own cutoff - clearing on total marks was not enough. Only 14 candidates qualified.
Round 3: combined technical and HR interview (~30 min)
- Self-introduction, then straight into the skills listed on the resume.
- One medium-difficulty coding problem with roughly 10 minutes to solve it, followed by questions on the approach taken.
- Final-year project discussion.
Result: Selected.
What it shows: a single short round decides it. There is no room to warm up - the interviewer moves from introduction to resume to code inside half an hour.
Experience 2: the recurring campus pattern
Section titled “Experience 2: the recurring campus pattern”Consolidated from several published Deloitte campus and off-campus write-ups, because the format varies by year, role (Analyst, Associate Analyst, Business Technology Analyst) and campus.
- The aptitude test is often on AMCAT. One reported configuration: 75 minutes total, with logical reasoning at 25 questions in 25 minutes and quantitative at 25 questions in 35 minutes, plus verbal ability. Sectional timing means you cannot bank time from an easy section.
- Eligibility is usually stated as the “60-60-60 rule” - 60% or 6.0 CGPA in class 10, class 12, and graduation, with some drives quoting 6.5. Backlog rules vary by cycle.
- A group discussion appears in some drives and not others. Where it runs, topics are current-affairs or business-oriented and the panel is watching whether you let others speak.
- The technical content is fundamentals, not algorithms: OOP concepts, SQL queries, and whatever languages or tools you listed. Reported coding questions stay easy to medium.
- Your resume is the question bank. Multiple write-ups say almost every question traced back to something written on it - the most repeated advice is to know your resume by heart and not list anything you cannot defend.
- Communication is weighted heavily because the role is client-facing. Several accounts credit confidence and clarity over technical depth for the final call.
Sources for this section
- Deloitte Interview Experience for Analyst (On-Campus) 2023 - GeeksforGeeks
- Deloitte Interview Experience for Fresher - GeeksforGeeks
- Deloitte USI Interview Experience for Analyst (On-Campus 2021) - GeeksforGeeks
- Deloitte Interview Experience for Analyst (On-Campus) 2022-23 - GeeksforGeeks
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- 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
HR / behavioural
Section titled “HR / behavioural”- Why consulting?
- A client-facing or communication example
- Willingness to travel
- A time you influenced a decision
Practical tips for Deloitte
Section titled “Practical tips for Deloitte”- 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.
HR interview
Section titled “HR interview”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.