The Practical Guide to Building an Apprenticeship
summary
A concrete how-to: design a paid, entry-level program with a written master plan, budget for living wages and manager buy-in, and run a three-to-four month apprenticeship that aims to hire afterwards. Use an anonymized GitHub code‑challenge with commit‑scrubbing script and RSpec-style TDD exercises, score applications on a 1–6 rubric for eagerness and curiosity, rotate apprentices through teams, give code review and one‑on‑ones, and measure success — CallRail hires both apprentices who become productive engineers.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:33Internship
- 3:48what do you need to get it going?
- 4:29Material
- 6:16key factors to decide
- 11:57tell us about a problem
- 12:59reviewers rated each application on
- 13:50how we did it: code challenge
- 18:48how we did it: final interview
- 20:13how we did it: behavioral chat
- 20:46ways to improve
- 26:27Apprenticeship Patterns
related talks
41mBooting Up: Hiring and Growing Boot Camp Graduates
21mIf You Can Whisk, You Can Code
35mHow to become a famous Rails Developer, Ruby Rockstar or Code Ninja
26mProductive Unemployment
33mDo the Right Thing: Practical lessons for your..
48mHacking the academic experience
21mCode for America
27mScaling Ruby Applications: Challenges, Solutions and Best Practices