I applied through a recruiter. The process took 2 weeks. I interviewed at Klaviyo
Interview
A recruiter reached out to me about this position, I applied then there was an initial call, after which I was invited to do the coding collab.
The coding collab is with two engineers and you have to find the bug in the code and fix it. I successfully completed the task and even optimized the code, I left the interview knowing I did a great job. However, I was rejected in the most romantic way; telling me how impressed they are with my skillset but they decided not to move forward. I asked for feedback on the interview and was ghosted.
Interview questions [1]
Question 1
As noted here, candidates have to sign an NDA.
But essentially you're given code of a real-world problem and you have to find the bug and fix it.
Be familiar with http servers and clients , as well as basic SQL commands.
We appreciate the time you took to interview with us, and are disappointed to hear about your experience at the end of the process. Your feedback is important to us, and we’ve shared it with our team.
Other Software Engineer Interview Reviews for Klaviyo
HR screening. Asked me some questions about software basics and sent me a code signal link. Asked about how I utilized AI in day to day work and how much design work versus coding task
ICF Codesignal, recruiter screen, and then final interview. Codesignal was easy as long as you prepped for it, there are many examples of ICFs online. Recruiter screen was normal. Final interview was not DSA related. Mostly related to the real experience of being a swe.
I applied online. I interviewed at Klaviyo (London, England) in Mar 2026
Interview
The interview process was generally well structured. I had an initial 30-minute recruiter call, followed by an assessment task and a hiring manager interview. The final stage consisted of three separate one-hour interviews covering different skill areas, with two interviewers in each session. One focused on frontend skills, while the others leaned more toward backend and broader technical competencies. Overall, the experience was positive, though having a three-hour final stage in a single day felt quite intensive.
Interview questions [1]
Question 1
Do a code review and fix what might be wrong or how you would fix it.
