Deloitte India Interview Guide (2026)

1Snapshot, read this first#

The one thing to understand about Deloitte India: this is a client-facing services firm, not a product company.

• They are not only buying your code. They are buying someone they can put in front of a client.
• Technical skill gets you shortlisted. The way you explain, structure, and carry yourself gets you the offer.
• The interviewer is silently asking one thing through every answer: "Would I be embarrassed if this person said that on a client call?"
• Keep that question in your head and most of your prep decisions get easier.

2Getting the call (the part most guides skip)#

Deloitte India hires through three main doors, and the door you use changes everything.

Campus placements. The highest-yield path if your college is on the list.

• Per-candidate bar is lower than off-campus, because they are filling a block of seats in a day or two.
• Flow is usually online aptitude, then group or technical rounds on campus.
• Register early, clear the cutoff, and treat the pre-placement talk as a free preview of what they value.
• Sit in the front, write down the exact words the speaker uses for their values, and feed those words back in your HR round. Cheapest edge you will ever get.

Off-campus and test registration. Bulk hiring through assessment vendors.

• Deloitte runs registration drives on platforms like AMCAT, SHL, and similar.
• Watch the Deloitte careers page and trusted job boards, register with a clean resume, and finish the test window on time.
• Missing the window is the most common self-inflicted rejection. It is pure admin, so it stings twice.

Referrals and lateral. For experienced hires, a referral moves your resume to the top.

• A referral from inside the relevant service line (SAP, cloud, data) gets you seen fast.
• It does not skip the interview, but "getting seen" is half the fight at Deloitte's volume.
• Ask your referrer for the exact req ID and the hiring manager's team, then tailor your resume to that practice, not to "Deloitte" in general.

Resume rules. One page for freshers, two max for laterals.

• Lead every bullet with an action verb and a number.
• Weak: "Worked on a web project." Strong:

Built a React + Node inventory module used by 120 campus users, cutting manual stock entry time by 40%.

• Every bullet should answer three things fast: what you built, how big it was, and what changed because of it.
• If a bullet has no number, you have written a job description, not an achievement. Rewrite it.

ATS keywords. Deloitte screens at volume, so mirror the job description.

• If the role says "SAP ABAP," "SQL," "data migration," or "Agile" and you have real experience, those exact words belong on your resume, spelled the way the posting spells them.
• Do not keyword-stuff things you cannot defend.
• The technical round pulls a term straight off your resume and goes three questions deep on it. A keyword you cannot back up is a trap you set for yourself.

3The loop at a glance#

Not every candidate gets every round.

• Freshers often see aptitude, then technical, then HR.
• Consultants and laterals usually add a case or managerial discussion.

Spend your worry budget where the rejections happen.

• Freshers lose sleep over DSA, then get knocked out at aptitude timing or the "why consulting" question.
• The real failure points are sections 4, 6, and 8 below, not a hard graph problem.

4The aptitude and technical rounds, patterns not problems#

Deloitte's early filter is an aptitude-style assessment, not a competitive-programming gauntlet. Know the sections and you clear it comfortably.

Quantitative aptitude. Standard school math under speed pressure.

• Percentages, ratios, profit and loss, time-speed-distance, time and work, averages, permutations and combinations, probability, number systems.
• Nothing exotic. Speed and accuracy under time pressure are the real test.
• Memorize fraction-to-percent conversions (1/7 is about 14.28%, 1/8 is 12.5%) and squares up to 30, so you never burn seconds on arithmetic.

Logical reasoning. Pattern work plus puzzles that eat your clock.

• Series, coding-decoding, blood relations, seating arrangement, syllogisms, data arrangement, simple puzzles.
• Practice under a timer so you learn to skip and return.
• Seating-arrangement and puzzle sets are time sinks. If a puzzle has not cracked in 90 seconds, flag it and come back. Three medium questions beat one hero puzzle.

Verbal ability. Consulting runs on written English, so this one genuinely counts.

• Reading comprehension, sentence correction, para-jumbles, synonyms and antonyms, error spotting.
• Deloitte reads your grammar here as a proxy for the emails you will one day send a client. Treat it as a work sample, not a formality.

Pseudocode and basic programming (track-dependent). Read short code, predict the output.

• Many assessments include output-prediction or bug-spotting: arrays, strings, loops, conditionals, simple recursion.
• Developer tracks may add a short hands-on coding task.
• Classic traps: off-by-one loop bounds, post-increment versus pre-increment, integer division truncating a decimal, a variable that updates inside a nested loop.
• Trace with real values on scratch paper. Do not eyeball it.

How to practice. Timed sets, not endless untimed drills.

