Optum software engineer candidates report a variable 2–4-round process that commonly combines coding, resume and project discussion, technical fundamentals, and HR or manager conversations.
$115K
Avg. Base Comp
$131K
Avg. Total Comp
2-4 rounds
Typical Rounds
1 day
Process Length
Optum software engineer interviews reported here vary by team and stack, but your own projects and practical engineering judgment recur more often than one fixed question set. Several candidates described technical conversations driven by their resume, recent project architecture, personal contributions, and implementation choices. Prepare a concise walkthrough that explains the problem, your ownership, the technologies involved, and why you chose your approach.
Coding can be straightforward but still hands-on. Reported prompts include reversing a string, small coding programs, a Python problem, and an online assessment containing API-building tasks and a rate limiter. SQL, OOP, DBMS, and language fundamentals also appeared. Backend-oriented reports covered Java, Spring Boot, microservices, Kafka, Hibernate, and Elasticsearch, while another candidate discussed Terraform and infrastructure. Other interviews included basic Angular, JavaScript, or Java questions. Match your preparation to the advertised stack and everything listed on your resume.
Some candidates also encountered practical design or performance scenarios, including reducing API overhead and improving database performance. Be ready to clarify the goal, identify likely constraints, and explain the tradeoffs in your proposed solution. Technical depth was inconsistent: some candidates described multiple coding tests, while others received mostly basic questions and project discussion.
HR or manager conversations may cover background, goals, motivation, collaboration, and previous work situations. Reported processes ranged from two to three rounds in the supplied accounts, and one candidate completed the interview in a single day. Treat both the sequence and duration as team-specific rather than guaranteed.
Synthesized from 15 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 | |
| Sort Strings | |
| String Mapping | |
| Hurdles In Data Projects | |
| Concurrent LLM Serving | |
| String Palindromes | |
| Impossibly Iterative Fibonacci | |
| Azure Kubernetes Infrastructure | |
| Your Strengths and Weaknesses | |
| Fast Food Database | |
| Prime to N | |
| Weighted Keys | |
| P-value to a Layman | |
| Liked Pages | |
| Bagging vs Boosting | |
| Daily Retention Summary | |
| Delivery Estimate Model | |
| Detecting ECG Tachycardia Runs | |
| The Brackets Problem | |
| Valid Anagram | |
| Find Duplicate Numbers in a List | |
| Target Indices | |
| Success Measurement | |
| Priority Queue Using Linked List | |
| Customer Success vs. Free Trial | |
| Prime Numbers Identification | |
| Swap Variables | |
| RAG Strict Source Control | |
| Subscription Retention |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report recruiter conversations, AI-based screening, recorded introductions, and online coding assessments in different processes. Early prompts may cover your background, interest in the role, and core coding; be ready to summarize your experience clearly and explain the stack you have used.
Candidates report coding tasks ranging from string and array exercises to linked-list handling, plus discussions of OOP, DSA, DBMS, SQL, or language fundamentals. Some reports describe a shared-editor or online format, so practice explaining your approach and clarifying requirements while you code.
Multiple candidates report detailed questions about project architecture, individual contributions, and listed technologies. Depending on the team, discussions may cover Java and Spring Boot, infrastructure, web development, .NET, or other role-specific tools; connect your answers directly to work you have done.
Candidates report practical scenarios involving API overhead, database performance, traffic spikes and caching, Docker image size, or event-driven services. These topics are not universal, but you may be asked to reason through tradeoffs, failure points, and a pragmatic implementation plan.
Candidates report manager or HR discussions after technical evaluation, covering resume examples, collaboration, conflict, strengths, goals, and motivation. Prepare concise examples that show how you work with others and how your experience fits the team’s needs.
