Equipping your team to support junior developers
summary
Clear, practical checklist of what to build and what actually changes: write onboarding and friction logs, create a documented career ladder anchored to senior roles, split junior hires into their own job slot, and run a pairing schedule with a designated coach role rather than only mentors. The talk names concrete tools like a personal user manual, the pyramid of challenge, and a 20–30 minute rule, and includes a failure case where overpairing prevented ownership for three months so outcomes and tradeoffs are explicit.
AI-written summary · about
chapters (19)
- 0:00Start
- 3:13The Curse of Knowledge
- 4:08Distributing Challenge
- 5:06Pyramid of Challenge
- 7:45Onboarding Friction Log
- 10:21User Manual Prompts
- 10:58Career Ladders
- 15:25Job Descriptions
- 16:49Mentorship
- 17:51Training Mentoring
- 18:10Coach Requirements
- 18:38Alternative Methods
- 19:12Encouraging Questions
- 20:52Selecting Challenging Activities
- 22:02Trust and Power
- 24:27Beyond Rubber Ducking
- 25:42Recognize Progress
- 26:10Getting Perspective on Growth
- 27:14Summary
related talks
10mCommon pitfalls of junior developers
24mElevating Young Developers: Best practices for seasoned developers on onboardings
33mActionable Tactics for Leveling Up Junior Devs
40mInvesting in the Future: Unlocking the Potential of Junior Developers
28mTechnical Onboarding, Training, and Mentoring
23mThe Junior Jump
32mHow to Be Well Onboarded as a Junior Developer Who Retrained
23mSuccessfully Onboarding a Junior Engineer in Three Steps