Junior Gems: Hiring, Valuing, and Empowering the Next Wave of Ruby Developers
summary
Concrete claims and actionable steps not platitudes: hire for enthusiasm and potential, shortlist from bootcamps like General Assembly and Le Wagon, run a 1-hour take-home test then a one-hour collaborative code call with feedback and a follow-up extension to catch copy‑paste or LLM use, onboard with laptop day one and a designed junior program, pair remotely (tools mentioned include pairing in tup), expect a 144% more likely improvement in user understanding from diversity, and budget a critical 3–6 month ramp with regular feedback.
AI-written summary · about
chapters (11)
- 0:00Junior developers' untapped power
- 1:09Why hire juniors
- 4:15Three reasons to hire juniors
- 7:27Finding junior gems
- 10:17Hiring juniors process
- 12:03Creating a strong onboarding experience
- 13:52Challenge and support balance
- 15:36Psychological safety
- 17:26Mentoring juniors remotely
- 19:55Long-term junior strategies
- 20:18Junior turnover fear
related talks
13mGrowing Developers: Helping Junior Developers Improve & Succeed
31mFostering a Welcoming, Supporting Productive Environment for Junior Developers...
45mHiring Juniors
35m10 Lessons for Growing Junior Developers
46m"Junior" Devs are the Solution to Many of Your Problems
40mBuilding Senior Engineers
24mElevating Young Developers: Best practices for seasoned developers on onboardings
26mHow to be an Awesome Junior Developer