NTT Data Interview Guide (2026)

1Snapshot, read this first#

The one thing to understand about NTT Data: it is a large global IT services company, and fresher hiring runs like a funnel, not a boutique screen.

• They are filtering thousands of candidates for engineers who can bill on a client project within a few months of joining.
• You do not need to be a competitive-programming star. Nobody will hand you a hard dynamic-programming problem.
• You do need to clear a timed aptitude test, show solid CS basics, and look like someone who will show up and learn fast.
• Communication is not a soft extra here. A services engineer is often the face the client sees, so clear speech is scored as hard as your Java.

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

For a mass recruiter, getting shortlisted is mostly about being in the right pipeline and passing the automated filters. The test does not appear in your inbox by magic. You have to be inside one of three doors first.

On-campus is the easy door.

• The eligibility filter has already done half the work and the batch size is large.
• The placement cell registers eligible students, you sit the common online test, and shortlisted students move to interviews.
• Watch the eligibility bar: often a minimum aggregate (commonly 60% or 6.0 to 6.5 CGPA across 10th, 12th, and graduation) and an active-backlog cap, usually zero live backlogs at the time of the drive.
• Confirm these exact numbers with your placement officer before the drive window opens, so registration day holds no surprises.

Off-campus and drives need you to chase the mail.

• NTT Data posts fresher openings on its careers site and on job portals, and runs periodic drives, sometimes through aggregator platforms.
• Apply through the official careers page, register for any advertised drive, and watch for the test invitation by email.
• Read that mail line by line: it carries the test window (often a fixed 2 to 3 day slot), the platform link, and the system and webcam requirements.
• Miss the window and you usually wait for the next cycle, which can be months away. Set a reminder the moment the mail lands.

Referrals get your resume looked at faster.

• A referral from someone already at NTT Data can jump the queue and sometimes unlock a direct test invite.
• If you know an employee, send them your resume plus a two-line note on your skills and the role you want.
• Make it a copy-paste job for them, so forwarding it costs them nothing.

Resume rules: evidence, not claims.

• The first reader may be an ATS (applicant tracking system) scanning for keywords, then a recruiter who spends seconds per resume.
• One page. No photo needed. A clear skills line at the top, your degree with percentage or CGPA, and one or two projects with impact.
• Use quantified bullets. Instead of "made a website," write:

Built a student result portal (React + Node.js + MySQL) used by 300+ classmates; cut manual result lookup time from ~5 minutes to under 10 seconds.

• See the difference. The first version is a claim. The second is evidence, with a stack the interviewer can probe and a number that proves it mattered.

ATS keywords that actually help for a fresher data or software engineer role:

• The languages you truly know (Java, Python, C, SQL), plus DBMS, data structures, OOP, REST API, Git.
• Any cloud or data tool you have actually touched (AWS basics, Excel or Power BI, ETL).
• Only list what you can defend in the room. Recruiters test claimed skills, and a keyword you cannot back up does more harm than leaving it off.

3The loop at a glance#

The exact names and order shift by hiring cycle and college.

• Some drives fold the technical and HR conversations into one sitting of 40 to 50 minutes.
• A few add the versant round before the technical.
• Treat the table as the typical shape, not a guarantee.
• Read every email NTT Data sends you. The sequence in your invite overrides anything a senior tells you from last year's drive.

4The coding / aptitude rounds, patterns, not problems#

The online test is the single biggest filter. It is timed, often section-locked (you cannot go back once you leave a section), and sometimes proctored by webcam with tab-switch detection. Prepare it like an exam, not like LeetCode practice.

Quantitative aptitude: the usual placement set.

• Percentages, ratio and proportion, profit and loss, averages, time-speed-distance, time and work, simple and compound interest.
• Permutations and combinations, probability, number systems (LCM and HCF, divisibility, remainders), basic data interpretation from tables or charts.
• The math is not hard. If a percentage question takes you ninety seconds, you are already losing.
• Learn shortcuts (percentage-to-fraction conversions, the base-change trick for successive discounts) and drill timed sets until each question lands under a minute.

