DXC Technology's Software Engineer interviews in these reports lean on core programming fundamentals rather than advanced algorithms.
The most detailed entry-level account describes a half-day in-person visit: a short company introduction, a written test, a technical interview and a closing HR conversation. The technical questions were conceptual. They covered the difference between low-level and high-level languages, abstract classes versus interfaces in Java, and predicting the output of a code block, plus one simple problem to solve. Another candidate, on a technical lead track, was asked about:
- procedural versus object-oriented languages;
- encapsulation versus polymorphism;
- linear versus non-linear data structures;
- C# specifics such as IEnumerable versus ICollection.
If you're preparing, review OOP vocabulary and the basics of whatever languages you list on your resume, and practice tracing code by hand.
More experienced candidates should also expect a project-driven conversation. One senior candidate described four stages over about four weeks: a recruiter call, a panel with hiring managers, a technical panel with tech leads, and an offer discussion. Interviewers asked for detailed walkthroughs of past systems, including their architecture and flow, and about experience with tools like Spring Boot and Kubernetes. They also asked behavioral questions on conflict resolution and managing stakeholders. That candidate valued that the focus was on practical experience rather than memorized algorithms.
Some screens are lighter still: one candidate's first round was essentially a friendly self-introduction. Interviewer tone varies by report, from relaxed and conversational to dismissive, so stay composed and explain your reasoning clearly either way. Offer negotiation may move slowly; one candidate waited nearly two weeks for a response to a counteroffer.
Synthesized from 31 candidate reports by our editorial team.
