Skip to content

NTT Data Placement Papers 2026

NTT Data is a global IT services and digital transformation company founded in 1988, with operations in 50+ countries. NTT Data India is a large campus recruiter. Some campus drives add AMCAT-style papers or a GD. Associate is the usual entry role.


HQ: Tokyo, Japan
Employees: 190,000+
Revenue: $20+ Billion USD

Explore: Online Assessment · Coding Questions · Interview Experience · Preparation Guide · Certifications & Career · Download PDF

NTT Data is a volume campus hirer in the global IT services lane. The academic floor is usually printed. The OA is what actually deletes people.

  • For: B.E./B.Tech/MCA/M.Sc (CS/IT) students targeting Associate (and related entry engineering) via campus, pool, or off-campus careers.
  • Not the same track: Experienced digital-transformation loops, or non-engineering BPS posts with a different English-and-shifts story. This hub is the fresher Associate filter.
  • M.E./M.Tech: Often listed as eligible on NTT Data tables (unlike some services firms). Still read the mailer.
Route What usually changes What stays the same
Campus / pool PPT, college % list, possible GD Aptitude + coding bar
Careers portal Form + platform invite Same written flavour
Referral Visibility You still sit every elimination round

Off-campus does not mean easier quant. It often means more applicants who skip timed aptitude and die on sectional cutoffs.

Degree, 60% throughout, and “is 6.0 enough?”

Section titled “Degree, 60% throughout, and “is 6.0 enough?””

Is 6.0 CGPA enough? It matches many campus guides (or 60%). The phrase that matters is throughout 10th, 12th, and graduation. A 7.8 B.Tech with 58% in 12th is how people get dropped after OA. A 6.2 who finishes aptitude, submits one complete program, and can explain OOP beats an 8.5 who random-fills verbal.

10th / 12th: They count. Keep marksheets. “Throughout” is not a slogan.

Gaps: Maximum ~2 years education gap appears in eligibility tables. Live backlogs at exam time are a no.

What helps the resume screen: Readable English, one project, any internship. Cloud buzzwords without a sentence you can say aloud do not help. See certifications after aptitude and one language, not instead of them.

Academic snapshot

Marks: 60% or 6.0+ CGPA throughout 10th, 12th, UG (and PG if taken)

Degree: B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT)

Backlogs: None active at selection

Gap: Typically max ~2 years

Skills they actually filter

Written: Aptitude + technical MCQs

Coding: 1-2 easy-medium problems

Interview: OOP, DBMS, project

Languages: C, C++, Java, Python

Item Typical expectation (candidate-reported) Reality check
CGPA / % 60% or 6.0+ across 10th, 12th, graduation Mailer wins
Degree B.E./B.Tech/M.E./M.Tech/MCA/M.Sc CS/IT Related circuital branches on many drives
Year Final year + recent grads (often within 2 years) Confirm batch year
Backlogs None active Clear before joining
Gap ≤ ~2 years Explain honestly in HR
Course type Full-time only Distance degrees usually out

The minimum CGPA required is commonly cited as 6.0 / 60% across 10th, 12th, and graduation. Treat it as a shortlisting filter when printed. NTT Data still decides on OA cutoffs and interview narration.

Academic Level Minimum (typical) Notes
10th 6.0 CGPA / 60% Consistently applied on many drives
12th 6.0 CGPA / 60% Diploma holders evaluated similarly
Graduation 6.0 CGPA / 60% aggregate No active backlogs at hiring
Backlogs None active Cleared backlogs generally accepted

A 7.0+ helps shortlisting when volumes are high. It does not replace a complete coding submit.

NTT Data does not publish one permanent official paper set. Papers on placementpapers.app are pattern trainers for aptitude+technical+coding and interview themes.

Round (typical) What to practice
Aptitude Quant, logical, verbal under a 45-minute feel
Technical MCQs Programming, DSA basics, DBMS, OOP
Coding 1-2 array/string/basic algorithm problems
Technical interview Live coding + CS one-liners + project
GD (when present) 60-second stance, not a TED talk
HR Why NTT Data, relocation, CTC

