
One candidate who interviewed for a Product Manager role at Oscar Insurance in September 2024 described a recruiter call, a hiring manager call with a case, and a four-hour panel with two more cases.
$165K
Avg. Base Comp
$221K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The one Oscar Insurance Product Manager interview report we have, from September 2024, centers on case studies. The candidate describes three cases across the process: one during the hiring manager call, then two more in the final panel. One case asked how to make a workflow faster or more reliable. Another asked for a product improvement: pick a feature, say who it serves, and explain how you would measure success.
The candidate says the questions were not gotcha-style and the interviewers were friendly and curious about how they think. In their account, clear structure and talking through tradeoffs out loud counted for more than landing on a perfect answer. Practice both case types aloud, with a stated goal, a user, a few options, and a success metric.
The panel ran about four hours, with three interviews, and the candidate found the length tiring. Plan your energy so the later conversations are as sharp as the first. The candidate did not receive an offer and was told company policy prevents sharing feedback, so it helps to write your own notes after each round.
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 Oscar Insurance process.
I went through the Product Manager process at Oscar Insurance in September 2024, and it started with a recruiter call, followed by a hiring manager call that included a case study. The final stage was a long panel, around four hours, with three interviews and two more case studies. Once that wrapped up, I had another recruiter call to close things out. The format was fairly standard for a PM role, and nothing about it felt like a trick. The questions were not gotcha-style, and the people I met were curious about how I think and genuinely friendly. One case study centered on process improvement, asking me to look at how a workflow could be made faster or more reliable. The other was a product improvement case, where I had to think through a feature, who it serves, and how I would measure whether it worked. Both cases rewarded clear structure and talking through tradeoffs out loud, more than arriving at a perfect answer. The panel was the most demanding part, mainly because of the length. By the end I was tired, so I would suggest pacing yourself and keeping your energy up for the later interviews. I did not receive an offer. The part that stayed with me is that I got no feedback at all. The company told me its policy prevents the team from sharing feedback, which was hard to accept after investing that much time and effort. If you apply, plan on walking away without knowing what to improve, and prepare to learn from your own reflection rather than from the team.
Prep tip from this candidate
Expect two case studies, one on process improvement and one on product improvement, and practice structuring both out loud since the panel alone runs about four hours. Because the team does not give feedback, write down your own takeaways immediately after each round.
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 Oscar Insurance
Explain what a p-value is to someone who is not technical
| Question | |
|---|---|
| Confidence Interval Explanation | |
| Why Do You Want to Work With Us | |
| Risk Assessment Model | |
| 2nd Highest Salary | |
| Top 5 Turnover Risk | |
| Size of Joins | |
| Experiment Validity | |
| Employee Salaries | |
| Hurdles In Data Projects | |
| Google Maps Improvement | |
| Assumptions of Linear Regression | |
| Always Excited Users | |
| Lasso vs Ridge | |
| Duplicate Rows | |
| Total Spent on Products | |
| Bagging vs Boosting | |
| Multicollinearity in Regression | |
| Slow SQL Query | |
| Justify a Neural Network | |
| Branch Sales Pivot | |
| Booking Regression | |
| Type-ahead Search | |
| Type I and II Errors | |
| Bias vs. Variance Tradeoff | |
| Ride-Sharing App Schema | |
| Insurance Leads | |
| PCA and K-Means | |
| Skewed Pricing | |
| Target Indices |
Synthesized from candidate reports. Individual experiences may vary.
The candidate reports the process began with a recruiter call. The account gives no detail on its content or length, so treat it as an initial conversation and be ready to explain your background and interest in the role.
This candidate faced a case study during the hiring manager call. The report does not give the exact prompt, so practice structuring a product or process problem aloud and explaining your tradeoffs as you go.
The candidate describes the final stage as a panel of three interviews lasting about four hours, with two more case studies. One covered process improvement and one covered product improvement, including how to measure success. They found it the most demanding part mainly because of the length.
After the panel, the candidate reports another recruiter call to close things out. They did not receive an offer and were told the team does not share feedback, so it helps to record your own takeaways right after each round.