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.
Synthesized from 1 candidate report 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 process at DXC Technology for the Product Manager role was straightforward and focused on management fundamentals rather than deep technical implementation. I had two rounds of interviews conducted over the phone.
The first round was with someone from the management team, and they focused on behavioral and situational questions to understand how I'd handle real PM challenges. They asked me how I'd managed a difficult stakeholder—testing whether I could navigate complex interpersonal dynamics while keeping the project on track. The questions felt designed to assess my ability to lead cross-functional teams and communicate effectively under pressure. They also probed my IT knowledge and infosec awareness, which surprised me a bit, so I'd recommend brushing up on cloud fundamentals and basic security concepts if you're interviewing here.
The second round included members of the actual team I'd be working with, which was reassuring. The questions shifted toward my ambitions and competencies—they wanted to understand my career goals and whether I'd actually be invested in the role. One memorable question was a creative analogy: comparing the project manager role to a position in a soccer club. It was an interesting way to get me thinking about leadership dynamics and where PMs fit in organizational structure.
Throughout both rounds, I felt the interviewers were genuine and focused on whether I'd be a culture fit. The tone was conversational rather than adversarial, and the questions were directly relevant to the day-to-day work. No coding, no whiteboarding—just a solid conversation about management skills and how I think about problems.
Prep tip from this candidate
Focus on behavioral examples of stakeholder management and be prepared to discuss cloud and infosec basics—those came up as themes across the interview. The second round is team-based, so be ready to articulate your long-term ambitions and leadership philosophy clearly.
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 | |
|---|---|
| Data Preparation for Imbalanced Data | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Experiment Validity | |
| Manager Team Sizes | |
| Top 3 Users | |
| Button AB Test | |
| Size of Joins | |
| Employee Salaries | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Find the First Non-Repeating Character in a String | |
| Comments Histogram | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Upsell Transactions | |
| Lowest Paid | |
| Download Facts | |
| Cumulative Distribution | |
| First Touch Attribution | |
| Google Maps Improvement | |
| Random SQL Sample | |
| Compute Deviation | |
| Cyclic Detection | |
| WAU vs Open Rates | |
| 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.
