Pros: * Get to work on a really impactful project * Great teammates * Autonomy * Always learning and always interested to apply learning to new projects and infrastructure * Engineering department is good about promoting people who deserve to be

Cons: Sometimes long days. Getting better, but sometimes an expectation of being within phone's reach a lot of the time.

Pros: "Always learning" is one of Klaviyo's values, and they really mean it. The most notable example is the book stipend for any book. I also appreciate their support for side hustles and entrepreneurship generally. The people are great to work with, being professional, ambitious, and collaborative, and the company takes good care of its employees. The business fundamentals are strong, with good cash flow. Klaviyo is still relatively early and has a bright future.

Cons: Developing on top of a monolith can be slow and painful - the team is making progress in the right direction, but not fast enough IMO. It's not clear if I'll be able to keep my job when I eventually move out of Boston. I've lost a manager and many potential referrals because most roles are only available in Boston, which I think is a mistake that unnecessarily limits the talent pool.

Pros: - Leadership that is dedicated to employee retention, transparency, & education. This is the biggest pro as it leads to a great culture. - Onboarding process which is significantly better than most companies this size. - CEO who has a background in engineering (it's a pro for me anyway). - No QA dept. - Good engineering practices that are in place like code reviews, automated testing, & decent local dev setup. - Very diverse company. - Some great perks like free books, education, & fitness stipends. - The office that is pretty nice (a bit empty though, like most tech companies nowadays). - Likely to go public when market conditions are right. Not entirely sure when that will be.

Cons: - Both the back and front end code bases are monoliths, which could be a pro for some people but they're a little difficult to reason about. This is not mandated and could change or improve, as there are teams dedicated to improving the local dev experience. - Product teams run on a 2-week sprint cadence with many Scrum ceremonies in place. If you love Scrum, this will be a pro. I don't love Scrum so I'm not a fan. That said, Scrum isn't mandated from leadership so teams have some room for interpretation. - Not so much a con, but the company culture leans very liberal. If you're not used to that or are from a conservative state or area, it's a bit of a culture shock. Not a huge deal, but can be a learning curve for some. - Salary was a little on the low end of average for me. I was willing to take the hit for a better culture.