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, receiving positive feedback. Two weeks passed, and my recruiter said the role had been filled but he wanted to try to place me in an entry-level position. "Sure, why not?" I thought, and proceeded to two "technical" interviews with two sets of engineers, plus another managerial meeting. The recruiter assured me that although I do not have extensive experience in Java or Python, I would be fine. I completed both technical assessments, but apparently it was not good enough; they said I needed too many hints.
Overall, a 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 never have ended up in the technical interview.
For the Python weather app question, you basically have to implement a simple API. You'll need to read the provided documentation and write a few lines of code. Confirm with the interviewer that 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. Don't forget they want you to rename things and make the code more readable.
The following metrics were computed from 15 interview experiences for the Klaviyo Software Engineer role in Boston, Massachusetts.
Klaviyo's interview process for their Software Engineer roles in Boston, Massachusetts is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Klaviyo's Software Engineer interview process in Boston, Massachusetts.