First, I completed a moderately difficult email architecture project that was to be turned in. That was approved, and I was then moved to a phone screen and finally an in-person interview. The in-person interview crossed many departments. First, I met with HR. Then, I was brought to lunch by a few engineers. Afterwards, I met with the VP of Engineering and a few more engineers.

HR asked clarifying questions about Klaviyo, how career development works, and why I would want to work there.

The lunch interview was definitely an engineering culture interview, which went nicely.

The interview with the VP of Engineering was reasonably tough, asking about my current company's API architecture. I did my best to explain but admittedly could not describe it to a finite technical degree.

Finally, the last interview was a collaborative coding exercise where I was to refactor a snippet of Python code to be more efficient and easier to read while explaining my thinking to the other engineers.

Throughout the interview, I could tell there was a deep focus on general DevOps knowledge of deploy processes and large-scale data processing.

What is the most challenging project you worked on?

Describe a time that you failed as an engineer, how did you fix it, and then learn from it.

Given the collaborative Python exercise, how would you manage this as a server? What tools would you use as the sole owner of this new software? How do you handle server errors, and how will you determine when the server is down?