
Fetch Backend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 42 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Fetch.
Backend Engineer
So after you pass the take-home OA, you hop on a phone screen with at least one interviewer where you'll chat about the OA and your resume. If that goes well, you'll get invited to the office for three interviews in one day. The first is a coding challenge (like LeetCode easy), the second is an object-oriented design question, and the third is a behavioral interview. Oh, and after that, there's a background check.
- What's one area where you think the OA solution could be made better?
- Can you suggest an improvement for the OA solution?
- What is one thing you'd improve in the OA solution?
Backend Engineer
First, there's a take-home assignment. Seriously, don't skip this, you need to write production-ready code to get to the next stage. It'll probably take more than 2 hours, especially if you're not familiar with the tech. Then, a technical interview where you'll go over your take-home and explain your choices. After that, a recruiter screen, just a normal call. Finally, the "Super day" which has 5 parts: a coding interview (like Leetcode easy/medium), an OOP class design interview, a system design interview, a behavioral interview, and a hiring manager interview. It's a long and tough process; one slip-up and you're out. My feedback to Fetch: maybe don't ask about the architecture of your own app during interviews to avoid bias.
- How would you go about creating a discount offer feature?
Backend Engineer
There was a take-home assessment, available online. Other reviews mentioned it, largely attempt to make Fetch but on a smaller scale they will ask you to make it production level despite the project's initial requirements. you do not have much time to do it. if you do not respond within a few days, they won't get back to you at all. then you sit through a code review. this part was jarring. it was no nonsense, no small talk, no sense of humanness. straight to the chase, no pleasantries and no leeway or introductions at all. it was very robotic only i was talking to another human, assuming
- Can you design a REST API?
- How would you deploy this API?
- What are key considerations for deploying?
Fetch Backend Engineer Interview Questions
Quoted word for word from Fetch interview reports.
“Can you build a REST API that exposes the specified endpoints?”
Read reports →“Considering a database for this task, which would be a better choice: SQL or NoSQL?”
Read reports →“Design the class architecture for a shopping cart feature using Lucid chart.”
Read reports →“If you couldn't use an in-memory store, what database would you pick?”
Read reports →“How do you log errors and pinpoint the function causing issues in production?”
Read report →“Could you implement three new rules for the project: awarding 50 points for a first-time user, 20 points for the first receipt, and 10 points for the third receipt?”
Read report →“Seriously, don't even bother applying here. They just send a rejection email saying your assignment didn't work. A child could follow my readMe to run the code, so why are they wasting everyone's time?”
Read report →“Describe, from beginning to end, a high-level design for a microservice architecture that allows users to upload a receipt via the app and get a point score, mirroring the Fetch Rewards app functionality.”
Read report →“Given an unordered list of shopping items with specific data fields, how would you score them based on a set of rules? (Similar to a LeetCode easy problem).”
Read report →Formats, difficulty and experience
Across all 42 Fetch interview reports.