Fetch Software Engineer Interview Questions
& Process

The interview process begins with a really tough take-home test where you're expected to build a full application with docs. If you pass that, you move to a first technical interview where they discuss your project and might ask for code changes. Then, there's a whole day of on-site interviews: first with the hiring manager, then a coding interview, a frontend system design, a chat with product design, and another meeting with the hiring manager. The take-home was brutal, took me over a week, and just doing the basics isn't enough, you gotta go all out. System design was rough, the interviewers seemed unprepared and asked really open questions. If your answers aren't what they expect, you could get rejected even if you're good. One interviewer was even Googling questions mid-interview. The hiring manager wasn't very engaging either, barely asked anything and expected me to lead the whole conversation. Apply if you have tons of free time for a take-home before any human contact.

I applied and got an automatic coding challenge which seemed to be sent to everyone. The task was to build a react app, hit a couple of api endpoints and display the info. They said not to spend too much time on it, but the tasks they asked for would take at least 4 hours. They also recommended not doing the bare minimum. I spent extra time styling, making it responsive, and adding error handling. I was rejected for things they didn't ask for, like writing it in Typescript, adding unit tests, and responsive design (they critiqued one small part I missed even though I thought it was extra credit). They also didn't like the UI design I chose, which is funny since it's not a design job. Pretty horrible experience, I'd stay away unless you have tons of experience and can do all these things in 2-3 hours for less than average pay.

We recruited from campus for this internship. It kicked off with a take-home coding test. Then, there was a technical phone screen where we talked about the take-home and possible next steps. The final stage was an onsite interview at campus with three separate interviews. The questions varied by role, but for backend or data positions, you could expect an easy to medium LeetCode problem, an SQL challenge, and a surprise task to see how quickly you could pick up new technologies and tools.