Onboarding

Welcome to the team!

We care a lot about getting your first few weeks right. We want you to feel confident that you've chosen the right place - to work, to feel at home quickly, and to have plenty to get excited about as we build what comes next. By the end of your first month, you should feel settled in and understand where you can make a big contribution.

We mostly work in person, and onboarding is where that pays off most. Everyone starts with a week in Cambridge (UK), including people joining remote roles, so everyone gets a similar start. If an existing commitment makes that first week tricky, we'll arrange another week within your first month.

Before your first day

Getting set up should feel frictionless, so we start as soon as your contract is signed. By the time you arrive:

  • Your laptop has been shipped to you.
  • Your Google, Slack, GitHub, and Brex accounts are set up.
  • Most of your security setup and permissions are ready.
  • If your role is remote, your travel to Cambridge for onboarding is booked.

Once the paperwork is done, we move from email to Slack for everything else.

Onboarding checklist

Your personal checklist lives in GitHub, and covers everything you need to do in your first few weeks in one place. Tick things off as you go.

Onboarding buddy

Scott LewisExecutive Assistant coordinates your setup, so your start feels cohesive, and he'll be your main point of contact for anything outside the day-to-day of your role. Do ask the rest of the team too! Everyone is happy to help.

Your week in Cambridge

Make the most of your time together. There's no fixed timetable: you'll pick up context from the more structured sessions and the casual chats over coffee and dinner. The week usually includes:

  • An introduction to our values and strategy
  • A session with your interviewers on the feedback from your interviews and SuperDay
  • A deep dive into the code you'll work on first
  • A "no stupid questions" session, where you bring everything you've wondered about since starting
  • A conversation with James HawkinsCofounder and CEO or Josh SnyderCofounder, or both, to agree what good looks like at 30, 60, and 90 days and beyond
  • Finishing the setup of your equipment and accounts
  • Time with each person on the team, so you know who does what
  • Shipping something: aim for a real change merged to main by the end of the week, however small
  • Time away from work, like dinner or exploring Cambridge as a group

If you're traveling in for the week, book and pay for it with your Brex card, out of your $5,000 monthly limit. The week should cost a lot less than that, but if you need more room, request a higher limit in Brex. Keep it sensible, and use your best judgment, as with any spending. A team favourite is Wilde Hotel but you're welcome to book wherever you feel most comfortable.

Tools we use

We use a handful of tools to organize our work and talk to each other. These are the most important ones, though it isn't a complete list.

Everyone

  • Google Workspace: Gmail, Calendar, Docs, Sheets, and Slides
  • GitHub: most of our product work and conversations about it
  • Slack: our internal workspace, plus a Slack for users
  • Brex: company cards and expenses
  • Fleet: manages company laptops

Engineering

  • AWS
  • Incident.io
  • Heroku
  • Grafana

Design

  • Figma

Ops and people

  • Deel: international payroll and contracts
  • Ashby: recruitment

How we work

With the practical bits sorted, these are the pages worth reading first:

  1. Values, on how we make decisions
  2. Priorities, on what comes first when we change the stack
  3. Feedback, on how we help each other get better
  4. Spending company money, on what you can expense

Check-ins

Your manager checks in with you every week while you're on probation, so feedback flows both ways. On top of those, there are fuller check-ins at about 30, 60, and 80 days:

  • At 30 days, you'll talk about how things are going, what's working, and anything to change.
  • At 60 days, if things are on track, you'll hear it plainly, so you're not left wondering.
  • At 80 days, you'll have a clear idea of whether you're on track. If your probation is three months, this is where you'll hear whether you'll pass at the end of it. It should never be a surprise, because the earlier check-ins will already have told you where you stand.

In research, hardware, and software optimization roles, probation lasts six months. After your 80-day check-in, your weekly check-ins carry on, with a fuller check-in each month on how you're tracking until probation ends.

Finding answers

Most of what we know is written down, here or in the repository, and looking there first is usually the quickest way to get unstuck. Slackbot will be able to answer common questions too. When it isn't written down, or you're stuck, ask. Nobody minds, and a good question often shows us what to write down next.

Slack channels

Join these on day one:

  • #generalInternal only: announcements and anything everyone should see
  • #work-opsInternal only: day-to-day work, questions, and status updates
  • #signupsInternal only: a feed of new signups to the product
  • #feedbackInternal only: what users and customers tell us
  • #alertsInternal only: automated alerts from production