The Good:
The Bad:
The Ugly:
And then there’s this…
One of the recent reviews from a former CTO reads like it was written under duress. It’s full of praise for leadership that doesn’t align with what most employees experience daily. Describing the CEO as “demanding but well-respected” feels like an attempt to sugarcoat what is widely seen as toxic behaviour. The tone of that review, especially when compared to others, makes you wonder if it was written more out of obligation than genuine sentiment—it doesn’t reflect the reality many employees face. What’s even stranger is that this review seems to shoot itself in the foot regarding the CTO’s own credibility.
Publicly admitting that they left because they lacked the experience needed for the role raises questions about their suitability as a leader—especially in a review that can easily be tied back to them. It feels like an unnecessary self-own in an attempt to deflect from deeper issues within leadership at Buildkite.
It’s time for a clean slate at the top. Bring in leaders who know how to build trust, respect their teams, and create an environment where people can actually do their jobs. Stop ignoring feedback (and Glassdoor reviews) and start taking real action to address the issues that have been raised repeatedly in reviews and conversations.
Until that happens, Buildkite will continue its downward spiral, and it’ll be no one’s fault but your own.
Initial interview with hiring manager, then with Engineering manager, then a live coding exercise where I was given some info in advance but some on the spot and had to code while sharing screen, then interview with CTO at the end.
Usual recruiter screen, and then * Behavioural interview checking how you work. Are you a team player, do you think about customers, etc? * A take home coding challenge which is actually relevant to the job * A follow-up interview to discuss the cod
I only had an initial phone screen due to some timing complications, but the communication and follow-up afterwards to resolve the issues and make it right and find another suitable role were a class act.
Initial interview with hiring manager, then with Engineering manager, then a live coding exercise where I was given some info in advance but some on the spot and had to code while sharing screen, then interview with CTO at the end.
Usual recruiter screen, and then * Behavioural interview checking how you work. Are you a team player, do you think about customers, etc? * A take home coding challenge which is actually relevant to the job * A follow-up interview to discuss the cod
I only had an initial phone screen due to some timing complications, but the communication and follow-up afterwards to resolve the issues and make it right and find another suitable role were a class act.