DXC Technology Interview Experiences

How DXC Technology fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.

DXC Technology is a large US-headquartered IT services company - infrastructure and cloud, applications, security, analytics and engineering, plus a substantial insurance software business - with major India delivery centres in Bengaluru, Chennai, Hyderabad, Noida, Mumbai and Pune. Fresher roles are usually titled Associate Professional or Associate Software Engineer.

How to use this page

Read the round table first, then the experiences. The online assessment is the real filter, so practise it under time. Keep one clear story each for ownership, teamwork, and a project you would rebuild differently.

Round-wise process

Round	Duration	What they test
Online assessment	100-150 min	English, logical, quantitative, computer fundamentals, pseudo-code, essay (some versions), 1-2 easy coding questions
Technical interview	30-50 min	Resume and projects, chosen language, OOPs, DBMS, OS, basic DSA
Second technical (some drives)	~30 min	OS, DBMS theory, team/project conflict, company knowledge
HR	20-30 min	Motivation, relocation, shifts, situational questions

Reports vary

The assessment platform, section mix, and number of technical rounds differ noticeably between DXC drives - candidate accounts mention both AMCAT/Aspiring Minds (with a WriteX essay section) and SHL. Eligibility bars reported range from 60% to 65% in 10th, 12th and graduation with no active backlogs. Your college placement email for that cycle is the authority.

Real interview experiences

Experience 1: associate professional, on-campus (2024-2025)

Profile: B.Tech CSE, ~7.6 CGPA, no internship, steady aptitude practice

Online assessment

• A webcam-monitored test of roughly 100 minutes with several short, separately timed sections: English verbal ability, logical reasoning, quantitative aptitude, computer fundamentals, and a written essay.
• No negative marking, but once a question was submitted it could not be revisited - so guessing beat leaving blanks.
• The essay section surprised several candidates. Plan two minutes, write four short paragraphs, keep the grammar clean.

Technical interview (~35 min)

• Everything on my resume was fair game: the academic project, what I personally built, and why I chose the stack.
• Which language are you most comfortable with, and why that one?
• OOPs basics - inheritance, polymorphism, and an example from my own code.
• A simple DSA question described verbally rather than coded on a shared screen.

HR (~20 min)

• Why DXC, relocation flexibility, and comfort with rotational shifts.
• A situational question about handling a deadline slip.

Result: Selected, letter of intent first, formal offer later
What helped: Aptitude practice. The interview was fundamentals-level, but the assessment cut a large fraction of the batch.

Experience 2: on-campus with two technical rounds (2024)

Profile: B.Tech CSE, ~8.0 CGPA, one internship, average coding practice

What differed

• The assessment ran about two and a half hours on a different platform: arithmetic aptitude, cognitive MCQs, an English communication section, pseudo-code problems, and two coding questions that were genuinely easy.
• Two technical interviews rather than one. The first (about 45-50 minutes) covered my language of choice, OOPs, some cloud-computing awareness, project decisions, and career goals. The second (about 30 minutes) was OS and DBMS theory, what I knew about DXC, and a question about a conflict in a group project.
• The process was slow - roughly a month between rounds. Several classmates assumed they had been rejected and stopped preparing.

Mistakes that hurt other candidates

• Not being able to explain a resume project beyond the tech-stack list
• No answer at all to “what does DXC do?”
• Treating the gap between rounds as a rejection

Result: Selected after the second technical round and HR
Takeaway: DXC panels reward honesty and clear fundamentals over rehearsed depth. Interviewers were reported as friendly and fine with “I don’t know, but here’s how I’d approach it.”

Experience 3: off-campus associate software engineer (2025)

Profile: B.Tech IT, ~7.0 CGPA, applied through the careers portal

What differed from the campus drive

• The assessment leaned harder on computer fundamentals and pseudo-code than on coding; one short debugging block asked only for bug fixes rather than fresh solutions.
• Interview 1: DBMS and SQL - joins, primary vs foreign keys - plus OS basics like process vs thread.
• Interview 2 / managerial: how I would handle being staffed on an unfamiliar technology, and whether I was comfortable with client-facing support work and shift rosters.

Result: Selected after a second HR call
Takeaway: For an IT services role, willingness on shifts and location is a real evaluation criterion, not small talk. Answer it honestly and early.

Questions that come up often

Coding / technical

1. Explain your project end to end - your role, the stack, the hardest problem
2. Which programming language do you prefer and why?
3. OOPs: inheritance, polymorphism, abstraction vs encapsulation, with examples
4. DBMS/SQL: joins, keys, normalisation basics
5. OS: process vs thread, deadlock, scheduling basics
6. Basic DSA: arrays, strings, searching and sorting, simple recursion
7. Pseudo-code reading - trace the output carefully
8. Cloud and infrastructure awareness at a general level, for some panels

HR / behavioural

1. Why DXC Technology? What do you know about the company?
2. Relocation to a DXC India location, and comfort with rotational or night shifts
3. A conflict or disagreement in a group project
4. How you would handle being assigned an unfamiliar technology
5. Long-term plans and joining date

Practical tips for DXC Technology

• Treat the online assessment as the main hurdle. Timed sectional practice beats last-minute topic hopping.
• If your drive includes an essay section, practise writing 200-250 clean words in 20 minutes.
• Know every line of your resume. The technical round almost always opens there.
• Prepare a two-sentence answer to “what does DXC do?” - a surprising number of candidates have none.
• Be honest about shifts and location. IT services roles genuinely need that flexibility.
• If a round is followed by weeks of silence, keep preparing. Long gaps between DXC rounds are commonly reported.

HR interview

After the technical rounds, DXC usually closes with a short HR / hiring-manager conversation: motivation, location, shifts, joining date, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

HR interview questions→

Common DXC Technology HR questions, sample answer frames, and STAR tips.

Practice with DXC Technology placement papers

DXC Technology placement papers→

Placement-paper bank and online assessment practice for DXC Technology.

DXC Technology preparation guide→

Study plan and round-by-round strategy for the DXC Technology process.

WhatsAppFacebookTelegramEmail

Similar companies

Infosys · TCS · Wipro · Accenture · Capgemini · HCL

Pro tip: DXC’s interview bar for freshers is fundamentals, not brilliance. The candidates who fail usually fail the timed assessment or freeze on their own resume - so drill aptitude under a clock and rehearse your project story out loud.