The Junior Jump: from Student to Team Member
summary
Advice for onboarding new engineers focuses on concrete practices: set a plan with a first-30-day project that is useful but not mission-critical, pair each junior with a primary mentor who meets weekly and a quieter backup for low-pressure questions, and provide documentation plus dedicated learning time (one example is getting an hour a day to read design patterns). Examples include assigning around-to-it tasks and an owned project like automate DMCA posts to Chilling Effects, and running 30-minute meet with every engineer intros up front.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:29Welcome Gate
- 1:57Planning
- 3:07Resources
- 6:25Documentation
- 7:07Planning an Appropriate Project
- 7:32Assigning Work
- 8:25Balance
- 9:22Admin Tools
- 10:38Chilling Effects
- 11:43Mentorship
- 13:05Mentor
- 14:08Bono
- 15:00Edge
- 15:31Larry Mullen
- 16:26Recap
related talks
23mThe Junior Jump
23mSuccessfully Onboarding a Junior Engineer in Three Steps
28mTechnical Onboarding, Training, and Mentoring
40mInvesting in the Future: Unlocking the Potential of Junior Developers
24mElevating Young Developers: Best practices for seasoned developers on onboardings
32mHow to Be Well Onboarded as a Junior Developer Who Retrained
10mCommon pitfalls of junior developers
46m"Junior" Devs are the Solution to Many of Your Problems