The Practical Guide to Building an Apprenticeship
summary
A four-month apprenticeship is laid out end-to-end: build a plan, secure cash and managerial buy-in, hire two apprentices, and measure with a rubric. Hiring uses an anonymized workflow with hashed candidate IDs, a Ruby TDD code challenge reviewed via GitHub PRs and numerical scores (1–6), then a three-part interview. Onboarding includes a scavenger-hunt through the codebase; both apprentices are hired at the end and become productive members of their teams.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:45what do you need to get it going?
- 6:13key factors to decide
- 9:52tell us about a problem
- 10:44reviewers rated each application on
- 11:02how we did it: hiring
- 11:32how we did it: code challenge
- 15:59how we did it: final interview
- 17:29ways to improve
related talks
32mThe Practical Guide to Building an Apprenticeship
25mSoftware Craftsmanship's Missing Link: Apprenticeship
27m"Start your own engineering apprenticeship program"
02mLightning Talk: Apprenticeships
52mGreat Expectations: Power-Charging Apprenticeship Programs
01h 12mStart a Ruby Internship
27mSwitch Up: How to Switch Careers to Become a Ruby Engineer
49mApprenticeship programs