Junior Engineers Are Features, Not Bugs
summary
Team experiments show hiring juniors forces fixes: at one org a team handling 85% of web and API traffic runs with one third bootcamp grads and builds a shared four-by-six foot poster then a tiny web app to map service protocols; problems fall into architecture, process, tooling. Concrete actions: simplify or document topology, automate deploy steps and test rollbacks, add tooling between humans and databases, and run an onboarding buddy village that breaks work into mentorable chunks. Avoid hires where velocity, mentorship, or role clarity is missing.
AI-written summary · about
chapters (12)
- 0:00Introduction and background
- 1:48Challenging hiring myths
- 2:40Benefits of junior engineers
- 3:54Simplifying architecture
- 5:20Improving deploy processes
- 6:40Investing in robust tooling
- 7:25When not to hire juniors
- 8:46Creating a supportive culture
- 10:05Onboarding strategies
- 11:28The buddy village model
- 13:52Conclusion
- 14:51Q&A session
related talks
33mJunior Engineers Are Features, Not Bugs
45mHiring Juniors
19mFrom Junior Engineer to Productive Engineer
31mFostering a Welcoming, Supporting Productive Environment for Junior Developers...
46m"Junior" Devs are the Solution to Many of Your Problems
23mSuccessfully Onboarding a Junior Engineer in Three Steps
10mCommon pitfalls of junior developers
14mJunior.next()