First formal mentoring experience I delegated scope, ran 1:1s and watched two juniors grow into ownership. One of three parallel consulting contracts at the time.
Context
Cross-functional team running multiple full-stack features in parallel. One of three parallel consulting contracts at the time. First chance to lead juniors formally.
Mentoring
Two juniors. The bet was on autonomy: distribute scope so each owned a piece end-to-end, run weekly 1:1s for blockers and growth, pair only on the truly thorny problems.
Tech work
Full-stack feature work in Node.js + React. Optimized MongoDB queries on the heavier endpoints, raising response times noticeably without rewriting the schema.
Lessons
Delegation works when the scope is clear and the safety net (1:1s + pairing) is real. Both juniors moved from execution to ownership inside the contract the playbook I kept reusing afterward.
- Why pair only on the hard problems, not by default?Targeted pairingPairing 100% of the time stunts juniors they never get the muscle of solving alone. Targeted pairing keeps the safety net visible while letting them feel the weight of ownership.
- Why weekly 1:1s with juniors?Weekly cadenceBi-weekly is too long when blockers compound fast at junior level. Weekly catches problems before they become demoralizing patterns and gives space for growth conversations beyond ticket-pushing.
Two juniors leveled up; ownership culture took root in the team.