The interview process began with an initial call with the software engineering manager. The second step was a collaborative coding exercise conducted onsite. You would be in a room with two software developers and a laptop featuring Python code in a text editor. This code was designed to send a GET request to an API, which would return the 50 most logged events. The code presented issues, and your task was to identify and resolve them. These issues included creating a database connection before it was necessarily needed, performing this within a for loop, making duplicate GET requests, calculating the length of the JSON payload multiple times, saving an image to disk using its UUID, and then subsequently looking up the image in the database via its media URL (which was essentially another field). You were expected to refactor the code to remove unneeded elements and reorganize the order of calls for improved efficiency. Additionally, print statements were to be replaced with logging.
Following this, I spoke with the recruiter. Initially, they indicated a desire for an onsite interview. However, they later revised this to a take-home coding assignment. I reviewed the assignment, which involved creating a UI and implementing email/notification logic for a weather app. It was estimated to be a 10-hour commitment. I decided to proceed with the assignment due to the time commitment involved and the apparent lack of a clear direction from their end.
The following metrics were computed from 19 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.