If you're serious about leveling up your career in tech, you need a mentor. Not "maybe" or "eventually." You need one now.
Here's the thing most people won't tell you: the developers who advance fastest aren't necessarily the smartest or the hardest workers. They're the ones who have someone in their corner, someone who's already walked the path they're trying to navigate.
Let me show you how to find that person.
Why You Actually Need a Mentor
Before we get into the "how," let's talk about the "why."
A mentor isn't just someone who answers your questions (that's what Stack Overflow is for). A good mentor:
- Spots your blind spots: You can't see what you don't know. A mentor can.
- Saves you years of mistakes: They've already made them so you don't have to.
- Opens doors: Networking and referrals still matter more than your LeetCode score.
- Keeps you accountable: It's harder to give up when someone believes in you.
- Gives you the confidence to take risks: Knowing someone has your back makes bold moves easier.
I've seen developers waste 2-3 years grinding on the wrong things because they didn't have someone to tell them "that's not how this works."
Don't be that person.
The Biggest Myth About Finding a Mentor
Here's what most people think: "I need to find a senior engineer at a FAANG company who will dedicate hours every week to mentoring me for free."
Good luck with that.
The truth? Most mentorship happens organically, not formally.
You don't need to email a stranger and ask "Will you be my mentor?" (please don't do this). You need to build relationships with people slightly ahead of you, provide value, and let mentorship emerge naturally.
Where to Actually Find Mentors
1. Your Current Workplace
This is the most obvious and most underutilized option.
- That senior dev who writes clean code? Ask them to review your PRs more critically.
- The tech lead who always seems calm during incidents? Ask how they approach debugging.
- The engineer who switched from backend to frontend? Pick their brain about the transition.
Pro tip: Most senior engineers WANT to help, they just don't have time to help everyone. Make it easy for them by asking specific, thoughtful questions.
2. Open Source Communities
Contributing to open source is like a cheat code for meeting experienced developers.
- Join Discord/Slack communities for projects you use
- Submit PRs and ask maintainers for feedback
- Attend virtual or in-person contributor meetups
The best part? You're already providing value (contributions), so people are more willing to invest time in you.
3. Tech Meetups and Conferences
I know, I know. Networking feels awkward. Do it anyway.
- Go to local meetups (yes, in person)
- Don't just collect business cards, actually follow up
- Offer to grab coffee with speakers after talks
Script for after a talk: "Hey, really enjoyed your talk on [topic]. I'm working through [related challenge] right now. Would love to hear how you'd approach it. Free for coffee next week?"
4. Online Communities (Twitter, LinkedIn, Discord)
This works if you're intentional about it.
- Engage with developers whose work you respect (comment, share, discuss)
- Don't just lurk, contribute answers, insights, and questions
- DM people with specific, thoughtful questions (not generic "can I pick your brain")
What NOT to do: "Hi, I'm looking for a mentor. Can you help?"
What TO do: "I just read your post on system design. I'm struggling with [specific problem]. Have you encountered this before?"
5. 1:1 Mentorship Platforms and Self-Help Resources
Look, coding bootcamps are expensive. If you're super motivated to get the most out of it and you have some extra cash, we won't say it's a bad idea. But there are cheaper (and often better) ways to find mentorship.
1:1 Mentorship Platforms:
- ADPList (free): Connect with mentors for 1:1 sessions
- MentorCruise (paid): Monthly mentorship subscriptions
- Plato (free for mentees): Focuses on engineering leadership
Self-Help Books (Mentorship at Scale):
Books are mentorship at scale. The problem? You can spend all this time reading them and not implementing anything.
- "The Pragmatic Programmer" by Andy Hunt and Dave Thomas
- "Staff Engineer" by Will Larson
- "The Manager's Path" by Camille Fournier (even if you're not a manager)
- "Atomic Habits" by James Clear (for building better learning habits)
Pro tip: If a mentor recommends a book to you, the fastest way to earn their trust is to actually read it. Then prove you read it. Come back with specific questions, share what you implemented, or debate a point you disagreed with. Most people say "thanks for the recommendation" and never touch it. Don't be most people.
Look for mentors who specialize in your area (frontend, backend, DevOps, etc.) and whose experience matches where you want to go, not just where you are now.
How to Approach Someone Without Being Weird
The #1 mistake people make: asking for too much, too soon.
DON'T:
- "Hi, can you be my mentor?"
- "Can I pick your brain?" (with no context)
- "Can we schedule a weekly 1:1?" (before you've even talked once)
DO:
- Ask specific, well-researched questions
- Offer value first (share an article, give feedback, help with something)
- Start small (15-minute coffee chat, not a long-term commitment)
Example good outreach message:
"Hi [Name], I came across your blog post on microservices architecture and it really clicked for me. I'm currently working on breaking down a monolith at [company] and running into [specific challenge]. Have you dealt with this before? Would love your take if you have 15 minutes for coffee sometime."
Notice:
- Specific: not vague "pick your brain"
- Relevant: tied to something they've done/written
- Low commitment: 15 minutes, not a recurring meeting
- Respectful: acknowledges their time is valuable
What to Do Once You Have a Mentor
Congrats, someone agreed to meet with you. Don't waste it.
Before the Meeting:
- Prepare specific questions (not "how do I get better at coding?")
- Do your homework (Google first, ask humans second)
- Have a goal (what do you want to walk away with?)
During the Meeting:
- Listen more than you talk
- Take notes (shows you value their time)
- Ask follow-up questions
- Don't just complain, show what you've tried
After the Meeting:
- Send a thank-you message within 24 hours
- Share what you implemented based on their advice
- Stay in touch (occasional updates, not weekly check-ins)
Most important: Show them their advice mattered. Nothing makes a mentor happier than seeing someone take action.
The Long Game: Building Multiple Mentor Relationships
Here's a secret: you don't need ONE mentor. You need a personal board of advisors.
- A technical mentor (helps you level up your skills)
- A career mentor (helps you navigate promotions, job changes)
- A domain mentor (expert in the specific area you want to grow in)
Different people will help you with different things. That's okay.
Red Flags: When a "Mentor" Isn't Actually Helpful
Not all advice is good advice. Watch out for:
- The Know-It-All: Dismisses your ideas without listening
- The Gatekeeper: Makes you feel like you're not good enough
- The Self-Promoter: Every conversation turns into their achievements
- The Vague Advice Giver: "Just work hard" without specifics
- The Ghost: Agrees to help, then disappears
If someone makes you feel worse about yourself after every conversation, they're not a mentor. They're an energy drain. Move on.
What If You Can't Find a Mentor?
Sometimes, despite your best efforts, it's hard to find someone.
Here's what you can do:
- Consume content from mentors-at-scale: Blogs, YouTube, podcasts from experienced engineers
- Study people you admire: Follow their GitHub, read their code, reverse-engineer their thinking
- Mentor yourself: Document your own journey, review your code from 6 months ago, identify patterns
- Peer mentorship: Find someone at your level and grow together
Remember: mentorship is bidirectional. Even junior developers can teach each other. You don't need someone 10 years ahead of you. Someone 2 years ahead is often more helpful.
The Most Important Thing
Finding a mentor isn't about "networking" or "career hacking." It's about building real relationships with people who want to see you succeed.
- Be genuine. People can tell when you're transactional.
- Be patient. Good mentorship takes time.
- Be valuable. The best mentees become mentors themselves.
And here's the thing no one tells you: the best time to start mentoring others is now. You don't need 10 years of experience to help someone with 1 year of experience.
Teaching others will make you a better learner. Mentoring others will make you a better mentee.
So go find your mentor. And then, become one.
About gitGood.dev
We're building the best tech interview prep platform for developers who want to actually get better, not just pass tests. AI mock interviews, real coding challenges, and a community of people who get it.