Optum Software Engineer interview typically runs 3–4 rounds: recruiter screen, technical coding round, hiring manager discussion, and HR. The process spans 1–2 weeks and is notably backend- and project-driven rather than algorithm-heavy.
$117K
Avg. Base Comp
$151K
Avg. Total Comp
3-4
Typical Rounds
1-3 weeks
Process Length
We've coached candidates through Optum's software engineer process long enough to recognize its defining pattern: the depth of your project walkthrough matters more than your ability to solve abstract puzzles. Multiple candidates across different hiring cycles reported that interviewers circled back to resume line items — asking not just what technologies were used, but why certain architectural decisions were made, what the candidate personally owned, and how systems like Kafka, Elasticsearch, or Terraform fit into the broader design. If you listed it, be ready to defend it at a design level, not just a definition level.
What surprises many candidates is how much the process varies in intensity across rounds. Some interviews were described as conversational and light — basic SQL, JavaScript data types, Java fundamentals — while others pushed into API construction, rate limiter implementation, and microservices architecture under timed conditions. The CodeSignal-style assessment in particular caught candidates off guard because it leaned toward practical backend tasks like building services and implementing rate limiting, not the LeetCode-style problems most engineers drill for. That gap in expectations is where we see otherwise strong candidates stumble.
The non-obvious risk here is the process logistics. One candidate received a call with no advance notice because the recruiter forgot to include them in the invite; another had a final round cancelled four minutes before it started with no explanation. These aren't isolated complaints — they reflect a recruiting coordination layer that can feel inconsistent. Our advice: stay proactive with your recruiter, confirm every meeting link yourself, and don't let a disorganized scheduling experience shake your confidence going into the technical conversation itself.
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 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 | |
| String Palindromes | |
| Impossibly Iterative Fibonacci | |
| Azure Kubernetes Infrastructure | |
| Your Strengths and Weaknesses | |
| Prime to N | |
| Weighted Keys | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Liked Pages | |
| Bagging vs Boosting | |
| Detecting ECG Tachycardia Runs | |
| Daily Retention Summary | |
| The Brackets Problem | |
| Valid Anagram | |
| Find Duplicate Numbers in a List | |
| Prime Numbers Identification | |
| Target Indices | |
| Success Measurement | |
| Priority Queue Using Linked List | |
| Customer Success vs. Free Trial | |
| Swap Variables | |
| RAG Strict Source Control | |
| Subscription Retention | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Type I and II Errors | |
| Slow SQL Query |
Synthesized from candidate reports. Individual experiences may vary.
The process begins with a recruiter phone or video screen to confirm background, role fit, and availability. HR coordinates scheduling throughout and typically stays involved for package discussion at the end of the process.
Candidates complete one or two technical rounds 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.
Some candidates encounter a CodeSignal-style online assessment with multiple questions including API-building tasks and a rate limiter problem. This round is screen-shared and scored automatically, so practicing API design and rate limiting under time pressure is recommended.
A manager conversation follows the technical rounds and is more conversational in tone. It typically includes resume-based questions, situational or behavioral prompts, and discussion of the team, role expectations, and future tech stack.
The final stage is a standard HR or behavioral interview covering general fit, communication style, and compensation. This round is straightforward compared to the technical screens and often concludes with a package discussion.