Starting a new job as a Staff+
summary
Concrete, actionable checklist that decides whether to watch: clarify the exact hire rationale and the problem to own, build cross-org contacts and an onboarding buddy, and set measurable cadences and access (negotiate staff meetings, a 30‑minute biweekly slot). Practical tactics include seven questions to align expectations, time‑boxing like two and a half hours every Thursday afternoon, and investigative work such as draw an infrastructure diagram to surface surprises like running own servers not on AWS, fix paper‑cuts, map request paths, pair on incidents and shipping.
AI-written summary · about
chapters (17)
- 0:00Start
- 5:25IDENTIFY THE PROBLEM TO WHICH YOUR HIRING IS THE INTENDED SOLUTION
- 6:14BUILD ORGANIZATIONAL CONTEXT
- 8:59BUILD TEAM CONTEXT
- 9:19BUILD YOUR PEER NETWORK
- 11:48SETTING EXPECTATIONS
- 13:56MEETING & INFORMATION ACCESS
- 15:12COMMUNICATION CADENCE
- 15:46NETWORK TO FILL IN CONTEXT
- 17:29ACQUISITION MEANS THE DEATH OF INNOVATION
- 17:52CENTRALIZED ARCHITECTURE APPROVAL BREEDS UNHEALTHY POLITICS
- 18:43WORK BACKWARDS FROM GOALS
- 19:06VALIDATE YOUR LEARNING
- 21:23CAPTURE KNOWLEDGE
- 21:53RE-EXAMINE ASSUMPTIONS
- 22:42TACKLE PAPER CUTS
- 24:56DON'T BRIDGE MISMATCHED VALUES WITH OVERWORK
related talks
42mHow to Hit the Ground Running as a Staff + Software Engineer at a New Company
20mBreaking in a New Job as an SRE
36mHow To Onboard New Hires Into Happy and Productive Employees
39mOnboard yourself: How to get set-up for success in a new role
30mEquipping your team to support junior developers
21mHow to quickly get engineers up to speed
06mEffective Onboarding: From Zero to Full Speed
22mHumanising Onboarding: Helping New Team Members Find their Feet in the World...