Jobra
🐞Step 1 of Jobra:AI Debugging Rounds
DSA+AIPreparing you for both.
JOBRA · AI DEBUG ROUND (PREVIEW)sum.cpp
// buggy snippet
int total(vector<int>& a, int n) {
    int sum = 0;
    for (int i = 0; i <= n; i++) { // 🐞        sum += a[i];
    }
    return sum;
}
A real codebase. A real bug. You + AI.

Jobra drops you into a broken repo. Find it, fix it, ship it. AI helps you debug like on the job.

Prompt:Correct the loop condition
Tap 'Let Jobra fix it' below to simulate AI debugging...

Deloitte Data Analyst Interview Questions & Rounds

33 min read

Deloitte data analyst interview guide: the NLA and campus online assessment, technical and HR rounds, pandas and Excel tasks, and prep advice from real candidates.

In this article
On this page

How to Crack Deloitte: The Data Analyst Interview, From Real Experiences

Last updated November 20, 2026 · 27 min read · For freshers applying to Deloitte USI and Deloitte India data analyst and analyst roles on campus or through the NLA

Built by the Codinzhub team. This guide is built from Deloitte analyst interview experiences that candidates shared, including experiences and assessment questions on Codinzhub. The process changes by year, track, campus and member firm, so treat this as a map, not a promise.

The 30-second version. Deloitte hires most entry-level analysts through USI campus drives or the off-campus National Level Assessment (NLA). After resume shortlisting comes an online assessment: in most reports that give a length, 90 minutes of timed aptitude, verbal and CS-fundamentals MCQs, usually with 2 easy-to-medium coding questions, and it filters out the most candidates. Then comes either one combined technical and HR interview of 30 to 50 minutes, or a technical round followed by HR, managerial or partner rounds; some campuses add a group discussion or JAM round first. Interviews centre on your projects, OOP, SQL and one short program. Three campus reports got results the same day; NLA results took days to weeks. The habit that matters most: put only what you can defend on your resume, and know every project on it in depth.

What this guide is, and what it is not

This guide is built from 36 candidate records of Deloitte's entry-level analyst hiring: 3 experiences and 4 assessment question pages shared on Codinzhub, plus 29 public write-ups and comments. It also draws on 1 official Deloitte careers page. Most dated records are from 2023 to 2026, all from India, across Deloitte US-India (USI) campus drives, the off-campus National Level Assessment (NLA) and a few Deloitte India and Tax Technology drives. 16 records do not state the interview year.

It is:

  • A map of the process, stage by stage, as candidates described it
  • The question patterns that keep coming back, and the follow-ups to expect
  • A six-week plan and practice problems matched to those patterns

It is not:

  • A list of leaked questions or a promise of what you will be asked
  • An official description of Deloitte's process
  • An offer rate. Outcomes in candidate posts are self-reported and are not a statistical sample.

Important things to know before you start

These Deloitte-specific facts change how you should prepare.

The OA is timed by section. The assessment ran 90 minutes in 8 of the 14 reports that give a length, HirePro was the most named platform, and five reports describe a separate timer or cutoff for each section. With a cutoff per section, a strong coding score may not make up for a weak verbal or CS-fundamentals section, so practise every section under its own clock.

"Analyst" means different tests on different drives. Most USI campus and NLA tests had 2 coding questions, but 8 reports described an MCQ-only test, including a Deloitte India practice-area drive. Two tracks added a spoken-English Versant test. Read your drive's notice before deciding how much coding to practise.

Your resume is the syllabus. Projects came up in 19 of 27 interview reports, and interviewers asked about the language and tools candidates named, from C++ constructors to Arduino. List only what you can explain and code.

Interviews vary by panel. A few reports said some interviewers asked mostly HR questions and others only technical ones, even on the same campus. Prepare both, and do not read a short or friendly interview as a sign of an offer.

Round-by-round breakdown

Candidates described five stages: an application through a campus drive or the National Level Assessment, resume shortlisting, an online assessment, one or more interviews (with a group discussion on some campuses), then results and an offer.

Stage 1: Application, where candidates applied

Every record comes from India: mostly Deloitte US-India (USI) campus drives for Analyst, Technology Analyst and Business Technology Analyst roles, plus a few Deloitte India and Tax Technology drives.

