I can't say that I am a fan of the interview process. A panel of nine people with a time investment of 10+ hours, and the decision-making process isn't clear as to how many need to say 'yes' and how many 'no'.

The process included:

• A 30-minute chat with the recruiter
• 1 hour with the Hiring Manager
• 1 hour with a technical coding test (where they expected me to write CSS as an Engineering Manager)
• Then 8 hours of further interviews.

After this, they may want you to do more interviews (as was the case with me). I was reluctant to continue, but they said that all feedback had been positive from the rest of the panel, so I figured I would continue (also, it was a perfect fitting role for me, in my opinion).

• A 30-minute follow-up with product.
• 30 minutes with an executive.

I tried to better understand how I would be working with them, but this person did not understand engineering, nor could they articulate how they would be relevant to the job (which, up until this point, had been a very focused process on the job itself).

In the end, I (thankfully) got the result that it was a 'no' (by this point, I was exhausted and just wanted them to make a decision).

As to the reason why, the recruiter still did not know; they needed to sync with the team, even though the notes must have been in front of them. This made me chuckle, but I think it sums up the Klaviyo interview experience quite well.

Nothing crazy, but expect to know CSS. They expect engineering managers to be hand-rolling styling changes.