Technical Onboarding, Training, and Mentoring
summary
Claims a concrete, repeatable four-week onboarding plan that turns juniors into reliably independent engineers faster and cheaper: get a dev environment working first day dev setup, ship a small change like a ship a config file in week one, run safe weekly code labs and shadowing in week two, formalize goals and presentations in week three, then co-pilot larger projects in week four. Cites numbers and examples: attrition costs 1.5–2x salary, adding engineers can drop team productivity (LinkedIn case), and tiny teams built big products (Gmail <5 then maintained by ~400).
AI-written summary · about
chapters (36)
- 0:00Introduction
- 1:51What is onboarding
- 2:11Onboarding
- 3:13Confidence
- 4:16Why do you care
- 4:43What can go wrong
- 5:38Productivity
- 6:04Building onboarding
- 6:31Team debt
- 7:33The immediate team
- 8:20Existing engineers
- 8:32Teamwork
- 9:56Diversity
- 10:42Homophily
- 11:55Who can on board
- 12:34When can onboarding start
- 12:56How
- 13:23Handholding
- 14:00Automation
- 15:10Onboarding Categories
- 16:53Dev Environment Setup
- 17:42Shipping Code
- 18:13Journaling
- 18:39Social Events
- 19:16Week 2 Context
- 20:15Code Labs and shadowing
- 22:11Oneonones
- 22:35Goal Setting
- 24:37Presentations
- 25:05Independent
- 25:47Piloting
- 26:16Goals
- 26:36Apprenticeships
- 27:13Assessment
- 28:14Summary
- 29:09Github repository
related talks
06mEffective Onboarding: From Zero to Full Speed
27mDeveloping Devopsers
21mHow to quickly get engineers up to speed
38mQuit Frustrating Your New Developers - Tips From a Teacher
33mTapping into the power of junior developers
40mGamifying Dev Effectiveness in a Remote-first Work Environment
30mEquipping your team to support junior developers
52mSpeeding Developer Onboarding: Practical Lessons