Healthverity Software Engineer interview typically runs 7 rounds: recruiter, manager, manager again, several team members, assessment, presentation, final decision. It can stretch over weeks and is notably drawn out, with a heavy unpaid assessment.
$152K
Avg. Base Comp
$187K
Avg. Total Comp
7
Typical Rounds
4-8 weeks
Process Length
We’ve seen HealthVerity lean hard into whether candidates can think like someone shipping data products for healthcare clients, not just like an engineer solving isolated technical problems. The strongest signal in the candidate experience was the repeated focus on implementation tradeoffs for a real business case: the live conversations were framed around how to build solutions for a client scenario, which suggests they care a lot about practical judgment, not polished theory. That matters here because the company sits at the intersection of data infrastructure and healthcare, where the “right” answer often depends on data quality, integration constraints, and downstream client needs.
A recurring theme is the weight of the assessment. One candidate described spending 10+ hours on a take-home plus presentation, and that combination tells us HealthVerity is looking for people who can turn ambiguous requirements into something structured and explainable. We’d pay attention to how clearly you can justify design choices, especially when the problem involves messy healthcare data and multiple stakeholders. The odd part of the feedback loop — including post-interview coaching after a rejection — also hints that the bar may be less about a single brilliant solution and more about whether your thinking matches an internal standard they’re still calibrating.
We’ve also seen signs that internal alignment can be a hidden factor. The candidate felt like the team was still sorting out what they wanted, and that kind of drift can make consistency matter more than flash. In practice, that means candidates who do best here usually sound measured, client-aware, and specific about execution, rather than overly abstract or overly broad.
Synthetized from 1 candidates 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 Healthverity process.
This was one of the more drawn-out interview processes I’ve been through. It started with a recruiter and then turned into a protracted series of meetings with the manager, the manager again, and several team members. By the time I got to what felt like the fifth interview, I was already wondering if they had actually aligned internally on what they wanted. The whole thing ended up being seven interviews total.
The part that really stood out was the assessment. I spent 10+ hours on it, and it wasn’t just a take-home exercise — I also had to put together a presentation to move forward. The questions in the live conversations were mostly framed around how I would implement certain solutions for a client business case, so it felt more like walking through practical decision-making than answering textbook technical questions. That said, the amount of unpaid work required was hard to justify, especially with the process stretching on so long. After all of that, they told me I didn’t get the job, and then offered to coach my work afterward, which I found pretty odd. The position was still posted months later. Overall, I wouldn’t recommend it.
Prep tip from this candidate
Be ready to talk through implementation choices for a client business case in detail, and expect to defend a take-home plus presentation rather than a standard coding loop. I’d also prepare for a long process with multiple manager/team interviews before you ever get a decision.
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 Healthverity
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Subscription Overlap | |
| Comments Histogram | |
| Find the Missing Number | |
| Random SQL Sample | |
| Prime to N | |
| Upsell Transactions | |
| Monthly Customer Report | |
| Over-Budget Projects | |
| Rectangle Overlap | |
| Level Of Rain Water In 2D Terrain | |
| One Element Removed | |
| Basic Regex | |
| Target Indices | |
| String Subsequence | |
| Hurdles In Data Projects | |
| Real-Time Transaction Streaming | |
| Google Maps Improvement | |
| Unique Work Days | |
| Nearest Common Ancestor | |
| Find Duplicate Numbers in a List | |
| Cyclic Detection | |
| Groups of Anagrams | |
| Longest Increasing Subsequence | |
| Radix Addition | |
| Binary Tree Conversion | |
| String Mapping | |
| Total Spent on Products | |
| Most Repetition |
Synthesized from candidate reports. Individual experiences may vary.
The process begins with an initial conversation with a recruiter to cover background, interest in the role, and basic fit. This appears to be the first filter before moving into the longer interview loop.
Candidates then meet with the hiring manager multiple times. The experience described included repeated meetings with the manager, suggesting the team used these conversations to dig into role fit and practical problem-solving.
Several interviews are conducted with other team members after the manager conversations. These live discussions focus on how the candidate would implement solutions for client business cases rather than on textbook-style technical questions.
Candidates complete a substantial assessment that goes beyond a standard take-home exercise. In addition to the written work, they must prepare and deliver a presentation to advance in the process.
After the full interview loop and assessment, the company makes a final hiring decision. In the reported experience, the process ended in a rejection after seven total interviews.