Deloitte's National Level Assessment (NLA) is the main fresher gateway into Deloitte India's technology and consulting analyst roles. The structure is unusual: a heavy online assessment followed by a single, short interview — typically 15 to 25 minutes — that mixes technical and HR evaluation in one conversation. That compression changes how you should prepare.
In a 20-minute combined interview, there is no time to warm up. The panel usually opens with your introduction, jumps straight to your final-year project and resume skills, asks one or two fundamentals or a small coding/logic question, and closes with Why Deloitte and logistics. Every answer must be tight, because each one is a larger fraction of your total evaluation than in a long multi-round process.
This guide covers the assessment pattern, the interview questions that repeat across NLA cycles, and how to rehearse short-format answers — the specific skill this process rewards.
The NLA online assessment: what you clear first
The assessment typically runs about 90 minutes: quantitative aptitude, logical reasoning, verbal ability, and computer/programming fundamentals MCQs — OOPs concepts, data structures basics, DBMS, OS, networks, and cloud fundamentals. A separate coding section (commonly around 30 minutes, two problems) tests arrays, strings, and standard logic at easy-to-moderate difficulty.
The MCQ breadth is the real filter: candidates who prepared only coding get caught by pseudo-code tracing, SQL, and CS fundamentals questions. Balance your preparation accordingly — PrepInsta-style topic lists plus daily timed mocks for a week is usually sufficient for the assessment stage.
The combined interview: exact question flow
Reported flow across recent cycles: tell me about yourself; explain your final-year project (what, why this stack, your contribution, challenges); one or two questions on a resume skill (Java/Python basics, OOPs pillars, SQL query, or a quick logic problem); sometimes a situational question (client deadline conflict, team disagreement); then Why Deloitte, relocation and shift flexibility, and your questions.
Because it is one panel for everything, communication quality is scored continuously. Structure every answer as: direct point first, one concrete example, stop. Rambling in a 20-minute interview costs proportionally more than anywhere else.
Technical questions that repeat in NLA interviews
Fundamentals: four pillars of OOPs with examples from your project, difference between list and array, primary vs foreign key, write a query with a JOIN and GROUP BY, what is an API, basics of cloud (IaaS/PaaS/SaaS), and simple output-prediction snippets. If you list Python: lists vs tuples, dictionaries, and a string manipulation question. If Java: JVM basics, String immutability, collections.
Project questions go one level deeper than most freshers prepare: why this database, what would break with 10x users, how did you test it, what security did you consider. Prepare one honest "challenge I hit and how I fixed it" story — it is asked in nearly every NLA interview.
The HR half: consulting-firm specifics
Deloitte-specific angles: Why Deloitte over IT services companies (have a real answer: consulting exposure, client variety, USI delivery model); are you flexible with shifts and base location; how do you handle ambiguity — consulting staffing is fluid and they test comfort with it; and integrity/situational questions (a teammate takes credit for your work — what do you do).
Keep a 60-second Why Deloitte ready that names something specific — a practice area, a technology alliance, or the analyst growth path — rather than generic prestige lines. Panels hear the generic version twenty times a day.
How to rehearse for a 20-minute format
Practice with a hard timer: 90 seconds for introduction, 2 minutes for project explanation, 60 seconds per fundamental, 45 seconds for Why Deloitte. Record yourself or use CrackInterviewAI in mock mode to generate compact outlines for each expected question, then practice delivering them shorter than the outline. The target feeling is: every answer ends before the panel wants it to.
On interview day: one page of notes maximum (project bullets, three fundamentals you fear, Why Deloitte), stable internet for the video call, and formal setup. Short interviews amplify first impressions — the introduction is worth disproportionate rehearsal.
Rehearse the 20-minute Deloitte format
Practice compact, timed answers with CrackInterviewAI — resume-aware outlines for your project story, fundamentals, and Why Deloitte, ready to speak in under two minutes each.
Frequently asked questions
Is the Deloitte NLA interview technical or HR?
Both in one sitting — typically 15–25 minutes covering your project, resume skills, one or two fundamentals or coding questions, and HR staples like Why Deloitte and relocation flexibility.
What role does NLA hire for?
Primarily Analyst/Analyst Trainee roles across Deloitte India and Deloitte USI technology and consulting teams. The exact team is usually decided post-offer based on business need.
How hard is the NLA coding round compared to TCS or Infosys?
Comparable or slightly easier — usually two easy-to-moderate problems on arrays, strings, or standard logic. The MCQ breadth (aptitude + CS fundamentals + verbal) is where most candidates lose marks.
Keep exploring
Return to the CrackInterviewAI homepage to download the Windows app, or browse all guides on the interview prep blog.
Related guides
- AI Interview Assistant: How Real-Time Interview Answers Help You Stay Clear Under Pressure
- Coding Interview Help Tool: A Practical Guide to AI Support for Live Technical Rounds
- Live Interview Support Software: What to Look For Before a Remote Technical Interview
- Free Interview AI Assistant: 10 Best Tools Tested in 2026 (Honest Ranking)