Klaviyo reviews

I had high expectations coming into Klaviyo, but the reality fell far short. The biggest issue is leadership. There is a clear lack of the experience and judgment needed to effectively lead a modern engineering organization. Decision-making often feels reactive rather than strategic, and there’s little evidence of long-term technical vision. Instead of empowering experienced professionals, leadership tends to micromanage as if they’re overseeing a group of junior interns rather than seasoned engineers. From a technical standpoint, the quality of the codebase and product is concerning. Much of the system feels like a patchwork of rushed solutions—often reminiscent of a half-baked college project rather than a mature, production-grade platform. Core areas suffer from poor system design, weak data models, and significant technical debt that is consistently ignored rather than addressed. Project expectations are frequently unrealistic. Leadership pushes aggressive timelines without accounting for the underlying technical challenges or existing debt. There’s little regard for sustainable development practices, which leads to constant firefighting instead of building robust, scalable systems. The result is a frustrating environment where engineers spend more time working around problems than solving them properly. For a company at this stage, the gap between where things are and where they should be is hard to overlook.