The shift that makes coaching useful
Engineering careers reward a specific competence: understanding a system well enough to make it behave. That competence keeps working right up until the job becomes an organisation rather than a system — and organisations do not respond to being understood. They respond to attention, incentives, and repetition. Most engineering leaders who seek coaching are somewhere in that transition, often mid-way and effective enough that nothing is visibly broken.
Common presenting problems
- Newly promoted and still doing the previous job, with the new one unattended.
- Accountable for outcomes across teams you have no authority over.
- Calendar fully consumed; no time left for the thinking the role actually requires.
- Strong with your own team, undifferentiated in front of executives.
- Carrying a reorg, migration, or attrition wave with nowhere to think aloud.
- Competent, well-reviewed, and quietly unsure the next rung is worth it.
What the work covers
Scope without control
Above a certain level, the things you are accountable for outnumber the things you can direct. Coaching treats influence as a practice rather than a personality trait: where to spend credibility, which alliances actually matter, and how to get a decision made in a forum you do not own.
Executive communication
Engineers are trained to present reasoning and arrive at a conclusion. Executives want the conclusion, the confidence level, and what you need — in that order. This is one of the most mechanical improvements coaching produces, because the underlying judgement is usually already sound and only the framing is working against you.
Technical judgement at organisational scale
Deciding whether to fund a migration, absorb reliability debt for another quarter, or consolidate two platforms are technical decisions with organisational consequences, and they are rarely decidable on the merits alone. Having a thinking partner who understands both halves is the point of coaching with someone who has done the job.
Sustainability
On-call, incidents, and always-available expectations make burnout a structural risk in this work, not a personal failing. Coaching addresses capacity concretely: what to delegate and to whom, which escalation paths you are propping up personally, and what a defensible boundary sounds like when stated to your own manager.
Why the coach's background matters here
Coaching does not require domain expertise — a skilled coach can work effectively in an unfamiliar field, and a coach who knows your domain can be tempted to give advice instead of coaching. The specific advantage in engineering is that you skip the translation layer. When you say the migration slipped because two teams disagreed about the interface and neither escalated, that lands immediately, and the session is spent on your decision rather than on background.
Format
Engagements typically run three to six months, with 60-minute sessions every two to three weeks, held virtually. That spacing is deliberate: the work between sessions — trying a different approach in a real meeting — is where change happens. Every engagement begins with a free 30-minute discovery call.
Frequently asked questions
Is this for individual contributors or only people managers?
Both. Staff and principal engineers leading through influence rather than reporting lines face many of the same problems, particularly around executive communication and driving decisions without authority.
My company will not pay for coaching. Is it still worth it?
Many clients fund coaching themselves. One structural benefit: the engagement is accountable only to you, with no reporting line to your employer, which makes it easier to examine whether to stay in the role at all.
How is this different from having a good manager?
A good manager is invaluable and also structurally conflicted. They decide your promotion, your compensation, and your scope, which means there are things you will not say to them. A coach has no stake in those decisions and no position in your organisation's politics.
Will you tell me what to do about a specific technical decision?
No, and that restraint is deliberate. Coaching helps you reach a decision you can defend and own, because you hold the context a coach never fully will. If you need architectural advice, you need a consultant or an advisor, not a coach.
Ready to start?
Book a free 30-minute discovery call. No obligation to proceed.
Book a Discovery Call →