🧠 Mentoring doesn't solve all problems. The 4 people every software engineer needs to grow fast without burnout
"Struggling with slow engineering career growth? Leverage teachers, coaches, mentors & consultants for intentional, accelerated success."
The traditional approach to career growth is slow and passive.
Career growth isn't about working harder—it's about working with the right people and systems.
Most engineers rely only on self-learning or generic advice, missing structured support.
The best engineers take an intentional approach, leveraging mentors, coaches, and real-world experiences.
⭐ In this post you'll learn
The difference between teachers, coaches, mentors, and consultants
Why mentoring works best when sharing experiences, not instructions
How to connect technical growth to personal goals
How to use mentorship effectively for long-term growth
👨👩👧👦 #1 The 4 key roles that will accelerate your career
Teachers: Learning the fundamentals
Teachers provide structured knowledge through books, courses, and bootcamps. They help you build strong foundations, making them useful for beginners or when transitioning to a new skill.
If you want to master Kubernetes in 8 weeks, take a structured cloud architecture course.
Coaches: Improving performance through feedback
Coaches refine performance through structured practice and accountability. They fix code review habits, improve meeting communication, or set accountability for leadership goals. Unlike teachers, they focus on how you work, not what you know.
Coaching works well in short to medium-term engagements where you need consistent feedback.
Mentors: Guiding your long-term career path
Mentors share their experiences to help you navigate career challenges. They provide insights into both technical and non-technical growth. A senior engineer mentoring you on how to get promoted is a good example.
I see my mentor as someone very simlar to me, just a few years ahead of me. And I know my mentee sees the same in me.
Unlike teachers or coaches, mentorship is about long-term navigation—career pivots, office politics, and work-life balance.
Consultants: Solving specific career problems
Consultants provide expert advice for targeted challenges like resume reviews, salary negotiation, and interview prep. These are quick, high-impact engagements.
You can hire a consultant to optimize your resume for better job opportunities. The consultant won't worry about you learning, they will get the job done for you.
If you need results, not a relationship, hire a consultant.
👨🦳 #2 Mentoring is all about the experience
Reflection vs. external feedback
Your own perspective is limited. Others can spot lessons you might miss. Instead of assuming what you did right or wrong, share your story and let others extract insights.
When mentoring, don’t prescribe solutions. Instead of "Do X," say "When I faced Y, I used Z. What parts apply here?"
A mentor isn’t someone who imposes methods. They listen, share relevant experiences, and let you extract insights.
When my mentee asked about driving cross-team initiatives, I didn’t teach him to “lead meetings”. I didn't research about communication to teach about it. Instead, I shared how I once escalated operational concerns in another team's design and drove a change by sharing changes we did in my team to improve those aspects. My mentee identified parallels to his project and took action in those.
Growth through experience, not just knowledge
Career growth doesn’t come from waiting until you "know everything." Identify the first actionable step and start moving. What’s the first tiny experiment you can run?
At work, I saw this firsthand. Driving improvements on an initiative that got escalated to the CTO didn’t start as a strategized high-stakes move. It started with making small suggestions and improvements to another team’s design.
The importance of process over outcomes
Good leaders don’t just push for results—they evaluate how teams approach problems. Failures are part of the process.
When a team misses a deadline, the key question isn't: "Did we fail?" but "Did we anticipate this failure scenario?" If not, let’s map risks better next time.
Connect growth to personal goals
In my 1:1s with my mentee, we talk about career growth, his projects, and promotions—but also about personal finance and investing.
A promotion and higher salary don’t just impact work; they connect to personal goals like buying a home or investing more money.
⚙️ #3 Build systems, not just skills
Goal setting with a clear direction
Many engineers lack clarity on their career path. Vague goals like “get promoted” or “learn Rust" don't help much
It’s like walking blindfolded. Remove the blindfold, and even if you're not perfect, you move in the right direction.
Split goals into three categories:
Technical growth: Mastering a new framework, writing scalable code. Find teachers abour those topics
Career advancement: Getting promoted, leading projects. Find mentors to guide the ambiguity of these long-term goals
Personal development: Public speaking, networking, finances. Find coaches to keep you accountable and design a system to iterate and improve.
Creating systems, not just goals
Break long-term goals into:
Habits: Writing daily, practicing coding interviews weekly
Tasks: One-time actions like applying for a conference talk
Aim for consistency, not perfection. 3 hours/week on LeetCode is better than 10 hours once a month.
Block time for deep work, learning, and relationships.
Capture ideas in a backlog or "someday/maybe" list to prevent distraction. Review it quarterly, you'll find most ideas lose relevance. For those that stick, you can work on them as a taks
Accountability through regular check-ins
Set up recurrent progress review for the 3 types of goals. Mentors, coaches, or peers can keep you on track.
Example: A coach reviewing with you recordings of your public speaking engagements and giving feedback.
Identity > Goals
Don’t just "practice leadership", act as a leader. Saying “I’m a tech lead” changes how you act in meetings.
🎯 Conclusion
Career growth isn’t a sprint—it’s a series of intentional, well-supported leaps.
By leveraging teachers, coaches, mentors, and consultants, you gain guidance at every stage.
The core remains the same: start small, focus on systems, and let others help you see blind spots.
Pick one role you’re missing this week. Ask a senior engineer for coffee, or hire a resume consultant. The first step is the one that matters the most.
🗞️ Other articles people like
👏 Weekly applause
These are some posts I’ve liked from last week:
- . I particularly liked this small reflection from Alex. The satisfaction of doing things by yourself is higher than the disappointment of your work being used to train AI.
Frameworks for Managing Up as a Software Engineer by
and . Your relationship with your manager may be the most important one. This articles has a few strategies to improve that relationship. I particularly liked defining your “update stack“. If you never define with intention your system, it will be messyTurn Boring Projects into Opportunities by
. Sometimes the boring work reveals a bigger problem that makes a huge impact.From Engineer to Principal Solutions Architect at AWS with Prasad Rao by
and . The more senior you grow, the more important it is to understand lateral roles to have an holistic view.Common Mistakes That Cost You the Offer (And How to Avoid Them) by
. Interviews are more about communication than codingWhat is a Modular Monolith? by
. Start simple with a modular monolith and optimize for scalability later. It provides the benefits of flexibility with the smaller cost of building a monolithHow a 3.4 Million Concurrent Users Spike Took Down Fortnite’s Backend by
. If a plane crashes, it’s never a single failure. The same with this outage, it was about database overload, thread pool misconfiguration, Memcached saturation, and XMPP service disruption8 Guaranteed Ways to Annoy Your Senior Engineer by
. Better to avoid common pitfalls like vague requests, unchecked promises, and frequent priority shiftsSingle Responsibility Principle (SRP) In React: Write Focused Components by
. Good practices are good because they work in different languages and settings. SRP in the frontend also improves maintainability and reusability.How to Save 10 Hours Per Week as a Developer by
. As engineers we love optimizing, and this article provides a few ways.
Always in my inbox: Hungry Minds by
. A weekly curation of good articles.
The difference between Coaches and Mentors is subtle but important. In the past, I used to have a coach to help me grow personally and a mentor to help me grow technically. Different tools for different jobs.
Great article, Fran, and thank you for the mention!
Identity > Systems > Goals
Great post as always, full of interesting concepts and links. Gracias, Fran!