Candidates describe an Included Health software engineer process built around a recruiter call, a technical screen and a hiring manager conversation. Several reports describe unclear prompts or mismatched expectations, and all five ended without an offer.
$170K
Avg. Base Comp
$200K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Across five candidate reports for engineering roles at Included Health, the process usually opens with a recruiter call, then moves to a technical screen and a hiring manager conversation. One candidate describes five rounds in total, including a project deep dive and two technical panels. All five reports ended without an offer, so treat this as a picture of what went wrong as much as what to expect.
The technical screens differ. One candidate expected OOP-focused questions but received a four-part algorithmic problem. A Full Stack candidate describes a Python exercise on filtering and manipulating an unsanitized data structure, with follow-ups that built on each other and prompt wording that took time to decode. A senior Android candidate reports a LeetCode-medium problem on HackerRank, finding doctors whose service radius covers a client's coordinates and then picking the closest. That candidate's IDE failed mid-session. Another candidate found the technical screen easy.
The hiring manager round drew the most frustration. One candidate found the questions vague with no behavioral prompts. Another says the manager stressed mission and vision and seemed to want aligned answers.
Practice data filtering, string handling and distance calculations. Ask early what the interviewer is testing, and have a backup coding environment ready. Candidates also report scheduling delays and sudden rejections, so keep your own timeline flexible.
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 Included Health 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 Included Health
Implement the k-means clustering algorithm in python from scratch
| Question | |
|---|---|
| 2nd Highest Salary | |
| Top Three Salaries | |
| Top 3 Users | |
| Prime to N | |
| Weighted Keys | |
| Size of Joins | |
| Hurdles In Data Projects | |
| Bagging vs Boosting | |
| Google Maps Improvement | |
| Detecting ECG Tachycardia Runs | |
| Type I and II Errors | |
| The Brackets Problem | |
| Ride-Sharing App Schema | |
| P-value to a Layman | |
| Justify a Neural Network | |
| String Mapping | |
| Sort Strings | |
| Precision and Recall | |
| Most Repetition | |
| Valid Anagram | |
| Find Duplicate Numbers in a List | |
| Swap Variables | |
| Success Measurement | |
| Target Indices | |
| Priority Queue Using Linked List | |
| Client Solution Pushback | |
| Customer Success vs. Free Trial | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Prime Numbers Identification |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening recruiter conversation covering their resume, a recent project and career goals. One candidate was told the technical screen would focus on OOP rather than heavy algorithms, and it did not. Another was told a failed technical screen would cancel the manager interview. Confirm the format with the interviewer directly.
Candidates describe different problems: a four-part algorithmic question, Python data filtering with progressively harder follow-ups, and a HackerRank problem about doctors' coordinates and service radii. One screen was reportedly about 45 minutes. Expect to clarify ambiguous terms early, and have a backup environment ready in case the platform fails.
Several candidates report a hiring manager round. Accounts differ: one found the questions vague with no behavioral prompts, and another felt the manager wanted mission-aligned answers. The order varied too, as one candidate's manager screen came before the technical screen. Prepare clear stories about your experience and ask what skills the questions target.
One Full Stack candidate describes five rounds: a technical whiteboard, a project deep dive with the hiring manager, two technical panels and a behavioral conversation with leadership. Another candidate was told an onsite would be scheduled but received a rejection. Not every candidate reached later rounds, so this stage may vary by role and level.
