
Candidates describe Oscar software engineering interviews as medium-difficulty coding, with a design round in most reports. Reported design prompts include a campaign builder, a pastebin and an expiration-based deletion service. Some also report slow recruiter communication.
$194K
Avg. Base Comp
$310K
Avg. Total Comp
Not reported
Typical Rounds
2 months
Process Length
Candidates describe Oscar's engineering interviews as a mix of medium-difficulty coding and practical system design. One Software Engineer candidate reports a paired-programming first round at roughly medium-plus level with recursion or dynamic programming. A second round followed with two interviews, including a problem similar to LeetCode's "Heaters". That candidate says the system design round was where it went wrong. The prompt was a 60-minute "campaign builder" for configurable workflows, with draft and immutable versions, persistence, and execution against a target set. The interviewer did not confirm assumptions with simple yes-or-no answers, so practice stating assumptions aloud and designing around ambiguity.
Other reports point the same way at different levels. A Staff Software Engineer candidate describes a Morse code translator in both directions, then a virtual onsite with a technical deep dive, a product demo and a pastebin design. An Architect candidate reports a microservice that deletes records when an expiration date passes, with interviewers asking about the mechanics of orchestrating it. A Software Engineering Intern candidate describes an online assessment, a recruiter screen, and two technical rounds with heap and string problems, plus conflict-themed behavioral questions.
The most consistent non-technical theme is communication. The Staff and Architect candidates both describe silence from recruiting after their final interviews, in one case after positive onsite feedback and two follow-up emails. Ask about next steps and timing, and follow up in writing. Both also describe the engineers they met as thoughtful and collaborative.
Synthesized from 5 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 Oscar Insurance process.
First round was a paired-programming LeetCode-style round. I would place the question at a medium+ level with recursion/DP.
I moved to a second round with two interviews. One was a coding round with a question very similar to the "Heaters" problem on LeetCode.
The part I failed was the system design round, where the interviewer did not provide yes-or-no answers to stated assumptions. The question was to build a "campaign builder" that human agents could use to design and launch campaigns. The interview lasted 60 minutes.
A campaign is a defined workflow with no deterministic previous or next step. It has configurable stages, each with an undetermined number of next steps, and a terminal state of "campaign concluded" for any reason.
The design needed to support designing and saving drafts and final immutable campaigns in a database, then running campaigns for target sets. The example workflow used audience selection, language branching, phone calls, email/text follow-ups, waits, response handling, and successful or unsuccessful terminal states.
Prep tip from this candidate
Practice medium-to-hard recursive or dynamic-programming coding problems, then rehearse a system design for a branching workflow: model stages, transitions, terminal states, draft versus immutable versions, persistence, and execution for a target set. State assumptions clearly and explain how your design handles ambiguous requirements.
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 | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Top 5 Turnover Risk | |
| Size of Joins | |
| Prime to N | |
| Duplicate Rows | |
| Total Spent on Products | |
| Bagging vs Boosting | |
| Rectangle Overlap | |
| Hurdles In Data Projects | |
| Type I and II Errors | |
| Google Maps Improvement | |
| Type-ahead Search | |
| Ride-Sharing App Schema | |
| Always Excited Users | |
| The Brackets Problem | |
| Justify a Neural Network | |
| Valid Anagram | |
| Decision Tree Evaluation | |
| String Mapping | |
| Sort Strings | |
| Three Zebras | |
| Precision and Recall | |
| Find Duplicate Numbers in a List | |
| Swap Variables | |
| Target Indices | |
| RAG Strict Source Control |
Synthesized from candidate reports. Individual experiences may vary.
Openings vary by level. The intern candidate began with an online assessment of three coding questions, then had a recruiter screen covering background and company values. The Architect candidate had a roughly 30-minute recruiter phone screen followed by a coding round of about an hour. The Staff candidate's first conversation was a technical screen. Expect to talk through your background and be ready to code early.
Candidates report medium-difficulty coding: a paired-programming problem with recursion or dynamic programming for a Software Engineer, a two-way Morse code translator for a Staff candidate, and heap and string problems across two sessions for an intern. Practice explaining your approach aloud, since the intern candidate says interviewers welcomed questions while they worked.
A Software Engineer candidate describes a second round with two interviews, including a Heaters-style coding problem. A Staff candidate describes a virtual onsite with a technical deep dive, a product demo and a design session. An Architect candidate describes a 3 to 4 hour onsite block with interviewers from teams they might join. Format and length appear to vary by level and team.
Reported design prompts include a campaign builder (stages, transitions, terminal states, drafts versus immutable versions, execution for a target set), a pastebin, and a microservice that deletes records on an expiration trigger. One candidate says the interviewer did not answer yes-or-no assumption questions, so be ready to state and defend your own assumptions and explain how your design handles ambiguity.
The Staff candidate reports a final round with executive leadership after positive feedback from the hiring manager, followed by silence despite two follow-up emails. The Architect candidate also describes a quiet recruiter after the onsite and unanswered follow-ups. The intern candidate, by contrast, received an offer and describes the whole process as taking about two months. Confirm next steps and timing in writing.