index

From 0 to 180+ Mentees: Building a Mentorship Program That Actually Works

· 5min

The Journey

When I started my career, I had a mentor who changed my life. They didn’t just teach me code—they taught me how to think, how to grow, and how to help others.

Years later, I wanted to pay it forward. But I didn’t want to just mentor one person. I wanted to build something that could scale and help as many engineers as possible.

The result: A mentorship program that has helped 180+ engineers get jobs, grow their careers, and become better engineers.

88% job placement rate. 26k+ LinkedIn followers. AWS Community Builder.

Here’s how I built it and what I learned.

The Problem I Solved

When I was starting out, mentorship was hard to find:

  • Senior engineers were busy
  • Mentorship was informal and inconsistent
  • No structure, no accountability
  • You had to know someone to get help

I wanted to create something different: accessible, structured, scalable mentorship.

The Program Structure

Phase 1: Intake & Assessment (Week 1)

Every mentee starts with a structured intake:

1. Background Assessment
   - Current role/experience level
   - Goals (promotion? new job? skill building?)
   - Challenges they're facing
   - Learning style preferences

2. Goal Setting
   - 3-month goal (specific, measurable)
   - 6-month goal
   - 12-month goal

3. Baseline Assessment
   - Technical skills (1-10 scale)
   - Soft skills (communication, leadership)
   - Areas of strength
   - Areas for improvement

4. Mentorship Plan
   - Weekly meeting schedule
   - Focus areas
   - Success metrics

This takes 1 hour but saves months of wasted time.

Phase 2: Weekly Mentoring (Weeks 2-12)

Weekly 1-on-1 meetings (30-60 minutes)

Structure:

1. Check-in (5 min)
   - How's work going?
   - Any blockers?

2. Progress Review (10 min)
   - Review goals from last week
   - Celebrate wins
   - Discuss challenges

3. Deep Dive (30 min)
   - Focus on one topic
   - Could be: code review, system design, career advice, etc.

4. Action Items (10 min)
   - What will you do this week?
   - How can I help?
   - Next week's topic

Topics I cover:

  • Technical: System design, code quality, testing, performance
  • Career: Negotiation, promotions, job hunting, side projects
  • Soft Skills: Communication, leadership, conflict resolution
  • Mindset: Imposter syndrome, burnout, work-life balance

Phase 3: Accountability & Tracking

I use a simple tracking system:

Mentee: [Name]
Goal: [3-month goal]
Status: [On track / At risk / Off track]

Week 1: [Progress]
Week 2: [Progress]
...

Metrics:
- Skills improved: [List]
- Confidence level: [1-10]
- Job applications sent: [Number]
- Interviews scheduled: [Number]
- Offers received: [Number]

This creates accountability and makes progress visible.

What Actually Works

1. Specificity Beats Generality

Bad mentorship: “You should learn system design” Good mentorship: “Let’s design a URL shortener. Here’s what I’d consider…”

Specific problems with real solutions stick. Generic advice is forgotten.

2. Mentees Need to Do the Work

I learned this the hard way. I can’t make someone successful—I can only guide them.

My role:

  • Provide direction
  • Share experience
  • Hold them accountable
  • Celebrate wins

Their role:

  • Do the work
  • Ask questions
  • Apply learnings
  • Track progress

The mentees who succeed are the ones who take ownership.

3. Different Mentees Need Different Approaches

Junior engineers (0-2 years):

  • Need fundamentals (design patterns, testing, debugging)
  • Need confidence building
  • Need career guidance

Mid-level engineers (2-5 years):

  • Need system design skills
  • Need leadership preparation
  • Need negotiation skills

Senior engineers (5+ years):

  • Need strategic thinking
  • Need executive presence
  • Need mentorship skills (meta!)

I tailor my approach to each person.

4. Job Search is a Skill

Many engineers are great at their jobs but terrible at job searching. I teach:

Resume optimization:

  • Quantify impact (not just responsibilities)
  • Use keywords from job descriptions
  • Lead with achievements

Interview preparation:

  • System design practice
  • Behavioral interview coaching
  • Salary negotiation

Job search strategy:

  • Target companies (not spray and pray)
  • Leverage network
  • Follow up consistently

This alone has helped 50+ mentees get jobs.

5. Soft Skills Matter More Than You Think

The best engineers I know aren’t always the smartest. They’re the ones who:

  • Communicate clearly
  • Listen well
  • Build relationships
  • Handle conflict gracefully
  • Lead without authority

