Datavant logo

Datavant Software Engineer Interview Questions
& Process

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

Based on 23 interview experiences · FREE TO READ

3.5 Rounds average
Average Typical difficulty
47.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Datavant.

Showing 3 of 23
Datavant logo
Datavant

Software Engineer

Engineering · nearly a year ago

Entry Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Technical Coding System Design Behavioral

Recruiter reached out on LinkedIn, I sent my CV and we set up a HR screening call. After that went well, I moved to the debugging stage. I got most tests passing but ran out of time on one of the last two. Surprisingly, I was invited to the next round which was the hiring manager interview and system design interview, done in one block. The hiring manager seemed distracted and not always listening. Apart from that, the experience was positive, though the interview and the standard rejection email soured it a bit.

Confirmed questions1 question
  • Could you describe a project where you made a significant impact?
Datavant logo
Datavant

Software Engineer

Engineering · nearly a year ago

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Background check
Interview formats
Coding Technical Behavioral System Design

It's a pretty standard process. It begins with a quick chat with a recruiter to gauge your fit and cover the basics. If that goes well, you move to a coding test where you have to debug some code. After that, there's a hiring manager chat. They seem pretty chill and answered my questions, though they were a bit preoccupied initially. The vibe was relaxed and open. If you make it past that, the final stage is the onsite interviews: a 1-hour coding session with progressively harder LeetCode-style problems, a 1-hour system design interview focused on the company's area, and a behavioral interview. The recruiter gives you a heads-up on what to expect. The behavioral part wasn't strictly STAR, more like a career rundown. Sadly, after all that, I got totally ghosted, even after trying to follow up. It's frustrating not getting any feedback. So, yeah, the overall experience was pretty bad because of that.

Confirmed questions1 question
  • Can you solve multiple algorithms like those found on Leetcode?
Datavant logo
Datavant

Software Engineer

Engineering · a year ago

Mid Average Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Background check Offer Onsite
Interview formats
Technical Coding System Design Behavioral

The recruiter was super nice and explained each part of the interview process clearly, both by talking and sending emails, so I knew what to expect. They used Coderpad for the coding parts. The interviewers were all really respectful and friendly. Each interview gave me about 10 minutes at the end to ask them questions about the company. First up was a Technical Screen, which lasted 45 minutes. It involved debugging some code that was messing with data from a CSV file. There were failing tests, and I had to fix the code until all tests passed. They gave me a choice: either this debugging task or a test on a third-party platform with mixed algorithmic questions. If I had chosen the latter, those algorithmic questions would have been part of my virtual onsite instead. Then, I had a Hiring Manager Screen where I chatted with the manager of the team I'd be joining. This was more about seeing if I was a good fit for the team, and I got plenty of time to ask about their work and the company. The Virtual Onsite took about 2.5 hours total, though it can be split if you don't have that much time all at once. It had three parts: an Algorithmic Questions session (1 hr) with 3-4 LeetCode-style problems where getting a working solution was usually enough, no need for the absolute optimal one. Then a Systems Design Interview (1 hr) where I had to design a healthcare system. Interestingly, we didn't use any diagramming tools; we just wrote out the design using markdown in Coderpad. Finally, a Behavioral interview (30 minutes) with another manager, focusing on standard STAR method questions.

Confirmed questions1 question
  • Could you debug this code to make the test cases pass and also do some refactoring?

Datavant Software Engineer Interview Questions

Quoted word for word from Datavant interview reports.

Implement a helper function to determine if two strings are rotations of each other.

Read reports

Create a moveIndex function that repositions an element within an array.

Read reports

Could you debug the provided pre-written code for processing CSV files?

Read report

Could you debug this code to make the test cases pass and also do some refactoring?

Read report

Can you solve multiple algorithms like those found on Leetcode?

Read report

Formats, difficulty and experience

Across all 23 Datavant interview reports.

Interview formats

Technical 30.9%
Behavioral 26.5%
Coding 25%
System Design 13.2%
Presentation 2.9%

Interview difficulty

Easy 8.7%
Average 73.9%
Difficult 17.4%

Candidate experience

Positive 47.8%
Neutral 21.7%
Negative 30.4%