Our culture
Onboarding
Your first thirty days are planned before you arrive, and someone is accountable for them.
A new engineer waiting on an access request is the most common way a start goes badly, so accounts, hardware and permissions are raised against your start date rather than on it. The rest of the plan is below.
01 — The first thirty days
Week by week.
Before you start
Hardware shipped, accounts created, access approved and your first-week schedule sent. Your mentor and your manager are both named in it.
Orientation
The company, the process standard, security and the tools. Then straight onto the programme you were hired for — reading the code, sitting in the reviews.
First contribution
A scoped piece of real work, reviewed by your mentor. Small enough to finish, real enough to ship.
Thirty-day review
A two-way conversation: what you need, what is unclear, and what the next ninety days look like.
Joining remotely? The plan is identical — the only difference is that the hardware arrives before you do rather than waiting on a desk.
Ready when you are
See what is open.
Roles across engineering, AI, data and delivery — in ten countries and fully remote. The AI interview starts the moment you pick one.