How to Find the Right Mentor for You
Careers in tech rarely stall because of talent. They stall because direction is unclear.
Most engineers don’t struggle with learning itself—they struggle with deciding what deserves focus. System design or AI? Depth or breadth? Promotion track, freelancing, or startup path? Without someone who has already walked that road, it’s easy to spend years optimizing the wrong skills.
I’ve seen this repeatedly in my own career and with the engineers I mentor. Technical ability often grows fast, but positioning, communication, and career strategy grow slowly without guidance. A good mentor doesn’t just answer questions—they help you frame better ones.
I’m Mahmoud Zalt. For 16+ years I’ve built production systems, interviewed hundreds of engineers, and helped people move from mid to senior, senior to staff, and from traditional software roles into AI-focused careers. Through my mentoring program, I focus on practical progress: promotion strategy, interview readiness, architecture thinking, and realistic AI transition plans. You can read more about my background on my site.
What a Mentor Actually Changes
People assume mentorship is about getting answers. In reality it is about changing how you think. The biggest career jumps rarely come from a new framework or certificate—they come from better judgment about what to prioritize and what to ignore.
In the engineers I work with, the pattern is consistent: strong technical skills paired with weak positioning. They solve complex problems yet struggle to explain impact, choose the right next role, or prepare for interviews that test reasoning instead of syntax.
The Four Shifts That Matter
- From tasks to outcomes: learning to talk about value instead of features
- From coding to design: thinking in systems rather than tickets
- From learning to positioning: choosing skills that compound
- From reacting to planning: owning a multi-year direction
A mentor accelerates these shifts because they provide contrast. When someone with more distance reviews your decisions, blind spots become obvious. That outside perspective is what I try to bring in every session of my mentoring work.
What Mentorship Is Not
It is not outsourcing responsibility. It is not a shortcut around hard practice. The best relationships feel less like coaching and more like design reviews for a career—assumptions challenged, tradeoffs clarified, next experiments defined.
Over the years building products and leading teams, documented on my projects page, I learned that progress follows structure. Mentorship simply provides that structure earlier than most people discover it alone.
Who Benefits Most From Mentorship
Not everyone needs the same kind of mentor. The value depends on where you are in your career and what problem you are trying to solve right now. Mentorship works best when it is attached to a concrete transition rather than a vague wish to improve.
Common Situations I See
- Engineers aiming for senior or staff level but unsure what evidence leadership expects
- Developers wanting to move into AI roles without resetting their career
- Strong coders who struggle with system design interviews
- Professionals with good experience but weak storytelling on resumes
- Team leads learning how to influence without formal authority
The pattern behind all of these is not lack of intelligence. It is lack of translation. Technical people often assume quality speaks for itself, yet careers move through perception, communication, and positioning as much as through code.
Where Mentorship Has the Highest ROI
Mentorship delivers the biggest return during inflection points: first leadership role, first AI project, first serious interview cycle, or first time managing scope end-to-end. In stable periods it is helpful; in transitions it becomes decisive.
The goal is not to create dependency on a mentor but to compress years of trial and error into a few focused conversations, so decisions become deliberate instead of accidental.
What Actually Makes a Good Mentor
A good mentor is not simply the most senior person you can find. Titles and years of experience matter less than three practical qualities: relevance to your goals, willingness to engage, and the ability to give honest feedback without ego.
Experience That Matches Your Next Step
The best mentor is usually one or two stages ahead of where you want to be, not ten. Someone who recently solved the problems you are facing remembers the details: how interviews really feel, how promotions are actually decided, how AI transitions work in real companies rather than in theory.
Communication Over Brilliance
I have met brilliant engineers who were terrible mentors and average engineers who changed careers through clear guidance. Mentorship is a communication role. Listening, asking the right questions, and explaining tradeoffs matter more than showing off knowledge.
Alignment of Values
Careers are built on choices: speed versus quality, visibility versus depth, specialization versus breadth. A mentor whose values conflict with yours will push you toward a life you do not actually want. Alignment is more important than prestige.
The right relationship should feel practical rather than inspirational only. After each session you should leave with clearer decisions, not just motivation.
How to Find the Right Mentor in Practice
Finding a mentor is less about luck and more about structured exposure. Most people search in the wrong places—aiming for famous names instead of accessible professionals who actually have time to engage.
Start With Your Existing Radius
- Former colleagues who moved into roles you want
- Engineers from your previous teams
- Speakers from local meetups or conferences
- Authors of projects you genuinely studied
- Communities where you already contribute
Warm connections outperform cold messages. Someone who has seen your work or attitude is far more likely to invest time than a celebrity profile on the internet.
Approach With a Specific Problem
The best first message is not “will you be my mentor” but “I’m preparing for staff interviews and struggling with system design scope—could I get 20 minutes of feedback on my approach?” Concrete requests show seriousness and respect for time.
Think in Multiple Mentors
One person rarely covers everything. You might need one mentor for architecture, another for AI transition, and a third for leadership communication. A portfolio of mentors is healthier than a single dependency.
The process is iterative: short conversations first, relationship later. Mentorship grows from value, not from titles.
How I Work With Engineers
My mentoring is not motivational coaching. It is practical engineering guidance shaped by real hiring loops, production failures, and leadership decisions I’ve lived through.
What Sessions Usually Focus On
- Promotion strategy from senior to staff level
- System design thinking beyond interview templates
- Transition path into AI and applied LLM work
- Portfolio projects that prove impact
- Communication with stakeholders and leadership
I treat mentoring like architecture design: diagnose first, prescribe second. We begin with your current role, constraints, and target level, then design evidence that convinces hiring committees rather than impresses Twitter.
Typical Outcomes
- A clear 90-day growth roadmap
- Interview stories tied to measurable impact
- System design approach aligned with your domain
- Realistic plan to enter AI roles
Details about formats and plans are on the mentoring page. Sessions can be single focused consultations or ongoing monthly work depending on the goal.
Getting Started Without Overthinking
You don’t need a perfect plan before talking to a mentor. Most engineers arrive with a mix of ambition and confusion, and that is exactly the right starting point.
The first session is usually about three questions: Where are you now? Where do you want to be in 12–18 months? What is blocking that path? From those answers we can design concrete next steps instead of generic advice.
Before You Book
- Write one paragraph about the role you want
- List two situations that feel stuck
- Bring one piece of real material: CV, project, or interview story
Mentorship works when it touches real artifacts, not theory. A messy résumé or half-finished project is more useful than a polished idea.
If this resonates, you can start with a single session and decide later whether ongoing mentoring makes sense.
Choosing Progress Over Guesswork
Careers in technology rarely fail because people are not smart enough. They stall because feedback arrives too late, goals stay fuzzy, and no experienced voice helps translate effort into visible impact.
Mentorship is not about copying another person’s path. It is about shortening the distance between what you know today and what the next role expects from you.
If you want structured, practical guidance rather than generic motivation, you can explore the mentoring options on the mentoring page. For more context about my background and how I approach engineering and leadership, see the about page.
The goal is simple: clearer decisions, stronger evidence of impact, and a career that moves by design instead of chance.
