How NTT DATA fresher hiring usually runs across Associate Software Engineer, Technical Graduate Trainee, and related tracks, synthesized from recent campus and off-campus reports. We reorganized aptitude → programming → technical → HR patterns - treat this as a prep map, not a script.
Reported eligibility (from candidate and placement-cell reports): full-time BE/B.Tech/ME/M.Tech across all branches, commonly a 60-65% or equivalent CGPA requirement across academics, no active backlogs at the time of the drive, and education gaps generally capped at around one year. Criteria vary by drive.
Candidate Profile: Final year Computer Science student, ~7.8 CGPA, on-campus drive, consistent DSA practice
Round 1 - Online written test
Delivered on a proctored AMCAT-style platform with separate sectional timers
Four sections: verbal ability, quantitative ability, computer programming and logical reasoning, roughly two hours in total
The computer programming section was MCQ-based and pulled from C and C++, OOPs, DBMS, operating systems, computer networks and some Unix basics
Adaptive question difficulty meant you could not go back and revise answers
Tip: The sectional timers are unforgiving. Practise each section against a clock rather than doing untimed full papers.
Round 2 - Group discussion
Conducted online over a video call, in groups of roughly 7 to 15 candidates
A general workplace / current affairs topic with a few minutes of preparation time
The panel looked for whether you entered early, made a structured point and let others finish
This round eliminated a significant share of the shortlist in this drive
Tip: One clear, early, structured contribution beats interrupting repeatedly later.
Round 3 - Technical interview (30-45 min)
Video interview, and clearly a step up in difficulty from the written test
Started with a resume walkthrough, then the academic project in detail: architecture, database design, what broke
DSA: explain and compare sorting algorithms, then write code to reverse a linked list and find the middle element in one pass
Core CS: OOPs pillars with examples, SQL joins with a query to write, primary vs foreign key, process vs thread, TCP vs UDP
Asked for time and space complexity on every solution
Result: Selected
Tip: The panel probed follow-ups until something broke. Say “I am not sure, but here is how I would work it out” rather than guessing confidently.
Round 4 - HR interview (20-30 min)
Background, education, family context and interest in an IT services career
Relocation flexibility across NTT DATA’s India delivery locations
Discussion of the training programme, bond or service agreement terms, and joining timelines
Final Result: Offer received
Tip: In this drive HR felt procedural rather than eliminatory, but read the service-agreement terms carefully before you accept.
Key Takeaways: Clear the written test on speed, then treat the technical round as the real interview. Fundamentals in DBMS and OS were probed as hard as the coding questions.
Takeaways
What decided it: Sectional written speed plus deep DBMS/OS fundamentals alongside coding in the technical round
Common fail: Assuming aptitude clears you; shallow OS/DBMS when coding felt easy
How to practise: Timed aptitude+programming mocks; explain normalisation and process vs thread aloud
Candidate Profile: Electronics and Communication student, ~7.0 CGPA, off-campus applicant, self-taught Python
Round 1 - Online assessment
Same aptitude plus computer programming structure, no group discussion in this off-campus route
Logical reasoning was the strongest section for this candidate; verbal ability the weakest
Tip: Non-CS candidates should not skip the programming MCQs - OOPs, DBMS and OS basics are testable even without a CS degree.
Round 2 - Technical interview
More conversational, calibrated to a non-CS background but still technical
Python basics: list vs tuple, dictionaries, exception handling, and a string-manipulation problem on a shared editor
Basic SQL: select with a where clause, then joins and a GROUP BY
Questions about why an ECE student wanted a software role, asked seriously rather than as small talk
Result: Selected
Tip: If you are from a non-CS branch, prepare a genuine answer for the switch. It was asked in the technical round, not just HR.
Round 3 - HR interview
Motivation, long-term interest in IT services, relocation and shift flexibility
Compensation, training period and joining date discussion
Final Result: Offer received
Key Takeaways: A non-CS branch is not a blocker, but you need real depth in one language plus SQL, and a convincing reason for the switch.
Takeaways
What decided it: Real depth in one language plus SQL, and a convincing reason for switching into IT services
Common fail: Claiming CS topics without examples; vague Why-IT motivation
How to practise: One language end-to-end; handwritten JOINs; a crisp branch-pivot story
Interview experience 3: Information Technology Senior Associate (on-campus, AMCAT)
Interview experience 3
Candidate profile: IT/ECE-eligible branches, on-campus drive for Information Technology Senior Associate (GeeksforGeeks on-campus report)
Round 1 - Written examination (AMCAT / Aspiring Minds)
Aptitude, verbal reasoning, and logical reasoning - standard screening sections
Computer section: output questions, C strings, OS, computer networks, software engineering, SQL, data structures
Tip: The programming MCQ block is as important as aptitude; non-CS students still face core CS MCQs
Round 2 - Group discussion
GD after written shortlist; communication and relevance to topic
Tip: Speak early with one structured point - waiting for a “perfect” opening often means silence
Round 3 - Technical interview (~1 hour)
Heavy focus on C, DS, algorithms, databases, and OOP with implementation logic
Networking: topology and OSI layers
Puzzles and logical reasoning at the end to test problem-solving under pressure
Result: Shortlist for final round after ~1 hour
Round 4 - Managerial and HR combined
Deep project walkthrough (~15 minutes): role, coding, architecture, functional/non-functional requirements, test cases, database design, web tech, research angle, societal impact
Behavioral questions mixed in - described as easier than technical if project prep is solid
Final result: Selection in that account
Key takeaways: NTT DATA campus loops can merge managerial and HR into one long project-centric round. Prepare a 15-minute project narrative before you enter, not a 30-second summary.
HR interview experience
HR interview experience
Candidate Profile: Information Technology student, selected candidate
HR interview (20-30 min)
Conversational and, by this stage, mostly a fit-and-logistics conversation
Questions included:
Tell me about yourself
Why NTT DATA, and what do you know about the company?
Why do you want a career in IT services?
Are you willing to relocate to any of our India delivery locations?
Are you comfortable with shift work for client coverage?
What are your strengths and weaknesses?
Do you have any questions for us?
The interviewer explained the training programme and the service agreement terms
Final Result: Offer received
Key Takeaways: Know a few real facts about NTT DATA - it is the global IT services arm of the Japanese NTT Group, with large delivery operations across India. Generic praise reads as unprepared.
Common interview questions from the NTT DATA process
Based on candidate reports, these come up often:
Technical interview questions:
Walk me through your project - what was your specific contribution?
Reverse a linked list / find the middle node in one pass
Explain and compare bubble, merge and quick sort, with complexities
Find duplicates in an array without extra space
Explain the four OOPs pillars with examples from your own code
SQL: joins, GROUP BY, HAVING, primary vs foreign key
Be able to explain your project architecture in two minutes
Technical interview tips
State your approach and complexity before and after coding
Expect follow-ups until you hit your limit - admit it rather than bluffing
Revise SQL joins and OS fundamentals; both are asked in almost every panel
Only list technologies you can defend in depth
HR interview tips
Know that NTT DATA is part of the Japanese NTT Group and what it delivers in India
Be honest and specific about relocation and shift constraints
Read the service agreement terms before accepting
Always ask a question at the end
HR interview
After the technical rounds, NTT DATA usually closes with a short HR conversation: motivation, relocation and shift flexibility, training and service-agreement terms, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.
Sample answers for high-frequency questions
Use these as frames, not scripts - interviewers probe follow-ups.
Q. What is the difference between a process and a thread? A. A process is an independent program in execution with its own address space, file descriptors, and memory allocations, while a thread is a unit of execution inside a process that shares that address space, heap, and open files with sibling threads but keeps its own stack, registers, and program counter. Context switching between processes is expensive because it requires swapping page tables and flushing the TLB; switching between threads of the same process is much cheaper. The trade-off is isolation: a crash in one process cannot corrupt another, but one misbehaving thread can corrupt shared memory for the whole process, which is why threads need mutexes and other synchronisation.
Q. What is the difference between TCP and UDP? A. TCP is connection-oriented: it performs a three-way handshake (SYN, SYN-ACK, ACK), numbers every byte, retransmits lost segments, reorders out-of-sequence data, and applies flow control through the receive window plus congestion control through slow start and congestion avoidance. UDP is connectionless with an eight-byte header, no handshake, no retransmission, and no ordering guarantee, so it is faster and has lower overhead. Use TCP where every byte must arrive - HTTP, SMTP, file transfer - and UDP where timeliness beats completeness, such as DNS queries, VoIP, live video, and online games.
Q. Explain the four pillars of OOP with an example. A. Encapsulation binds data and the methods that operate on it into one unit and hides internal state behind private fields with public getters and setters, so a BankAccount class can reject a negative deposit. Abstraction exposes only what a caller needs through an interface or abstract class, hiding the implementation. Inheritance lets a SavingsAccount derive from Account and reuse its behaviour, modelling an is-a relationship. Polymorphism lets the same call resolve to different implementations - compile-time via method overloading, and runtime via method overriding through a base-class reference, which is what a virtual function table implements.
Q. Write a SQL query to find employees earning more than the average salary of their department. A. Use a correlated subquery: SELECT e.name, e.dept_id, e.salary FROM Employee e WHERE e.salary > (SELECT AVG(salary) FROM Employee WHERE dept_id = e.dept_id). The inner query recomputes the average for each row’s department. A window-function version is usually faster because it makes one pass: SELECT name, dept_id, salary FROM (SELECT name, dept_id, salary, AVG(salary) OVER (PARTITION BY dept_id) AS avg_sal FROM Employee) t WHERE salary > avg_sal. Remember that AVG ignores NULL salaries in both forms.
Q. What is normalization, and what do 1NF, 2NF, and 3NF require? A. Normalization organises tables to eliminate redundancy and update anomalies. 1NF requires atomic column values with no repeating groups or multi-valued fields. 2NF requires 1NF plus no partial dependency - every non-key attribute must depend on the whole composite primary key, not just part of it. 3NF requires 2NF plus no transitive dependency, so a non-key attribute must not depend on another non-key attribute. In practice teams often stop at 3NF or BCNF and then deliberately denormalize hot read paths, because each extra normal form adds joins that cost query performance.
Tips from successful candidates
Assessment tips
Confirm the current NTT DATA pattern from the drive mail before practising old papers
Finish one problem or section fully before starting the next
Revise the fundamentals listed in the round table on this page
Interview tips
Narrate trade-offs; expect “why” after every answer
Only list projects you can defend under follow-ups
Prepare 3-4 STAR stories for behavioural prompts
HR tips
Know why NTT DATA, not just why the industry
Be clear on location / notice period / higher studies
Round-wise notes on this page are curated from public candidate reports, then reorganized with prep takeaways and outcome context. Cross-check the current drive mail for timings. For OA practice, see NTT Data placement papers.