I spend 30% of mentoring time on soft skills.

Lessons Learned

1. Mentorship Doesn’t Scale Linearly

I started mentoring 1-on-1. Then 5. Then 20. Then 50.

At 50 mentees, I hit a wall. I couldn’t give everyone enough attention.

Solution: I created leverage:

  • Group sessions (office hours, workshops)
  • Written content (guides, templates, frameworks)
  • Peer mentoring (senior mentees mentor junior ones)
  • Community (mentees help each other)

Now I can support 180+ mentees with 10 hours/week of my time.

2. Not Everyone Wants to Be Mentored

Some people are resistant:

  • “I don’t need help”
  • “I’ll figure it out myself”
  • “I don’t have time for meetings”

I learned to recognize this early and not force it. Mentorship only works if both people are committed.

3. Mentors Need Mentors Too

I still have mentors. I still learn. I still get stuck.

Staying humble and continuing to learn is essential. My mentees can tell when I’m genuinely trying to help vs. just dispensing advice.

4. Celebrate Wins (Even Small Ones)

When a mentee gets a job, I celebrate with them. When they solve a hard problem, I acknowledge it.

This builds momentum and keeps them motivated.

5. Track Everything

I keep detailed notes on every mentee:

  • Their goals
  • Their progress
  • Challenges they’ve overcome
  • Wins they’ve achieved

This helps me:

  • Remember context between meetings
  • Spot patterns
  • Measure impact
  • Improve the program

The Program Today

180+ mentees mentored

  • 88% job placement rate
  • 50+ promotions
  • 30+ career transitions
  • 100+ skill improvements

How it works:

  • 1-on-1 mentoring (30-40 active mentees)
  • Group office hours (weekly, 20-30 people)
  • Workshops (monthly, 50+ people)
  • Peer mentoring (senior mentees help junior ones)
  • Content library (guides, templates, frameworks)

Time investment: ~10 hours/week

Impact: Helping engineers change their careers, get better jobs, and grow as people.

How to Build Your Own Mentorship Program

If you want to start mentoring:

Start Small

  • Pick 1-2 people
  • Be consistent
  • Build trust
  • Then expand

Be Specific

  • Set clear goals
  • Track progress
  • Measure impact
  • Adjust as needed

Create Leverage

  • Document what you teach
  • Create group sessions
  • Build community
  • Enable peer mentoring

Stay Humble

  • You don’t have all the answers
  • Learn from your mentees
  • Admit mistakes
  • Keep growing

Measure Impact

  • Track job placements
  • Measure skill growth
  • Celebrate wins
  • Share stories

Real Stories

Mentee 1: Junior to Mid-Level

  • Started: Junior developer, imposter syndrome, stuck in first job
  • 6 months: Learned system design, built confidence, got promoted
  • 12 months: Senior developer, mentoring others

Mentee 2: Career Transition

  • Started: QA engineer, wanted to become a developer
  • 6 months: Learned programming, built portfolio
  • 12 months: Software engineer at FAANG company, 40% salary increase

Mentee 3: Leadership Journey

  • Started: Senior engineer, wanted to lead
  • 6 months: Learned leadership skills, led a small project
  • 12 months: Engineering manager, managing a team of 5

These aren’t exceptions. They’re the norm in my program.

The Takeaway

Mentorship is one of the highest-leverage activities you can do as an engineer.

You can:

  • Help someone change their career
  • Accelerate their growth by years
  • Build a community
  • Make a real impact

And the best part? You learn as much from mentoring as your mentees do.

If you’re a senior engineer, consider starting a mentorship program. It doesn’t have to be formal. It doesn’t have to be big. Start with one person. Be consistent. Track impact.

The world needs more great mentors. Be one.

Resources I Use

  • Tracking: Notion (simple spreadsheet works too)
  • Meetings: Google Meet / Zoom
  • Content: Google Docs (shared templates)
  • Community: Slack or Discord
  • Learning: Books, courses, podcasts (I share recommendations)

Books I recommend to mentees:

  • “The Effective Engineer” by Edmond Lau
  • “Cracking the Coding Interview” by Gayle Laakmann McDowell
  • “Crucial Conversations” by Kerry Patterson
  • “The Manager’s Path” by Camille Fournier
  • “Radical Candor” by Kim Scott

If you want to start mentoring, these resources will help you get started.