Fetch Interview Questions
& Process

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.

It started with a recruiter chat to go over my background and see if I was a good fit for the job. Then I spoke with the hiring manager, who asked me behavioral questions and we talked about the role's challenges. After that, I got a call from the recruitment team to prep me for the panel interviews, telling me who I'd meet and what they'd cover. I then had three interviews with peers, mixing behavioral questions with discussions about the job's functions, challenges, and context. The recruitment team at Fetch was really great throughout the whole process. They were professional, respectful of my time, always got back to me quickly, and were super clear with communication. They managed to be thorough without taking too long, and everyone I talked to was smart, ready, and just nice to chat with. You can tell they care about how candidates feel and are proud to represent the company.

So, my interview experience with Fetch, which I was using as practice for FAANG interviews, began with a take-home assignment. It was a capture the flag challenge as part of the application. I got the take-home a few days after applying. The take-home itself, contrary to what I'd heard, was super easy, like an hour max if you have any real-world experience, you could probably even use AI, but be careful about hidden prompts. They want a 'production ready' app, so document well, use config, and provide a readme. You can find examples on GitHub since you submit it there. If your take-home passes, you have a review call with an engineer to discuss Fetch and your project, and you'll need to make a small modification to your project live. Then, there's a recruiter call to go over the panel interview details. The panel interview itself is a lengthy, about 5-hour, multi-round ordeal: intro with hiring manager, coding challenge, data modeling (which was super ambiguous and felt more like class design), system design (where the interviewer seemed clueless about basic concepts like DMZs and clustered databases), a behavioral interview, and a final recap with the hiring manager. It's draining and felt more like interrogation than collaborative. After that, I got ghosted by the recruiter for about a week, then finally received a rejection call. The salary discussion early on was okay, but comparable or better elsewhere with easier interviews. Fetch feels like a FAANG wannabe without the structure or pay.

So first thing was an automated take home assessment, before any calls about salary, team, etc. I know it's a red flag but I went ahead and built a fully deployed site, met all requirements and used the tech stack specified. After I submitted, I got an automated rejection email saying they can't share feedback for compliance reasons and other template stuff. I really don't like these business practices. If you're going to make people spend significant time on an interview, at least give some feedback. Feels like a lot of modern job market issues in one company. I'd avoid this one, there are better companies out there doing things the right way.