Real, anonymous reports from people who interviewed for Software Engineer at Zipline, newest first and distilled into what to expect across the loop.
After applying, I started with a short Talent Acquisition screening where I talked through my background and current work schedule. A bit later I moved into a technical session with someone on the team. The conversation again stayed anchored to my resume, and I had to answer a technical question while we dug into how I thought about the work behind the projects I’d listed.
My process dragged out over more than three months and felt like I was constantly being passed around. I ended up talking with two different hiring managers, and the work they asked me to do was substantial: a very large take-home assignment that I put real effort into and delivered a strong solution for. In a subsequent take-home review, I was told the work looked great and that it wasn’t something they saw often.
The interview process typically begins with a recruiter call, followed by a technical screen, a take-home assignment, and culminates in an onsite interview consisting of multiple rounds. Candidates noted that the overall timeline can extend significantly, sometimes lasting several months, with varying levels of communication throughout.
Most candidates completed a take-home coding challenge that varied in complexity and focus, often requiring significant effort and time. The assignment is typically reviewed in a subsequent interview, where candidates discuss their approach and solution.
The onsite interviews can be intensive, often involving multiple rounds that assess both technical and behavioral competencies. Candidates reported a mix of technical questions, system design discussions, and cultural fit evaluations, with some experiencing logistical issues during the onsite.
Candidates frequently expressed frustration with the communication throughout the process, citing delays, lack of updates, and vague feedback after interviews. Many felt that the process could be improved with clearer and more timely communication regarding their status.
Interviews emphasized practical technical knowledge relevant to the role, often moving away from traditional algorithm questions to real-world applications and system design. Candidates noted the importance of demonstrating autonomy and depth in their technical discussions.
Overall candidate experiences varied widely, with some feeling respected and engaged while others reported feeling undervalued or strung along. The inconsistency in candidate treatment and the perceived professionalism of the process significantly impacted their overall impression of the company.