Many engineering leaders get the job the same way. They were the strongest engineer on the team, someone needed to lead, and they said yes. On Monday they wrote code. On Tuesday they were responsible for people, priorities, and hiring.
The skills that made them a great engineer still matter, but they are no longer enough. Coaching can help close that gap faster and with less damage along the way. It is not the answer to every problem, though, and it is worth being clear about what it is and is not.
Signs a lead would benefit from coaching
None of these signs means someone is failing. Most of them are normal in the first year of leading a team. Coaching helps when a lead wants to work through them deliberately instead of by trial and error.
They are still doing most of the hard work themselves
The new lead takes the difficult tickets, reviews every pull request, and fixes problems late at night. The team waits on them. It feels responsible, but it does not scale, and it keeps others from growing.
Every day is full, but little moves forward
Their calendar is packed. Their to-do list resets every morning. They are busy all the time and still cannot point to clear progress on what matters most.
One-to-ones are skipped or turn into status updates
They know one-to-ones are important, but the meetings get moved, cancelled, or spent reading through a task board. Team members are not getting the attention, feedback, or direction they need.
Hard conversations get postponed
Someone is underperforming. Two people are in conflict. A stakeholder keeps changing priorities. The lead knows they need to say something and keeps waiting for a better moment.
They inherited a team and are not sure where to start
A new manager joins a team that already has its own history, habits, and frustrations. They want to make changes but do not yet know which ones will help.
Hiring feels like guesswork
They are asked to grow the team, but the interview process is improvised, decisions rest on one person’s impression, and nobody is sure what “a good hire” means for this team.
They are tired in a way that rest does not fix
Leading people can be lonely. A lead who has nobody to think out loud with tends to carry every problem alone, and that weight shows up in their health, their patience, and their decisions.
What coaching covers
Matthew has led iOS and web engineering teams, and he wrote a four-part series on building great engineering teams. Our coaching draws on the same ideas. The work is practical and specific to the lead’s real situation.
Leading yourself first
The first part of the series, Start With You, makes a simple point: a team’s ability to thrive is tied to how well its leader is leading themselves. Coaching often starts here. That means choosing what to say yes to, and just as importantly, what to say no to. It means aiming for progress rather than perfection, asking trusted people for honest feedback about blind spots, and protecting physical, mental, and emotional health instead of treating burnout as part of the job.
Building with the team you have
Most leads inherit a team rather than build one from scratch. Part two of the series argues for getting to know each person before imposing a new vision: spend time with them, ask questions, and listen. It also observes that most teams are not short of direction. They are overwhelmed by too many commitments.
In coaching, this becomes concrete. How should regular one-to-ones run? What is a team meeting for? Where could pairing help people solve problems and communicate better? And who on the team is ready for more ownership? As the series puts it, you do not scale, but your leadership can.
Hiring with a clear process
Part three covers hiring: weigh character alongside skill, involve a small group of interviewers instead of deciding alone, give each interviewer a specific focus, and use a process you can repeat. It also stresses written communication, which matters on any engineering team. A coach can help a lead design or tighten that process and practice the conversations it involves.
Keeping good people
Part four turns to retention. People stay when they are part of something bigger than the daily task list, when the pace is sustainable rather than a grind, and when the company invests in their growth. Coaching helps a lead act on those ideas within the limits of their role and budget.
The practical, day-to-day questions
Beyond the series, coaching sessions often deal with what is in front of the lead this week: a difficult conversation to prepare for, a technical decision with people consequences, a stakeholder who needs managing, or a plan for the next quarter. Because Matthew has built products himself, the technical side of a decision is part of the conversation, not something set aside.
What coaching is not
Being clear about limits keeps coaching useful and keeps everyone honest.
It is not therapy
Leadership is personal, and stress, confidence, and burnout come up. A coach can talk about how those affect someone’s work and help them build healthier habits. A coach is not a licensed mental health professional. If someone is dealing with anxiety, depression, or a personal crisis, the right person to help is a qualified therapist or doctor, and a good coach will say so.
It is not a substitute for their manager
The lead still has a manager, and that relationship matters. Their manager sets expectations, evaluates performance, and makes decisions about their role. A coach works alongside that, not instead of it. Coaching is a space to think and prepare. It does not make decisions about pay, promotion, or performance.
It is not someone doing the job for them
A coach will not run their one-to-ones, write their team’s roadmap, or make their hiring decisions. The point is for the lead to grow into the role, and that only happens when they do the work. If a team needs hands-on technical help, that is a different kind of engagement, such as architecture guidance or a code review and second opinion.
It is not a quick fix
A single conversation can help with a single problem. Real change in how someone leads usually takes repeated practice, reflection, and adjustment over weeks or months.
How to tell if it is the right time
Coaching tends to work best when three things are true:
- The lead wants it. Coaching imposed as a correction rarely works.
- There is a real situation to work on, not just a general wish to “be better.”
- Their manager supports the time and keeps their own role in the lead’s development.
If those are in place, coaching can shorten the hard first year of leadership and help a strong engineer become a leader people want to follow.
If you are a manager considering coaching for someone on your team, it is worth talking to them first. Ask what they are finding hardest. Their answer will tell you a lot about whether coaching is the right kind of help. You can read more about how we work with teams on our services overview.
Talk it through
If you lead an engineering team, or you are supporting someone who does, and you want to talk about whether coaching would help, learn about technical leadership coaching. Matthew reads every message himself and usually replies within one business day.