Taro Logo

Data Engineering Interview Experience - United States

January 1, 2022
Neutral ExperienceNo Offer

Process

I applied on LinkedIn and the recruiter responded in about 2 days to set up a phone call There was a 30-minute recruiter phone call explaining the process and a potential next step of 4 hour-long assignment

I had fun doing the code assignment and thoroughly enjoyed my time while doing it. I received rejection promptly after the submission. While disappointed, I thought about the assignment and what precisely the interviewers might be looking for. Below is my high-level feedback on the assignment.

The assignment involves fetching data from source A and comparing it with source B.

Sounds simple and very relevant to a data engineer job? Here are some issues with it - Issue 1: An email from the PM says, let's understand the overlap between the two sources. If there is meaningful overlap, we will take this further! Candidate thinking - okay, so we don't know if all of this is useful yet; let's get the overlap number to the PM and worry about performance gold plating later. Issue 2: Source B is called a data warehouse, and the candidate does not have write access to the warehouse. Candidate thinking - okay, this is making some quick comparison and send it to the PM. When we want to productionize it, we will use the ELT pattern, store source A into the warehouse, and compare it there.

Why would we want to run futuristic millions of rows comparison in a container for this use case? Issue 3: There was a reference to a 15-minute timeline to be the max for execution; if it takes longer than that, the candidate was to write an explanation. Candidate thinking - okay, so my code runs under 4 minutes, and I need not worry about performance.

In all honesty, the decision may be right. I failed to think like all the interviewers, so I am not like-minded and would not fit in.

Sorry for the rant, but I had to do this to get it out of me.

Questions

Compare data from Source A and Source B.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Doximity Data Engineering role in United States.

Success Rate

0%
Pass Rate

Doximity's interview process for their Data Engineering roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral100%
Negative0%

Candidates reported having mixed feelings for Doximity's Data Engineering interview process in United States.

Doximity Work Experiences