Optum-UHG Interview Experience for Internship (On-Campus 2019)
Interview Experience
Optum(UHG) visited our campus on 14th August 2019 for the position of SDE Intern at multiple locations. There were 3 rounds for selection in the company. Around 600 studen...
Full Details
Optum(UHG) visited our campus on 14th August 2019 for the position of SDE Intern at multiple locations. There were 3 rounds for selection in the company. Around 600 students gave the first round -online test. Round 1 (Online Test): The first round was an online test conducted on CoCubes which comprised 2 sections that had to be solved in a duration of 1hr. Section 1: There were 30 MCQ which had to be solved in 30 minutes. The first 20 MCQ were based on Visual Reasoning and Comprehension based logical reasoning questions with some Quant part mixed in it. The last 10 questions were based on maths and data interpretation. Section 2: This section had to be solved in 30 minutes and consisted of 2 coding questions. Both the questions were very easy and could be solved using a brute force approach. (one question was to find the sum of numbers in an array which are at prime indexes) Tips: Try to solve the last 10 questions first as they are easy to solve because it takes too much time to solve the first 20 questions and there is a high chance that you might know the answer to the last questions but you won't have enough time for them. Also, practice some Einstein riddle problems. After the first round, 60 students including me were shortlisted for the
next round which was a development based round. Round 2 (Technical Interview Round-1): This round was a technical interview round. The interviewer asked me to give a brief introduction about myself. I started my introduction by telling most of them that were written on my CV. He interrupted me and started the discussion on IoT, what is IoT? What are the recent technologies that are using IoT and what is the future of IoT, where do you see IoT being used and in which industries? Then he started his stopwatch on his phone and said: "Let's play a game, you have 5 mins, and he asked me to explain completely one of my projects which were mentioned in my CV". Fortunately, I was able to explain it. He then asked me do you know what is JSON (since I used it in my project)? Then he asked what is the difference between JSON and XML and why JSON is more preferred in the industry as compared to XML. Then finally he gave some good advice and ended the interview on a good note. After this round, only 30 students including me were shortlisted for the
next round which was an HR round Round 3 (HR Round): In this round, the interviewer asked me some common HR questions Tell me something about yourself. Why do you want to join Optum? Do you have any Location constraints? Then she explained to me the entire internship process, how things work, and how teams and locations are decided. Finally, the company selected all the 30 students from the campus. Fortunately, I was one of them to be selected as an intern for the world's largest healthcare company
About This Question
This is a candidate experience report from a uhg interview for a data science role (intern level) during the oa round reported in 2020.
It covers the following topics: Arrays, Sql, 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.