• For aptitude, do one full mock section every day in the final two weeks.
• Review every single wrong answer and write down why you missed it: concept gap, careless, or too slow.
• For pseudocode, trace code by hand on paper until predicting output feels automatic.
• Untimed practice builds false confidence. The real test punishes hesitation.

How to win the technical round. Narrate, and be honest when you do not know.

• Talk your reasoning out loud: "I'll trace this loop with i = 0, 1, 2."
• Interviewers reward a clear thought process even when the final answer slips, because that process is exactly what they will put in front of a client.
• If you do not know something, say so plainly, then show how you would find out: "I haven't used that in production, but based on how X works I'd expect Y, and I'd confirm in the docs."
• Deloitte values honesty and learnability over bluffing. A confident wrong answer reads as a future client-call disaster.

5CS fundamentals and your track#

For freshers, round two is a fundamentals interview. For laterals, it is a deep-dive into your service line. Prepare both the general base and your specialty.

The depth tracks your experience.

• A fresher gets definitions and one example.
• A two-year lateral gets "walk me through how you'd actually migrate that in a live client system."

General CS base (every tech candidate):

• DBMS: normalization, keys, joins, indexing, ACID, writing SQL (joins, GROUP BY, subqueries). SQL is asked constantly, be fluent. Be ready to explain why an index speeds up reads but slows down writes, and clustered versus non-clustered, because "what is an index" always has a follow-up.
• OOP: the four pillars with real examples from your own projects. "Polymorphism is many forms" scores nothing. "I used an interface so my payment code called charge() without caring if it was card or UPI" scores the point.
• OS: process versus thread, deadlock, scheduling basics, memory and paging at a high level. Know the four deadlock conditions well enough to name one you would break to prevent it.
• Networking: OSI/TCP-IP layers, HTTP versus HTTPS, DNS, what happens when you type a URL. The URL question is a favorite because it shows how far your understanding stretches. Rehearse it as a 60-second story from DNS lookup to rendered page.
• Data structures: arrays, strings, linked lists, stacks, queues, hashing, trees at a conceptual level. Be able to say when you reach for a hash map versus a sorted array, not just define both.

Track-specific depth:

• SAP: module basics (ABAP, FICO, MM, SD depending on the posting), transport requests, data dictionary. Know how a change moves from a dev system to production through a transport request, because that is the daily reality of the job.
• Java / full-stack: collections, exception handling, Spring basics, REST APIs, a front-end framework if claimed. Be crisp on ArrayList versus LinkedList, checked versus unchecked exceptions, and what @Autowired actually does.
• Data / analytics: SQL joins and window functions, ETL concepts, one BI tool, Python/pandas basics. Be able to write a ROW_NUMBER() or RANK() query on the spot. Window functions separate the people who learned SQL from the people who copy SQL.
• Cloud: core AWS/Azure services, IaaS versus PaaS versus SaaS, basic deployment flow. Name two or three services you have actually touched (S3, EC2, Lambda, or Azure equivalents) and what you used each for.

The project deep-dive. Expect "walk me through your biggest project."

• Be ready to explain the problem, your specific contribution, the tech choices and why, one hard bug you fixed, and what you would do differently.
• Say "I" when you mean you and "we" when you mean the team. Never claim the whole project if you owned one module, because the follow-ups expose it fast.
• Anything on your resume is fair game, so only list what you can defend.
• Prep a two-minute version and a ten-minute version of each project, since you will not know in advance how far they want to go.

6Behavioral and culture fit#

Deloitte's culture centers on its Shared Values: integrity, commitment to each other, serving clients with distinction, and strength from cultural diversity, plus the idea of being "as one" across teams.

What this looks like in the room.

• Questions about teamwork, handling pressure, owning mistakes, and whether you actually want consulting (not just any job).
• The subtext is always the same: are you someone the firm can trust in front of a client and inside a team under deadline stress.

Write four or five STAR stories before you walk in. Situation, Task, Action, Result.

• Cover a teamwork conflict, a tight deadline, a failure you learned from, a time you led, and a time you handled an unhappy stakeholder or client.
• Always land the Result with a number or concrete outcome.
• Keep each story to about 90 seconds spoken. If you cannot, you are narrating, not answering.

Common prompts: "Tell me about yourself," "Why Deloitte and why consulting," "Describe a conflict in a team project," "A time you failed," "How do you handle ambiguity," "Where do you see yourself in five years."

One full worked STAR example:

S, In my final-year team project, two members stopped contributing a week before the demo, and our booking app's payment flow was still broken. T, As the unofficial lead, I had to get a working demo ready without alienating the team. A, I split the remaining work into small, clearly owned tasks, took the payment integration myself since I knew the API, and ran two short daily check-ins so no one felt ambushed. I paired with one struggling teammate instead of taking over his part. R, We shipped a fully working demo on time, scored the highest in our batch (18/20), and the teammate I paired with later told me it was the first time he understood REST APIs. I learned that structure and clear ownership beat last-minute heroics.

