
Truveta Software Engineer interview typically runs 3 rounds: recruiter screen, technical round 1, technical round 2. It usually takes a few weeks and can feel low-energy and inconsistent.
$152K
Avg. Base Comp
$187K
Avg. Total Comp
3
Typical Rounds
2-3 weeks
Process Length
We’ve seen a clear pattern in the one candidate report we have for Truveta: the company appears to care more about whether you can work through basic data-structure mechanics and a slightly messy edge-case problem than about pushing for especially deep algorithmic insight. The questions themselves were familiar—one straightforward implementation exercise and one grid-based reasoning problem—but the candidate’s experience suggests the real test is whether you can stay precise when the prompt gets a little awkward and the interviewer doesn’t do much to steer you.
What’s more revealing is the tone. Multiple details point to an interview loop that felt low-energy and transactional: late interviewers, a recruiter screen that felt like a formality, and a panel that came across as disengaged. For candidates, that means the non-obvious risk here may not be the difficulty of the problems, but whether you can maintain clarity and confidence without much conversational support. In our view, Truveta’s signal is less about dazzling with cleverness and more about showing you can reason cleanly through implementation details under a somewhat sterile process.
That matters because companies in HealthTech often sell mission first, but candidates still judge the team by how the interview feels. Here, the reported mismatch between a strong mission and a flat process is itself a data point. Our read is that candidates should expect a practical, not polished technical screen, and that the interviewers may be looking for steady execution rather than standout creativity.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Truveta process.
The recruiter screen was basically a formality and didn’t add much, then I moved into two technical rounds that were honestly pretty underwhelming. Both interviewers showed up late by about 10 to 15 minutes, and the whole thing felt oddly checked out from the start. The first coding question was to implement a stack using two queues, which was straightforward enough. The second was more awkward: I had to traverse a binary matrix and flip bits depending on their neighbors. That one was less about a clean algorithmic pattern and more about carefully reasoning through the grid logic while the interviewer stayed pretty disengaged.
What stood out most wasn’t the difficulty of the questions, but the vibe. I was interested in Truveta on paper because the mission is solid, but the interview process didn’t do much to build confidence. It felt like a tepid waste of everyone’s time, and the interviewers came across as soulless and robotic, which was a bad sign for the quality of the team. I didn’t get an offer, and if I had to do it again I’d go in expecting a couple of basic data structure questions plus one slightly messy matrix problem, but not much warmth or energy from the panel.
Prep tip from this candidate
Be ready for a classic stack-using-two-queues implementation and a grid traversal problem where you have to reason about neighbor-dependent bit flips. The bigger surprise here was the interviewer demeanor, so don’t expect much guidance or engagement during the technical rounds.
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 Truveta
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Monthly Customer Report | |
| Find the Missing Number | |
| Upsell Transactions | |
| Prime to N | |
| String Shift | |
| Largest Salary by Department | |
| Scrambled Tickets | |
| Total Spent on Products | |
| Rectangle Overlap | |
| Over-Budget Projects | |
| Size of Joins | |
| Minimum Change | |
| Google Maps Improvement | |
| Green Dot | |
| Hurdles In Data Projects | |
| Project Pairs | |
| The Brackets Problem | |
| Integer to Roman | |
| Sum to N | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Detecting ECG Tachycardia Runs | |
| Target Indices | |
| Nearest Common Ancestor | |
| One Element Removed | |
| Unique Work Days |
Synthesized from candidate reports. Individual experiences may vary.
The first conversation was a brief recruiter screen that felt mostly like a formality. It did not go very deep and mainly served as an initial checkpoint before technical interviews.
The first technical round focused on a standard coding problem: implementing a stack using two queues. The question was straightforward and centered on basic data structure knowledge.
The second technical round was a more awkward grid/matrix problem involving traversing a binary matrix and flipping bits based on neighboring cells. It required careful reasoning through the logic rather than a clean, familiar algorithm pattern.