Signing up takes 2 minutes. Scan this QR code to send the app to your phone.
Or head to the app store:
Interviewing can be scary ☠️ And we want you to have everything you need to help you showcase your skills in the best way.
Lets face it, no one likes interviewing ☠️ Unless you get a big ol’ buzz off of talking about yourself under pressure - it's not the most exciting thing one can do!
However, here at Cleo, we are trying our best to make the interview process as easy and comfortable as possible. With a streamlined process, short and sweet interviews and as much coverage of the business as we can cram in - we feel our interview process is one of the best - both for us, and for you lovely candidates.
We want you to have everything you need to help you showcase your skills in the best way.
We’re looking for Engineers who care about fighting for the world’s financial health. If our values and our engineering principles ring true for you, we’re off to a really strong start. Technical skill is important too, and we test that, but it’s lower on our list.
We’ll get feedback to you within 1–2 working days.
We’ll cover:
Preparation:
You’ll speak with two Cleo Engineers about our mission, values, and engineering principles. Our lovely team lead the chat, but we won’t just be listening to your answers -we want to treat it like a conversation and gather more detail with follow-up questions. We’re doing our best to assess your skills and also put you at ease! Like talking to your engineering pals! 😀
We’ll also explore your technical knowledge and ways of working, your previous experience and your alignment with our engineering principles and values.
Preparation:
We have different exercises for Frontend and Backend Engineers, designed so you can show us how you’d work on day-to-day activities at Cleo.
Why a Technical Interview over a Take home Task you ask? We respect your time at Cleo - the last thing anyone wants to do after a long day's graft is work on a project for another company!
The purpose of this session is primarily to assess your technical skills in real time. We're looking to see your coding skills, how you approach problems, how you communicate and explain your decisions.
Don't worry - we don’t just watch! Our Engineers will work together with you on the exercises, so don't be shy - lean on your (potential!) colleagues!
Pair-coding preparation:
Split into two sessions via zoom.
With two Engineers, you’ll do some exercises that you’d come across at Cleo. We use this exercise to gauge what level on our engineering progression framework you’d be at.
We’ll cover:
The interview is structured as 3 exercises, all based on designing a complete system.
We’ll share the problem statement with some requirements at the start of the interview and give you time to read through and ask clarifying questions. At the end of the session, we give you the opportunity to interview us.
Preparation:
The first two parts are done in Miro. You won’t need an account but if you’ve never used it, it’s a canvas-style application. Don't worry, we won't assess your Miro skills!
For the final part, we will ask you to write code so you should have a working dev setup on your machine. What that means is:
We won’t need a database or server or any other infrastructure.
As a successful candidate, you will have shown us what it is like to collaborate with you on some of the things we do every day as engineers at Cleo. You may have finished all the exercises, but completion is not all we’re looking for. An incomplete exercise with lots of discussion about why's and trade-offs are as informative as a complete exercise with no discussion.
OR
You’ll work with 2 Cleo Frontend Engineers to implement some changes on an existing small React application. We’ll send you instructions to get your environment and repository set up ahead of the interview.
We’ll cover:
We are attempting to recreate a realistic product engineering team environment and we’ll use a team project board to guide our work. We’ll pick some feature tickets from that board and implement them together, guided by a reference UX design. You’ll need to understand the key requirements of each, so feel free to ask questions.
There’s no requirement nor expectation to get through all the cards. We’re looking to understand how you work most effectively and give you an understanding of how we work. That said, a big part of writing code at Cleo is ensuring we have tests that cover our changes, so we will be looking for you to add tests for the added features.
Preparation:
We’ll send you the repository and instructions on how to get your environment ready.
We’ll work on a React application. You'll need to these dependencies:
We also recommend you come prepared with your preferred IDE set up to your liking.
Look at that, you're on the home stretch!
We've recently adapted our final stage interview to be better for everyone involved.
We've picked out the core bits from both our previous "Meet the Team" and "Meet the Engineering Leaders" interviews and combined them into one session.
TLDR; Less time, more effective. You'll meet 1 Engineering Leader and 1 person outside of engineering at the same time, in one session.
This section is here to measure how you can work cross functionally, how well you work with others, and one of our values – Bring Good Vibes. Having tangible examples for all of these is an awesome start!
Additionally, this is your chance to talk to Cleo folks outside of the engineering space to get a different perspective of what life is like at Cleo, so make sure you have some questions ready to ask our team!
Preparation:
This stage of the process is mostly for self-reflection. It’ll give you the opportunity to look back at what you’ve learnt about Cleo throughout the process, and which parts of working at Cleo you particularly resonate with.
One of our leaders will look at how you could help move us forward in our mission to fight for the world’s financial health. They’ll also ask some behavioural questions to understand what kind of coaching and support you’d need in the role.
We’ll cover:
Preparation:
If you have any questions about any stages of the process or feedback, please send them directly to your dedicated Talent Partner at Cleo - we’re here to help! 💙
Finaly, check out our open roles!
I joined Cleo in March as a Backend Ruby Engineer, three weeks after I joined the UK went into lockdown and I was working in a fully remote team. These four approaches to working have helped me stay an active contributor to the team over the last three months of isolation.
.jpg)
How Fell Sunderland, a Tech Lead at Cleo, thinks about documentation and why it matters.
It is a truth universally acknowledged that if you develop software, things will break and go wrong. Here at Cleo, we accept that this is a part of life — but it’s important to take the time to learn and improve as a result.