ChannelWhat candidates said
Campus driveThe main route, in 24 of 36 records. Some drives opened with a pre-placement talk (PPT), and one 2024 campus offered three USI profiles in the same drive.
National Level Assessment (NLA)Deloitte's off-campus test for freshers, in 9 records. You register on Deloitte's site with a resume; one candidate got the cleared-test email a few months after the test, and one could book the interview slot.
Open Talent NetworkOne 2023 route for Risk & Financial Advisory: a six-month in-person cybersecurity bootcamp and a final assessment came before any offer.

Eligibility. Campus reports gave no active backlogs plus a floor of 60 percent, 6.0 CGPA or 6.5 CGPA, depending on the drive. Deloitte's US-India careers pages say you submit a job-specific profile with your resume, campus applicants also enter transcript details, and students may be asked to apply through their campus career centre; the placement office or a Deloitte professional then schedules the campus interview.

What helped. Candidates credited taking notes at the PPT and referring to it in the interview, and a resume that lists only what you can defend, because interviewers dig into every line.

Stage 2: Shortlisting, how candidates moved forward

Shortlisting happened before and after the online assessment, and on some tracks a spoken-English test sat between the assessment and the interviews.

  1. Resume and eligibility shortlisting. On campus, three reports said most students cleared it. NLA applicants were shortlisted on their resume before getting a test slot, and applicants in one 2026 discussion said they got a rejection email at this step with no reason given.
  2. The online assessment as a filter. Candidates called the assessment the step that filters out the most people (details in Stage 3). Reported campus numbers: about 300 took the test and 49 were shortlisted in one 2024 drive; about 700 took it and 127 were shortlisted in another; 160 took it and 44 were interviewed in a 2022-23 drive.
  3. Communication test (two tracks). A 2023 Business Technology Analyst drive and a Tax Technology drive added a spoken-English test (Versant, by Pearson) after the assessment. The 2023 report called it an elimination round, and in the Tax Technology drive only 25 candidates passed it. The tasks: repeating sentences, answering short questions, retelling a story and open-ended answers.

Stage 3: Online assessment

Every track in the data started with an online assessment (OA), a timed online test. What changed by drive was whether it had a coding section.

Online assessment

How it works. 14 of the 22 reports that describe the content had timed multiple-choice (MCQ) sections plus 2 coding questions; 8 had MCQs only, including a Deloitte India practice-area drive and three AMCAT-run tests. MCQs cover quantitative aptitude, reasoning, verbal or English, and CS fundamentals (OS, DBMS, SQL, cloud computing, pseudocode), plus programming, testing and MS Office in NLA versions. HirePro was named in 4 reports and AMCAT in 3. Five reports describe a timer or cutoff per section, and two said there was no negative marking.

At a glance

  • Length: 90 minutes in 8 of the 14 reports that give a length; others reported about 3 hours (2), 60 minutes (2) or 120 to 129 minutes for an aptitude-only test (2)
  • Questions: usually MCQ sections plus 2 coding questions; reported totals were 65 MCQs plus 2 coding (3 reports), 50 plus 2 (2 NLA reports) and 52 plus 2 (one 2023 Open Talent Network test)
  • What was asked: easy to medium coding in 10 reports, mostly short string and array programs; MCQs on aptitude, English and CS fundamentals
  • Most common: No single repeated question

The coding questions are short string or array programs. One 2026 candidate who stayed too long on the first question ran out of time for the second; a 2024 candidate finished with 6 to 7 minutes to spare and said speed and accuracy decide this round.