Think of papers as simulators for 90-minute sectional stamina. NTT Data reuses themes (percentages, puzzles, SQL, array manipulation) more than exact clones.

  • GFG virtual on-campus (widely cited 2020 note): AMCAT-style aptitude plus CS/web/SQL/cloud sections. “Out of 121 students, nearly 41 students were shortlisted for Interview Rounds.” GD skipped because virtual. Then ~25-minute technical and friendly HR; 10 of 20 HR candidates selected.
  • PrepInsta 2025 on-campus selectee: Four-stage funnel: multi-section aptitude (quant/verbal/logical/technical timed blocks), a 45-minute GD (e.g. work-life balance myths), ~30-minute technical on OOP, queues, Java finalize, then ~15-minute HR.
  • Composite 90-min OA: Aptitude 15-18 + technical 5-7 + coding 1-2. Sectional + overall cutoffs (~60-65%) claimed on many guides. No negative marking commonly reported.
  • 2026 expectation: Aptitude still kills. One complete code still matters. GD is possible, not guaranteed. C-output/pointer depth shows up on some older-style campus notes; do not ignore your resume language.

How to use one paper set in a single sitting

Section titled “How to use one paper set in a single sitting”
  1. Timed: 45 min aptitude → 20 min technical MCQs → 25 min one or two coding problems.
  2. Review: list three quant types you slow on; rewrite the coding solution clean.
  3. If your drive mentions GD: 10 minutes of a 60-second stance on a generic topic.
  4. Speak a 40-second project and a 20-second Why NTT Data.
  5. Log one CS one-liner you blanked (primary key, deadlock, polymorphism).
Theme you saw Drill next Why NTT Data asks it
Percentages / ratio Speed arithmetic Volume aptitude
Puzzles / series 45-second skip rule Logical section
SQL / OOP MCQs One-liners Technical section + interview
Array / string code Complete submit Coding gate
C output (if mailer) Pointers, loops Older campus papers

NTT Data placement process, round by round

Section titled “NTT Data placement process, round by round”

NTT Data hires freshers through campus cells, the careers portal, and referrals. After eligibility, the shape is classic Indian IT services: timed written, then technical, then HR. Some colleges add GD. Some older notes mention AMCAT.

Campus recruitment

Primary path. PPT, written, (optional GD), interviews. Strong presence across major India IT cities.

Online applications

ntt-data.com careers or job portals. Follow the assessment mail for platform and duration.

Referrals

Help the screen. You still need aptitude accuracy and a complete coding submit.

60% throughout, branch list, no live backlogs, gap rule. Gate.

Section Questions (reported) Time feel Focus
Aptitude 15-18 ~45 min Quant, logical, verbal
Technical 5-7 ~20 min Programming, DSA, DBMS, OOP
Coding 1-2 ~25 min Arrays, strings, basic algorithms

Languages: C, C++, Java, Python. Negative marking: commonly reported as none. Cutoffs: sectional + overall (often cited 60-65%). At least one coding problem must be fully correct on many playbooks.

Pass habit: 45-second skip rule on quant. Trace MCQ code on scrap paper. Do not leave coding for the last five minutes.

Minute Move
0-5 Skim sections; mark easy aptitude
5-40 Aptitude: skip monsters, bank easy marks
40-55 Technical MCQs
55-85 Coding problem 1 fully; start 2 only if 1 is passing
85-90 Flagged aptitude items

Deeper OA notes: NTT Data Online Assessment.

3. Group discussion (some campus drives, ~15-45 min)

Section titled “3. Group discussion (some campus drives, ~15-45 min)”

PrepInsta 2025: ~45-minute GD on topics like work-life balance myths. GFG 2020 virtual: GD skipped. If your mailer lists GD:

  • 60-second opening with a stance
  • One supporting point, one counter, one close
  • Do not interrupt; do not stay silent

