Fabio, a Data Engineer, talks about why we introduced Espresso, our MLOps framework.

Claire, a Backend Engineer, outlines what CI/CD looks like at Cleo.

Cassie explains the difference between config programming - programming in an ideal world, and vibes programming - programming in reality. Guess which one we love at Cleo?

Graham, Engineering Manager here at Cleo, explains how our Chapters work in Engineering including some examples of how our chapters have worked collaboratively over the past 12 months.

Hello there! We'd love to help you learn how we run effective postmortems at Cleo. Interested? Let's get to it.

Cassie, Technical Lead, explains how we approach production incidents and outlines our on-call process for Engineering.

Collaborate. Innovate. Create. Fell explains our approach to innovation at Cleo.

Josh, Tech Lead, dives into what he looks for when reviewing pull requests at Cleo. If you're looking to write code that scales better, this is a must read.

Our Engineers share their favourite talks and memorable moments from Brighton Ruby Conference 2022.

At Cleo we think that the deliberate, conscious and careful accumulation of tech debt is a powerful tool that lets us ship code and value to our users faster. Fell explains how we manage our technical debt.

Josh, Tech Lead at Cleo, outlines our approach to migrating our primary key columns from integer to bigint.

Fell, Tech Lead at Cleo, shares his techniques for effective problem solving.