Ntt Data Corporation Software Engineer interview typically runs 3-5 rounds: HR screen, technical test, technical interview, client interview, and HR discussion. Timeline is a few weeks; it is resume-driven and often includes salary and client-fit checks early.
$100K
Avg. Base Comp
$176K
Avg. Total Comp
4-5
Typical Rounds
2-4 weeks
Process Length
We've seen Ntt Data evaluate software engineers less like a pure coding screen and more like a resume-to-role match. Multiple candidates reported that the conversation stayed anchored in what they had actually built: custom middleware, JWT handling, route guards, Azure Functions, Python code samples, and project-specific decisions. Even when the questions were broad, the interviewers kept circling back to recent work and expected candidates to explain their own implementation choices, not just recite definitions.
A recurring theme is how much the process changes by team and client. Our candidates report everything from a quick checklist of stack questions to a much longer, more detailed backend discussion, but the common thread is that the bar is usually practical rather than algorithmic. The non-obvious signal here is clarity under scrutiny: if you can walk through a project, justify a code path, and answer follow-ups on the spot, you tend to do well. If your experience is thin or disconnected from the role, that gap shows up quickly.
Compensation and fit also surface earlier than many candidates expect. Several experiences mention salary expectations, role alignment, and client-fit questions becoming part of the evaluation before the process feels “finished.” That means the company is not only checking technical readiness; it is also screening for direct experience in the proposed stack and level. Candidates who assumed the title alone would carry them were often disappointed, while those who matched the role closely found the process straightforward, if somewhat uneven in communication.
Synthetized from 3 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Ntt Data Corporation process.
My process started with a telephonic HR screen where they checked technical fit, current and expected CTC, and a few basic background details. After that, I went through an L1 technical round for a full stack .NET developer role, then a second technical round, followed by a client technical round and finally an HR discussion about personal information, salary negotiation, and releasing the offer. In practice, the process felt longer than the “3 rounds” I had expected, but the core evaluation was still mostly technical and based on my resume.
The questions were centered on .NET Core, Web API, Entity Framework, SQL Server, and Angular. I was asked about challenges from my recent project, a custom middleware I had worked on, how JWT token mechanisms work, custom extension methods, route guards and how to implement one, GC levels and how garbage collection works internally, Angular versions and the differences between them, design patterns, Azure Functions, and Web API status codes. There was also a SQL query question and a code-tracing problem, plus a code review-style discussion. The difficulty was easy to moderate overall, but it was very resume-driven, so they expected you to explain what you had actually built rather than just answer theory.
What stood out to me was that the interviewers seemed to move quickly through a broad checklist of stack topics instead of going very deep on any one area. If you are comfortable with your recent project and can explain your .NET and Angular work clearly, that covers a lot of the ground. I did not get an offer, and the feedback was essentially that they wanted someone with more experience.
Prep tip from this candidate
Be ready to walk through your recent .NET project in detail, especially custom middleware, JWT flow, route guards, and any code review or tracing exercise. Also practice SQL interview questions like second-highest salary and be able to explain GC internals and Web API status codes clearly.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Ntt Data Corporation
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Implementing the Fibonacci Sequence in Three Different Methods | |
| DDoS Attack Response | |
| Offer Matching API Design | |
| Stakeholder Communication | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Largest Salary by Department | |
| Prime to N | |
| Employee Salaries | |
| Bagging vs Boosting | |
| Raining in Seattle | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Closest SAT Scores | |
| Over-Budget Projects | |
| P-value to a Layman | |
| Size of Joins | |
| Hurdles In Data Projects | |
| First Touch Attribution | |
| Top 3 Users | |
| The Brackets Problem | |
| Get Top N Frequent Words | |
| Employee Project Budgets | |
| SELECTive Wine Connoisseur | |
| Manager Team Sizes | |
| Find Duplicate Numbers in a List | |
| Real-Time Transaction Streaming |
Synthesized from candidate reports. Individual experiences may vary.
The process often begins with an HR or recruiter call, sometimes after outreach on LinkedIn. This stage covers basic background details, academic history, current and expected CTC, salary expectations, and initial role fit.
Candidates then complete an initial technical evaluation, which may be a technical test or a live interview. The questions are usually practical and resume-driven, focusing on the candidate’s own projects and stack familiarity rather than heavy algorithmic problems.
The core of the process is one or more technical rounds, often with an L1 and a second technical interview. For software engineer roles, these rounds can cover .NET Core, Web API, Entity Framework, SQL Server, Angular, Java, Spring Boot, JavaScript, Python code review, and project deep-dives, along with code tracing or simple SQL questions.
Some candidates also have a client-facing technical round or a basic manager interview. This stage tends to focus on project experience, how problems were solved, and whether the candidate fits the client’s expectations and the role’s scope.
The final stage is an HR discussion covering personal information, compensation, and offer alignment. Salary expectations and role fit are checked again here, and in some cases the offer amount is discussed before a final decision is made.