iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Technical mentoring works best when it develops both engineering judgment and the person applying it. Daniel Llach’s approach pairs technical guidance with trust, autonomy, meaningful opportunities, and attention to the mentee’s circumstances. It is practical advice from one mentor—not a proven formula—but it offers a useful way to make mentoring more than a stream of code reviews.
Why mentoring needs to look beyond code
Code reviews and architecture discussions matter, but they show only part of how an engineer is growing. A mentee may also need room to build confidence, communicate more comfortably, make decisions, or take on responsibility. Llach’s central idea is to treat those needs as part of technical development, not as distractions from it.
That does not mean a mentor should pry into someone’s private life or assume every personal concern belongs in a work conversation. It means making space for the mentee to raise what matters to them, listening without judgment, and adapting support to the person rather than applying the same script to everyone.
Recommended Free Tools
Set a rhythm that can change
Llach suggests beginning with weekly 30-minute meetings, then moving to every other week as the mentee becomes more independent, and eventually having monthly deeper conversations while staying available between meetings. These are his suggested starting points, not a universally validated schedule.
#1 Best Overall
Let the mentee’s priorities shape the conversation. An open check-in can surface a technical obstacle, an upcoming challenge, a confidence concern, or something outside work that affects how they are approaching it. Technical topics still belong; the point is to make the session useful to the mentee rather than filling every meeting with a fixed agenda.
Shift from giving answers to building judgment
Direct answers can help when someone is blocked, but a mentor’s reasoning is often more valuable than the answer alone. Llach recommends initially explaining how he approaches a decision, then using questions to help the mentee work through similar problems independently.
- Make the reasoning visible: Explain what information you consider, what trade-offs matter, and why one option seems appropriate.
- Invite the mentee’s analysis: Ask what they have considered, what they would choose, and what risks they see.
- Reduce prompting over time: As their judgment develops, leave more of the problem-solving to them and remain available for discussion.
The aim is not to turn every exchange into a quiz. Offer a clear answer when one is needed; use questions when they help transfer the decision-making process.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #2
- Staff Engineer: Leadership beyond the management track
- Will Larson
- ABIS BOOK
Transfer responsibility gradually
Independence is easier to build when responsibility grows in manageable steps. Llach describes a progression for technical discussions: first attend alongside the mentee, then let them lead while you provide backup, and later join only when they ask.
- Start together: Attend a meeting with the mentee and explain your role and any context they may need.
- Hand over the lead: Let the mentee guide the discussion while you listen and step in if needed.
- Be available on request: Give the mentee room to represent their work independently, with a clear way to ask for support.
Move at a pace suited to the person and the stakes. A high-risk decision may call for closer involvement than a routine discussion; graduated independence is not the same as withdrawing support.
Use stretch opportunities with a safety net
Growth often requires work that is a little beyond someone’s current comfort zone. Llach recommends beginning with lower-risk tasks and increasing complexity or visibility over time, while making sure the mentee knows support is available.
Rank #3
- Invite the mentee to present their work or contribute to an architecture discussion.
- Increase the scope of assignments as they gain experience.
- Agree in advance how they can get help if an unfamiliar challenge becomes difficult.
- Recognize their contribution publicly when appropriate.
A stretch assignment should provide a real chance to learn, not simply transfer risk to the mentee. The mentor’s backup and the task’s stakes should match the challenge.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Notice growth in more than technical output
Llach suggests looking for signs such as taking initiative, proposing solutions, advising colleagues, communicating with more confidence, accepting challenges, and making better work-life balance decisions. These are observations he recommends, not a validated measurement system or a scorecard.
Use them to guide a conversation, not to label someone. Ask what the mentee feels has changed, where they still want support, and what opportunity would help them take a next step. Their own view of progress belongs alongside what you observe.
Rank #4
- The Five Dysfunctions of a Team
- English
- hardcover
- First Edition
- gelatine plate paper
Respect the life around the work
Personal milestones, time off, and responsibilities outside work can shape what support is useful. Llach advises supporting time-off requests and personal milestones, and judging contribution by the value delivered rather than hours spent. In practice, that means discussing expectations clearly, respecting boundaries, and avoiding the assumption that longer hours demonstrate stronger performance.
Care should not become pressure to disclose. A mentee can be supported without explaining every personal detail; follow their lead and focus on what they want to discuss or what adjustment they are asking for.
Free tools Windows power users keep installed
One-click scans. No signup required.
What Llach’s example can—and cannot—show
Llach recounts recommending a technically strong candidate whose English was still developing, despite a manager’s hesitation. He says he supported her during English-language calls; over the following two years, she became a trusted contributor and was promoted to technical lead. He later describes her sharing plans for a month-long trip to Japan and the experience of seeing autumn leaves for the first time.
Best Value
- we like to ship out right away
The anecdote illustrates his view that a mentor should see a person’s potential and life beyond immediate technical performance. It is one account from the author; it does not independently establish that his mentoring caused the reported career outcome.
Turn the idea into a mentoring practice
A practical starting point is to agree on what the mentee wants from the relationship, set an initial check-in rhythm, and revisit both as their needs change. Use conversations to develop judgment, create supported opportunities to lead, and ask what kind of help is useful now. Keep personal context welcome but voluntary, and treat signs of growth as prompts for discussion rather than proof of success.
Llach’s argument is ultimately a reminder about scope: technical mentoring is still about engineering, but engineers do not develop apart from the people they are. His approach is personal professional guidance, not independent evidence that any particular cadence or technique works for every mentor and mentee.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
