Garner Health Software Engineer interviews vary across three candidate accounts, with two reporting four to five rounds. They typically include a recruiter call, a hiring manager conversation, a live coding round, and a technical or case-style discussion.
$154K
Avg. Base Comp
$190K
Avg. Total Comp
4-5 rounds
Typical Rounds
Not reported
Process Length
Three candidates describe Garner Health's Software Engineer interview, and the accounts differ. One reports four rounds and an offer. Another reports five rounds and no offer. A third reports a shorter technical loop that ended without an offer.
The common thread is a live coding round that leans toward healthcare-flavored problems rather than generic puzzles. One candidate was asked about the difference between Array.find and Array.filter in TypeScript. Another was asked to analyze a data set on how members succeed at scheduling appointments with recommended providers, in HackerRank. That candidate says AI was allowed for debugging. A third did a TypeScript list-processing exercise. Practical TypeScript and JavaScript fluency looks like the safest thing to prepare.
The later rounds vary. The candidate who received an offer describes a project-deep-dive round about technical decisions, so be ready to explain your reasoning on past work. The five-round candidate describes a culture interview on giving and receiving feedback, then a marketing-campaign case study that felt confusing without a marketing analytics background. The third candidate had a system design discussion about a room scheduling app that stayed on filtering and pagination.
Two candidates found the early stages thin on role detail, and one of them also had sessions start late or get rescheduled at the last minute. Ask the recruiter and hiring manager about the stack, the team and the loop format early. Not every candidate saw every round, so confirm your own schedule.
Synthesized from 3 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 at Garner Health was definitely lengthy—five rounds spread across several weeks. It started with a short recruiter call reviewing my background, which was pretty standard. If you pass that, you move to a hiring manager conversation where they dig into your experience and finally explain what the role actually involves. Round three is a live coding exercise on HackerRank. They give you a data set and ask you to determine how members succeed at scheduling appointments with recommended providers. It's not inherently difficult, but HackerRank itself can be tricky to navigate if you're not used to the platform, and the instructions could be clearer. They do allow you to use AI to debug your code, which helps. After that comes a culture interview focused on how you work with others—how you give feedback, how you receive it, that kind of thing. The final round is a case study exercise based on a marketing campaign, where you need to show how you'd approach analyzing it. Again, not super hard, but genuinely confusing if you don't have a background in marketing analytics. By the end, the whole process felt experimental, like they were still working out kinks in their pipeline. It's thorough, but also unnecessarily long and fragmented for what should be a cleaner hiring flow.
Prep tip from this candidate
The HackerRank coding round focuses on analyzing appointment scheduling success data with providers—get comfortable with that specific domain before going in. The case study round involves marketing analytics, so if that's not your background, spend time understanding how to approach marketing campaign analysis and key success metrics.
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
How would you decide whether Google should build a game feature for Google Home
| Question | |
|---|---|
| 2nd Highest Salary | |
| Top Three Salaries | |
| Prime to N | |
| Weighted Keys | |
| Top 3 Users | |
| Hurdles In Data Projects | |
| Bagging vs Boosting | |
| Detecting ECG Tachycardia Runs | |
| Size of Joins | |
| The Brackets Problem | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Sort Strings | |
| String Mapping | |
| Precision and Recall | |
| Most Repetition | |
| Valid Anagram | |
| Find Duplicate Numbers in a List | |
| Success Measurement | |
| Target Indices | |
| Priority Queue Using Linked List | |
| Customer Success vs. Free Trial | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Prime Numbers Identification | |
| RAG Strict Source Control | |
| String Palindromes | |
| Concurrent LLM Serving | |
| Type I and II Errors | |
| Swap Variables |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter or phone screen that reviews your background and experience. One candidate says the outreach gave little detail on the stack or team, so it may help to ask what the role involves and what the remaining rounds will cover.
Two candidates describe a hiring manager conversation that digs into your experience. One says this was where the role was finally explained, so come with questions about the team, the work and what success looks like.
Candidates report a live coding round that is not leetcode-style. Reported tasks include Array.find versus Array.filter in TypeScript, a TypeScript list-processing exercise, and a HackerRank data analysis of appointment scheduling success. One candidate says AI could be used to debug.
One candidate reports a deep dive into past projects and technical decisions. Another reports a room scheduling system design exercise that centered on filtering and pagination. Formats appear to differ, so prepare to explain past decisions and basic backend design.
One five-round candidate reports a culture interview about giving and receiving feedback, followed by a marketing-campaign case study. It may not appear in every loop, but reviewing how to approach campaign metrics could help if you are asked.
