
November 12th: Sh*t You Didn't Learn In School
How to not get screwed this holiday season 👀
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.
Interviewing can be scary ☠️ And we want you to have everything you need to help you showcase your skills in the best way.
Here’s an overview of our interview process for Engineers, as well as some tips 💡
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. We’ll also explore your technical knowledge and ways of working, your previous experience and where you want to go in your career.
We’ll cover:
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.
This will show us your coding skills, how you approach problems, how you communicate and explain your decisions. We don’t just watch (awkward), our Engineers will work together with you on the exercises.
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.
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.
You’ll meet two Cleo people outside of Engineering. They’ll think about how you could contribute to Cleo’s culture, focusing in particular on behaviours which closely match our core values.
We’ll cover:
Preparation:
Congratulations on making it to the final stage! You’ll meet an Engineering Manager or two. They’ll 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! 💙
Also, check out our open roles.
How to not get screwed this holiday season 👀
You know what sucks? When you really want to buy that new jacket but your bank balance tells you it’s a bad idea. You know what sucks even more? When rent is around the corner and you’re not sure if your bank balance is even going to cut it this time around. Wouldn’t it be nice if there was just like, infinite money in there? We’d have to rework the whole capitalist society thing and our big unfortunately misplaced sense of purpose, but it’d probably be great in the end. The point is, life is better when you’re not worried about your bank balance. But how do you get your sh*t together enough to literally not have to think about it? With Cleo. Here’s how to keep your bills in check and maybe even manage a treat-yourself budget too. Tips incoming.
Manifesting our dream house on Sunset Boulevard while we cry broke people tears