Virtual or onsite. 1-2 coding problems plus CS fundamentals and project.

Problem types: array manipulation, string processing, basic DSA, SQL, OOP.

Evaluation: approach, working code, one-liners on DBMS/OOP/OS, project ownership.

Pass habit: “I wrote the login API and fixed a null on empty email” beats “we used React.”

Some nested interview notes describe heavier C output / pointers / pattern printing funnels. Treat those as drive-specific. If the PPT or mailer screams C, add pointer drills. If it says Java/Python OA, do not pivot to a 1990s C paper the night before.

Why NTT Data, relocation, shifts, strengths/weaknesses, joining date. Know ₹4-5.5 LPA Associate. Friendly is not optional-prep. Integrity and location answers still fail people.

# Round Duration What they check
1 OA ~90 min Sectional accuracy + one complete code
2 GD (optional) 15-45 min Clarity, not volume
3 Technical 30-45 min Code + CS + project
4 HR 15-30 min Fit, location, logistics
Phase Typical duration Notes
Apply / campus register 3-5 days Eligibility check
OA 1 day Aptitude + technical + coding
Results 2-3 days Sectional cutoffs
GD + interviews Days to 2 weeks Sometimes same day
Offer / paperwork 3-5 days Written offer wins
End to end ~2-3 weeks often Services calendars slip

Aptitude skip rules that save the 90-minute paper

Section titled “Aptitude skip rules that save the 90-minute paper”
  1. Percentages, ratio, average: do first.
  2. Time-work / TSD: one equation, not five tricks.
  3. One DI table: question first, then two cells.
  4. Seating / puzzle: 45 seconds then skip.
  5. Verbal: stem first.

Log every mock: which of the five ate the clock. That log is the prep plan.

An NTT Data campus can take a meaningful batch. That is not a participation trophy. Aptitude still deletes a chunk. Incomplete coding still deletes a chunk. Technical still deletes people who cannot explain their project. Your job is to be easy to say yes to: complete written, one passing program, short CS answers, documents ready, city answer ready.

The GFG virtual campus note used an AMCAT flavour (aptitude plus CS/web/SQL/cloud). Current mailers may say HackerRank, Mettl, or “NTT Data assessment platform.” Do not memorise one vendor. Memorise the three blocks: speed aptitude, CS MCQs, one complete program.

If the invite lists cloud/SQL MCQs, add 20 minutes of “what is a primary key / what is a JOIN / what is IaaS” the night before. That is not a cloud certification course. It is one-liners.

C-heavy campus notes (when the mailer actually says C)

Section titled “C-heavy campus notes (when the mailer actually says C)”

Some nested interview pages describe pen-paper C output, pattern printing, and even a mini-application round. Treat that as drive-specific archaeology. If your PPT or mailer never mentions C output, do not throw away Java/Python the night before. If it does mention C:

  • 20 pointer/array output questions
  • 5 pattern-printing programs written by hand
  • One file-handling or address-book style mini app if listed

Hand-writing C on paper is a different muscle from HackerRank. Practise on paper once if that is your invite.

10th, 12th, all semesters, ID, photo if asked, resume one page. Throughout 60% means the 12th PDF matters. Name, percentages, and dates must match the campus form and any job-portal profile. Background checks are not a rumour at a firm this size.

  • Charger, ID, resume print
  • 10th/12th PDFs on phone and drive
  • Language chosen; platform login tested
  • Bond/relocation sentence if the PPT mentioned either
  • One light aptitude set already reviewed
  • Sleep. Sectional cutoffs after a 3 a.m. mock are how easy verbal items die

PPTs talk digital transformation, healthcare, and financial-services clients. Day-one work is still a staffed project and a stack you are assigned. “I will only do GenAI” is a bad HR answer. “I will learn the stack on the project and I already write Java/Python” is the Associate answer. Keep that sentence ready.

