Truveta logo

Truveta Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 39 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
23.1% Positive experience

Which role are you interviewing for?

16 roles · 39 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Truveta.

Showing 4 of 39
Truveta logo
Truveta

Financial Planning & Analysis Intern

Finance · nearly a year ago

Intern Easy Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

The interview was pretty straight forward, just asking about basic resume stuff and questions related to the role. It also covered start date, and other things related to those topics. It was helpful to know what truveta was about too, and what the companies goals are

Confirmed questions6 questions
  • Can you provide a summary of your resume?
  • Can you walk me through your resume?
  • Tell me about your resume
Truveta logo
Truveta

Software Engineer

Engineering · nearly a year ago

Mid Easy Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite
Interview formats
Technical Coding Behavioral System Design

so first there was like a recruiter call, then two one hour technical interviews, then a 30 min culture fit interview with an executive. every interview was like a week apart and you had to pass the previous one to move on. the recruiting team got back to you super fast, usually within 1-2 days. the two technical interviews were pretty easy and straightforward. the recruiter said they don't do leetcode style questions and it's more like "real-world" problems but the questions were actually medium leetcode questions. the recruiter also told me they don't do system design, which was weird bc the "culture fit" chat was basically a system design interview. they asked me how i'd design a system to process millions of patient data a day, what db i'd use, how i'd pre-process, etc. i felt like the process was fine until that last interview which was a total crapshoot because i didn't prep for system design at all. it's a startup so maybe they don't have a standardized process and interviewers just do whatever they want, which i felt like was the case for the final interviewer trying to put me on the spot with questions that shouldn't have been there.

Confirmed questions3 questions
  • Was the first interview okay, maybe easy, where you were asked to solve the Valid Sudoku leetcode question, and then some behavioral questions like: Describe a time when you faced a significant obstacle in meeting a key goal, Tell me about a time you were under pressure to meet a deadline, Tell me about a recent project or challenging project and what you learned from it?
  • Was the second interview straightforward and easy, where you were asked to Given a binary matrix of 0s and 1s, replace 0s with 1s if it not surrounded by 1s in all directions. Then he expanded the question to: if you have groups of zeroes, convert groups of 0s to 1s if not surrounded by 1s in all directions, and also behavioral questions like: Tell me about your recent work, What was challenging about it, and What would I do differently, What is something I want to learn or a goal I have in my next role, and What is something new you learned recently?
  • In the culture fit chat interview, which was probably the worst interview, were you asked questions like How would you design a system that could handle processing millions of patient data a day? What database would you use? What open-source tools would you use? How would you pre-process the data? How would you handle structured data and unstructured data differently? What level of (healthcare) domain knowledge do you think an engineer has to have in the this space?, and also behavioral questions like: Why Truveta? Why healthcare tech?, Tell me about a time when you had conflict with a teammate and the debates went on and on for days with no end, how did you resolve that situation?, and What does culture mean to you?
Truveta logo
Truveta

Business Development

Sales · a year ago

Mid Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Panel Background check Offer
Interview formats
Behavioral Technical Group

The remote process had several 30-minute behavioral interviews with different team members, who had really vague job titles. Then there was a panel session to check cultural fit. The recruiter was bad at communicating—I never got a clear description of the actual role or any info about who I would be talking to or why. In one round, the person who turned out to be the director of sales engineering (but listed differently) asked directly why I would even want this job, saying it didn't match my past projects, which just showed the overall confusion.

Confirmed questions2 questions
  • What makes you want this role?
  • What's your motivation for seeking this position, considering your previous projects?
Truveta logo
Truveta

Analyst

Analytics · a year ago

Entry Average Neutral experience No offer 6 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Coding Technical

The process felt way too long. You know, like 1 recruiter chat, a coding test, and then 4 interviews with team members... it just felt like a huge waste of time for everybody, especially since it didn't even end with an offer. If they'd just put everyone in a panel interview, like they usually do, it could've probably been done in like a week. Also, it seemed like nobody really knew what the role was actually about, what the day-to-day would look like, or what skills were actually needed. Everyone I spoke to was really nice though. The whole thing just felt super disorganized, and I got the vibe that the culture might be a bit intense, you know, like that whole 'we're a startup, you won't have a life outside of work' thing. What they're doing is pretty cool and I hope it works out, but I don't think I'll be applying again.

Confirmed questions2 questions
  • Is working only 40 hours a week a strict requirement for you, or would you be open to working longer hours?
  • Would you be alright with putting in more than 40 hours per week?

Truveta Interview Questions

Quoted word for word from Truveta interview reports.

How would you optimize the removal of duplicates from a sorted array to achieve O(n) time and O(1) space complexity?

Read reports

Can you build a Tic Tac Toe game using only vanilla JavaScript?

Read reports

Can you implement an NLP classifier using a huggingface dataset like IMDB?

Read reports

How would you traverse a binary matrix and flip bits based on their neighbors?

Read report

Describe how you would remove duplicates from a sorted array.

Read report

Could you explain the concept of positional encoding in the context of transformers?

Read report

How would you approach parsing JSON data embedded within a large string?

Read report

Formats, difficulty and experience

Across all 39 Truveta interview reports.

Interview formats

Technical 34.9%
Behavioral 33.7%
Coding 19.3%
System Design 4.8%
Presentation 3.6%

Interview difficulty

Easy 25.6%
Average 69.2%
Difficult 5.1%

Candidate experience

Neutral 33.3%
Positive 23.1%
Negative 43.6%

Reports by job function

Engineering 21
Analytics 5
Research 4
Sales 4
Product 2
Finance 1