Logical reasoning: practice beats cleverness.

• Series (number and letter), coding-decoding, blood relations, directions, seating arrangements, syllogisms, puzzles, pattern recognition.
• These reward repetition because the question types recur across drives.
• Seating-arrangement puzzles are the usual time sink. Decide a per-question cap and bail if you blow past it.

Verbal and English: keep comprehension speed up.

• Reading comprehension, sentence correction, fill in the blanks, synonyms and antonyms, para-jumbles, error spotting.
• Read a little every day, even one news article, so the passage does not eat your time.

Coding and pseudo-code: tracing is a separate skill.

• Many services tests include a pseudo-code section: MCQs where you read a short snippet and predict the output, spot the bug, or complete the logic.
• Practice tracing loops, arrays, recursion, and simple conditionals on paper, because reading code by eye under a clock is not the same muscle as writing it.
• If there is a hands-on section, expect 1 to 2 easy problems: string manipulation (reverse, palindrome, vowel count), array basics (max and min, sum, search), simple number logic (prime, factorial, Fibonacci, Armstrong), basic patterns.
• Write in the language you are strongest in, usually Java, Python, or C.

Here is the kind of snippet a pseudo-code MCQ throws at you. What does this print?

def f(n):
    if n <= 1:
        return 1
    return n * f(n - 1)

print(f(4))

How to win the round:

• Watch the clock per section. Flag a time-eater and move on. A blank answer and a wrong answer often score the same, so an unattempted easy question later is pure lost points.
• Attempt the easy coding problem first and fully. One clean, fully-passing solution beats two half-done ones, since most platforms score on test cases passed, not partial logic.
• Test your code mentally on edge cases before you submit: empty input, single element, the largest value, a zero or a negative. Most failed submissions die on an edge case, not the main path.
• Do at least five full-length timed mocks before the real one. Speed under pressure is trained, not born. The first mock will feel awful. That is the point: fail it in practice, not in the drive.
• Check the test rules for section locking and tab-switch flagging. Set up a quiet space, good internet, a charged laptop, and a working webcam the day before, not an hour before.

5CS fundamentals (the technical backbone)#

For a fresher at a services company, the technical interview leans on core computer-science subjects more than hard algorithms. The interviewer is usually a project lead who wants to know you can be trained, not whether you can invent an algorithm. Prepare these four pillars and you handle most of what they ask.

Operating systems.

• Process vs thread (separate memory vs shared memory is the one-liner).
• Scheduling (round robin, FCFS, priority).
• Deadlock: the four conditions (mutual exclusion, hold and wait, no preemption, circular wait) and how to prevent them.
• Paging and segmentation, virtual memory.
• Semaphore vs mutex (a mutex is a lock owned by one thread, a semaphore is a counter).
• What a context switch is and why it costs performance.

DBMS and SQL.

• Normalization (1NF, 2NF, 3NF and the "why," reducing redundancy and update anomalies).
• Primary vs foreign key, ACID properties (atomicity, consistency, isolation, durability, a one-liner each).
• Joins (inner, left, right, full), indexes and why they speed reads but slow writes.
• DELETE vs TRUNCATE vs DROP (row-level and rollback-able, table-level and fast, structure-gone).
• Be ready to write a query live. The second-highest-salary question is almost a rite of passage:

SELECT MAX(salary) AS second_highest
FROM employees
WHERE salary < (SELECT MAX(salary) FROM employees);

• They may also ask "count employees per department" (a GROUP BY) or a basic JOIN across two tables.
• SQL comes up a lot in data-engineering tracks. If your resume says "data," expect at least two SQL questions.

Computer networks (lighter touch).

• OSI vs TCP/IP layers, TCP vs UDP (reliable and ordered vs fast and fire-and-forget).
• What happens when you type a URL and press enter (DNS lookup, TCP handshake, HTTP request, response, render).
• Basics of IP, DNS, and HTTP vs HTTPS (the S is TLS encryption).
• Usually a quick checkbox, not a deep grilling, but a blank stare here reads badly.