If NTT Data and Infosys/TCS/Wipro all land the same week, compare city, joining date, and training stipend months. A 5 LPA letter you will actually join beats a rumour 6 LPA with a city you refused in HR. Keep the same email thread from PPT to offer. Classroom “selected” is not a letter. Wait for the PDF.

Week-by-week calendars live on the preparation guide. This section is the focus map.

Bucket Share This week’s proof
Aptitude 40% One timed 45-minute set with a skip log
Coding 30% One fully passing array/string problem + one cousin
CS fundamentals 20% 15 OOP/SQL/OS one-liners from a list
Interview 10% 40-second project + Why NTT Data

If OA is next week, raise aptitude + coding to 80%. If interviews are next week and OA is done, flip to live coding + one-liners + location answer.

  • You finish a 90-minute mock with sectional accuracy, not 90% in quant and 20% in verbal.
  • You submit one complete coding problem with sample tests, then attempt the second.
  • You can define polymorphism, primary key, and deadlock in one sentence each.
  • You can answer Why NTT Data without saying “global company.” Talk client-delivery work, India hubs, or a digital project you actually understand.
  • If GD is listed: you can speak for 60 seconds without reading a phone note.

Saturday 10:00: 90-minute OA.
Saturday 12:00: untimed rewrite + error log.
Saturday 16:00: 15-minute GD stance practice (even if optional).
Sunday 11:00: 30-minute technical oral (OOP + SQL + project).
Sunday 12:00: HR including city and CTC.

Two weekends of that beat twelve nights of random YouTube.

  • Staff-level system design before you can finish an array problem.
  • Certificate stacks before sectional mocks.
  • Switching from Java to C the night before because a 2018 blog said “NTT is C only.”
  • Memorising company revenue instead of one project metric.
  • Charger, ID, resume one page, 10th/12th PDFs
  • Language chosen; platform login tested
  • One light aptitude set already reviewed
  • Sleep. Sectional cutoffs after a 3 a.m. mock are how easy verbal items die

You do not need a debate trophy. You need a stance. Template: “I think X because of A. The other side says B. I still pick X because of C.” Sixty seconds. Record it once on a generic topic (work from office, AI in jobs, four-day week). If you freeze, restart the sentence. Silence in a 45-minute GD is how people get remembered for the wrong reason.

If aptitude is 18 questions and the cutoff is “clear each section,” 16/18 in quant and 4/7 in technical is still a fail. Practise all three blocks in one sitting. A 90-minute mock that you treat as three 30-minute papers is closer to the real filter than three days of only quant.

If a NTT Data invite is 3-8 weeks out, treat this hub as the map and the nested pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.

Typical fresher CTC chatter for NTT Data sits around ₹4-5.5 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.

Eligibility reminder (from student reports): NTT Data fresher eligibility is candidate-reported. Common campus baseline: B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT); final-year students and recent graduates (often within 2 years); typically 60% or 6.0+ CGPA across 10th, 12th, and graduation; no active backlogs; maximum ~2 years education gap; full-time degrees. Always verify the drive notice.

What you are training for: Many NTT Data fresher loops run: Online Assessment (~90 min, aptitude + technical + 1-2 coding) → Technical interview (~45 min) → HR (~30 min). Some campus drives add AMCAT-style papers and a GD. Total is often 2-3 weeks from application to offer. Count the mailer.

Short version of the prep split: Split time roughly: 40% aptitude (quant, logic, verbal), 30% coding (arrays/strings/basic algorithms in C/C++/Java/Python), 20% CS fundamentals (OOP, DBMS, OS), 10% interview stories. Clear sectional OA cutoffs first. Finish at least one coding problem completely.

Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the NTT Data previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.

Week 2 - the steep filter. Most NTT Data drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.

Week 3 - talk tracks. Technical interviews at NTT Data usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why NTT Data?” with one concrete product, lab, or business line - not a slogan.

Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. If you still have energy, redo only the questions you failed in week 2.

