Engineering 🧑 💻

We are adaptable, creative and product-focused engineers who ship working software. We have a deep understanding of our users, and are passionate about helping them.

Cleo Values

Make a Difference (Engineering)

As an engineer the most obvious way to make a difference is by writing software that delivers customer or business value and doing so at pace, while retaining the appropriate level of quality. However, writing software is only one part of everything you can do on your squad to deliver value, so don’t fixate on time in your text editor as the metric for making a difference.

Our principles “Do the simple thing”, “We are considerate coders”, “We innovate in our product, not our tech stack” express this value for engineers.

Used in

positions

Iterate with Data (Engineering)

We’re a data-driven company and as an engineer you are well placed to incorporate data into your day-to-day. We want to ship early, and ship often. We want to measure the results and then iterate forwards. We want to test things and use data to decide on the next course of action.

Our principles “Do the simple thing”, “We are considerate coders”, “Tech debt is useful” express this value for engineers.

Used in

positions

Bring Good Vibes (Engineering)

As an engineer this is measured in how you work with the rest of your squad to deliver software. Delivery is a team sport and everyone has to work together to achieve great things and make sure we’re working on the right stuff.

Our principles of “We are considerate coders” and “We help each other” express this value for engineers.

Used in

positions

Engineering

Technical Skill (Engineering)

We’ve hired you as an engineer, and an important part of your progression is tied to your technical skill. Your knowledge of the languages, frameworks, and technologies we use is part of this, but also how you use that knowledge to deliver working software and make changes to the Cleo architecture.

All our principles apply here; they are engineering principles, after all 😉

Used in

positions

Engineering Principles

We have a set of principles that shape our thinking about engineering at Cleo. They’re there to help us make decisions about the right thing to do. All our engineers, regardless of level, should hold these principles close and use them in their day-to-day work. For example: use them in discussions to break deadlocks, use them to focus designs, use them to decide which trade-offs to make.

Used in

positions

Product Engineering

This means finding the sweet-spot between technical needs, business needs, and customer needs. You do this by shipping early, testing and measuring results, and iterating based on that data. It’s a bias for action and a fail-fast mentality. Crucially, this is not an engineers-only practice; you work closely with other chapter members on your squad (e.g. Product Owners, Analysts, User Researchers, Designers, UX Writers, Data Scientists) to create features that serve our customers. Writing code isn’t always the most important thing for you to be doing to shape what your squad delivers.

Used in

positions