---
title: Onboarding
sort: 1
tags: [people-ops]
---

# Onboarding

Your first week at ZephyrCart, in checklist form. Your buddy and your manager are responsible for
unblocking you when something here is wrong.

## Day 1

- [x] Laptop arrived. (If not — ping People Ops on `#peopleops`.)
- [ ] SSO works for Google Workspace, Slack, GitHub, Linear.
- [ ] 1:1 booked with your manager.
- [ ] You've been added to your team's Slack channel and the company-wide `#announcements`.

## Day 2–3

- [ ] You've read the [team handbook](team-handbook.md) end to end. It's short.
- [ ] You've read the [code of conduct](policies/code-of-conduct.md). Signed acknowledgment goes to
      People Ops.
- [ ] You've cloned the `zephyrcart/platform` monorepo and run the local stack against a test
      tenant. Your buddy can pair on this if the bootstrap script falls over.

## Week 1

- [ ] You've shipped one small change to production. "Small" can be a typo fix; the point is to
      walk through the deploy pipeline once with someone watching.
- [ ] You've attended one all-hands and one of your team's weekly syncs.
- [ ] You've met the people listed in your `who-to-know.md` (your buddy will send this).

## When you get stuck

The single best move is to post the question in your team channel before slacking individuals
directly. We bias toward asynchronous, searchable answers — see the
[communication norms](team-handbook.md#communication) in the handbook.