How to Be Well Onboarded as a Junior Developer Who Retrained
summary
A concrete onboarding plan for junior developers who switched careers: provide a documented sandbox with step-by-step technical readings (architecture, tests, JS for those from a PHP background), run a two-week technical ramp before production, assign a dedicated mentor with blocked calendar time for daily 1.5–2h pair-programming, and use a six-week “rapport d’étonnement” feedback loop. The talk gives example metrics (5-month bootcamp hire into a ~60-person company, two weeks to first commit, six weeks to formal feedback) and argues these practices reduce confusion, improve retention, and speed newcomers to productivity.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:07DANS QUELLES SITUATIONS?
- 5:21AVEC QUELS ENJEUX ?
- 14:21TRONC COMMUN
- 18:33OPTION RECONVERSION
- 26:06RAPPEL DE NOS OBJECTIFS
related talks
35mHow to Be Well Onboarded as a Junior Developer...?
24mElevating Young Developers: Best practices for seasoned developers on onboardings
28mTechnical Onboarding, Training, and Mentoring
10mCommon pitfalls of junior developers
46m"Junior" Devs are the Solution to Many of Your Problems
35m10 Lessons for Growing Junior Developers
23mSuccessfully Onboarding a Junior Engineer in Three Steps
17mThe Junior Jump: from Student to Team Member