Dxc Technology Software Engineer interview typically runs 3 rounds: online assessment, technical interview, HR interview. The process usually takes about half a day to a few weeks and is often fundamentals-focused and fairly straightforward.
$69K
Avg. Base Comp
$97K
Avg. Total Comp
3-4
Typical Rounds
2-4 weeks
Process Length
We've seen DXC Technology evaluate software engineers as much on clarity and composure as on raw technical depth. Across candidate reports, the recurring pattern is a fundamentals-first filter: Java OOP basics, Python and SQL essentials, code tracing, and standard CS concepts like linked lists, trees, graphs, and caching show up far more often than tricky algorithm puzzles. Even when candidates described the process as relaxed, the questions still tested whether they could explain core ideas cleanly, such as abstract class vs. interface, low-level vs. high-level languages, or the difference between a view and a function in SQL.
A second theme we've seen is that DXC seems to care about how candidates connect their experience to practical work. Multiple candidates mentioned being asked about their current role, past projects, or take-home work, with follow-ups around caching and Java concepts tied to that assignment. That suggests the interviewers are looking for people who can talk through implementation choices and tradeoffs, not just recite definitions. The strongest experiences also had a conversational tone, and candidates who came across as clear and calm seemed to do well.
The non-obvious risk here is inconsistency. Some candidates described a polished, friendly process, while others reported rushed or disorganized conversations and a more skeptical tone from managers. That means our candidates should be ready for a wide range of interviewer styles, but the signal remains the same: clean fundamentals plus practical explanation. If you can move comfortably between basic theory and the reasoning behind your own work, you’re aligned with what DXC appears to reward.
Synthetized from 5 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Dxc Technology process.
The hardest part of my interview was actually the technical round with the architect. It was done online and felt pretty rushed, with the interviewer seeming a bit uninterested, which made the whole thing less comfortable than I expected. Before that, the process had been fairly straightforward: I had a total of three rounds for a Java developer role, and overall it didn’t feel especially deep on algorithms. The questions stayed pretty close to the basics, with DSA fundamentals and Java-related topics coming up early, so I wouldn’t call it a heavy coding interview. In my case, they also asked about my current role, which felt more like an HR screening question than a technical one. The most specific technical discussion came around a take-home assignment, where they asked about caching and then followed up on Java concepts tied to that work. One question that stood out was the difference between hash and encryption methods, which was more conceptual than code-heavy. The process itself felt a little last-minute and not very polished on the coordination side, but the interviewers were generally okay and the role seemed decent for someone looking for a new opportunity. I didn’t get an offer, and the main takeaway for me was that it’s worth being ready for Java basics, simple DSA, and practical system concepts like caching rather than expecting a very hard algorithm round.
Prep tip from this candidate
Be ready to explain your current role clearly, then review Java basics, simple DSA, and practical concepts around caching and the difference between hashing and encryption. If you have a take-home assignment, expect follow-up questions that dig into the choices you made there.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Dxc Technology
Describing a data project and its challenges
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Prime to N | |
| Employee Salaries | |
| Top 3 Users | |
| Size of Joins | |
| Rolling Bank Transactions | |
| Customer Orders | |
| String Shift | |
| Comments Histogram | |
| Closest SAT Scores | |
| Random SQL Sample | |
| Largest Salary by Department | |
| Find the Missing Number | |
| Upsell Transactions | |
| Monthly Customer Report | |
| Manager Team Sizes | |
| First Touch Attribution | |
| Raining in Seattle | |
| P-value to a Layman | |
| Cumulative Distribution | |
| Job Recommendation | |
| Minimum Change | |
| Address Schema | |
| Lowest Paid |
Synthesized from candidate reports. Individual experiences may vary.
Candidates were often contacted through LinkedIn or after applying to a posted opening. The first conversation was usually a light HR screen focused on self-introduction, background, motivation for the role, and basic expectations such as salary or fit.
Some candidates completed a basic online assessment before the live interviews. The test was centered on fundamentals, including Python basics and SQL questions, and was designed to check core knowledge rather than advanced problem-solving.
The technical round was generally conversational and focused on fundamentals. Questions covered Java OOP concepts, DSA basics, SQL, code tracing, and practical topics like caching, linked lists, trees versus graphs, and the difference between views and functions.
In some loops, candidates met with a manager or architect, sometimes online. This stage could include discussion of current work, project experience, Java concepts, and follow-up questions tied to a take-home assignment or practical system topics.
For some candidates, the process was completed in person over several hours. It typically started with a short company introduction, then a written test, followed by the technical interview and an HR conversation at the end.
The last step was a standard HR discussion covering fit, general background, and role alignment. In the experiences shared, this conversation was brief and served as the final check before the offer decision.