Garner Health Data Scientist interview prep: one candidate reports a recruiter screen, a statistics round on sample sizes, and a product-specific case with coding. Includes salary estimates and how to prepare.
$140K
Avg. Base Comp
$175K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The one Data Scientist candidate account we have points to a loop built around healthcare measurement rather than generic data science trivia. The first technical round was described as a stats quiz centered on sample sizes and uncertainty. One question asked how to rank a doctor with 20 successes out of 100 procedures against one with 3 out of 10. The candidate says the interviewers wanted more than a comparison of raw rates, so practice explaining why small samples are noisy and how you would account for that.
The next round combined a case study with coding. This candidate found the case closely tied to Garner's product, including a question about a violation rate for knee replacement surgeries versus knee pain patients. They also described a prompt about measuring or ranking doctor performance from patient outcomes, where the expectation was to bring in external data sources beyond the doctor's own sample. The candidate says they missed that angle and believes it hurt them.
In practice, rehearse a few things. Compare providers with uneven volumes. Define a metric clearly before ranking anything. Name outside data you would add to make a ranking more reliable. Be ready to walk through a past project, which the candidate says came up earlier.
Synthesized from 2 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 Garner health process.
The process felt a bit uneven from the start. My recruiter screen was rushed, and the first technical round was basically a stats quiz centered on sample sizes and how to think about them. That part was straightforward on paper, but it was clear they wanted more than just a formulaic answer. One of the questions was about comparing doctors with very different sample sizes, like ranking someone with 20 successful procedures out of 100 versus 3 out of 10, so I focused on how I would account for uncertainty rather than just the raw rates.
The next round was a case study plus coding interview, and that was where things got more frustrating. The case felt heavily tied to their product, and one question was directly about a violation rate involving knee replacement surgeries versus knee pain patients. It honestly seemed like you would need inside knowledge of their product to do well, which made it feel unfair. There was also an emphasis on how to measure or rank doctor performance using patient outcomes, but they wanted me to think beyond the doctor’s own sample and recommend external data sources as well. I didn’t catch that angle quickly enough, and I think that hurt me. Earlier in the process, they also asked me to walk through a project I had completed, but the overall vibe was pretty disengaged and not especially professional. I didn’t move forward, and my main takeaway was to prepare for sample-size and ranking questions, but also be ready for product-specific assumptions and outside-data discussions.
Prep tip from this candidate
Be ready to explain how you’d compare doctors or outcomes with very different sample sizes, and practice discussing what external data you’d use to make those rankings more reliable. Also expect product-specific case questions, not just generic stats or coding.
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 Garner health
What kind of analysis would you conduct to recommend changes to the UI?
| Question | |
|---|---|
| Game Feature Home | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Experiment Validity | |
| Prime to N | |
| Weighted Keys | |
| Button AB Test | |
| Top 3 Users | |
| Hurdles In Data Projects | |
| Network Experiment Design | |
| Bagging vs Boosting | |
| Detecting ECG Tachycardia Runs | |
| Size of Joins | |
| The Brackets Problem | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Declining Applicants | |
| Random Forest Explanation | |
| Sort Strings | |
| String Mapping | |
| Precision and Recall | |
| Valid Anagram | |
| Find Duplicate Numbers in a List | |
| Xgboost vs Random Forest | |
| Success Measurement | |
| Target Indices | |
| Priority Queue Using Linked List | |
| Customer Success vs. Free Trial | |
| Skewed Pricing |
Synthesized from candidate reports. Individual experiences may vary.
The candidate describes the recruiter screen as rushed. Candidates may want to prepare a short background summary and be ready to discuss a project they have completed, since this candidate reports being asked to walk through one earlier in the process.
The candidate reports the first technical round was essentially a stats quiz on sample sizes. One example compared a doctor with 20 successes out of 100 against one with 3 out of 10. The interviewers appeared to want reasoning about uncertainty, not just raw rates.
The candidate reports a case study plus coding interview tied closely to Garner's product, including a violation-rate question on knee replacement surgeries versus knee pain patients. They also faced a doctor-performance ranking prompt where recommending external data sources was expected. Exact coding content was not described.
This candidate did not receive an offer and did not advance past the case and coding round. Their takeaway was to prepare for sample-size and ranking questions, product-specific assumptions, and discussion of outside data.
