Horrible legacy interview pipeline, as described by literally every single person that works there. I applied for a senior level role and met with the hiring manager and received positive feedback. 2 weeks went by and my recruiter said the role had been filled but he wanted to try to place me for an entry level position -- sure why not, 2 "technical" interviews with 2 sets of engineers, and another managerial meeting. The recruiter ensured me although I do not have extensive experience in Java or Python I will be fine. I completed both technical assessments but apparently it was not good enough, said I needed too many hints.
Overall horrible experience, I don't get what kind of entry level engineer they are looking for, I was clear about my experience upfront, if they weren't looking for someone to learn on the job I should've never ended up in the technical interview.
Interview questions [2]
Question 1
Python weather app question, basically you have to implement a simple api, read provided documentation, and write a few lines of code. Confirm with interviewer what you're doing is okay.
For the Java portion, they had me rewrite a function, basically you delete most of the function because part of it is useless, and don't forget they want you to rename things and make the code more readable
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.