
Dxc Technology Product Manager interview typically runs 1 round: screening. It usually takes one day and is straightforward and well organized.
$143K
Avg. Base Comp
$160K
Avg. Total Comp
3
Typical Rounds
1 day
Process Length
Our candidates report that DXC Technology’s Product Manager interviews are less about dazzling with frameworks and more about showing you can explain your own work cleanly and credibly. In the experience we saw, the conversation stayed close to the role, with the interviewer listening carefully and keeping things straightforward rather than adversarial. That’s a useful signal: this process seems to reward candidates who can connect past responsibilities to the job without overcomplicating the story.
A recurring theme is that the company wants a clear, positive rationale for the move. One candidate specifically called out being asked why they were looking for a change, and that question appears to matter as much as the resume itself. We’ve also seen the interview lean toward fit, motivation, and practical experience rather than heavy technical depth or case-style pressure. The question about hurdles in data projects suggests they still care about how you handle real-world execution issues, but in a grounded, conversational way.
What makes or breaks candidates here is usually not polish alone, but whether they can stay direct and relevant under a structured conversation. The strongest signal is a candidate who can speak plainly about strengths, weaknesses, and past project challenges without sounding rehearsed. In other words, DXC seems to value clarity, maturity, and role alignment over theatrics.
Synthetized from 1 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 interview was pretty straightforward and, honestly, well organized. I went through the whole process in one day, and it felt planned out rather than dragged across multiple weeks. Most of the conversation was direct and stayed close to the role, which I appreciated. The interviewer was a good listener and didn’t make it feel like they were trying to trip me up. The first part was mostly about my background and past experience, so I spent a lot of time walking through what I had done in previous roles and how that connected to the position. One of the main questions was why I was looking for a change, so I made sure to answer that clearly and keep it positive.
There wasn’t anything especially technical or case-heavy in my process, at least not in the way I expected. It felt more like a structured screening around fit, experience, and motivation. Because everything happened in a single day, the pace was quick, but not stressful. The questions were direct and related to the subject, so preparation really came down to being able to explain your own experience well and give a solid reason for wanting the move. In the end, I received the offer letter, and overall it was a smooth experience.
Prep tip from this candidate
Be ready to clearly explain your past experience and your reason for changing jobs, since those were the main questions asked. Since the process was completed in one day, practice giving concise, direct answers without rambling.
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 | |
| Top Three Salaries | |
| Manager Team Sizes | |
| Employee Salaries | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Upsell Transactions | |
| Experiment Validity | |
| Monthly Customer Report | |
| First Touch Attribution | |
| Cumulative Distribution | |
| Top 3 Users | |
| Button AB Test | |
| Lowest Paid | |
| Download Facts | |
| Size of Joins | |
| Google Maps Improvement | |
| Average Quantity | |
| Last Transaction | |
| Instagram TV Success | |
| Group Success | |
| Cyclic Detection | |
| Random SQL Sample | |
| Largest Salary by Department |
Synthesized from candidate reports. Individual experiences may vary.
The process was completed in one day and focused on fit, experience, and motivation rather than heavy technical or case-style questions. The interviewer spent most of the time reviewing the candidate’s background, past roles, and how that experience connected to the Product Manager position.
A key part of the conversation was explaining why the candidate was looking for a change and why the move made sense. The discussion stayed direct and role-focused, with the interviewer listening closely and asking straightforward questions about the candidate’s experience and interest in the role.
The process concluded quickly after the screening conversation, and the candidate received an offer letter. The overall experience was described as smooth, organized, and not dragged out over multiple weeks.