I applied through a recruiter.
There was an initial call with a recruiter, then a very brief call with the software lead to get an idea of my background. The recruiter was friendly and gave me a good overview of the company. They informed me that they first see what teams you'd best fit with, then do a take-home coding challenge, and then an onsite.
I got set up to do a second-round interview that I thought would be 45 minutes, but it ended up only being 15. The software lead asked a few basic questions, answered a few of mine, then said he would get in touch with the lead of the team that my background would be most suitable for. He didn't probe super thoroughly into my background and skills, but I thought this was because I had very relevant experience.
I totally was not expecting the rejection a day later. I appreciate them getting back instead of ghosting me, but I was told that there wasn't an open role for the decided team that aligned with my skills and interests. That doesn't make much sense to me because I conveyed both general and specialized experience, both of which are clear from my resume. It would've been nicer to know up front which software teams had openings. I would've liked to have had a chance to display my coding skills, since I think I could've excelled in a couple of different teams. So overall, it was a disappointing experience.
Describe your interests and what you're looking for, as well as your experience and the projects you've worked on.
The following metrics were computed from 21 interview experiences for the Zipline Software Engineer role.
Zipline's interview process for their Software Engineer roles is extremely selective, failing the vast majority of engineers.
Candidates reported having good feelings for Zipline's Software Engineer interview process.