Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

5 stories

Likes earn the author +10 XP for the first 3 likes each day

DatavantSoftware Engineer
Reported May 2026

Datavant Software Engineer, debugging a few-hundred-line codebase

I went through a focused process centered on debugging. It began with a recruiter screen and then moved to a technical round where I had to debug an existing codebase. In the setup I saw, it was on the order of a few hundred lines and included multiple nested classes. The expectation was straightforward, step-by-step debugging: I worked through the code until the tests passed. I made good progres…

RejectedOther0
DatavantSoftware Engineer
Reported Dec 2025

Datavant Software Engineer interview with debugging and system design rounds

The process started when a recruiter reached out on LinkedIn. I sent over my CV, completed an HR screening call, and then moved into debugging. The technical work focused on debugging code and getting the tests to pass. I got most of them through, but I ran out of time while trying to fix one of the last issues. I was surprised to receive an invitation to the next round after that time squeeze. T…

RejectedHR Screen0
DatavantSoftware Engineer
Reported Dec 2025

Datavant Software Engineer interview: debugging, coding, and system design

The process started with recruiter outreach. After a quick call about logistics and my background, I was invited to a coding round that focused entirely on debugging. We worked with a pre-existing file, and I passed that round, which moved me to an interview with the hiring manager. The manager was easy-going and spent real time answering my questions. They seemed distracted at the beginning beca…

No responseTechnical Screen0
DatavantSoftware Engineer
Reported Jun 2025

Datavant Software Engineer interview disrupted by rescheduling

The part that defined my experience wasn’t the interviews. It was the coordination. I was scheduled for an HR screen and then a technical screen, but rescheduling became a mess. It took about two weeks and several different coordinators to move the interview. On the day of the rescheduled interview, I arrived early, only for the interviewer not to show up. The recruiter and coordinator didn’t res…

HR Screen0
DatavantSoftware Engineer
Reported Jan 2025

Datavant Software Engineer interview: CSV debugging and a 2.5-hour virtual onsite

A friendly recruiter started the process and explained each step during the call and in follow-up emails. The interviewers used CoderPad, and I appreciated that the process felt structured and respectful. The 45-minute technical screen focused on debugging. I worked with code that loaded and modified data from a CSV, then worked through failing test cases until they passed. After that, I had a hi…

Technical Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP