Breaking in a New Job as an SRE
summary
Quick, practical checklist: negotiate relocation, RSU volume, laptop specs and phone reimbursement up front; generate a new SSH key and encrypt it; pair with IT to script elevated access; switch tools deliberately (example move from screen to tmux), pick a personal wheelhouse (Cassandra, Postgres, Kubernetes) and use it to learn the system, shadow on-call immediately, and aim to deploy early deploy often (push real changes by week two). Write a four-week observations memo that catalogs wins, risks, and suggested owners — that memo often spurs role clarity or new teams.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:11Agenda
- 1:36Backstory
- 2:16Job Descriptions
- 3:09Before You Start
- 7:32Onboarding
- 10:23Week 1 Passwords
- 12:53Week 2 Deploy
- 15:46Writing a Doc
- 18:21Beginners Mind
- 19:32Outro
related talks
29mStarting a new job as a Staff+
13mSucceeding as the Lone SRE in a Small Team
42mHow to Hit the Ground Running as a Staff + Software Engineer at a New Company
29mZero to SRE
13mWhat To Do When SRE is Just a New Job Title?
31mStartup Security, 2nd Edition
31mConfessions of an SRE Manager
30mEquipping your team to support junior developers