Prepare for the DXC Technology HR interview with commonly reported questions, answer frameworks, and tips. This is the round that closes the DXC fresher process after the technical interviews.
A structured summary rather than a resume read-out
What kind of work you actually enjoy
A link between your background and the role
Sample direction:
“I’m a final-year Computer Science student. Most of my project work has been backend - my main academic project was a Java web service with a MySQL database, and the part I enjoyed most was tracking down why one endpoint slowed down under load. I applied to DXC because a services role means seeing many client environments early rather than one codebase, and I’d like that breadth at the start of my career.”
Tips:
Present, past, future - keep it to 60-90 seconds
Name one project and one thing you learned the hard way
End on why this DXC role, today
Walk me through your strongest project
What they’re looking for:
Ownership: what you personally built
The reasoning behind your technology choices
What broke, and how you found it
Sample direction:
“I owned the API layer of our team project. The slow endpoint turned out to be an N+1 query - each result row triggered another database call. I found it by logging query counts per request, then fixed it with a join. If I rebuilt it I’d add query-count assertions to the tests so it couldn’t regress.”
Tips:
Say what you would rebuild differently - panels ask this often
If a teammate owned a part, say so
Keep the explanation plain; the panel may not know your stack
Sample direction:
“DXC is a global IT services company - it came out of the merger of CSC and HPE’s enterprise services business - and it runs and modernises the systems large enterprises depend on: cloud and infrastructure, applications, security, and a big insurance software business. That appeals to me because a fresher here sees production systems and real client constraints early, which is harder to get in a single-product team.”
Facts worth knowing before you answer:
DXC Technology was formed in 2017 from the merger of CSC and the Enterprise Services business of Hewlett Packard Enterprise
It is headquartered in the United States and operates globally, with major India delivery centres including Bengaluru, Chennai, Hyderabad, Noida, Mumbai and Pune
Its service lines span cloud and infrastructure, applications and modernisation, security, analytics and engineering, and insurance software and BPS
Fresher roles are commonly titled Associate Professional or Associate Software Engineer
Tips:
Two sentences on what DXC does is enough - but have them ready
Candidates report being asked this in the technical round too
Show you understand services work involves clients, not just code
Are you willing to relocate and work rotational or night shifts?
What they’re looking for:
An honest, calm answer
Awareness that support and infrastructure roles often involve shift rosters
Sample direction:
“Yes, I’m open to relocating to any DXC India location. I understand some delivery roles run rotational shifts, including nights, and I’m comfortable with that. I’d just like to know the roster pattern for this role so I can plan.”
Tips:
This is a genuine evaluation criterion in IT services, not small talk
If you have a real constraint, say so early and plainly rather than discovering it after the offer
Asking about the roster is reasonable and shows you took the question seriously
When can you join? What happens after this round?
What they’re looking for:
A concrete availability date
How to handle it:
Give your actual availability - exam schedule, result date, or notice period for experienced hires. It is fine to ask about the next steps: candidates commonly report receiving a letter of intent first, with the formal offer letter following later, and gaps of several weeks between stages. Ask for the expected timeline in writing where you can.
Sample direction:
“Two of us disagreed about whether to rewrite a module or patch it before the demo. Instead of debating, we timeboxed half a day to estimate both, and the rewrite clearly didn’t fit. We patched it for the demo and scheduled the rewrite after. The disagreement stopped once we had numbers instead of opinions.”
Tips:
This exact question appears in DXC reports, sometimes in the technical round
One concrete resolution beats a philosophy of teamwork
Always end with the result
How would you handle being staffed on a technology you’ve never used?
What they’re looking for:
Comfort with the reality of services work
A concrete learning method
Sample direction:
“I’d expect that, honestly - clients use what they use. I’d start from the existing codebase and documentation, ask for one small well-scoped task to get my hands dirty, and keep a running list of questions for whoever knows the system. That’s roughly how I picked up SQL tuning for my project: read, try, break, ask.”
Tips:
Never answer this with reluctance
Name an actual thing you taught yourself as evidence
Tell me about a missed deadline or something that failed
What they’re looking for:
A real failure and what changed afterwards
Sample direction:
“I under-estimated integration time on a group project and we demoed a half-working build. Since then I schedule integration as its own task with a buffer, and on the next project we integrated a week early.”
Sample direction:
“I’d like to be the person the team trusts on one area end to end - probably cloud or backend, depending on where I get depth - and to have mentored at least one newer engineer. I care more about owning something real than about a title change.”
Pro tip: DXC HR panels are reported as friendly and receptive to honest answers. The two things that reliably cost candidates the round are going blank on what DXC does, and giving a vague answer on shifts and relocation. Fix both before you walk in.