Real, anonymous reports from people who interviewed for Software Engineer at Zapier, newest first and distilled into what to expect across the loop.
After a recruiter chat, I moved through a hiring manager conversation and then into a take-home that was framed as “time boxed” for 2.5 hours. The rest of the loop leaned into technical discussions, including system design, and I also ran into later rounds described as a bar raiser style interview with senior leadership plus a director-level conversation. What surprised me was how much the take-home felt less like realistic development and more like a fast output test—there wasn’t much room to think deeply about maintainability or how the code would be reviewed months later. It felt like the expectation was to produce quickly, and even the “2.5 hours” constraint was hard to take at face value.
My path started with an initial one-hour interview with a hiring manager. After that, I was given a 2.5-hour, time-limited technical project to build an API for a provided project brief. It was backend-only, and the focus was on creating a reliable usage tracking system.
The interview process typically begins with a recruiter screen, followed by a hiring manager conversation, a take-home assignment, and then technical discussions that include system design and leadership interviews. Candidates noted that the process is structured but can vary in pacing and clarity, sometimes leading to confusion about next steps.
Candidates are often given a time-limited take-home coding assignment, usually around 2-4 hours, focusing on building a specific project. Feedback on these assignments can be vague, and the expectation is often on speed and deliverables rather than thoroughness or maintainability.
Following the take-home assignment, candidates engage in a technical review with engineers that assesses their work and thought process. This round can feel disconnected from the take-home, with some candidates reporting a lack of constructive feedback or engagement during the discussion.
Interviews often include behavioral questions aimed at assessing cultural fit and collaboration skills, especially in later rounds with senior leadership. Candidates appreciated the friendly atmosphere but noted that the focus could shift unexpectedly from technical skills to broader team dynamics.
Candidates reported mixed experiences with communication throughout the process, with some feeling well-informed while others experienced delays and vague feedback. This inconsistency can lead to frustration and uncertainty about their standing in the process.
While many candidates felt the interview experience was positive, several did not receive offers, often without clear reasons. The offer process can also involve unexpected changes to role details, leading to dissatisfaction even after a smooth interview experience.