Skip to content
Interview Questions

Deloitte Interview Experience 2026

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.

How Deloitte differs from product-only campus loops

  • Analyst / consulting-flavoured campus paths emphasise communication and case clarity alongside tech basics.
  • HashedIn by Deloitte is a different engineering-heavy pipeline (coding + design) from classic Deloitte Analyst.
  • Role confirmation matters: preparing only LeetCode for Analyst, or only GD for HashedIn SDE, mismatches the bar.
  • HR/behavioural weight is typically higher than at pure product startups.

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

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.

Takeaways

  • What decided it: Clearing every OA section cutoff, then defending resume skills and a medium coding problem inside a ~30 min combined tech+HR slot
  • Common fail: Strong overall OA score but failing one sectional cutoff, or warming up too slowly in the short interview
  • How to practise: Timed sectional AMCAT/NLA mocks; 60-second proof stories for every resume line; one medium DSA with approach narration under 10 minutes

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.

Takeaways

  • What decided it: Sectional aptitude discipline plus resume-backed SQL/OOP answers delivered with client-ready communication
  • Common fail: Listing tools you cannot defend, or dominating a GD so the panel marks listening poorly
  • How to practise: Know the resume cold; write one join+aggregation SQL on paper; rehearse GD turn-taking; practise Why Deloitte for a combined panel

Sources for this section

Experience 3: HashedIn by Deloitte - SDE intern + FTE, on-campus 2024

Published GeeksforGeeks write-up. Seven students received offers from this campus batch.

Round 1: Online assessment (~90 min) - coding and aptitude mix; details in source article.

Round 2: Technical interview 1 (~45–50 min) - friendly interviewer; internship discussion; 3–4 DSA problems, then DBMS/SQL and resume questions. Candidate reported answering all satisfactorily.

Round 3: Technical interview 2 (~70 min) - project deep-dive (Next.js e-commerce capstone); SQL vs NoSQL; write queries in both paradigms; graph DSA problem; restaurant table-booking database design (entities, relationships, constraints).

Round 4: HR / managerial (~20 min) - motivation, strengths, what you bring to HashedIn, location, common HR prompts.

Result: Selected.

Source: GeeksforGeeks - HashedIn by Deloitte SDE Intern + FTE 2024

What it shows: Subsidiary loops can be more DSA-heavy than classic Analyst USI - multiple coding problems plus schema design in one day.

Experience 4: 2026 consolidated campus pattern (synthesized from public 2026 guides)

Not one single candidate diary - pattern described across FacePrep, Jobaaj, and ClearRound 2026 articles. Verify against your drive mail.

Stage What candidates report
Profile screen Resume + eligibility (60-60-60, backlogs, gap rules)
NLA (~90 min) English, quant, logical, technical MCQs; two coding problems; sectional submit
Single interview Technical + HR combined - project/resume, 1 easy DSA, SQL/OOPs, Why Deloitte, relocation
Optional Versant Spoken English for some client-facing tracks

What it shows: With only one live interview, opening with a weak project story or vague “Why Deloitte?” may end the loop - no second HR chance. Prep HR answers as if they share the same timer as SQL.

Sources: FacePrep Deloitte fresher 2026, Jobaaj Deloitte India 2026, ClearRound NLA 2026

Pre-interview checklist

  • Read drive mail: NLA vs AMCAT, number of coding questions, Versant or not
  • Verify 60-60-60 (or 65%) against your marksheets - screening is automated
  • Resume = question bank: every skill line has a 60-second proof story
  • One SQL join + aggregation query written on paper without IDE
  • One easy array/string problem with two-pointer and hash explanations ready
  • STAR stories on HR page rehearsed out loud (45-minute consolidated loops leave no warm-up)
  • Confirm business line: USI Technology vs Audit/Tax vs HashedIn subsidiary

Questions that come up often

Coding / technical

  1. Simple array or string warm-up. Usually expects two pointers / hashing
  2. SQL joins and aggregations. Usually expects GROUP BY, window functions
  3. OOPs design for a small system (ATM / library). Usually expects classes and relationships
  4. Discussion on SQL and OOPs, bottlenecks, failure modes, simple APIs
  5. Detailed project discussion, architecture, hardest bug, what you would change

