Optum Software Engineer interview typically runs 3-4 rounds: recruiter screen, technical interview(s), hiring manager, and HR. The process usually takes about 1-2 weeks and is practical, resume-driven, and sometimes uneven.
$120K
Avg. Base Comp
$210K
Avg. Total Comp
3-4
Typical Rounds
1-3 weeks
Process Length
We’ve seen Optum evaluate software engineers less like algorithm specialists and more like practical backend builders. Across candidate reports, the strongest signal is how well you can explain your own projects: multiple candidates were pressed on architecture, personal contributions, and the technologies they listed, from Spring Boot and Hibernate to Elasticsearch and Terraform. That tells us the team is listening for real ownership, not just familiarity with buzzwords. If your resume says you built it, expect to defend the design choices behind it.
Another recurring theme is that Optum cares about working knowledge over puzzle-solving. Candidates repeatedly described questions at an easy-to-moderate level, with SQL basics, Java fundamentals, and API-building tasks showing up more often than deep whiteboard problems. Even the more unusual assessment leaned toward practical backend work like rate limiting and service-style tasks rather than abstract DSA drills. We also noticed that some interviews stayed broad and conversational, which means clarity and precision matter: vague answers about your stack tend to stand out here.
The non-obvious make-or-break factor is consistency. Our candidates report a process that can feel uneven, with some rounds light on depth and others unexpectedly focused on specific tools or recent work. That means preparation should be anchored in the exact systems you’ve used recently, especially microservices, SQL joins, and core Java/Spring concepts. At Optum, the candidates who did best sounded like engineers who had actually shipped and supported backend systems, not just studied them.
Synthetized from 5 candidates 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.
The hardest part for me was the online coding round, because it wasn’t a typical LeetCode-style interview. I had a recruiter phone screen first, then a video interview with the hiring managers, and after that came two technical tests where I had to share my screen and solve the problems on my own, although I could ask clarifying questions. The technical rounds were very focused on core backend work: Java, Spring Boot, microservices, SQL, and whatever I’d actually built on my resume. In my case, they spent a lot of time on my recent project and asked me to explain the architecture and my contributions clearly.
The AI-based assessment was the most unusual part. It was an online CodeSignal-style round with four questions, including three API-building tasks and one rate limiter, and it felt hard to crack because I wasn’t sure how the scoring worked. In the live rounds, they also checked problem-solving first and then moved into domain knowledge, including Kafka and DBMS. The final step was behavioral/HR, which was pretty standard compared with the technical screens. Overall, the process felt very backend-heavy and practical rather than algorithm-heavy. I ended up receiving an offer, and my main takeaway is to be ready to talk through your project deeply and to practice building APIs and rate limiters under time pressure, not just generic coding problems.
Prep tip from this candidate
Practice CodeSignal-style API-building tasks and a rate limiter implementation, since that online round was the most distinctive part. Also be ready to explain your recent project in detail and answer focused questions on Java, Spring Boot, microservices, Kafka, SQL, and DBMS.
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 | |
| String Palindromes | |
| Impossibly Iterative Fibonacci | |
| Azure Kubernetes Infrastructure | |
| Your Strengths and Weaknesses | |
| Top Three Salaries | |
| Prime to N | |
| Top 3 Users | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Liked Pages | |
| The Brackets Problem | |
| Daily Retention Summary | |
| Find Duplicate Numbers in a List | |
| Valid Anagram | |
| Most Repetition | |
| Prime Numbers Identification | |
| Subscription Retention | |
| Type I and II Errors | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Slow SQL Query | |
| Swap Variables | |
| Combinational Dice Rolls | |
| Uber Eats Customer Experience | |
| Why Do You Want to Work With Us | |
| Stakeholder Communication | |
| Client Solution Pushback |
Synthesized from candidate reports. Individual experiences may vary.
The process often starts with a recruiter phone screen to confirm background, role fit, and scheduling. In some cases, HR stays involved throughout coordination and follow-up, including package discussion later in the process.
Candidates typically complete one or more technical interviews focused on practical backend skills rather than heavy algorithms. Expect coding problems, basic SQL, and questions on Java, Spring Boot, Hibernate, microservices, Kafka, DBMS, Angular basics, Terraform, and Elasticsearch, along with deep discussion of your resume projects and architecture decisions.
A manager conversation follows in many cases and is more conversational than the technical rounds. It usually includes resume-based questions, situational or behavioral prompts, and discussion of the team, role, and future tech stack.
The final stage is often a standard HR or behavioral interview. This round may cover general fit, communication, and compensation or package discussion after the technical interviews.