What technical leadership coaching actually is (and isn't)
By Luigi Di Lena · June 2026 · 8 min read
There's a lot of confusion around technical leadership coaching. People picture someone sitting on a couch talking about their feelings, or a consultant who shows up with a 50-slide deck of generic management advice. Neither is accurate.
I've been doing this work for years — both as someone who received coaching and as someone who provides it. Here's what it actually looks like.
Let's start with what it's not
It's not therapy. We're not exploring your childhood. We're working on specific professional challenges you're facing right now.
It's not consulting. I'm not going to audit your organization and hand you a report. The goal is to develop your ability to solve problems, not to solve them for you.
It's not training. There's no curriculum, no slides, no certification at the end. Every session is driven by what you bring — your current challenges, decisions you're wrestling with, situations you want to handle better.
It's not mentoring (though it includes elements of it). A mentor shares their experience. A coach helps you develop your own judgment. In practice, I do both — I'll share what I've seen work, but the core of the work is helping you think more clearly about your own situations.
What actually happens in a session
A typical session starts with a question: "What's the most important thing you want to work on today?"
Sometimes it's a specific situation: "I have an underperformer and I don't know how to have the conversation." Sometimes it's a broader challenge: "I feel like I'm constantly firefighting and never doing strategic work." Sometimes it's a decision: "Should I take this director role or stay as a senior manager?"
From there, we dig in. I ask questions that help you see the situation more clearly. I challenge assumptions that might be limiting you. I share relevant experience when it's useful. And we usually end with a specific action — something concrete you're going to try before our next conversation.
It's collaborative, practical, and focused on your real world. Not theory.
Curious what this would look like for your situation? The 30-minute intro session is exactly this — a real coaching conversation, not a sales pitch.
Why "technical" matters
Generic leadership coaching works at a surface level for technical leaders. But there are challenges specific to engineering leadership that a coach without a technical background simply doesn't understand:
- How to maintain technical credibility while spending less time in the code
- When to override a technical decision your team made versus letting them learn from mistakes
- How to translate engineering concerns into language that resonates with non-technical stakeholders
- Managing the tension between technical debt and feature delivery
- Evaluating engineers whose work you no longer directly review
- Navigating the unique culture of engineering organizations
A technical leadership coach has lived these challenges. They don't need you to explain what a sprint retrospective is or why your team is stressed about on-call rotations. They've been there.
Who benefits most from it
In my experience, the people who get the most value from technical leadership coaching are:
New managers (0-2 years). You're learning everything at once. A coach accelerates the learning curve dramatically because you're not figuring out each problem from scratch — you have someone who's seen the pattern before.
Managers preparing for director roles. The jump from managing a team to managing managers is a different game entirely. You need to develop strategic thinking, learn to lead through others, and build influence across the organization.
Senior leaders who feel stuck. You've been in the role for a while. Things are fine but not great. You want a confidential space to think about what's next, work through political challenges, or develop a capability you haven't needed before.
Tech leads becoming managers. You had influence without authority. Now you have authority but aren't sure how to use it without becoming the kind of boss you used to dislike.
What results look like
Coaching results are often hard to measure because they're behavioral, not numerical. But here's what people typically report:
- More confidence in difficult conversations — performance reviews, pushback on unreasonable requests, saying no
- Better 1:1s — moving from status updates to actually developing their direct reports
- Clearer thinking about priorities — knowing what to focus on instead of being reactive to whatever lands in their inbox
- Faster decisions — less second-guessing, more willingness to act on imperfect information
- Concrete career progress — promotions, expanded scope, new opportunities
In harder numbers: roughly 70% of my clients achieve a promotion or significant role change within 6 months. Not because coaching is magic — because focused attention on development tends to compound quickly.
How it differs from what your company offers
Many tech companies provide internal coaching or leadership development programs. These are valuable but different in important ways:
- Confidentiality. An internal coach or HR partner may have organizational obligations that limit true confidentiality. An external coach works for you and only you.
- No agenda. Company programs often have a curriculum or goals that align with organizational needs. External coaching is entirely about your goals.
- Direct experience. Many internal coaches come from HR or L&D backgrounds. They understand management theory but may not have managed engineering teams themselves.
- Flexibility. No enrollment periods, no cohorts, no mandatory sessions. You book when you need it and stop when you don't.
Common objections
"I should be able to figure this out myself." Maybe. But why spend 6 months struggling when you could spend 6 weeks with someone who's seen the pattern before? Top athletes have coaches. It's not a sign of weakness — it's an investment in faster growth.
"It's expensive." Relative to what? If coaching helps you get promoted 6 months earlier, the salary increase alone pays for it many times over. And that's before counting the reduced stress, better team outcomes, and career momentum.
"I don't have time." One session is 30-60 minutes every few weeks. If you genuinely can't find that time, that's itself a symptom of the problem coaching would help with.
What to look for in a coach
If you're considering working with a technical leadership coach, here's what matters:
- Relevant experience. Have they actually managed engineering teams? Do they understand the tech industry from the inside?
- Chemistry. You need to feel comfortable being honest with this person. Most coaches offer an intro call — use it to see if the relationship feels right.
- Practical orientation. Beware coaches who only ask questions and never share perspective. Good coaching includes challenge, provocation, and occasionally direct advice.
- No hard sell. A good coach doesn't pressure you into long-term packages. They let the value of the work speak for itself.
How to get started
If you're curious, the simplest thing is to try one session. Come with a real challenge — something you're actually dealing with at work. See if the conversation helps you think about it differently. That's all the proof you need.