How many rounds is the Ntt Data Europe & Latam Full Stack Engineer interview process?

Candidates report 4 stages: HR Screening, Technical Assessment, Internal Team Evaluation, and Client Interview. The interview process section above breaks down what each stage covers.

What topics come up in the Ntt Data Europe & Latam Full Stack Engineer interview?

Ntt Data Europe & Latam Full Stack Engineer interviews most often cover Full Stack Development, Java, React, Node.js (Backend), and Problem Solving (Technical Challenges), based on topics extracted from real candidate reports.

What questions does Ntt Data Europe & Latam ask Full Stack Engineer candidates?

Recent candidates report questions like "Balance Debt and Feature Delivery" and "Optimizing Time and Space Complexity". The question bank above tracks 20 questions for this role, ranked by how often they come up in Ntt Data Europe & Latam interviews.

Ntt Data Europe & LatamFull Stack Engineer

Updated Aug 24, 2025

Ntt Data Europe & Latam Full Stack Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Full Stack Engineer at Ntt Data Europe & Latam, newest first and distilled into what to expect across the loop.

Get your personalized Ntt Data Europe & Latam Full Stack Engineer prep plan

Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.

Build my free plan

Hot & recentNewest first

> 1 year

Easy Negative Rio de Janeiro

The process I went through started with an unusual challenge and then mostly stalled afterward. After an initial contact and the recruiter collecting my info, the next step was a technical take-home where I had only five days to build a streaming platform concept with playlists management. It used a React frontend and Node backend, and it required a relational database plus Docker, Git with Gitflow, and tests with at least 25% coverage.

Honestly, the deadline felt extremely tight for the scope. I managed to complete and deliver the project anyway, but four days later I got a message saying they couldn’t run the environment using what was in my README. I responded with a detailed, step-by-step explanation of the likely causes and how the setup should work.

Share your interview experience

Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.