Why that example works: it is calm, specific, honest about the team, and ends with both a number and a lesson. That is exactly the register Deloitte wants.

On "why Deloitte / why consulting," do not wing it.

• A good answer names something only consulting gives you (variety of clients and industries, fast exposure, learning across domains).
• Then it ties that to one real thing about Deloitte you can point to: a service line you want, a project type, the scale of the firm.
• A bad answer could be pasted onto any company's name.
• The test: if your reason survives someone swapping "Deloitte" for "Accenture," it is not an answer yet.

7Your prep plan#

4-week plan

• Week 1: Lock aptitude basics, one quant topic plus one reasoning topic per day. Refresh SQL and OOP.
• Week 2: Full timed aptitude mocks every other day. Deep-dive your track (SAP/Java/data/cloud). Write your project story.
• Week 3: CS fundamentals pass (DBMS, OS, networking). Draft all five STAR stories. Start pseudocode tracing.
• Week 4: Mock interviews out loud, polish "why Deloitte," rehearse the project deep-dive, light revision. Rest the day before.

2-week plan

• Days 1-4: Aptitude mocks daily plus SQL/OOP refresh.
• Days 5-8: Track depth plus CS fundamentals plus pseudocode.
• Days 9-11: STAR stories plus "why Deloitte" plus project walkthrough.
• Days 12-14: Two full mock interviews, fix weak spots, rest.

2-day crash plan

• Day 1 AM: One full aptitude mock. Review every wrong answer.
• Day 1 PM: SQL, OOP, and your project story written out and said aloud.
• Day 2 AM: CS fundamentals skim plus pseudocode tracing plus three STAR stories.
• Day 2 PM: Practice "tell me about yourself" and "why Deloitte" until smooth. Sleep early.

8Why people get rejected at Deloitte India#

1. Weak communication. Correct answers delivered in halting, unclear English. Deloitte puts you in front of clients, so fluency and structure are non-negotiable. Structure spoken answers like a bullet: one clear point, then support, then land it.
2. No clear "why Deloitte / why consulting." Generic answers signal you will leave the moment a product company calls. They have been burned by exactly this, so they listen for it hard.
3. Shaky fundamentals. Can write a quick-sort but cannot explain a database index or the four OOP pillars. The firm would rather have strong basics than a memorized algorithm you cannot reason about.
4. Resume you cannot defend. Listing skills or projects that collapse under two follow-ups. One exposed exaggeration poisons the whole resume.
5. Rote STAR stories. Memorized, numberless, obviously rehearsed, with no real reflection. A story with no result and no lesson lands as filler.
6. Missing the test window or going silent. Administrative drop-off, not completing the assessment on time or not answering scheduling emails. The most avoidable rejection on the list, and it still happens constantly.

9The offer, comp and negotiation#

Structure. Deloitte India offers come as a CTC: fixed base, a performance-linked variable or bonus, and standard benefits (insurance, PF).

• Freshers land roughly ₹6.5-9 LPA depending on service line and role.
• Consultants ₹10-16 LPA; Senior Consultants ₹16-26 LPA.
• Hot tracks like cloud, data, and cyber tend to sit at the higher end.
• The number quoted is CTC, so always separate fixed take-home from variable before you react. A shiny CTC can hide a thin base.

Negotiation tips:

1. Lead with a competing number, not a feeling. A documented offer or a credible market range moves the fixed component far more than "I was hoping for more." Recruiters discount feelings and respond to evidence.
2. Negotiate the fixed, understand the variable. Variable pay depends on firm and personal performance, so weight your ask toward base and ask exactly how variable has paid out historically, as a percentage of target over the last couple of cycles.
3. For laterals, benchmark your band. Know the typical range for your target level and location before the HR call, and justify your number with specific skills and client-ready experience. A Bangalore or Hyderabad cloud consultant with billable certifications has more room than a generalist, so bring the specifics that move you up the band.

Hold your nerve on the call.

• Be polite and firm. Deloitte expects some negotiation from laterals; freshers have less room but can still ask clearly and respectfully.
• Never accept on the call out of nervousness.
• "Thank you, this is exciting, can I confirm by tomorrow morning" is a complete and professional sentence.

CTC is the headline; the fixed base is the story. Read the story before you react to the headline.

10FAQ#

Want this turned into a personalized, dated plan around your actual interview date? Map your weak spots to the weeks above and build a day-by-day schedule you can actually follow.