DXC interview process & guide 2026
Everything we know about interviewing at DXC: the process stage by stage, what each round tests, compensation by level, and reports from candidates who interviewed.
- 1Initial screening
- 2Technical rounds
- 3Technical assessment
- 4HR discussion and/or additional HR touchpoints
- 5Manager or leadership interviews and final evaluation
Interviewing at DXC
DXC’s interviews mix recruiter or HR conversations with technical evaluation, then further discussions with managers or leadership. Across reports, the tone is often described as friendly or conversational, but there are also reports where logistics or interviewer engagement felt poor.
What you are tested on shows up strongly in the extracted topic data. SQL is the most prominent programming topic (percentile 94), with Python (83) and Java (80) also heavily represented, alongside problem solving (79), communication skills (76), and stakeholder communication (62). QA engineering and UX/UI design are also marked at percentile 100 in the topic set, and Four Pillars of OOP and Java core programming appear at percentile 100 in the technical skill topics set.
The reported process steps commonly include an initial screening, then technical rounds, and technical assessment that may involve a proctored SQL or coding task, sometimes with additional aptitude or foundation checks. From candidate reports, some loops include a take-home or project-based mini project and then a review and discussion that covers design and tradeoffs. There is no offer made in the aggregated candidate data provided, and positive sentiment is 66.8%, so expect mixed experiences and do not rely on offers data here.
The interview topic data is heavily weighted toward SQL, then Python and Java, and the process steps include a technical assessment that may be a proctored SQL or coding task. Even when the format feels conversational, you should still prepare to discuss fundamentals and connect them to your project decisions, including design choices and tradeoffs.
How hard is the DXC interview?
Aggregated from 500 interview experiencesAbout 1 in 2 candidates with a known outcome convert.
The interview process, end to end
5 rounds · based on 500 candidate reports- 1Initial screening
You typically meet a recruiter or Talent Acquisition partner to discuss qualifications and fit. Some reports include an agency or external headhunter step, and candidates describe the screening as straightforward and conversational.
- 2Technical rounds
You may complete one or more technical interviews with managers or senior team members. Reports describe scenario-style questions and guided discussions, and the extracted topics indicate focus on problem solving and core programming and data fundamentals.
- 3Technical assessment
Some loops include a proctored SQL or coding task to validate technical capability, and other reports describe take-home mini projects followed by a review and discussion. In the review, you can be pushed on design reasoning, tradeoffs, and improvement opportunities.
- 4HR discussion and/or additional HR touchpoints
You may meet HR to discuss alignment, compensation expectations, and fit with the company. Reports describe this as fit and dialogue focused rather than only strict Q&A.
- 5Manager or leadership interviews and final evaluation
You may have interviews with department managers or leadership, and there can be final discussions to finalize assessment and discuss logistics. In some reports, the overall experience ended without follow-up, so be ready for variable communication after interviews.
What DXC actually tests for
How prominent each skill is across reported loopsFind the guide for your role
This is your next step: open the guide for the role you are interviewing for. Each one carries the questions DXC interviewers actually ask that position, the loop structure, and pay by level.
Real interview experiences
What candidates said about the loop, difficulty, and outcomes, straight from recent reports for these roles.
What DXC pays, by level
Estimated total compensation: base salary plus stock and annual cash bonus.
What separates offers from rejections
Patterns from candidates who got offers, and the mistakes that most often sink a loop.
Do this
- Prepare to use SQL in a practical way during a proctored SQL or coding assessment, and be ready to explain your approach rather than only provide results.
- Be ready to discuss Python or Java fundamentals plus OOP concepts, and connect them directly to what you built in past projects, including why you structured things that way.
- Practice clear, stakeholder-style communication: summarize tradeoffs, explain what you would improve, and state assumptions when you are unsure.
- If you get a take-home or project mini assignment, expect a follow-up code review or discussion focused on design reasoning, improvements, and tradeoffs.
Avoid this
- Do not treat the process as purely behavioral or purely conversational. The extracted topics show heavy coverage of SQL, Python, Java, and problem solving.
- Do not underprepare for OOP and core programming concepts, since Four Pillars of OOP and Java core programming are both listed at the top percentile in the topic set.
- Avoid being vague about your project work. Several reports describe expectations to connect concepts to what you actually implemented and your responsibilities.
- Do not ignore practical execution details during logistics. Reports mention no-shows, camera issues, and abruptly ended or frustrating interactions, so confirm scheduling and be ready to keep the session moving professionally.
DXC interview FAQ
Answered from real candidate and workplace dataHow hard are the interviews, and how does that show up in the data?
The aggregated difficulty split is 28.6% easy, 61.0% medium, 10.2% hard, and 0.2% very hard. Candidate reports generally describe approachable or friendly sessions, but there are also reports of mismatched expectations and more demanding technical depth in some cases.
Do candidates get offers, and what is the offer rate here?
In the aggregated candidate data provided, the offer rate is 0.0%. Candidate reports include non-offer outcomes, and positive sentiment is 66.8%, so you should treat the process experience as the main signal, not the offer rate.
What technical topics should I prioritize?
Prioritize SQL first (percentile 94), then Python (83) and Java (80). Problem solving (79) and communication skills (76) also appear strongly. For deeper technical preparation, Four Pillars of OOP and Java core programming are at percentile 100 in the topic set.
Is there a take-home, proctored task, or assessment?
The process steps include a technical assessment stage that may include a proctored SQL or coding task, and some candidates report take-home mini projects reviewed by an interviewer. The review discussion can include design choices, improvements, and tradeoffs.
How long does the process take?
One candidate report describes about two weeks for the process. Another report describes a structured half-day evaluation on the day a technical interview occurred after earlier steps. The aggregated steps do not provide a single universal duration.
What if I do not get an offer, can I re-apply?
The provided data includes no re-application policy or guidance. Since the aggregated offer rate is 0.0%, focus on using each loop as preparation and improve the specific weaknesses you see in feedback, if any is provided.
What people say about DXC
Verbatim snippets from employee and candidate reviews“The company offers remote work flexibility and fosters a friendly work culture.”
“There is a need for improvement in the appraisal percentage.”
“Promotions and salary hikes are infrequent, leading to slow overall growth.”
“Career advancement opportunities depend on your manager's support for role changes.”
“DXC is a good starting point for freshers, but career growth can be slow and heavily influenced by management.”
“The work-from-home setup provides a good work-life balance, along with decent job security and a supportive company culture.”
Ready for your DXC interview?
Practice the exact questions from this guide with AI feedback, and walk into your loop knowing what to expect.





