NTT DATA Software Engineer Interview
A proctored aptitude + coding online test, a technical interview on DSA and CS fundamentals (DBMS, OOP, OS), and an HR round — the classic NTT DATA graduate-hiring funnel.
A free AI panel interview that questions you in NTT DATA’s style, follows up when an answer is thin, and returns a scored, evidence-backed report — seeded from your own practice history on Wrexa Edge.
The NTT DATA interview, in brief
NTT DATA is one of the world’s largest IT-services companies and a large graduate employer, hiring associate software engineers and technical graduate trainees at scale, largely through campus and off-campus drives. Its process is aptitude-heavy at the top of the funnel: a single proctored online test blends quantitative ability, logical reasoning, English, and computer-programming fundamentals, and only a moderate-difficulty adaptive filter is needed to reach the interviews. The technical interview is fundamentals-first — DSA in one language, DBMS/SQL, OOP, operating systems, and a walk through your resume projects — rather than a heavyweight distributed-systems bar. An HR round closes on communication, teamwork, relocation, and long-term fit.
Standard flow: (1) an online aptitude + computer-programming test (proctored, no negative marking, sectional cut-offs, adaptive) then (2) a technical interview covering DSA, DBMS/SQL, OOP, one programming language, and project deep-dive — one or two rounds depending on campus — then (3) an HR interview. Some campus drives add a Group Discussion between the test and the technical round.
Interview rounds
-
Online aptitude + coding test Proctored online, ~99 questions in ~120 min
-
Group Discussion (some campuses) Panel GD, ~10–15 min
-
Technical interview 1–2 rounds, ~30–45 min each
-
HR interview ~15–30 min
Coding & DSA topics
System design
Design is light for associate/fresher roles: object-oriented / low-level modelling (a library system, an ATM, a parking lot) and a small schema or data model for a simple application, judged on a clean class model and the OOP pillars rather than distributed-systems scale.
Behavioural round
Expect motivation (“why NTT DATA?”), a project you owned, a hard technical decision or a conflict you resolved, teamwork, and practical fit — relocation, shift flexibility, and willingness to keep learning. STAR-structured, specific answers land best.
Representative question categories
Patterns in NTT DATA’s style — not verbatim proprietary questions.
- DSA / codingGiven an array, find the second-largest element in a single pass — and state the complexity.
- DBMS / SQLWhat is the difference between a primary key and a foreign key, and when would you add an index?
- OOPExplain the four pillars of OOP with an example from a language you know.
- Operating systemsWhat is the difference between a process and a thread, and what causes a deadlock?
- Aptitude / logical reasoningA work-and-time or ratio problem, or a coding-decoding logical-reasoning question.
- HR / behaviouralWhy do you want to join NTT DATA, and are you open to relocation?
How to prepare
Do
- Optimise for accuracy, not attempts — the online test is adaptive and has sectional cut-offs.
- Clear each section: don’t neglect English or logical reasoning to over-invest in coding.
- Be fluent in exactly one language (C, C++, Java, or Python) rather than shaky in three.
- Revise DBMS/SQL and the OOP four pillars — they come up in almost every technical interview.
- Know your resume projects cold: your role, the stack, and one hard decision you made.
- State time/space complexity for every solution, and dry-run the edge cases aloud.
Avoid
- Blindly attempting every question and tripping a sectional cut-off through wrong answers.
- Memorising OOP or DBMS definitions without being able to give an example or apply them.
- Jumping straight to code without clarifying the problem or naming edge cases.
- Claiming projects on the resume you cannot explain end to end.
- Ignoring aptitude and English, assuming coding alone carries the test.
- Being vague about relocation or shift flexibility in the HR round.
Who can apply
Typically B.E./B.Tech in CSE, IT, ECE, or allied branches (some drives include MCA/M.Sc.) with around 60% or above throughout and no active backlogs at joining. Exact criteria vary by drive — confirm on the official posting.
NTT DATA interview FAQ
- How many rounds does NTT DATA have for software engineers?
- Usually three: an online aptitude + coding test, a technical interview (one or two rounds), and an HR interview. Some campus drives add a Group Discussion.
- Is there negative marking in the online test?
- Publicly described drives report no negative marking, but sectional minimum cut-offs apply, so you must clear every section — not just score high overall.
- Which programming language should I use?
- Any one you are fluent in — C, C++, Java, or Python. Depth in one beats shallow familiarity with several.
- How hard is the coding?
- Mostly easy-to-medium: arrays/strings, searching/sorting, linked lists, recursion, and the occasional simple DP. Correctness, complexity, and edge cases matter more than exotic tricks.
- What CS fundamentals should I revise?
- DBMS and SQL, the OOP four pillars, operating-systems basics (process vs thread, deadlock, paging), and a little computer networking.
Practise now
Rehearse the full loop with an AI panel modelled on NTT DATA’s process, in text, voice, or video.
Other company interviews
Verified from
- NTT DATA Careers (official)
- PrepInsta — NTT DATA recruitment process & test pattern
- GeeksforGeeks — NTT DATA recruitment process
- InterviewBit — NTT DATA interview questions
Wrexa Edge is an independent exam-prep platform and is not affiliated with, authorised by, or endorsed by NTT DATA. This guide is based on publicly documented interview practice; it does not reproduce any employer’s internal rubric or question bank, and it does not predict a hiring outcome.