Zipline Software Engineer interview: Rust or C++20 take-home and automation panel

Zipline·Software Engineer·Reported Apr 2024
Take-home ProjectMedium

I entered the process through LinkedIn, then had a short recruiter call followed by a brief conversation with the hiring manager about my past experience. Next came a take-home assignment in either Rust or C++20, which took me a little over two hours. My impression was that they cared more about whether the solution worked than about polish such as code quality or tests.

After that, I had a roughly hour-long conversation with an engineer on the automation team. We reviewed my solution and my design decisions, and they asked good follow-up questions. I then entered a larger panel that included two system design interviews, a behavioral conversation in an "outdoor walk" style, and an interview focused on bus and sensor communication. We discussed how signals from sensors travel over serial connections to more centralized computers.

The panel felt oddly unorganized. I had trouble showing the design flow they wanted, and some of the questions made me feel that the interviewers weren’t fully aligned with industry flight-safety standards.

I was told they’d deliberate and get back to me the following week, but I received a call the next morning saying I didn’t have enough autonomy. The feedback didn’t seem to connect with what the panel had emphasized, especially given how quickly the decision came.

Location: San Francisco, CA. Overall feedback: Negative. Offer status: No offer.

Published

Curated and edited by PracHub

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
Zipline
Role
Software Engineer
Rounds
Take-home Project
Difficulty
Medium
Date
Reported Apr 2024

Real Zipline interview experiences

First-hand reports from Zipline candidates — the rounds, the questions they were asked, and how it went.

All 9 Zipline interview experiences