Mentoring a Junior Developer

Mentoring, for me, is about shrinking the time to independent judgment — my rule is to default to questions over answers so the engineer builds their own debugging instincts instead of depending on mine. With Priya I used short daily check-ins where she brought specific blockers after attempting her own fix first, and I pointed at Spring docs or source code instead of narrating solutions. That constraint forced her to develop the habit of reading before asking, which is the single highest-leverage skill a junior engineer can build.

Her first real feature was paginated order history; when she proposed naive offset pagination I asked what happens when the orders table reaches fifty million rows rather than rejecting the design outright. She researched cursor-based pagination overnight and came back the next day with a better proposal entirely on her own. A few weeks later she caught a subtle null-check issue in one of my PRs, which I praised publicly in Slack because visible recognition from seniors is rocket fuel for junior confidence and signals to the whole team that good catches are valued regardless of seniority.

By three months she was shipping at team cadence and eventually mentored the next hire herself. The arc I highlight is deliberate scaffolding that comes off intentionally — daily check-ins shrink to weekly, reviews shift from guidance to peer, and the goal from day one is independence, not permanent reliance on my calendar. The tip I close with: the only mentoring outcome worth measuring is whether the person you mentored can eventually disagree with you and be right.