Pros: The product development team is the best I've ever seen. Out of the 60-odd-person team, there's nobody whom I wouldn't want to work directly with, which is something I've never been able to say about any previous workplace. The office is beautiful, quiet, and full of natural light. It's not a developer sweatshop, and they encourage a good work-life balance for their employees. It's nice to be treated as part of a team and not as an interchangeable cog who produces finished work.

Cons: The office is in Burnaby; it's well-served by bus routes, but there are no decent restaurants or food around. Clio tries to compensate by providing free lunch once a week and subsidizing burritos and sandwiches regularly, but you still get in the habit of bringing leftovers for lunch. At least it's an incentive to cook more often. The performance review system for promotions and raises is ad-hoc and basically nonexistent. They keep saying that they're going to implement something of the sort, but they've been saying that for three years and it still hasn't happened yet.

Pros: Clio's leaders deserve lots of praise for growing the company responsibly. Unlike many other tech companies that overhired during the pandemic and then underwent multiple rounds of layoffs later, Clio did not let its employee count outpace its revenue growth. Executives frequently share with employees that Clio continues to achieve its financial goals.

Cons: Clio's frugality also has consequences. Too much work for too few workers means some parts of the product are effectively unowned, despite having a team notionally assigned to them. An injection of unplanned work can cause under-resourced teams to abandon their main project for days at a time while the injection is resolved.

Pros: Lots of opportunities for the following: * Self-development * Cross-team collaboration * Knowledge sharing from senior devs * Practicing soft skills

Cons: Some parts of the tech stack feel old, but they're too integrated to rip out. People smarter than me call it "revenue-generating code," but I'm still stuck on the term "legacy code."