As a Software Engineer at NTT DATA, you play a central role in driving modern digital transformation for global enterprises and enterprise clients. Operating as a major global IT services and consulting leader, NTT DATA positions its software engineers at the intersection of custom software development, modern enterprise architectures, and specialized client delivery. You will work on cross-functional teams building microservices, integrating cloud platforms, and modernizing complex systems for industry-leading clients across healthcare, finance, telecommunications, and public sector industries. The impact of this role extends across high-consequence enterprise applications and cloud transformations. Whether you are engineering distributed Java/.NET backends, designing reactive frontends using Angular or React, or configuring automated cloud infrastructure on AWS and Azure, your solutions directly impact system scalability, security, and runtime reliability. Engineers at NTT DATA frequently interact with global enterprise software ecosystems, implementing robust RESTful APIs, event-driven integrations with platforms like Apache Kafka, and scalable relational or NoSQL database architectures. What makes this role compelling is the sheer breadth of technology environments and business domains you will engage with.
Phone Screening
reportedInitial screening conducted by a recruiter covering professional background, project experiences, and compensation expectations.
What to demonstrate
- Initial screening conducted by a recruiter covering professional background, project experiences, and compensation expectations
- Depth in Java
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Online Assessment
reportedCandidates may complete an online assessment with analytical aptitude questions and coding tasks, especially for entry-level positions.
What to demonstrate
- Candidates may complete an online assessment with analytical aptitude questions and coding tasks, especially for entry-level positions
- Depth in Java
How to prepare
- Answer aloud and timed: How do Java Streams work internally, and how do you use functional interfaces to optimize collection filtering?
- Answer aloud and timed: Explain memory management and Garbage Collection (GC) generations in Java.
Technical Discussion L1
reportedInitial technical evaluation covering core programming fundamentals and framework concepts.
What to demonstrate
- Initial technical evaluation covering core programming fundamentals and framework concepts
- Depth in Java
How to prepare
- Answer aloud and timed: What key changes and language features were introduced in Java from version 8 through recent LTS releases?
- Answer aloud and timed: What is the fundamental difference between
stateandpropsin React, and how do custom hooks work?
Technical Discussion L2
reportedAdvanced technical or architectural round to evaluate deeper technical knowledge.
What to demonstrate
- Advanced technical or architectural round to evaluate deeper technical knowledge
- Depth in Java
How to prepare
- Answer aloud and timed: How do Route Guards work in Angular, and how do you implement a custom auth guard?
- Answer aloud and timed: What are RxJS Observables, and how do they differ from Promises in handling async data streams?
Client Interview
reportedFinal interview to confirm domain fit and project-specific requirements for client-facing roles.
What to demonstrate
- Final interview to confirm domain fit and project-specific requirements for client-facing roles
- Depth in Java
How to prepare
- Answer aloud and timed: What is the difference between HTTP and HTTPS, and how does the SSL/TLS handshake mechanism work?
- Answer aloud and timed: Explain the difference between TCP and UDP, detailing when each protocol should be utilized in web architectures.
Managerial and HR Discussion
reportedFinal discussion to finalize compensation and logistical details.
What to demonstrate
- Final discussion to finalize compensation and logistical details
- Depth in Java
How to prepare
- Answer aloud and timed: How do you implement custom middleware in.NET Core or Spring Boot to intercept incoming web requests?
- Answer aloud and timed: How do you prevent cascading failures between dependent microservices? Explain patterns like Circuit Breaker.
3 candidate reports. Individual accounts describe a particular role and hiring cycle.
NTT DATA Software Engineer interview: unclear Java questions
The technical interview leaned heavily on Java and software fundamentals. I expected clear, role-focused questions, but the interviewer was not always clear about what was being asked, so it was hard to judge how much detail an answer needed. The conversation also covered version control and GitHub, HTTP basics, database management, a project I had worked on, and other practical experience. That…
Read full experienceSoftware Engineer interview at NTT DATA: interview experience
I went through two technical discussions and one assessment round. The structure seemed meant to confirm that I could do the work rather than repeat buzzwords. The overall atmosphere was professional and calm, and the interviewers came across as technically solid. The technical conversations followed my resume in a natural way, and the assessment did not feel like a gotcha. I felt the interviewer…
Read full experienceNTT DATA Software Engineer interview: graduate assessment-centre logistics
The interview itself was not technically difficult, but the logistics threw me off immediately. I attended a graduate assessment centre scheduled to begin at 9:00 and was told to arrive early. At about 9:10, I was still waiting at the front desk with no staff in sight. During the introduction, I learned that the session was actually supposed to start later, around 9:30, and that the expected arri…
Read full experiencePracHub editorial advice for the preparation topics above.
Master Your Core Stack Basics
Interviewers focus heavily on fundamental concepts. Ensure you can comfortably explain core language features (such as Java Streams, garbage collection, or React hook rules) without stumbling over syntax or basic definitions.
Structure Your Project Explanations
When discussing past project experience, use the STAR approach (Situation, Task, Action, Result). Highlight your specific technical contributions, architectural choices, and the measurable business impact of your work.
Be Prepared for Diagnostic Scenarios
Expect situational questions like "How would you debug a service taking 10 seconds to respond?" Practice walking through systematic diagnostic steps (checking network calls, analyzing logs, inspecting DB execution plans, checking CPU/memory metrics).
Clarify Client and Project Contexts
During technical and managerial rounds, ask thoughtful questions about the tech stack, team structure, client domain, and deployment environments. This shows professional maturity and engagement.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
What are the core pillars of Object-Oriented Programming (OOP) and how do you implement runtime polymorphism?
What are the core pillars of Object-Oriented Programming (OOP) and how do you implement runtime polymorphism?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
What is the difference between `HashMap`, `Hashtable`, and `ConcurrentHashMap` in Java?
What is the difference between HashMap, Hashtable, and ConcurrentHashMap in Java?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Explain memory management and Garbage Collection (GC) generations in Java.
Explain memory management and Garbage Collection (GC) generations in Java.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
What are RxJS Observables, and how do they differ from Promises in handling async data streams?
What are RxJS Observables, and how do they differ from Promises in handling async data streams?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
How do you write a SQL query to find the second highest salary in an employee table using subqueries or window
How do you write a SQL query to find the second highest salary in an employee table using subqueries or window functions?
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- Handle the rows that do not match: that is usually the actual question.
Follow-up
- How does the query change if that join becomes one-to-many?
- What happens to this when the table is ten times larger?
What are the key differences between SQL and NoSQL databases, and how do you decide which to use?
What are the key differences between SQL and NoSQL databases, and how do you decide which to use?
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- Handle the rows that do not match: that is usually the actual question.
Follow-up
- How does the query change if that join becomes one-to-many?
- What happens to this when the table is ten times larger?
What are the different types of SQL JOINs (INNER, LEFT, RIGHT, FULL) and how do query execution plans optimize
What are the different types of SQL JOINs (INNER, LEFT, RIGHT, FULL) and how do query execution plans optimize them?
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- Handle the rows that do not match: that is usually the actual question.
Follow-up
- How does the query change if that join becomes one-to-many?
- What happens to this when the table is ten times larger?
How do Java Streams work internally, and how do you use functional interfaces to optimize collection filtering
How do Java Streams work internally, and how do you use functional interfaces to optimize collection filtering?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What key changes and language features were introduced in Java from version 8 through recent LTS releases?
What key changes and language features were introduced in Java from version 8 through recent LTS releases?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What is the fundamental difference between `state` and `props` in React, and how do custom hooks work?
What is the fundamental difference between state and props in React, and how do custom hooks work?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How do Route Guards work in Angular, and how do you implement a custom auth guard?
How do Route Guards work in Angular, and how do you implement a custom auth guard?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What is the difference between HTTP and HTTPS, and how does the SSL/TLS handshake mechanism work?
What is the difference between HTTP and HTTPS, and how does the SSL/TLS handshake mechanism work?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Explain the difference between TCP and UDP, detailing when each protocol should be utilized in web architectur
Explain the difference between TCP and UDP, detailing when each protocol should be utilized in web architectures.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
How do you implement custom middleware in.NET Core or Spring Boot to intercept incoming web requests?
How do you implement custom middleware in.NET Core or Spring Boot to intercept incoming web requests?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
How do you prevent cascading failures between dependent microservices? Explain patterns like Circuit Breaker.
How do you prevent cascading failures between dependent microservices? Explain patterns like Circuit Breaker.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Explain the JWT authentication flow and the signing algorithm mechanism used to secure REST APIs.
Explain the JWT authentication flow and the signing algorithm mechanism used to secure REST APIs.
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
What is the role of Apache Kafka in distributed systems, and how does it manage event messaging across partiti
What is the role of Apache Kafka in distributed systems, and how does it manage event messaging across partitions?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
What is dependency injection, and why is it critical for achieving loose coupling and testability in clean arc
What is dependency injection, and why is it critical for achieving loose coupling and testability in clean architecture?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
How do Primary Keys and Foreign Keys enforce integrity in Many-to-Many junction tables?
How do Primary Keys and Foreign Keys enforce integrity in Many-to-Many junction tables?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What is idempotency in REST API design, and why is it vital for retry logic in distributed architectures?
What is idempotency in REST API design, and why is it vital for retry logic in distributed architectures?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
Describe the principles of Hexagonal Architecture (Ports and Adapters) and how it decouples business logic fro
Describe the principles of Hexagonal Architecture (Ports and Adapters) and how it decouples business logic from external frameworks.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Explain how you would design a scalable URL shortening service like Bitly, detailing database schema and hashi
Explain how you would design a scalable URL shortening service like Bitly, detailing database schema and hashing strategies.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
How do you troubleshoot a server that experiences intermittent performance degradation under unpredictable tra
How do you troubleshoot a server that experiences intermittent performance degradation under unpredictable traffic spikes?
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- Separate the trigger from the cause; the deploy is rarely the bug.
Follow-up
- What would you look at first, and what would it rule out?
- How would you tell a cause from a coincidence here?
What are DRS affinity and anti-affinity rules in virtualized environments, and how do they maintain continuous
What are DRS affinity and anti-affinity rules in virtualized environments, and how do they maintain continuous system availability?
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- Separate the trigger from the cause; the deploy is rarely the bug.
Follow-up
- What would you look at first, and what would it rule out?
- How would you tell a cause from a coincidence here?
Built from the rounds and topics NTT DATA candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the NTT DATA loop
- Write out the reported sequence: Phone Screening, Online Assessment, Technical Discussion L1, Technical Discussion L2, Client Interview, Managerial and HR Discussion.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 6 reported rounds, with the weakest marked.
02Work Java
- Spend the session on Java, which NTT DATA candidates report being tested on.
- Write one worked example in Java and time yourself on it.
Deliverable: One timed worked example in Java.
03Work JWT (JSON Web Tokens)
- Spend the session on JWT (JSON Web Tokens), which NTT DATA candidates report being tested on.
- Write one worked example in JWT (JSON Web Tokens) and time yourself on it.
Deliverable: One timed worked example in JWT (JSON Web Tokens).
04Work Angular
- Spend the session on Angular, which NTT DATA candidates report being tested on.
- Write one worked example in Angular and time yourself on it.
Deliverable: One timed worked example in Angular.
05Answer out loud: Core Java & Object-Oriented Programming
- Answer aloud, timed: What are the core pillars of Object-Oriented Programming (OOP) and how do you implement runtime polymorphism?
- Answer aloud, timed: What is the difference between `HashMap`, `Hashtable`, and `ConcurrentHashMap` in Java?
Deliverable: Spoken answers to 2 reported Core Java & Object-Oriented Programming question(s), under time.
06Answer out loud: Frontend Frameworks & Web Fundamentals
- Answer aloud, timed: What is the fundamental difference between `state` and `props` in React, and how do custom hooks work?
- Answer aloud, timed: How do Route Guards work in Angular, and how do you implement a custom auth guard?
Deliverable: Spoken answers to 2 reported Frontend Frameworks & Web Fundamentals question(s), under time.
07Answer out loud: Backend Frameworks, Microservices & Integration
- Answer aloud, timed: How do you implement custom middleware in.NET Core or Spring Boot to intercept incoming web requests?
- Answer aloud, timed: How do you prevent cascading failures between dependent microservices? Explain patterns like Circuit Breaker.
Deliverable: Spoken answers to 2 reported Backend Frameworks, Microservices & Integration question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
How do you handle database migration, indexing strategies, and query performance tuning in large datasets?
How do you handle database migration, indexing strategies, and query performance tuning in large datasets?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Argue against a design, lose, and commit anyway
Describe a design you argued against and lost. State the failure you predicted as a named mechanism, not a feeling about complexity: two services that would need one transaction, a projection with no rebuild path, a write path with no idempotency key. Say what evidence you brought, what the decision maker weighed instead, and what you did after the decision was made: what you instrumented, what you wrote down, and whether the prediction came true. Five minutes.
Approach
- State the prediction in falsifiable form up front: the mechanism, the condition that triggers it, and the observable outcome. A prediction that cannot be checked also cannot be credited to you later.
- Show the evidence you had at the time and label each piece honestly as measured, analogous, or intuition. Keeping the intuition is fine; disguising it as data is the thing that erodes your standing in the next argument.
- Represent the opposing case at full strength, including the constraint you did not control: a fixed date, a team boundary, or the fact that the decision was cheap to reverse and yours was not.
- Make disagree-and-commit concrete. Name the artefact you left behind so the prediction could be settled without you: the alert and its threshold, the counter on the dashboard, the decision note that recorded the trade-off and the condition that would revisit it.
Follow-up
- What threshold on that alert would have proved you right, and did anyone ever look at it?
- If the same proposal arrived tomorrow with the same deadline, would you argue it the same way?
Narrate an outage you owned from page to postmortem
Pick an incident you personally drove, ideally one where writes were affected rather than reads. In six to eight minutes: state the symptom as it first appeared on a dashboard, the blast radius you established before you knew the cause, the mitigation you applied and when, the mechanism you eventually proved, and the follow-up that would prevent a repeat. Bring numbers: error rate, tenants affected, minutes to mitigate, minutes to resolve. If you cannot name what you measured, choose a different incident.
Approach
- Open on the signal rather than the cause: which metric at which percentile moved, on which service, at what time, so the listener follows the same evidence you had rather than a conclusion you already reached.
- Separate mitigation from diagnosis out loud. State what you did to stop the bleeding (flag off, shed traffic, drain a lease, roll back a deploy) and say plainly that you did it before the mechanism was known, because those are two jobs with different deadlines.
- Establish blast radius in countable terms: how many tenants, how many writes, and crucially whether the effect was loss or only delay. An append-only revision table or a pending outbox row means the change survived and the projection was merely behind, which is a repair rather than a data-loss incident.
- Prove the mechanism instead of asserting it. Name the trace span that grew, the plan that flipped to a sequential scan, the lease that expired, plus one alternative you ruled out and the signal that stayed flat while you ruled it out.
Follow-up
- What would you do differently in the first five minutes, given the same dashboard and no more information?
- Which follow-up action did you deliberately not take, and why was dropping it the right call?
- 01
How do you handle database migration, indexing strategies, and query performance tuning in large datasets?
- 02
Describe a design you argued against and lost. State the failure you predicted as a named mechanism, not a feeling about complexity: two services that would need one transaction, a projection with no rebuild path, a write path with no idempotency key. Say what evidence you brought, what the decision maker weighed instead, and what you did after the decision was made: what you instrumented, what you wrote down, and whether the prediction came true. Five minutes.
- 03
Pick an incident you personally drove, ideally one where writes were affected rather than reads. In six to eight minutes: state the symptom as it first appeared on a dashboard, the blast radius you established before you knew the cause, the mitigation you applied and when, the mechanism you eventually proved, and the follow-up that would prevent a repeat. Bring numbers: error rate, tenants affected, minutes to mitigate, minutes to resolve. If you cannot name what you measured, choose a different incident.
How technical are the interview rounds at NTT DATA?
The technical rounds focus heavily on core language fundamentals, framework mechanics, and real-world application. Rather than complex competitive programming algorithm puzzles, expect direct questions on design patterns, memory management, database querying, and debugging scenario problems.
NTT DATA Software Engineer candidate reports ↗Does NTT DATA require client-facing interviews?
Yes, for many project assignments—particularly in consulting or client delivery roles—you will complete an internal technical round followed by a client interview. The client round verifies that your technical background and soft skills closely match the specific project's domain requirements.
NTT DATA Software Engineer candidate reports ↗What differentiates successful candidates in this process?
Successful candidates articulate their thought process clearly, demonstrate strong foundational knowledge of their core tech stack, and show enthusiasm for client problem-solving. Being honest about what you know—and logically walking through how you would solve what you don't know—is highly valued by interviewers.
NTT DATA Software Engineer candidate reports ↗What is the typical timeframe from initial screening to receiving an offer?
The entire process typically takes between 2 to 4 weeks. However, because hiring schedules can depend on specific client project pipelines and onboarding windows, communication timing may occasionally vary between rounds.
NTT DATA Software Engineer candidate reports ↗What remote or hybrid work options are available?
Work arrangements depend on the specific team, regional delivery center, and client security requirements. Many roles offer hybrid arrangements, while certain project positions require onsite attendance at client facilities or regional NTT DATA offices.
NTT DATA Software Engineer candidate reports ↗What topics does NTT DATA test in interviews?
NTT DATA interviews most often cover Problem Solving, Python, SQL, Java, and Databricks. The exact emphasis depends on the specific role you apply for.
NTT DATA Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01NTT DATA Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
GitHub Software Engineer Interview Questions & Guide 2026
Testing exercises for GitHub software engineer prep: choosing boundary cases over repetition, isolating tests from shared clock and ordering, and treating an intermittent failure as a defect rather than noise.
Zoom Communications Software Engineer Interview Guide
What Zoom Communications asks Software Engineer candidates, from reported rounds and questions.
Zemoso Technologies Software Engineer Interview Guide
What Zemoso Technologies asks Software Engineer candidates, from reported rounds and questions.
YASH Technologies Software Engineer Interview Guide
What YASH Technologies asks Software Engineer candidates, from reported rounds and questions.