10 Lessons for Growing Junior Developers
summary
A concrete apprenticeship case study shows a hiring and training pipeline that actually produces developers: selection criteria favor persistence and teachability, pairing and weekly one‑on‑ones become mandatory, and project days plus structure speed learning. Metrics are specific: 46 trained since 2014 with 88% still in software and retention jumping from 60% to 95% after process changes. Expect practical methods, real numbers, examples of what was built and how outcomes improved.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:46Thank you
- 1:18Erikas background
- 3:33Senior vs Junior Developers
- 4:13Big Points
- 4:57Look for Potential
- 9:44The Right Fit
- 11:23Expectations
- 14:16Pairing
- 17:24Structure
- 19:13Positive Feedback
- 21:18Growth Feedback
- 25:18OneonOne
- 27:15Addressing Problems
- 32:21QA Session
related talks
13mGrowing Developers: Helping Junior Developers Improve & Succeed
45mHiring Juniors
32mHow to Be Well Onboarded as a Junior Developer Who Retrained
31mFostering a Welcoming, Supporting Productive Environment for Junior Developers...
10mCommon pitfalls of junior developers
22mJunior Gems: Hiring, Valuing, and Empowering the Next Wave of Ruby Developers
24mElevating Young Developers: Best practices for seasoned developers on onboardings
14mJunior.next()