The interview process included multiple rounds:
I only made it through the first two rounds.
The tech screen was okay. My recruiter was five minutes late, and the interaction felt rushed and impersonal. However, they moved me to the next round immediately.
For the second round, I was told to come prepared with technical examples from prior projects. My interviewer asked me to describe a difficult project I had worked on, and we used that one example for the rest of the questions. Looking back, I wish I had brought up more than one example, as I felt that single project didn't highlight all of my experience. Don't be afraid to bring up other experiences or examples you have.
I was pretty disappointed with how my recruiter handled delivering the rejection. They included the wrong name of the hiring manager, so I had to message back to confirm the denial was intended for me. They apologized for the incorrect name but confirmed that the rejection did reflect my candidacy status. I asked for some feedback, and I've since been ghosted, so I have no clue why I was rejected or what I need to improve. This was not helpful.
Describe a difficult project you've worked on and what the outcome was.
Describe the tech stack.
Describe a project you've worked on and the challenges you had to overcome.
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.