Klaviyo interview questions

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.

I applied, a recruiter got in touch with me, and we spoke as the initial interview. From there, I was brought in for a back-to-back interview format with four employees. They had serious energy and seemed really excited to not only be a part of the interview process, but also speak with me about the company. I was brought in for an interview with the CEO afterwards, which I found to be an underwhelming experience. It's incredibly admirable that Andrew is so involved in the interview process, especially as his company is experiencing an exponential growth period. However, it was easy to see that he seemed exhausted and he came across as having almost too much on his plate already to remain involved in the process. He arrived about twenty minutes late and our conversation was not very fluid. Until that point in the process, the representatives I'd spoken to were really engaging. The following day, I received a very generic email from my recruiter that I was not being brought forward in the process. I was more disappointed with how much of a contrast that was to how the process had been to that point, than actually hearing I wasn't being brought in.