OOP (a grader favorite).

• The four pillars: encapsulation, abstraction, inheritance, polymorphism, each with a one-line definition and a tiny real example (a Car class, a Shape with an area method).
• Overloading vs overriding (same name different params in one class vs redefining a parent method in a child).
• Abstract class vs interface.
• It is quick to ask and easy to grade, and a crisp, example-backed answer sets the tone for the whole round.

Your language and projects.

• Know your primary language well. For Java: JVM basics, the collections framework (ArrayList vs LinkedList vs HashMap), checked vs unchecked exceptions. For Python: data types, lists vs tuples (mutable vs immutable), list comprehensions.
• Walk through one project end to end: what problem it solved, your exact contribution (not "we," say "I"), the stack, and one thing you would improve.
• Interviewers probe projects to check you actually built what the resume claims. If a teammate wrote a module, say so and explain what you did instead.

A classic DSA sampler they might pick from:

• Reverse a linked list, detect a loop (Floyd's two-pointer), check balanced parentheses with a stack.
• Find a duplicate in an array, binary search.
• Sort basics (why quicksort averages faster but mergesort is stable and worst-case safe).
• Explain your approach and complexity in Big-O before you code. Saying "this is O(n) time and O(1) space because I scan once with two pointers" out loud, before writing a line, is often what separates a pass from a maybe.

6Behavioral & culture fit#

NTT Data presents itself around clients-first delivery, teamwork, continuous learning, integrity, and respect for diverse global teams. You do not need to memorize a slogan. What HR and the technical interviewers are really checking is simpler.

• Can this person communicate clearly?
• Will they stay and grow instead of jumping after six months?
• Are they flexible on location and shift? Services projects run on client time zones, sometimes night shifts.
• Do they genuinely want this job?

Prepare short STAR stories (Situation, Task, Action, Result) for:

• A team project.
• A conflict or setback you handled.
• A time you learned something fast.
• A time you took initiative.
• Keep each to about 60 to 90 seconds and end on a concrete result. Rambling past ninety seconds is itself a red flag for a client-facing role, so time yourself when you rehearse.

One full worked STAR example, "a time you handled a setback":

• Situation: In my final-year team project, our group of four was building a college event-management web app, and two weeks before the demo our backend developer dropped out.
• Task: I had only worked on the frontend, but someone had to finish the Node.js APIs and database so we could ship on time.
• Action: I spent three evenings learning the existing Express routes, split the remaining work into a checklist, took the login and registration APIs myself, and paired with a teammate daily so we never blocked each other.

• Result: We delivered all core features for the demo, scored 9 out of 10 from the review panel, and the app handled registrations for an event with about 200 students without a crash.

• Notice the result has a number. Always land your story on something measurable, and keep the "Action" in the first person. The interviewer is grading what you did, not what the team did.

For "why NTT Data," have a genuine two-line answer.

• A large, stable global company where a fresher gets structured training, exposure to real client projects across industries, and a clear path from trainee to engineer to lead.
• Avoid "I just need a job" and avoid naming only the salary.
• Tie it back to one thing you actually want: the training, the scale, or the client exposure.

7Your prep plan#

4-week plan

• Week 1: Aptitude foundations, quants topic by topic, learn shortcuts, start timed logical-reasoning sets.
• Week 2: Coding and pseudo-code, trace snippets daily, solve 3 to 5 easy problems a day in your main language, revise SQL basics.
• Week 3: CS fundamentals, OS, DBMS, CN, OOP; make one-page notes per subject; rehearse your project walkthrough.
• Week 4: Full-length timed mock tests, HR and STAR stories out loud, mock interview with a friend, polish resume and "why NTT Data."

2-week plan

• Days 1 to 4: Quants + logical, timed.
• Days 5 to 7: Verbal + pseudo-code + easy coding.
• Days 8 to 10: OS, DBMS, SQL, OOP core notes.
• Days 11 to 12: Two full mock tests.
• Days 13 to 14: STAR stories, project revision, resume and HR answers.

2-day crash plan

• Day 1: One timed aptitude mock; review every wrong answer, not just the score. Revise OOP four pillars, normalization, joins, TCP vs UDP, process vs thread. Write and run 5 easy coding problems end to end.
• Day 2: One more aptitude mock. Rehearse your project walkthrough and 3 STAR stories out loud. Write your "why NTT Data" line. Check webcam, internet, charger, and quiet space for the test.

8Why people get rejected at NTT Data#

1. Running out of time on the aptitude test. Strong candidates who never practiced timing get filtered before any human sees them. This is the number one killer, and it is entirely preventable with mock tests.
2. Going silent in the technical round. Interviewers need to hear your thinking. A right answer with no explanation reads as a guess, and a wrong answer with clear reasoning often still earns credit.
3. Resume claims that collapse under questions. Listing a skill or project you cannot explain ends the interview fast and makes the interviewer distrust the rest of the page.
4. Weak communication. For a client-facing services role, unclear spoken English is a real blocker. The versant or HR round exists partly to catch this, so practice speaking answers aloud, not just thinking them.
5. No clear reason for wanting the job. "Any company is fine" signals you will leave the moment something else appears, and attrition is expensive for a mass hirer.
6. Inflexibility on relocation or shifts. Being rigid about location or timing when the role requires it often closes the door, since projects get staffed by availability, not preference.

9The offer, comp & negotiation#

For freshers in India, expect a package roughly in the Rs 3.5 to 7 LPA range.

• It varies by the specific role, your degree, the hiring cycle, and whether it is a standard trainee hire or a higher "digital" or "premium" track.
• The structure is typically a fixed base, a smaller variable or performance component, and standard benefits (provident fund, health insurance, and sometimes a joining or retention element).
• Higher offers in this band usually go to candidates who clear a more advanced or specialized track in the test. The way to a bigger number is to attempt and pass the harder section, not to negotiate afterward.

Negotiation reality and tips:

• For bulk fresher hiring, the base number is often fixed by band, so there is limited room to move the headline figure. Do not treat it like a lateral negotiation and do not open with a demand.
• Your one real lever is a competing offer or a stronger track. If you have a genuine competing offer, mention it politely and ask whether a higher band is possible. That is the thing that occasionally moves the number.
• Get the details in writing: fixed vs variable split, bond or service agreement (if any), location, shift, and expected joining date. Understanding the full package matters more than squeezing the base, because a surprise night shift or a two-year bond you did not read costs more than a few thousand rupees of base.

10FAQ#

Q: Does NTT Data have a single named test like TCS NQT or Infosys InfyTQ? A: Not one universally branded exam the way some peers do. The online assessment format (aptitude plus coding or pseudo-code) varies by drive and college and may run on different assessment platforms. Always rely on the exact instructions in your invitation email rather than a fixed name or a senior's description from an earlier cycle.

Q: How hard is the coding section for freshers? A: Light. Expect pseudo-code output and MCQ questions and 1 to 2 easy hands-on problems (strings, arrays, basic number logic). Clean fundamentals and a fully-passing easy solution beat fancy algorithms here.

Q: Which programming language should I use? A: Whichever you are strongest in, commonly Java, Python, or C. Pick one and know it well, including its standard library basics, rather than spreading thin across three.

Q: Is there a bond or service agreement? A: Services companies sometimes include a service agreement or training commitment for freshers. If one applies, it will be in your offer letter. Read it before signing and ask HR to clarify the duration and any exit penalty before you accept.

Q: What matters most if I only have two days to prepare? A: Aptitude timing and CS fundamentals. Do one full timed aptitude mock, revise OOP, DBMS and SQL, and OS basics, and rehearse your project walkthrough and a couple of STAR stories out loud. Speaking the answers aloud is the step most people skip and the one that shows up in the room.

Want this turned into a personalized, dated study schedule that fits the weeks you have left before your test? Build your own plan from the week-by-week outline above and start with the very next step today.