J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Klaviyo (Boston, MA) en mars 2019
Entretien
Initial call with sweng manager. Second step was a collaborative coding exercise onsite. You'll be in a room with 2 swdevs and a laptop with some python code in a text editor. The code sends a GET request to an API that returns the 50 most logged events. The code had issues and you're tasked with finding them. Things like it creates a db connection before conditions arise that may not necessitate it being created yet and it's inside a for loop, there are duplicate GET requests, calculates the length of the JSON payload multiple times, saved the image by UUID to disk but then looked up in the db the image via the media url (another field basically). You need to refactor a bit (basically remove unneeded code) and reorganize the order of calls for efficiency, replace print statements with logging, etc.
After this I talked with the recruiter and they initially said they wanted me to come in for an onsite. Then they changed their mind and wanted me to do a take home coding assignment. I looked at the coding assignment. You create a UI and some email/notification logic for a weather app. It's probably a 10 hour assignment. I passed just to do the time commitment and the fact they didn't seem to know what they wanted to do.
9
Autres retours d’entretien d’embauche pour un poste comme Software Engineer chez 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.
J'ai postulé en ligne. J'ai passé un entretien chez Klaviyo (Londres, Angleterre) en mars 2026
Entretien
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.
Questions d'entretien [1]
Question 1
Do a code review and fix what might be wrong or how you would fix it.