I applied through a recruiter. I interviewed at Klaviyo (Dublin, Dublin) in Apr 2026
Interview
Very well structured and organised interview process. There were multiple interview rounds covering systems design, programming, systems deep dive and leadership. The whole process took a bit more than a month, approximately 2 interviews per week.
Interview questions [1]
Question 1
Walk me through a major system that you designed, implemented, and delivered in the past and let's dive into implementation details, trade-offs, etc.
I applied through a recruiter. The process took 5 weeks. I interviewed at Klaviyo (Boston, MA) in Oct 2024
Interview
Good experience. Klaviyo followed a pretty standard approach to tech interviews, handled it all smoothly.
Interviewing for this role in late 2024 included these phases:
1. initial recruiter screening
2. timed online assessment
3. discussion of past experience & technical interests with hiring managers
4. Coding collab on CoderPad
5. Panel (virtual on-site) with 4 rounds: 2 leadership, 1 systems design (on CoderPad), 1 system deep-dive (any drawing tool).
6. Offer & negotiation.
Everyone that I met was friendly, polite, welcoming, and interesting.
Interview questions [1]
Question 1
Could you describe a technical challenge where two or more people disagreed on how to solve a problem? How did you resolve the disagreement and address the challenge?
I applied through a recruiter. The process took 5 weeks. I interviewed at Klaviyo in Nov 2023
Interview
Call with the hiring manager. Thought we had a good conversation. Got a call from the recruiter saying they would have to pass because I was not able to speak to certain aspects of the code. Problem was the manager only asked vauge qualitative questions with no follow up on questions about technical implementation or details. I even asked if there was anything I could expand on or clarify and he did not seem interested in technical details, and did not take the opportunity to rephrase his question. He just assumed his bad questions would elicit in depth technical responses in a behavioral/get to know you call. If you want technical details (or really any question) ask the question in a way that tells the answerer what you are looking for. "How did that scale" is vague and does not really get to the heart of what you want to know. "Can you explain the mechanisms you used to make that system scale" gets across that you are looking for more technical details. Either way I would not want to work with a manager that expects you to be able to read his mind to figure out what question he is really asking and even less so one that will not ask clarifying questions when its obvious someone did not read his mind correctly.
Interview questions [1]
Question 1
Explain a project you worked on and How did it scale?