← Oscar Interview Insights

Oscar·Software Engineer·Onsite - System Design / Architecture·Senior

SeniorPrefer not to say
Jun 2026

Summary

System design onsite at Oscar Health for a software engineer role. The problem was interesting enough but the interviewer was pretty checked out and gave zero feedback throughout, which made it hard to know if I was on track.

Questions Asked (1)

Q1

Design a web-based queuing system that lets licensed physicians manage incoming telehealth consultation requests, where each physician can only be matched with patients from states they hold a license in.

System DesignData ModelingTechnical Trade-offs
Author's notes

The core constraint here is the state licensing thing, which actually makes the queue design more interesting than a basic FIFO queue.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and scale, then design a high-level architecture with separate services for request intake, matching, and state management. Focus on the core matching logic that filters physicians by state licensure and availability, and discuss data models, consistency, and trade-offs.

Pro tip: Emphasize the importance of state licensure as a hard constraint and discuss how to handle edge cases like multi-state licenses and license expiration. Also, mention the need for audit logs for compliance in healthcare.

1. Clarify Requirements and Scale

Ask questions to understand expected user base, request volume, latency requirements, and compliance needs. Establish functional and non-functional requirements.

2. High-Level Architecture

Propose a microservices architecture with components like API gateway, request queue, matching service, physician service, and state license service. Consider using a message broker for asynchronous processing.

3. Data Modeling

Design schemas for physicians (including licenses with states and expiration), patients (with state), and consultation requests. Discuss indexing for efficient queries.

4. Matching Algorithm

Detail how to match requests to physicians: filter by state license, then by availability, and possibly by specialty or other criteria. Discuss real-time vs batch matching and load balancing.

5. Trade-offs and Scalability

Discuss trade-offs between consistency and availability, SQL vs NoSQL, and how to scale the matching service. Address failure scenarios and monitoring.

Key Points to Mention

  • State licensure as a hard filter in matching
  • Use of a message queue for decoupling and handling spikes
  • Data consistency for license updates and expiration
  • Scalability considerations: sharding by state or physician ID
  • Compliance and audit logging for HIPAA
  • Handling multi-state licenses and license verification

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.