HR / behavioural

  1. Why consulting?
  2. A client-facing or communication example
  3. Willingness to travel
  4. A time you influenced a decision

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

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.

Sample answers for high-frequency questions

Use these as frames, not scripts - interviewers probe follow-ups.

Q. Write a SQL query using joins and GROUP BY to find each department’s average salary.
A. A correct answer is SELECT d.dept_name, AVG(e.salary) AS avg_salary, COUNT(*) AS headcount FROM employees e JOIN departments d ON e.dept_id = d.dept_id GROUP BY d.dept_name HAVING COUNT(*) > 5 ORDER BY avg_salary DESC; The points interviewers check are that every non-aggregated column in the SELECT list also appears in GROUP BY, that filters on aggregates belong in HAVING while filters on individual rows belong in WHERE, and that WHERE runs before grouping so it is the cheaper place to filter. Mention that AVG silently ignores NULL salaries, which can skew the result.

Q. What is a window function and how does it differ from GROUP BY?
A. A window function computes a value over a set of rows related to the current row while keeping every row in the output; GROUP BY collapses rows into one row per group. For example SELECT emp_name, dept_id, salary, RANK() OVER (PARTITION BY dept_id ORDER BY salary DESC) AS rnk FROM employees; returns every employee alongside their rank within their department. The common functions are ROW_NUMBER (always unique), RANK (ties share a rank and leave gaps), DENSE_RANK (ties share a rank with no gaps), and LAG/LEAD for comparing against the previous or next row. Window functions are evaluated after WHERE and GROUP BY, so filtering on one requires wrapping it in a subquery or CTE.

Q. When do you use two pointers versus hashing on an array problem?
A. Two pointers works when the data is sorted or can be sorted and gives O(1) extra space - for a sorted two-sum you move the left pointer right when the sum is too small and the right pointer left when it is too large, which is O(n) after an O(n log n) sort. Hashing works on unsorted data and gives O(n) time for O(n) space by remembering values or counts already seen. The choice comes down to whether the interviewer cares more about memory or about preserving the original order and indices. State both options and the trade-off before writing code - Deloitte panels weight the approach explanation as heavily as the code.

Q. Explain inheritance and polymorphism with a class design example.
A. Inheritance lets a subclass reuse and extend a base class - an Account base class with balance, deposit, and withdraw, extended by SavingsAccount and CurrentAccount that override withdraw to apply different overdraft rules. Polymorphism means calling withdraw through an Account reference runs the subclass version, chosen at runtime via the virtual dispatch table, so an ATM class can process any account type without knowing its concrete class. Compile-time polymorphism is method overloading, resolved by signature; runtime polymorphism is overriding. The payoff is that adding a new account type needs no change to the ATM code - the Open-Closed Principle in practice.

Q. How would you design classes for a library management system?
A. Start with the entities: Book (ISBN, title, author), BookCopy (copy_id, ISBN, status) kept separate from Book because five physical copies share one title, Member, and Loan (copy_id, member_id, issue_date, due_date, return_date). Behaviour lives on a Library service class handling issue, return, and fine calculation, with an abstract Member base class subclassed by StudentMember and FacultyMember that override maxBooksAllowed and loanPeriodDays. Keep fine calculation in its own FinePolicy class so the rule can change without touching Loan. Interviewers mainly check that you separate the title from the physical copy - conflating the two is the most common mistake.

Tips from successful candidates

Assessment tips

  • Confirm the current Deloitte pattern from the drive mail before practising old papers
  • Finish one problem or section fully before starting the next
  • Revise the fundamentals listed in the round table on this page

Interview tips

  • Narrate trade-offs; expect “why” after every answer
  • Only list projects you can defend under follow-ups
  • Prepare 3-4 STAR stories for behavioural prompts

HR tips

  • Know why Deloitte, not just why the industry
  • Be clear on location / notice period / higher studies
  • Practise answers on the dedicated HR page

Sources

These links are research inputs used to map Deloitte Analyst, NLA, and HashedIn loops - not copied page mirrors. We reorganized reports into process tables, outcome notes, and prep takeaways.

Cross-check the current drive mail for timings and USI vs HashedIn track. For OA practice, see Deloitte placement papers.

Deloitte hub

HR interview questions

Placement papers

Preparation guide

Similar companies

EY · PwC · KPMG · McKinsey · BCG · Bain