Received an email for a phone screen less than a week after applying.
After screening, they sent a link for a CodeSignal technical assessment, which wasn't too bad. It consisted of three parts, each iterating over the previous implementation. I really enjoyed it as it was more practical than the usual LeetCode-style problems.
A day or two later, there was a system design interview. I felt like I over-prepared, but essentially, I was explaining in detail a feature I implemented in my previous role.
The final step was a three-hour final round interview. The first part was a simple Weather App assignment with an obscure library to test how you problem-solve and look up documentation. I definitely did not perform as well as I could have here, as I was stuck on the obscure library. The second part dealt with an existing Python/SQL script, which we had to review, optimize, and spot any mistakes or security concerns. Finally, it ended with an interview with the hiring manager, which I can't recall at the moment.
Overall, it was a positive experience. The only reason I put neutral is because I don't believe they were upfront about hybrid; it sounded like they will transition to full on-site soon.
Be prepared to go through documentation on an obscure library live (e.g., PonyORM).
Be able to troubleshoot and modify/optimize code.
Explain a difficult project, system design-wise.
The following metrics were computed from 2 interview experiences for the Klaviyo Software Engineer II role in Boston, Massachusetts.
Klaviyo's interview process for their Software Engineer II roles in Boston, Massachusetts is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Klaviyo's Software Engineer II interview process in Boston, Massachusetts.