Slice Share of weekly hours What “done” looks like
Timed papers / OA ~40% You finish a NTT Data-style sit without guessing the clock
Coding / role technical ~30% You can explain a solution out loud in your chosen language
Fundamentals / domain ~20% You can teach one OS/DBMS/networks (or domain) topic to a friend
Stories + HR ~10% Two STAR stories and a specific Why-this-company answer

If you only have 10 days, keep the same ratios and cut volume, not the timed sits.

Use this hub for the NTT Data story (eligibility, rounds, salary). Use those pages for reps. If a card 404s on your campus mirror, the explore links at the top of this page are the same destinations.

  • Collecting 12 NTT Data PDFs and never sitting one under a timer.
  • Switching languages every weekend because a senior used a different one.
  • Memorising HR answers before they can finish the OA.
  • Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.

If you do one thing after reading this: schedule three timed NTT Data papers on three different days, then interview prep on the leftovers.

If you are starting from a service-company prep base

Section titled “If you are starting from a service-company prep base”

A TCS/Infosys aptitude deck still helps the quant/logic slice of many NTT Data papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in NTT Data-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.

Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on role, location, hiring year, and written components.

Band Typical CTC (candidate-reported) Notes
Associate (fresher) ₹4-5.5 LPA Primary band for this hub
Associate (1-2 years) ₹6-7 LPA Not campus default
Software Engineer (2-3 years) ₹8-10 LPA Experience track
QA / BA (indicative) Lower / adjacent bands Different JD; confirm posting

Confirm base vs variable and joining location on the written offer. Do not negotiate like a product company.

Health insurance, PF/gratuity, learning programs, shift/hybrid norms (ask), relocation to Bengaluru/Chennai/Hyderabad/Noida/Pune/Mumbai. Digital-transformation is the PPT story; day-one work is still project staffing.

Know ₹4-5.5 LPA Associate. Ask when full CTC starts if there is a training stipend period. Ask location. Do not demand 10 LPA on a campus Associate drive.

  • Online assessments remain the default first filter alongside campus drives.
  • Aptitude + one complete code still decide more outcomes than contest ratings.
  • GD is back in some 2025 campus notes; virtual 2020-style drives skipped it. Prepare a 60-second stance anyway.
  • AMCAT-style papers appear in older widely cited write-ups. Trust the current invite for platform.
  • Treat ₹4-5.5 LPA as a reported Associate band, not a promise for every role or college.
  • India hiring stays multi-city. Relocation questions are not flavour text.
What is the NTT Data placement process for freshers?

Typical path: Online Assessment (~90 min) → Technical (~45 min) → HR (~30 min). Some campus drives add GD or use AMCAT-style papers. Often 2-3 weeks. Confirm round names on your invite.

How many interview rounds does NTT Data usually have?

Common map is 3 after resume (OA, technical, HR). PrepInsta 2025 describes 4 including GD. Count the mailer.

Can I download NTT Data placement papers PDF for free?

Yes. Free NTT Data placement papers PDF and 2024-2026 style practice are on placementpapers.app. Start with the 2026 PDF or the archive.

What does the NTT Data Online Assessment look like?

Often ~90 minutes: aptitude 15-18, technical 5-7, coding 1-2. Sectional and overall cutoffs commonly cited. No negative marking on many reports. Languages: C, C++, Java, Python. Verify yours.

Does NTT Data still conduct a group discussion?

Sometimes. 2025 campus notes include a ~45-minute GD. 2020 virtual GFG skipped GD. Practise a 60-second stance if the mailer lists it.

What eligibility / CGPA do fresher Associate drives usually expect?

Commonly 60% or 6.0+ throughout 10th, 12th, graduation; listed degrees; no active backlogs; gap ≤ ~2 years; full-time only. Your drive notice overrides this page.

What is NTT Data fresher salary in India?

Candidate-reported Associate CTC often lands around ₹4-5.5 LPA (as of August 2026). The written offer letter is the only number that matters.

Can I apply with backlogs or a gap year?

Active backlogs: usually no. Cleared backlogs: usually yes. Gaps up to about 2 years appear in tables. Confirm the posting.

