
Three candidates describe Optum Product Manager interviews built around scenario and behavioral questions, with two to four stages. Outcomes ranged from an offer to a hiring freeze, so prepare structured stories and a worked business problem.
$125K
Avg. Base Comp
$145K
Avg. Total Comp
2-4 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Optum's Product Manager interviews as heavily scenario-based and behavioral, with little emphasis on product design exercises. One candidate reported a rigidly scripted process with a panel of three. The questions covered handling a difficult stakeholder, absorbing new requirements when a timeline is locked for compliance reasons, and working with cross-functional teams. That candidate also got some PM metrics questions and "What's your favorite product?", and reported no case studies. They did not receive an offer.
Another candidate interviewed remotely in two rounds with people from product, engineering, management and marketing. The first was a domain round structured around the STAR method. The second ran over an hour and was techno-managerial, with questions about explaining API testing to a newcomer, setting up an automation framework, and a workplace conflict. Salary expectations came up near the end, but HR later said the position was on hold.
A third candidate reported four stages: a technical round built around a real-world business scenario, a managerial conversation, an HR discussion and a final face-to-face meeting. They received an offer, although an internal reorganization delayed it by over a month.
In practice, prepare a small set of STAR stories on stakeholder conflict, constraints such as compliance deadlines, and cross-functional work. Also practice walking through a business problem from analysis to recommendation, naming the trade-offs. Since the process may involve technical-leaning questions, be ready to explain technical concepts plainly to non-technical listeners. Stage counts and timing varied between candidates, so confirm the schedule with your recruiter.
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 Optum process.
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 Optum
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Size of Joins | |
| Hurdles In Data Projects | |
| String Palindromes | |
| Azure Kubernetes Infrastructure | |
| Account Personalization Strategy | |
| Your Strengths and Weaknesses | |
| Fast Food Database | |
| Experiment Validity | |
| Button AB Test | |
| Liked Pages | |
| Google Maps Improvement | |
| Decreasing Comments | |
| P-value to a Layman | |
| Network Experiment Design | |
| Bagging vs Boosting | |
| Daily Retention Summary | |
| Delivery Estimate Model | |
| Detecting ECG Tachycardia Runs | |
| Success Measurement | |
| Target Indices | |
| Customer Success vs. Free Trial | |
| Declining Applicants | |
| Random Forest Explanation | |
| Subscription Retention | |
| Slow SQL Query | |
| Xgboost vs Random Forest | |
| Audio Chat Success | |
| Skewed Pricing | |
| Assumptions of Linear Regression |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a first round focused on scenarios. One described a STAR-structured domain interview, and another a technical round where they analyzed a real-world business problem and recommended a solution. Expect to explain your reasoning and trade-offs rather than just a conclusion.
One candidate reported a panel of three asking about difficult stakeholders, locked compliance timelines with new requirements, and cross-functional collaboration, plus some PM metrics questions. Another reported a managerial conversation. Interviewers may follow a fixed script, so prepared stories that match common PM scenarios typically help.
One candidate described a second round of over an hour mixing technical and management topics, including explaining API testing to a beginner, challenges setting up an automation framework, and handling a workplace conflict. Interviewers came from several disciplines, so tailor explanations to a mixed audience.
One candidate discussed salary expectations near the end of their second round. Another had an HR conversation followed by a final face-to-face meeting. Outcomes differed: one candidate got an offer after a delay of over a month from an internal reorganization, while another was told the role was on hold. Timelines may be uncertain, so follow up with your recruiter.