Fetch logo

Fetch Data Engineer Interview Questions
& Process

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

Based on 11 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
27.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Fetch.

Showing 3 of 11
Fetch logo
Fetch

Analytics Engineer

Analytics · nearly a year ago

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

So, first there was a take home assignment. Then I had 2 interviews: one with HR where we mainly talked about my resume and why I wanted this job, and another where they presented an open ended problem. I had to guess why a situation was happening based on minimal data and then write SQL queries to explore it. Finally, there was a full day loop which included meeting the hiring manager, discussing architecture, and doing some SQL and Python coding, and another chat with the hiring manager.

Confirmed questions1 question
  • How would you design an architecture for a fictional app similar to ours?
Fetch logo
Fetch

Analytics Engineer

Analytics · a year ago

Senior Difficult Negative experience No offer 2 rounds
Interview process
Take home Recruiter call
Interview formats
Technical Coding

The interview process was awful. I was given a take-home assignment that would have taken about 30 hours to complete. It involved creating a Git repo, unpacking messy JSON data, exploring the data, building a data model, writing basic SQL queries, creating a presentation, adding documentation to the Git repo, and then writing a Slack message to a non-technical person explaining the analysis. This take-home was ridiculous. The worst part is that I messaged the recruiter to ask clarifying questions about the role before starting the assignment (like salary range, hybrid/remote status), but I never heard back. I don't think Fetch is serious about filling this role; it seems like some recruiters are just getting paid to conduct interviews and send out take-homes, and based on other reviews, the interviewers don't seem serious about hiring anyone.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Fetch logo
Fetch

Analytics Engineer

Analytics · more than a year ago

Entry Average Negative experience No offer 1 round
Interview process
Take home Technical screen
Interview formats
Technical

I applied and they immediately sent a take home assessment due the next day. It was a pretty involved assessment. After I finished it, they immediately asked for interview availability. I mention the immediacy because there was no time for a human to review my application or the assessment. The interview didn't go well, which is on me. But I was never given a chance to review my assessment, which took a lot of time. If you're going to ask an applicant to spend a lot of time on an assessment, the least you could do is offer a chance to review it with them.

Confirmed questions1 question
  • Can you describe your previous involvement in a data engineering project?

Fetch Data Engineer Interview Questions

Quoted word for word from Fetch interview reports.

Could you write an ETL application that connects AWS SQS to a PostgreSQL database?

Read reports

Can you write SQL queries given some business questions and an ERD?

Read reports

How would you design an architecture for a fictional app similar to ours?

Read report

Can you walk me through the code you wrote for the take-home assessment?

Read report

Can you describe your previous involvement in a data engineering project?

Read report

Formats, difficulty and experience

Across all 11 Fetch interview reports.

Interview formats

Technical 52.4%
Coding 28.6%
Behavioral 14.3%
System Design 4.8%

Interview difficulty

Easy 9.1%
Average 72.7%
Difficult 18.2%

Candidate experience

Negative 54.5%
Positive 27.3%
Neutral 18.2%