The Junior Engineer After Code
Growing engineers when agents do the implementation
Slide contents
1. The Junior Engineer After Code
Growing engineers when agents do the implementation
2. In demos, artifacts look nearly equal
Ownership becomes visible after the first version
3. Output, skill, and ownership need separate metrics
Output, learning, and ownership cannot be collapsed
4. Junior gains depend on the tool
Overall and junior estimates are not interchangeable
5. Task expertise is associated with outcomes
Job seniority does not define expertise in a new domain
6. Acceleration fades before release
A cheap local step still meets the whole system
7. A finished artifact does not guarantee skill
Task speed and acquired skill can diverge
8. Learning must be designed
It no longer emerges automatically from the task queue
9. The bottom rung is at risk
Agents may absorb safe entry-level work
10. Productive struggle became scarce
Preserve effort where causal understanding is formed
11. A strong junior retains the judgment loop
The agent executes; the human owns criteria and consequences
12. The same patch can hide different levels
The signal is in the model, falsification, and transfer
13. The correctness oracle stays human
The generator must not accept its own result alone
14. Growth through ownership
Working hypothesis: level follows the autonomy radius
15. Growth is measured by the ownership unit
Fragment → task → change → episode → component
16. PR is the midpoint, not finish
Ownership ends with an observed outcome
17. Mid-level starts with repeatable component ownership
Trade-offs, operations, and incidents are part of the job
18. Growth appears across repeated work episodes
Direction matters more than one successful project
19. Hiring changes too
Expose the work loop rather than typing speed
20. Make the full agent workflow visible
Plan, history, diff, checks, and a changed constraint
21. Hire for judgment, not typing
The same artifact can carry opposite signals
22. Hire juniors only with apprenticeship
A role without apprenticeship exports cost to seniors
23. Apprenticeship is a production system
Its owners, cadences, and measures must be explicit
24. Three owners create the learning loop
Mentor, manager, and platform are not interchangeable
25. The team needs two scoreboards
Value today and independence tomorrow
26. Code is cheaper. Judgment is not
The agent accelerates work. The team grows the engineer.
27. Full analysis and sources
The Junior Engineer After Code
The longread is linked on slide one; new materials are in Knizhny kub
Alexander Polomodov, Technical Director & Fellow, T-Technologies
@book_cube