How should I prepare for NTT Data?

Split time roughly 40% aptitude, 30% coding, 20% CS one-liners, 10% interview. Finish one coding problem completely. Details: preparation guide.

Which programming languages are allowed?

C, C++, Java, and Python are the usual set. Confirm on the invite. Do not switch the week of the drive.

Is NTT Data a C-only company?

No. Some older campus notes emphasise C output and pointers. Many current OAs allow Java/Python. Follow your mailer and resume language.

NTT Data vs Infosys vs TCS for freshers?

All volume services with aptitude gates and similar fresher CTC bands. NTT Data is Japan-headquartered with a large India workforce. Compare city, training, and the letter.

Any pro tip that actually changes outcomes?

Time-box aptitude. Finish one code completely. Be ready for GD if listed. Know ₹4-5.5 LPA before HR. Print 10th and 12th.

Where can I read real interview experiences?

Start with NTT Data interview experience on placementpapers.app, then GFG/PrepInsta notes for your year. Use them as maps, not scripts.

What is the Associate role at NTT Data?

Associate is the usual fresher title: project staffing, development/testing/support depending on the account, growth toward Software Engineer. CTC commonly reported around ₹4-5.5 LPA. Ask HR when full CTC starts if there is a training period.

Where does NTT Data hire freshers in India?

Bengaluru, Chennai, Hyderabad, Noida, Pune, and Mumbai appear often in student notes. Relocation and shifts are common HR topics. Answer the city you will actually join.

AMCAT paper covering aptitude plus CS/web/SQL/cloud. “Out of 121 students, nearly 41 students were shortlisted for Interview Rounds.” GD skipped due to virtual format. Then ~25-minute technical and friendly HR; 10 of 20 HR candidates selected. Source: GeeksforGeeks. Takeaway: written volume is the first filter; HR is still a filter.

Four-stage funnel: multi-section aptitude (quant/verbal/logical/technical timed blocks), 45-minute GD (work-life balance myths), ~30-minute technical on self-intro, project rating, OOP, linear vs non-linear structures, queues, Java finalize, then ~15-minute HR on dream job and hobbies. FAQ quote from that explainer: “There are 4 rounds in the NTT Data interview process: Written-test, Group discussion, technical interview, and HR interview.” Source: PrepInsta. Takeaway: GD can return; Java one-liners still matter.

Helped: skip rules on aptitude; one fully passing code; short OOP/SQL answers; a project with a bug you actually fixed; calm location answer.

Hurt: chasing one seating puzzle; two half-coded programs; “we used many technologies”; refusing relocation after the PPT named cities; treating HR as a formality.

  1. Re-solve every miss from your last two mocks cold.
  2. Speak project + Why NTT Data without notes.
  3. Warm one array/string medium in your interview language.
  4. If GD is listed, record a 60-second stance twice.
  5. Sleep and document pack (10th/12th/semesters).

Technical oral composite: Candidates who only practised HackerRank and then blanked on “what is polymorphism” still fail 30-minute interviews. Write 15 one-liners on a card: OOP four, SQL four, OS three, DSA four. Say them aloud once a day for a week. That is the entire CS prep if your coding is already at “complete one array problem.”

HR composite: “Global company, 50+ countries” is a slogan, not an answer. Pick one: a city you will join, a domain you saw on the PPT (banking, healthcare, manufacturing), or a training story you actually want. Then stop talking.

Pool campus: denser aptitude, same coding bar. Your college rank in the pool does not replace a complete submit.

If you miss NTT Data, the same aptitude muscle transfers to Infosys, TCS, Wipro, and Cognizant. Reuse the skip log. Do not start a new dump site.

Print 10th and 12th tonight. The drive will not wait for a missing marksheet after you already cleared OA. That is eligibility in the only way that still matters once you can code and speak. Keep a backup services process live until NTT Data’s PDF and the cell list agree.

More narratives: NTT Data interview experience.

Infosys · TCS · Wipro · Accenture · Capgemini · Cognizant