QuestionWhat it testsLevel
Maximum subarray sum (Kadane's algorithm)Kadane's algorithm, running maximumTax Technology analyst or engineer
Convert a length in inches to centimetresBasic input, arithmetic and outputTax Technology analyst or engineer
Letter-number sequence puzzleNot reportedNot reported
Milk and water mixture profitNot reportedNot reported
OA coding question on arrays (medium)Not reportedNot reported

OA questions shared on Codinzhub.

QuestionDriveTopic
Letter-number sequence puzzleIIT Kharagpur (30 MCQs, 60 minutes, HirePro)Reasoning
Milk and water mixture profitIIT KharagpurQuantitative aptitude
OA coding question on arraysNot statedArrays, medium

A 2026 IIT (BHU) Varanasi page on Codinzhub lists the pattern as MCQs plus a "vibe coding" task. See all Deloitte OA questions in the question bank.

Stage 4: The interviews

After the OA, reports split almost evenly between one combined technical and HR interview (11 of 27 reports) and a technical round followed by separate HR, managerial or partner rounds (12 of 27). Some drives added a group discussion or a JAM round first. Interviews were mostly online in the reports that say where, and 10 reports put the technical or combined interview at 30 to 50 minutes. A few reports said panels varied: some asked mostly HR questions, others only technical ones.

How a combined interview usually runs

PhaseWhat usually happensWhat to do
OpeningIntroductions; some interviewers also introduce themselves and their workGive a 60-second pitch that names only skills you can defend
ProjectsA deep-dive into one resume project: purpose, stack choice, challengesExplain why you chose each tool and what you would change
FundamentalsOOP, SQL or DBMS, plus questions on the language you namedAnswer in one line, then give an example
Live codingOne or two short programs, sometimes in a built-in editorSay your approach and complexity before typing
HR and closeWhy Deloitte, goals, a scenario; "any questions for me?"Ask about the interviewer's role or the PPT

Five reports describe this flow; in one 2023 NLA interview of about 50 minutes, the live-coding phase was 20 minutes for 2 questions and a puzzle took 5 minutes.

Group discussion or JAM round (some campuses)

At a glance

  • Length: Not reported as a whole; one GD ran 15 minutes, and JAM turns were about 1 to 2 minutes per person
  • Questions: one topic per group (GD) or per candidate (JAM)
  • What was asked: a business case in one 2024 report; short technology topics in JAM rounds
  • Most common: No single repeated question

6 reports mention a GD or JAM ("just a minute": speak on a random topic for about a minute) round. A 2024 Deloitte India drive ran a 15-minute GD in cohorts, then asked each person one question, and cut 34 students to 19. The JAM topics below come from one 2020 drive, the only report that listed them, so treat them as examples of the style.

Reported prompts.

  • An electric-vehicle maker with strong sales but poor after-sales service and little digitalisation: propose fixes (2024)
  • Internet of Things in day-to-day life (JAM, 2020)
  • Voice calls versus video calls (JAM, 2020)
  • Using technology to battle climate change (JAM, 2020)
  • Classroom learning versus e-learning (JAM, 2020)
  • Television versus OTT platforms (JAM, 2020)
  • Chatbots in different areas (JAM, 2020)

Technical interview

At a glance

  • Length: 30 to 50 minutes in 10 reports; 15 to 25 minutes in 2
  • Questions: a project deep-dive, several fundamentals questions and usually one or two short coding problems
  • What was asked: projects (19 of 27 reports), live coding (19 of 27), SQL or DBMS (14 of 27) and OOP (12 of 27)
  • Most common: walking through a resume project, in 13 reports

Most reports describe a resume-driven interview: the interviewer picks a project or a skill you named and keeps asking until you reach the edge of what you know. The coding is easy to medium, and two reports coded in the platform's built-in editor. Puzzles appeared twice: make 9 - 9 = 3 by moving one matchstick, and three wrongly labelled bags of balls.

QuestionFollow-upLevel
Walk through a resume project: purpose, stack choice, challenges, what you would changeHow would you migrate its database, then handle concurrency?Analyst tracks
Explain the four OOP pillars with real-life examplesExplain polymorphism in detailAnalyst tracks
Which programming language do you prefer? Then questions in itDifference between C and C++; the assert keywordAnalyst tracks
Explain SQL join types with examplesLeft-join a 17-row table to a 6,000-row table, then count the rowsAnalyst
Explain cloud computing: service models, deployment models, why firms move to cloudAmazon Web Services versus SalesforceNLA, level not reported
Find the missing number from 1 to N, then time and space complexityNot reportedAnalyst or Associate (NLA)
Check whether a string is a palindromeNot reportedNLA, level not reported
Sort an array: explain bubble sort, then code merge sort with complexityNot reportedBTA and DAS

See all 47 technical-interview questions in the question bank.

HR, managerial and partner questions

At a glance

  • Length: 15 to 30 minutes when it was a separate round (3 reports); otherwise the last part of a combined interview
  • Questions: 4 to 8 short questions in the reports that list them; one 2023 managerial round ran about 45 minutes
  • Themes: why Deloitte, five-year goals, leadership and teamwork, your resume, and scenarios about deadlines
  • Most common: "Why Deloitte?", in 6 of 19 reports

Some USI drives had a separate round taken by a manager, and one Deloitte India drive had a Director interview and then a Partner round. One 2025 candidate who felt they had answered every question was still not selected, so treat this part as scored.

Reported questions.

  • Why Deloitte, then what you expect from Deloitte
  • A time you led a team, then the qualities of a leader
  • Where do you see yourself in 3 to 5 years?
  • Where do you live, and what are your hobbies?
  • A difficult situation in a team and how you handled it
  • A project is cancelled close to its deadline: what do you do?
  • Your colleague's deadline is close and so is yours: how do you help?
  • The worst thing you have heard about Deloitte, then Deloitte's revenue (partner round)

See all HR questions in the question bank.

Stage 5: Results and offer

Results. On campus, results were fast: the same day or within a few hours of the last interview in three reports, and through the college list a day or two later in one Deloitte India drive. Off-campus NLA results were slower, from a few days after the interview to about two weeks, and one 2023 Open Talent Network candidate heard about four weeks after the interview. There is no hiring committee or team-matching step in the data.

Selection numbers. After the interview, reported cuts varied: 22 of 38 selected in one 2023 drive, 5 of 14 in another, 7 of 44 in a 2022-23 drive, and 4 of 7 from one college in an NLA batch.

Offer. Two reports said Deloitte goodies arrived before or around the offer letter, and one campus report said offer letters had not been mailed yet and joining dates came later than at other companies. Open Talent Network hires get a USI offer only after the six-month bootcamp and its final assessment.

The Codinzhub Next-Round Playbook

Candidates who moved forward cleared the OA on speed, then defended their resume.

To get past shortlisting

  • Keep the resume to what you can explain. Interviewers asked about listed technologies, down to "what is Arduino?".
  • If your track has a Versant test, practise retelling a short story aloud. One candidate wrote down the characters and events while listening.

To get past the OA

  • Treat it as the main filter. In reported drives, about 300 candidates became 49, and about 700 became 127.
  • Respect each section's timer. Five reports describe per-section timers or cutoffs, so do not leave the verbal or CS-fundamentals section for last.
  • Budget about 20 minutes for the two coding questions, as one 2024 candidate's test allowed. Solve the easier one fully first; one 2026 candidate lost both by staying too long on the first.

To get past a GD or JAM round

  • Make two or three clear points with a reason and an example, rather than speaking most.
  • In JAM, use the thinking time, then speak for the full minute without repeating yourself. One report said crossing the time limit was "a strict no-no".

To get past the technical interview

  • Open with an introduction that names only skills you can defend; one candidate said the interviewer built every question from it.
  • For your strongest project, prepare the purpose, the stack choice, one hard problem and what you would change. Projects came up in 19 of 27 interview reports.
  • Before any live code, say the approach and its complexity. One 2025 NLA candidate was asked for time and space complexity after the missing-number problem.

To get past the HR, managerial or partner questions

  • Have a specific answer to "Why Deloitte?", the most common HR question; one 2024 candidate advised referring to the PPT.
  • Ask the interviewer a question at the end. Four reports were asked "Do you have any questions for me?".

How the loop differs by level

Every record is a fresher hire, so the differences are by track and route, not seniority. No track had a system design round.

TrackWhat candidates describe
USI campus Analyst and Technology AnalystThe largest group. An OA of MCQs plus 2 coding questions, usually 90 minutes, then either one combined 30 to 50 minute interview or a technical round and a short HR round (15 minutes in one report). Examples: left-join two tables and count the rows, reverse a string, SQL versus NoSQL.
Business Technology Analyst (USI)Two reports. One 2023 drive: an OA with 1 SQL query and 1 easy coding question, a Versant test, then technical, managerial and HR rounds of about 45, 45 and 30 minutes. Another: an aptitude test, a JAM round and a 25-minute video interview.
NLA: Analyst Trainee, Associate Analyst, Software EngineerAn off-campus 90-minute test of 50 or 65 MCQs plus 2 coding questions, then one online interview of 15 to 50 minutes. One NLA 3.0 Associate Analyst interview was almost entirely HR and resume questions. Examples: missing number from 1 to N, palindrome string, cloud deployment models.
Open Talent Network (Risk & Financial Advisory)One 2023 report: a 90-minute HirePro test (10 English, 12 reasoning and quant, 30 technical MCQs, 2 easy coding), a 30-minute interview on C, C++ and OOP, then a six-month cybersecurity bootcamp before an offer.
Tax Technology (Business Solution Analyst, Software Engineer)One report: a 5-section OA with 2 easy coding questions, a Versant test, an HR interview, a technical round (merge two sorted lists, keys and indexes) and a final round with live tree traversal.
Deloitte India practice areasOne 2024 report: 50 MCQs in 60 minutes with no coding, a GD, a Director interview on generative AI and projects, then a Partner round of HR and corporate scenarios.

Most-asked topics

Across 34 reports that described a technical stage (the OA's coding part or an interview), questions concentrated in a few topics. Your own projects came up more than any algorithm, and dynamic programming was rare.

TopicWhat it meansSeen inReported examples
OOP and language basicsClasses, the four OOP pillars, and the language you named19 of 34 reportsExplain the four OOP pillars; C versus C++; Python list versus dictionary
Your projectsExplaining what you built, why, and what you would change19 of 34 reportsWalk through a resume project; what is Arduino and what is it used for?
SQL and DBMSWriting queries and explaining database concepts14 of 34 reportsExplain join types; left-join and count; TRUNCATE versus DELETE
Short string and array programsLoops and indexes on strings or arrays8 of 34 reportsReverse a string; palindrome check; missing number from 1 to N
Cloud, web and newer techCloud models, web basics, AI and data handling8 of 34 reportsCloud service and deployment models; generative AI use cases; Excel into pandas
Classic DSA warm-upsSorting, linked lists, trees and small dynamic programming6 of 34 reportsMerge sort; reverse a linked list; minimum steps to climb a staircase
Puzzles and aptitudeLogic puzzles in interviews, aptitude MCQs in the OA3 of 34 reportsMatchstick 9 - 9 = 3; three mislabelled bags; milk and water mixture

The question patterns that keep coming back

Most Deloitte analyst questions fall into a handful of patterns, and almost all of them start from something you said or wrote.

1. OOP and the language you claim

In 19 of 34 technical reports, interviewers asked about OOP or the language the candidate named. Five reports said the questions followed the language or skills the candidate named: one who chose C++ was asked about the assert keyword and C versus C++, and another was asked why C++ is still relevant. For any "explain X" question, give a one-line definition, then one example from your own code.

Reported examples. The four OOP pillars with real-life examples, then polymorphism in detail; overloading versus overriding; multiple inheritance in Python; constructors and destructors; Python list versus dictionary.

2. Your own projects, explained deeply

Walking through a resume project was the most repeated question in the data, in 13 reports, and projects came up in 19 of 34. Expect why you picked each tool, what was hard, and what you would change; one 2023 managerial round asked how the project's database could be migrated. Anything you list can become a question, as with one candidate asked what Arduino is.

Reported examples. Walk through a resume project; what is Arduino and what is it used for?; suggest improvements for an autonomous parking system.

3. SQL queries and DBMS concepts

SQL or DBMS questions appeared in 14 of 27 interview reports, some verbal and some written. If a question says "every row of A", use a left join, which keeps all of A's rows; if it asks for totals per group, use GROUP BY with an aggregate.

Reported examples. Explain SQL join types; left-join a 17-row table to a 6,000-row table, then count; joins with pattern matching; primary key, foreign key and index; TRUNCATE versus DELETE; SQL versus NoSQL.

4. Short string and array programs

Most OA coding and much of the live coding were short programs. For "reverse" or "palindrome", use two pointers from both ends; for "missing number from 1 to N", compare the expected sum with the actual sum; for the best contiguous run, keep Kadane's running maximum.

Reported examples. Reverse a string; palindrome check; missing number from 1 to N, then complexity; maximum subarray sum; print a string's characters by ASCII code.

5. Classic DSA warm-ups

Six reports included a textbook data-structure problem. Know merge sort, linked-list reversal and merging, and one tree traversal well enough to write them without help. Draw the pointers before writing a linked-list loop.

Reported examples. Explain bubble sort, then code merge sort; reverse a linked list; merge two sorted linked lists; tree traversal coded live; minimum steps to climb a staircase.

6. Cloud, web and newer-tech awareness

Cloud computing is in the OA's CS-fundamentals section and came up in interviews, along with web basics and, in one 2024 Deloitte India drive, generative AI. Answer as a definition, why a client would want it, and one example.

Reported examples. Cloud service and deployment models, then AWS versus Salesforce; the HTML marquee tag and Bootstrap; == versus === in JavaScript; generative AI use cases.

7. Puzzles and aptitude (less common)

Two interviews included a puzzle, and the Codinzhub OA pages show reasoning and quantitative MCQs. Think aloud; the interviewer is watching how you reason.

Reported examples. Make 9 - 9 = 3 by moving one matchstick; three mislabelled bags of balls; letter-number sequence puzzle; milk and water mixture profit.

Preparing for the HR and managerial questions

The HR questions come either at the end of a combined interview or in a separate HR, managerial or partner round (see Stage 4). They are short, but they are scored.

Build your story bank. Prepare five or six real stories, each under two minutes, and know why you want Deloitte specifically. Cover the themes candidates were asked about:

ThemeReported prompt (paraphrased)Follow-up to expect
MotivationWhy Deloitte?"What motivates your interest?" and "What do you expect from Deloitte?"
LeadershipA time you led a team"What are the qualities of a leader?" and, for hackathons, "How many did you win?"
TeamworkA difficult situation in a team and how you handled itWould you do a project in a team or alone, and why?
DeadlinesA project is cancelled close to its deadlineYour colleague's deadline is close and so is yours: how do you help?
SetbacksA failure, and how you overcame it"What will you do if you are rejected?"
GoalsWhere do you see yourself in 3 to 5 years?"Do you plan to pursue higher studies?"
Company knowledgeWhat do you know about Deloitte, and what did you learn at the PPT?"The worst thing you have heard about Deloitte", then its revenue

Structure each story. Give the situation in one line, then what you did, the result, and what you would do differently. Use your own experiences and say "I" for your actions.

Expect a personal tone. Interviewers also asked about your home town, hobbies, daily routine and certifications. One 2023 candidate felt a weak leadership answer contributed to their rejection, so have a leadership story ready.

A six-week plan

The plan follows the patterns above, most common first, and ends with timed mocks. Plan on two focused hours a day, plus 30 minutes of aptitude practice daily from week 1, because the OA is the main filter.

  1. Week 1: OOP and your chosen language. The four OOP pillars, overloading versus overriding, constructors and destructors, and the basics of the one language you will name. Habit: answer every concept in one line, then give an example from your own code.
  2. Week 2: Your projects. Write a one-page brief per project: purpose, stack choice, the hardest problem, what you would change, and one basic question per listed tool. Habit: explain each project aloud in under three minutes.
  3. Week 3: SQL and DBMS. Joins (especially left join and its row counts), GROUP BY with aggregates, LIKE, keys, indexes, views, TRUNCATE versus DELETE and SQL versus NoSQL. Habit: write every query by hand before you run it.
  4. Week 4: Short string and array programs. Reverse a string, palindrome check, missing number, maximum subarray, printing characters by their ASCII codes. Habit: give the complexity before you code.
  5. Week 5: DSA warm-ups and awareness topics. Merge sort, linked-list reversal and merging, one tree traversal, climbing-stairs style DP; then cloud service and deployment models, web basics, and two puzzles a day. Habit: write each one without looking anything up.
  6. Week 6: Mocks. Take three timed 90-minute OA mocks with sectioned MCQs and 2 coding questions, and three 30 to 45 minute video mock interviews: introduction, project, fundamentals, one live program and HR questions. Rehearse your "Why Deloitte?" and leadership stories out loud.

If your drive has no coding in the OA (some Deloitte India and AMCAT tests), move week 4 time to aptitude.

Only two weeks? Spend 3 days on OOP and your language, 2 on your projects, 3 on SQL and DBMS, 2 on string and array programs, 1 on cloud basics and puzzles, and 3 on timed OA mocks and mock interviews with your HR stories.

Practice problems that match these experiences

These are well-known practice problems that match the patterns above. They are not claims about Deloitte's question bank unless a row says the problem was asked as-is. The project, OOP, cloud, puzzle and HR patterns have no matching practice problems here; prepare them with your own resume and notes.

#Practice problemPatternSeen in these experiences as
1Combine Two TablesSQL left joinLeft-join a 17-row table to a 6,000-row table, then count
2Patients With a ConditionSQL LIKE pattern matchingSQL queries using joins and pattern matching
3Reverse StringTwo pointers on a stringReverse a string
4Palindrome StringTwo pointers on a stringCheck whether a string is a palindrome
5Missing in ArrayExpected sum or XORMissing number from 1 to N, then complexity
6Maximum SubarrayKadane's running maximumOA question named as Kadane's algorithm
7Program to Print Inverted Full Pyramid PatternNested loopsAsked as-is in one report (in Python)
8Sort an ArrayMerge sortExplain bubble sort, then code merge sort
9Reverse Linked ListPointer reversalAsked as-is in one report
10Merge Two Sorted ListsTwo pointers on listsAsked as-is in one report
11Binary Tree Inorder TraversalTree recursionTree traversal coded live
12Climbing StairsSmall dynamic programmingMinimum steps to climb a staircase

How to handle a question you have never seen

Deloitte's questions are short, so the risk is freezing, not a hard algorithm. A simple method helps.

  1. Repeat the question and one example. For a coding task, say the input and output back; for a scenario like the autonomous parking question, restate the goal before suggesting anything.
  2. Say the simple approach and its complexity. One 2024 candidate gave both a brute-force and an optimised answer to an easy searching and sorting problem and was selected.
  3. Name the tool the problem needs. Reversing or comparing ends suggests two pointers; a count or total per group suggests GROUP BY; "every row of one table" suggests a left join; a running best suggests Kadane's idea.
  4. Say when you are stuck. Two candidates advised saying plainly that you cannot recall something rather than guessing, and one selected 2023 candidate added that you will work on it.
  5. Code in small pieces while talking. Some interviews used a built-in editor, so keep code short, name variables clearly and keep talking.
  6. Dry-run one case and fix the wrong line. Trace your example by hand before saying you are done, and state the time and space complexity, which one 2025 interviewer asked for.

Why candidates were rejected

Five records in the data ended in a rejection, and only one gives a reason, which comes from the candidate's own reflection. Read these as warnings, not as rules.

  • Stumbling on a basic technical question. One 2023 Open Talent Network candidate, in a first-ever interview, could not answer one technical question (the round asked about the assert keyword, C versus C++ and OOP versus procedural programming) and felt that cost the offer.
  • A weak leadership answer. The same candidate felt they did not explain their leadership skills well when asked.
  • No reason given after a good interview. One 2025 campus candidate cleared a GD, answered a coding question and felt every technical and HR answer went well, but was not selected and never learned why.
  • Final-round drop-offs. A Tax Technology candidate reached the final round, which asked about DBMS views, trees and live tree traversal, and was not selected; 4 of the 9 to 12 finalists got offers. A DAS candidate and a 2025 NLA candidate were also not selected after technical and HR rounds, with no reason reported.

Selected vs. rejected: do this, not that

Selected candidates mostly described easy-to-medium interviews; what repeated were a few habits.

Do thisNot thatWhat the reports show
Speed in the OA: practise timed aptitude sections and two short programs in about 20 minutesGetting stuck: spending most of the time on one coding questionOne 2026 candidate lost both coding questions this way; a selected 2024 candidate finished with minutes to spare.
Defend every resume line: know why you chose each tool in each projectPadding the resume: listing tools you cannot explainFour reports, three of them from selected candidates, said interviewers dig into resume items; one 2024 candidate said misrepresentation can disqualify you.
Know your language's basics: definitions plus one example for eachFreezing on fundamentals: no answer to a basic language questionOne 2023 candidate felt a missed technical basic cost the offer.
Have a leadership story: one real example where you led or coordinatedVague soft-skill answers: "I am a good leader" without an exampleThe same 2023 candidate felt the leadership answer was weak.
Say when you do not know: answer briefly and offer what you do knowBluffing: guessing to fill silenceTwo candidates, one of them selected, advised saying calmly that you do not know rather than confusing the interviewer.

If you remember only five things

  1. The process is short. An online assessment, sometimes a GD or JAM round, then one combined interview or a technical round plus HR, managerial or partner rounds; in three campus reports, results came the same day.
  2. The OA is the main filter. It ran 90 minutes in most reports that give a length, with timed aptitude, verbal and CS-fundamentals sections and, on most tracks, 2 easy-to-medium coding questions.
  3. Your resume is the syllabus. Projects came up in 19 of 27 interview reports, and questions followed the language and tools you name.
  4. The core topics are basic. OOP, SQL and DBMS, and short string or array programs, with cloud basics and the odd puzzle.
  5. "Why Deloitte?" is the most common HR question. Have a specific answer and a real leadership story ready.

FAQ

Does every route start with an online assessment?

In this data, yes, but its content varies. Most had MCQs plus 2 coding questions; 8 of 22 reports that describe the content had MCQs only.

Do I need advanced DSA?

Not in this data. The coding was easy to medium: reverse a string, palindrome check, missing number, merge sort, linked-list reversal and one tree traversal. Dynamic programming appeared in 3 of 34 technical reports.

Is there a system design round?

No. No record describes one; the closest was a 2024 scenario question on improving an autonomous parking system.

How long does it take?

On campus, results came the same day or within a few hours in three reports. Off-campus NLA candidates waited from a few days to about two weeks after the interview. The gap from OA to interview ranged from 8 days to about 5 weeks, and one NLA candidate learned they had cleared the test only a few months later.

Is there a group discussion?

On some drives. 6 reports mention a GD or JAM round, including a Deloitte India practice-area drive and a Business Technology Analyst drive.

About this guide

The Codinzhub team researched and wrote this guide from 36 Deloitte analyst interview records, mostly from 2023 to 2026, including experiences and assessment questions shared on Codinzhub. We kept only what candidates described, plus what Deloitte's careers pages state. The questions are our own short summaries, and the practice links are similar problems unless marked as asked as-is. If you interviewed recently, share your experience on Codinzhub and we will update this guide.

Disclaimer. Deloitte's process changes by member firm, track, year and campus. Use this guide to build a foundation, and confirm the current format with your placement cell or recruiter.

Search the question bank

The questions from each round above, with practice links for similar problems. Log in to search every question we collected for this role, including questions shared on Codinzhub.

Showing 20 of 88 questions

  • OA coding question on arrays

    A Deloitte online assessment question shared on Codinzhub (Not stated).

    On CodinzhubNot statedArrays, mediumCodingOnline assessment
  • Maximum subarray sum (Kadane's algorithm)

    Level: Tax Technology analyst or engineer.

    Kadane's algorithm, running maximumCodingOnline assessment
  • Convert a length in inches to centimetres

    Level: Tax Technology analyst or engineer.

    Basic input, arithmetic and outputCodingOnline assessment
  • Letter-number sequence puzzle

    Level: Not reported.

    Not reportedCodingOnline assessment
  • Milk and water mixture profit

    Level: Not reported.

    Not reportedCodingOnline assessment
  • OA coding question on arrays (medium)

    Level: Not reported.

    Not reportedCodingOnline assessment
  • Walk through a resume project: purpose, stack choice, challenges, what you would change

    Level: Analyst tracks.

    How would you migrate its database, then handle concurrency?CodingRound not stated
  • Explain the four OOP pillars with real-life examples

    Level: Analyst tracks.

    Explain polymorphism in detailCodingRound not stated
  • Which programming language do you prefer? Then questions in it

    Level: Analyst tracks.

    Difference between C and C++; the assert keywordCodingRound not stated
  • Explain SQL join types with examples

    Level: Analyst.

    Left-join a 17-row table to a 6,000-row table, then count the rowsCodingRound not stated
  • Explain cloud computing: service models, deployment models, why firms move to cloud

    Level: NLA, level not reported.

    Amazon Web Services versus SalesforceCodingRound not stated
  • Find the missing number from 1 to N, then time and space complexity

    Level: Analyst or Associate (NLA).

    Not reportedCodingRound not stated
  • Check whether a string is a palindrome

    Level: NLA, level not reported.

    Not reportedCodingRound not stated
  • Sort an array: explain bubble sort, then code merge sort with complexity

    Level: BTA and DAS.

    Not reportedCodingRound not stated
  • OOP and language basics

    Level: 19 of 34 reports.

    Classes, the four OOP pillars, and the language you namedCodingRound not stated
  • Your projects

    Level: 19 of 34 reports.

    Explaining what you built, why, and what you would changeCodingRound not stated
  • SQL and DBMS

    Level: 14 of 34 reports.

    Writing queries and explaining database conceptsCodingRound not stated
  • Short string and array programs

    Level: 8 of 34 reports.

    Loops and indexes on strings or arraysCodingRound not stated
  • Cloud, web and newer tech

    Level: 8 of 34 reports.

    Cloud models, web basics, AI and data handlingCodingRound not stated
  • Classic DSA warm-ups

    Level: 6 of 34 reports.

    Sorting, linked lists, trees and small dynamic programmingCodingRound not stated
Page 1 of 5

Keep preparing on Codinzhub

Ready for the next topic?

Keep track of what you’ve learned.