Doximity logo

Doximity Data Engineer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

2.4 Rounds average
Average Typical difficulty
20% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Doximity.

Showing 3 of 5
Doximity logo
Doximity

Data Engineer

Engineering · more than a year ago

Mid Easy Neutral experience No offer 2 rounds
Interview process
Recruiter call Take home
Interview formats
Technical Coding

I applied on LinkedIn and heard back from the recruiter in about 2 days to schedule a phone call. We had a 30-minute recruiter phone call where they explained the process and mentioned a potential next step: a 4-hour take-home assignment. I actually enjoyed working on the coding assignment and had a good time doing it. Unfortunately, I got rejected pretty quickly after submitting it. Even though I was disappointed, I reflected on the assignment and tried to figure out what the interviewers might have been looking for. The assignment's core task was to fetch data from source A and compare it with source B, which sounds like a typical data engineer task. However, there were a few tricky parts. First, the PM's email mentioned understanding the overlap between the sources, implying that the usefulness of the data wasn't yet confirmed. My initial thought was to just get the overlap number to the PM and worry about optimizing performance later. Second, Source B was described as a data warehouse, but I didn't have write access to it. My thinking was that for a quick comparison, this setup was fine, and for production, I'd use an ELT pattern, load Source A into the warehouse, and then compare. I wondered why we'd need to run a comparison on millions of rows in a separate container for this specific use case. Third, there was a note about a 15-minute execution time limit, requiring an explanation if it took longer. My code ran in under 4 minutes, so I figured performance wasn't an issue. In hindsight, maybe my approach wasn't what they were looking for, and I didn't think like the rest of the team. It's possible we just weren't a good fit.

Confirmed questions5 questions
  • Can you explain how you would compare data between Source A and Source B?
  • How would you approach fetching data from source A and comparing it with source B?
  • Given that Source B is a data warehouse and you lack write access, what method would you use to compare it with Source A?
Doximity logo
Doximity

Data Engineer

Engineering · more than a year ago

Lead Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Take home Onsite
Interview formats
Technical

The whole process was kind of a bummer. It started with a phone call, then a take-home test, and finally an on-site with four technical rounds. Honestly, the job posting was misleading; they were actually looking for a lead data engineer. The interviewers seemed totally unprepared and disinterested, making me wonder why I was even brought on-site. I never got any proper feedback, and after the interviews, they ghosted me. When I emailed them, they just said the role was filled. I had other offers and was just waiting around like a fool.

Confirmed questions1 question
  • Can you design a process or model for managing multiple A/B tests?
Doximity logo
Doximity

Data Engineer

Engineering

Entry Average Positive experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

I had a good interview with Doximity. The process was pretty organized and the interviewer was nice and professional. But, the questions felt a bit too standard and didn't really let me show what I can do. Still, it was useful, and I got a sense of the company culture and values.

Confirmed questions1 question
  • Could you explain what a data engineer does?

Doximity Data Engineer Interview Questions

Quoted word for word from Doximity interview reports.

Given that Source B is a data warehouse and you lack write access, what method would you use to compare it with Source A?

Read reports

How would you approach fetching data from source A and comparing it with source B?

Read reports

Can you explain how you would compare data between Source A and Source B?

Read reports

What would be your strategy for productionizing a data comparison task between two sources, considering potential performance constraints and the ELT pattern?

Read report

Can you design a process or model for managing multiple A/B tests?

Read report

How would you handle a scenario where a data comparison task must be completed within a 15-minute time frame, and what would you do if the execution time exceeded this limit?

Read report

Could you confirm your experience with the technologies outlined in the job description?

Read report

Formats, difficulty and experience

Across all 5 Doximity interview reports.

Interview formats

Technical 50%
Behavioral 25%
Coding 25%

Interview difficulty

Easy 40%
Average 60%
Difficult 0%

Candidate experience

Positive 20%
Neutral 20%
Negative 60%