Don't Panic: Mentoring Engineers

Mentoring is the practice of helping an engineer build judgment through real work, guided practice, feedback, and reflection. It is not a ceremonial transfer of wisdom from a person with more calendar years to one with fewer. Calendars are poor debuggers.

The useful unit is a working agreement: one capability, evidence that shows progress, a cadence, and boundaries. A goal such as becoming better at backend engineering is a fog bank with good intentions. A goal such as explaining the rollback plan for a service change gives both people something they can inspect.

Then comes the loop. Frame the capability. Ask what the engineer knows and has tried. Model reasoning when an example earns its keep. Let the engineer practice. Observe the work and the reasoning, give feedback, ask for reflection, and adjust the next attempt. The engineer does the thinking and the work, which is inconvenient only if the point was to collect grateful listeners.

The surprise is that less help can be more useful help. A question is appropriate when there is enough context to reason. A hint fits one missing connection. A demonstration earns its place when a convention or tool is unfamiliar. Direct instruction is for material risk to users, data, security, or production. After that, return ownership. A correct answer delivered too early can move today’s task while leaving tomorrow’s task exactly where it was.

Use an artifact such as a pull request, design note, incident log, or runbook. It makes a decision visible. Feedback can then name an observation, its effect, the reason it matters, and a next action. Keep comments about the work, not the person. Separate required corrections from optional learning. Vague praise is pleasant weather. Specific reinforcement tells someone what to repeat.

Safety matters because uncertainty must be visible before it can be worked on. Questions, hypotheses, and admitted gaps need room to exist without embarrassment. This does not retire engineering standards. It gives them better evidence.

Read the Intro for the full model and role boundaries. Use Slides to see the loop and support ladder at a glance. Keep the Cheatsheet nearby during a review. Field Notes covers the costs that hide inside helpful-looking mentoring. Then try one bounded change with a working agreement and see whether the next first draft needs less of you.

Don't Panic: Mentoring Engineers

Relevant careers