Real, anonymous reports from people who interviewed for Software Engineer at Fetch, newest first and distilled into what to expect across the loop.
I started with a take-home where they’d share a GitHub link and the task was to build an API in the language and framework of my choice. There wasn’t much of a deadline, but the expectation was that it was usually solvable in about an hour or two, so I focused on getting a clean, complete submission rather than trying to over-engineer it.
After applying, my first real step was a take-home project that felt more scrutinized than the usual “send code and wait” style. I submitted it, and it wasn’t just about passing the main tests—there were checks that looked at small details and even automatic testing, which made me spend extra time making sure everything was consistent.
Candidates start with a take-home project that typically involves building an API or application, with expectations for production-level quality and thorough documentation. The time commitment can be significant, often requiring several days to complete.
After submitting the take-home, candidates participate in a technical review where they explain their work and decisions to engineers, focusing on understanding rather than just correctness. This stage is crucial for demonstrating comprehension of the project.
Successful candidates move into a structured interview loop that includes multiple technical rounds, such as coding, object-oriented design, and system design, often conducted in a single day. The pace is intense, with short, timed segments.
Interviews also include behavioral components, assessing candidates on communication skills and how they articulate their thought processes during technical discussions. This aspect is emphasized as much as technical ability.
Many candidates report a lack of meaningful feedback throughout the process, often receiving generic rejections without constructive criticism. This can lead to frustration and a feeling of wasted effort.
Candidates express mixed feelings about the overall experience, noting that while the process is structured, it can feel disorganized at times, particularly regarding scheduling and clarity of expectations. Some feel the difficulty of the interviews does not align with the role level.