
DXC Technology Business Analyst interviews, as candidates describe them, start with an HR call and continue with conversational manager, project manager or panel rounds on your current role, projects and fit.
$79K
Avg. Base Comp
$93K
Avg. Total Comp
2-4 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the DXC Technology Business Analyst process as conversational and centered on experience rather than technical testing. One candidate said there was no heavy case or coding exercise, and another described the technical questions as light. Reports range from two stages to four rounds.
The HR phone call opens most accounts. Topics reported include expected salary, preferred shift, tell me about yourself, why DXC, and current responsibilities. One candidate was also checked on spoken English because the role involves international clients.
After that, the path differs. One candidate had a functional discussion about recent projects, then a culture-fit panel with some personal and academic questions and a domain question on indemnity in case of an accident. Another had a roughly 40-minute Microsoft Teams conversation with hiring managers and team leads, who explained the day-to-day work and a heavy workload. A third spoke with a project manager and more HR staff about project planning, competing tasks and teamwork. A fourth was told a group interview with managers would follow a positive HR round, though passing HR did not guarantee it.
Prepare to explain what you owned versus supported on recent projects, and know your salary range before the first call. Of four relevant reports, three ended in offers and one in no offer.
Synthesized from 5 candidate 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.
What stood out to me most was how much of the process was about fit and practical experience rather than any heavy case or coding exercise. I went through four rounds in total. It began with an HR phone call where they covered the basics like my expected salary and preferred shift, which felt pretty straightforward. After that came a technical interview that was really more of a functional discussion about my background and how I’d handled work in my current role. They asked about recent projects and dug into the kinds of responsibilities I’d had as a business analyst, so I made sure to speak clearly about what I actually owned versus what I supported.
The next step was a panel interview focused on culture fit. That round was less about technical depth and more about attitude, interests, and how I’d present myself in the team. They also asked some personal and academic background questions, and there was a deeper dive into a few job-related topics. One question that surprised me was around indemnity in case of an accident, which felt very specific to the role and the company’s line of business. Overall, the interviewers were conversational and seemed to want to understand whether I could handle the work and fit the environment. I ended up accepting the offer, and my main takeaway is to be ready to talk through your current job in detail, recent projects, and any domain-specific concepts that might come up, not just generic BA skills.
Prep tip from this candidate
Be ready to explain your recent projects and current responsibilities in detail, since the technical round focused on functional experience more than formal testing. Also review domain-specific concepts tied to the business, like indemnity in case of an accident, because they may ask practical questions like that in the deep dive.
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 | |
| Empty Neighborhoods | |
| Customer Orders | |
| Top Three Salaries | |
| Prime to N | |
| Cumulative Distribution | |
| Top 3 Users | |
| Find the Missing Number | |
| Button AB Test | |
| Employee Salaries (ETL Error) | |
| Size of Joins | |
| Rolling Bank Transactions | |
| Employee Salaries | |
| 500 Cards | |
| Paired Products | |
| Bagging vs Boosting | |
| Comments Histogram | |
| Closest SAT Scores | |
| Retailer Data Warehouse | |
| Minimum Change | |
| Subscription Overlap | |
| Month Over Month | |
| Jars and Coins | |
| Monthly Customer Report | |
| Lowest Paid | |
| Upsell Transactions | |
| P-value to a Layman | |
| Experiment Validity |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe an opening call with HR or recruitment that felt friendly and straightforward. Reported topics include expected salary, preferred shift, tell me about yourself, why DXC, and current role and responsibilities. One candidate was also assessed on spoken English for client-facing work.
One candidate describes a technical interview that was really a functional conversation about recent projects and business analyst responsibilities. Another said the technical questions were light. Not every account includes this stage, so be ready to explain what you owned versus what you supported.
Later conversations varied. One was a Teams interview of about 40 minutes with hiring managers and team leads about daily work and workload. Another was a culture-fit panel with a domain question on indemnity in case of an accident. A third covered project planning, multiple tasks and teamwork with a project manager and HR.
Among the four relevant reports, three candidates received offers and one did not. One offer came in above the salary the candidate had mentioned. The no-offer candidate noted that a positive HR conversation did not guarantee progression to the group interview with managers.