Fetch Frontend Engineer Interview Questions
& Process

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.

I had a really bad experience with the recruiting team; they seemed to waste my time. I completed a take-home project where I had to fetch dog information. I put way more time into it than the instructions suggested. It took nearly two months for the recruiter to finally email me back after I submitted it. I tried to follow up several times, but I never got any reply. Eventually, I talked to two frontend engineers about the project. The conversation went well, and they were friendly. I thought I did great and was ready for the next step. But then the Fetch recruiting team went silent again for another two weeks, ignoring my follow-up emails. In the end, I just got a generic rejection email. The whole hiring process felt super disorganized and disrespectful. I never even talked to a recruiter about the job, the team, the hiring process, salary, or expectations. While the engineers could answer some general questions, I had no real info about the role or the team, which is usually what a recruiter provides.

So first, I got this take-home coding project where I had to build a web app using a basic API. After that, I had a Zoom interview with an engineer. I thought it would be mostly about the take-home, but we only spent a little time on it. Then, they asked me a bunch of frontend questions to see what I knew and talked about my experience. They also gave me a straightforward coding problem. Later, I went for an on-site interview with two more sessions. The first one was similar, focusing on my knowledge of frontend development, web app development, and best practices. The second one felt more like we just worked on a coding problem together. Everyone, engineers and recruiters, was really nice and helpful throughout the whole thing.