Optum - UnitedHealth Group Interview Experience for TDP 2
Question Details
It is an on-campus experience.Round-1The test was done in online mode. In the first round, there was 1 coding question and 50 MCQ questions.The coding question was based o...
Full Details
It is an on-campus experience. Round-1 The test was done in online mode. In the first round, there was 1 coding question and 50 MCQ questions. The coding question was based on an array and was of medium level. The MCQ questions included topics like statistics, logical reasoning, data structures, OOPS, etc. The time duration for the test was 1 hour 30 minutes. This round was easy to medium level. Suggestion : I really recommend to do practice from sites like GeeksForGeeks. It is very helpful. Tips: Be calm and patient. Solve the questions with a peaceful mind. Always think you can do it. Don't panic. Round-2 (Technical Interview Round ) This was an online round. This round lasted for about 45 minutes. At first, he told me to Introduce Myself. Then he asked me what are my technical skills. Then he asked what is object-oriented programming. Explain all OOPS concepts i.e. class, object, inheritance, polymorphism, etc. He asked about hashing and constructors. He also asked about function overloading and recursion. Then he asked me about my project and told me to explain it and also show it. He asked me 2 coding questions: A code was given and I had to identify whether it is run time or compile time polymorphism. Write the code for the Fibonacci series. Tips : Do practice basic concepts like oops, sorting, etc. Be confident and keep smiling. Also only write the things you know in your resume. Do not write anything that you don't know in your resume.
Result I got selected as TDP2.
About This Question
This is a reported interview question from a uhg interview for a swe role during the phone screen round reported in 2025.
It covers the following topics: Arrays, Recursion, Sorting, Probability Stats, Oop, Math .
Difficulty rating: Easy
More Uhg Interview Questions
About Uhg Interview Reports
This question was reported by a candidate who interviewed at Uhg. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Uhg are the higher-signal extractions to take from this report.
For broader preparation context, the Uhg interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Uhg reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Uhg Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Uhg reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.