Hiring junior developers remotely
summary
Argues that remote teams can hire juniors if they meet concrete conditions and then lists them: two senior mentors for 3–6 months, clear onboarding that gets a hire to ship something to production in week one, daily check-ins first week and ongoing weekly feedback, deliberate testing of written communication in interviews, good documentation that juniors can improve, matching time zones and at least some face time within six months and pair programming to accelerate learning and bonding.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:31Fears
- 2:52My story
- 4:32The general agreement
- 5:24Working remotely
- 6:41New thing removed
- 7:16Should you go ahead
- 8:02Be ready
- 11:00Burn out
- 15:48Finding an engineer
- 16:11Being there on the first day
- 19:57Validate Learning
- 21:19Shop for Dust
- 22:49Deliver Feedback
- 23:50Team Retreat
- 24:41Giving feedback
- 25:29Conclusion
related talks
22mWorking Remotely as a Junior Developer
45mHiring Juniors
40mBeing a remote developer
31mFostering a Welcoming, Supporting Productive Environment for Junior Developers...
36mSupporting Each Other: Growth for Juniors and Seniors
40mInvesting in the Future: Unlocking the Potential of Junior Developers
46m"Junior" Devs are the Solution to Many of Your Problems
28mTechnical Onboarding, Training, and Mentoring