“Why do you want to work at Zapier?” — how to answer it well

“I want to work at Zapier because I've spent my career doing quietly what Zapier productized. At my last company I built an internal integration layer that cut a five-hour weekly reconciliation to zero, and the reason I liked that work isn't the code — it's watching someone get an afternoon back permanently. Doing that as a product for millions of small teams is a strictly better version of the same job. The remote model is the other half: I've worked fully async for four years and I write for a living at this point. My default is a written proposal, not a meeting invite, and Zapier is one of the few companies where that's the norm rather than a quirk.”

“Two reasons. First, Zapier's users are non-technical people doing technical things, which makes support genuinely high-leverage — a good answer teaches someone a concept, not just a fix. Second, I've been a heavy Zapier user; I automated our entire lead-routing process without engineering help, and I know exactly where new users get stuck because I got stuck there. On the remote piece, I've worked async since 2021 and my strongest skill is writing something once, well, so nobody has to ask again.”

“Because the growth motion is content and the content has to be genuinely useful — Zapier's library ranks because it solves the problem on the page. That's the only kind of marketing I want to do. I've built a content program on the same principle and I can talk about which pages actually converted and why. And the fully-remote, written-first culture matches how I work: my best output has always been the doc, not the meeting.”