Why Mentorship Matters

A trusted mentor can do more than boost your sense of belonging at work. Data from the 2021 State of the Octoverse Report shows that pairing a commitment to mentorship with friendly, timely code reviews is linked to a 46% productivity boost in open source projects and a 16% increase within companies.

To understand how developers can actually find and benefit from these relationships, we spoke with developer advocates Michelle Mannering and Damian Brady about their experiences on both sides of the mentoring equation.

The Personal Payoff of Good Mentors

Mannering describes mentors as a form of "time travel"—a way to learn from someone else's experiences and apply those lessons to your own situation. "Mentors aren't gods that have all the answers," she says, "but they are invaluable colleagues who are fantastic for bouncing around ideas and asking for advice." In her experience, she often arrives at her own answer, but only after a mentor helped her think it through. Beyond guidance, they validate ideas, help chart career pathways, and champion your wins.

Brady's mentors have helped him identify what he is good at and what he enjoys. "Focusing on that combination has meant I'm more likely to put in the work," he notes, adding that they have steered him toward decisions that lead to success.

Neither advocate ever formally declared they needed a mentor. Instead, the relationships grew organically. Mannering suggests approaching people for small favors rather than large time commitments. Instead of asking for advice on a broad topic, ask if they can point you to resources or content they have already created. This respects their schedule and often yields material that is directly useful.

Brady took a different route: he identified people already doing what he wanted to do. "I realized I enjoyed public speaking, so I spent time with people who were good at it to learn what they did." Approaching someone you respect from a distance can feel intimidating, but he reminds early-career developers that "they're also just people. In general, people want you to succeed."

This approach paid off in a concrete way when a mentor, knowing Brady was growing into a specialty, vouched for him as a co-author for a book series. Although the book was unlikely to earn money, the mentor explained it was a strategic way to get his name in front of the right people. That opportunity led to a Microsoft MVP award and launched his public speaking career.

Mentoring in Communities vs. Companies

Context matters when setting expectations. In open source communities, Mannering emphasizes that the person you are asking is typically not paid for their community work. Their time is more valuable because they likely have a full-time job on top of their volunteer contributions.

The key to making the most of their attention is specificity. "Mentors can better help you when you ask specific questions tied to an outcome," she says. A vague question like "How do I have a good career?" is far less actionable than asking for tips on what to look for when searching for an open source community to join.

When Do You Become the Mentor?

Neither advocate recalls a specific moment when they became mentors themselves. Mannering notes it happens as a natural progression—you start sharing knowledge with those around you and answering DMs when people reach out for advice.

For Brady, the shift came through developer advocacy. While advocacy is often a "one-to-many" effort aimed at helping as many people as possible, he finds equal value in one-on-one interactions. "I love helping people one-on-one where you can really focus on what's important to that person," he says, even if he has never formally claimed the mentor title.

Structuring the Relationship for Maximum Value

A formal arrangement isn't required, but structure still helps. Brady recommends a regular cadence, whether weekly, monthly, or longer. "Having a regular cadence means there's continuity and the ability to get the most out of each meeting."

Both advocates stress the importance of clarity. As a mentee, be explicit about what you want—whether that is guidance on what to learn next, career advice, or simply support through difficult periods. Mannering approaches her mentors with pointed requests: "I'm having trouble with X, can you please give me some advice."

Mentors have a responsibility too. It is important not to take it personally if a mentee doesn't follow your advice. "Everyone has their own unique situations and what worked for you might not work for them," Mannering says. A mentor's role is to pass on knowledge and experience, then trust the mentee to make their own best decision. Brady adds that connecting a mentee with someone else is a valid outcome if you are not the right person to help them at that moment.

Key Takeaways

  • Maintain a regular rhythm. Whether in person or virtual, keep a consistent meeting schedule for continuity.
  • Come prepared with specifics. Bring concrete topics, challenges, or relevant projects rather than asking broad, general questions.
  • Stay open and curious. Be ready to be challenged—that is where real growth as a developer happens.