Two candidates describe DXC Technology's Product Manager interview as conversational: stakeholder management, a constrained project scenario, and career goals, with no coding. Both reported receiving offers.
$125K
Avg. Base Comp
$145K
Avg. Total Comp
2 rounds
Typical Rounds
Not reported
Process Length
The two reports we have for DXC Technology's Product Manager interview describe a conversational process built around management fundamentals rather than coding or whiteboarding. Both candidates received offers, and each account is one person's experience, so details vary.
One candidate had two phone rounds. The first was with someone from the management team and leaned on behavioral and situational questions, including how they handled a difficult stakeholder. It also touched on IT knowledge and infosec awareness, so a refresher on cloud fundamentals and basic security concepts is sensible. The second round included members of the team the candidate would join and focused on ambitions, competencies and career goals. One memorable question compared the project manager role to a position in a soccer club.
The other candidate began with an HR screening that covered their background and previous work in detail. A conversation with the hiring manager followed, built around a constrained scenario: bring a project timeline back on track with no re-baseline, no extra resources and no management buy-in. The candidate felt the interviewer cared more about how they reasoned through trade-offs than about a named framework, and waited a few weeks for a decision.
To prepare, line up two or three stories about stakeholder conflict, practice talking through delivery problems where the usual levers are unavailable, and be ready to explain your long-term goals plainly.
Synthesized from 3 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.
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 | |
| Rolling Bank Transactions | |
| Employee Salaries | |
| Customer Orders | |
| Find the First Non-Repeating Character in a String | |
| Comments Histogram | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Lowest Paid | |
| Upsell Transactions | |
| 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.
One candidate began with an HR screening that was straightforward and professional. The recruiter asked them to describe previous work experiences in detail and made sure they understood the role and what the position would involve. Have a concise summary of your background ready.
Another candidate's first phone round was with someone from the management team. It focused on behavioral and situational questions, including how they had managed a difficult stakeholder, and also probed IT knowledge and infosec awareness. Brushing up on cloud fundamentals and basic security concepts was their advice.
In a separate account, the technical conversation with the hiring manager posed a scenario: pull a project timeline back on track with no re-baseline option, no additional resources and no management buy-in. The candidate felt the interviewer cared more about trade-off and stakeholder reasoning than a memorized framework.
The second phone round in the two-round account included members of the team the candidate would work with. Questions centered on career goals, competencies and whether they would be invested in the role, and included an analogy comparing the project manager role to a position in a soccer club. The tone was conversational.
