Taro Logo

Half-baked company strategy, disappointing execution.

Principal Software Engineer
Former Employee
Worked at Canonical for 6 years
June 28, 2021
2.0
Doesn't RecommendNegative OutlookDoesn't Approve of CEO
Pros

Teammates and my manager were the saving grace for me. They were helpful, kind, and fun to work with. I couldn’t have lasted as long as I have without them.

Cons

The company keeps clinging to Juju and even usurped the term “Operator Framework” as a desperate attempt to keep it relevant in the new cloud-native landscape, nevermind the confusion it creates in the community. Systemic issues abound inside resulting in many problems such as engineering and sales not being synchronized (products sold that haven’t been QA’d in months, features and improvements critical in the field are not given the attention they deserve, etc).

Again, widespread problems like this point to a systemic failure rather than a team-specific problem.

Advice to Management

Look deep into the motivations behind your decisions and make sure you are doing it to move the industry forward, not hold it back due to sunk-cost-fallacy-driven fears.

Take a step back and examine the company’s value stream at a systemic level and really identify the things that are holding it back. You will not like what you will find, but it’s the only way to start fixing things.

Stop re-inventing wheels. Stop taking on this not-invented-here attitude and actually work with the community. Listen to the community. If the community doesn’t adopt your tool, admit that it’s not a good fit and move on. Lastly, get rid of the fear-based management style that emanates from the CEO and CTO. Whether that’s intentional or not doesn’t matter. That style is toxic to company growth.

Was this helpful?

Canonical Interview Experiences