Short answer: choose a coach who has managed engineers themselves, holds a recognized coaching credential (an ICF ACC, PCC or MCC), has worked with first-time managers before, and will agree with you on two or three concrete goals in the first session. Then test the fit on a free first call. If your company is paying, also agree up front what your manager will and won’t hear.
That is the checklist. The rest of this guide explains why each point matters, what a new engineering manager actually works on with a coach, and the questions that separate a good fit from an expensive conversation.
Why a new engineering manager needs a different kind of help
You were promoted because you were a strong engineer. Then, overnight, the job changed. Your output is now your team’s output, your calendar fills with other people’s problems, and the feedback loop you relied on (write code, see it work) is gone. The skills that got you here won’t get you there.
I learned this the hard way. Early in my career I was given a team with a reputation for shipping little, and what it shipped was full of bugs. Most of the work landed on a few senior people while everyone else waited, support requests kept interrupting project work, nobody knew who owned what, and some engineers were working 14-hour days. Sorting that out took one-on-ones, clear roles, a support rotation, honest conversations with stakeholders and healthy working hours. I wrote up the full story in From Chaos to Structure on the Operations Team.
Later, as co-founder and CTO of AdvisorEngine, I grew the company from 4 to 140 people and watched many strong engineers step into management for the first time. Today I coach engineering managers, directors and CTOs as an ICF Professional Certified Coach. The pattern is consistent: new managers don’t struggle because they lack ability. They struggle because the human side of the job feels like undocumented code running in the background. A good coach helps you document it.
What a new engineering manager actually works on in coaching
Before you compare coaches, know what you will be working on. In my experience, these topics come up again and again in the first six months:
- Letting go of the code. Deciding what you still do hands-on, and accepting that your best contribution is now unblocking others, not being the best engineer on the team.
- Delegation. Spreading work beyond the two or three people you trust most, and growing everyone else so the team stops depending on them.
- One-on-ones and feedback. Running one-on-ones that aren’t status updates, and giving direct feedback to people who were your peers last month.
- Reading people, not just systems. Noticing when a “performance problem” is really a person in the wrong seat. I use a simple four-question routine for this, described in Self-Awareness in Leadership: A Debugging Approach.
- Managing up and across. Setting expectations with product, other teams and your own manager, and saying no without burning trust.
- Visibility. Making your team’s work understood by the people who decide on budgets and promotions. See Why Engineering Leaders Struggle With Visibility.
- Accountability. Owning outcomes, not just effort, and holding others to that standard without micromanaging. See What Real Accountability Looks Like for Tech Leaders.
If a coach can’t talk concretely about most of these, they are probably a general life or career coach. That can be valuable, but it isn’t what a new engineering manager needs first.
Six things to look for in a coach
1. They have led engineers, or at least worked closely with them
You shouldn’t have to explain what a sprint, an on-call rotation or a reorg feels like. A coach who has led technical teams asks sharper questions, recognizes the paths the industry has already proven to be dead ends, and earns your trust faster. That matters, because engineers tend to discount advice from people who “don’t get it”.
2. They hold a recognized coaching credential
Experience tells you the coach understands your world. Training tells you they can coach, not just tell war stories. The International Coaching Federation (ICF) offers three credentials, ACC, PCC and MCC, each requiring training hours, logged client hours and an assessment. You can verify any credential in the ICF directory.
3. They have worked with first-time managers specifically
Coaching a new engineering manager is different from coaching a CEO. Ask how many first-time managers they have worked with and what changed for them. Good answers are specific: “she stopped reviewing every pull request and her team’s cycle time improved,” not “they grew a lot.”
4. They coach rather than just advise
A mentor shares what worked for them. A coach starts from your situation and helps you find the answer that fits it. You need both, but advice drawn from someone else’s path often doesn’t transfer. One company’s culture doesn’t work in another. The best coaches for technical people mix the two: mostly questions, plus a relevant story from their own experience when it helps you decide.
5. The structure is clear
Agree on cadence (every week or every two weeks works well in the first months), session length, how you can reach them between sessions, and how you will measure progress. Two or three written goals at the start, reviewed every month or so, keep the work from drifting into pleasant conversation.
6. You can be honest with them
Coaching only works if you can say “I don’t know what I’m doing” out loud. Pay attention to how the first call feels. If you’re filtering what you say, keep looking.
Questions to ask on the first call
- Have you managed engineers yourself? What was hardest for you as a new manager?
- How many first-time engineering managers have you coached, and what changed for them?
- What does a typical session look like? How much is questions, and how much is advice?
- How do we set goals and track progress?
- How often do we meet, and can I reach you between sessions when something blows up?
- If my company pays, what do you share with my manager or HR?
- How is pricing structured, and how long do engagements usually run?
Red flags
- Guaranteed outcomes. No coach can promise you a promotion in 90 days. They can promise structure, honesty and accountability.
- One framework for everyone. If the program is identical for every client, it isn’t built for your team, your company or you.
- Vague answers about confidentiality. You will be talking about your boss, your peers and your own doubts. The rules have to be clear before the first session.
- No interest in your context. A coach who doesn’t ask about your team size, your stage of company and your manager is guessing.
If your company is paying
Many companies cover coaching for new managers from a learning and development budget. It is worth asking, especially in your first year. When the company pays, a good setup has three parts:
- A short three-way goal-setting conversation between you, your manager and the coach, so everyone agrees on what success looks like.
- Confidential sessions. What you say in coaching stays between you and the coach.
- A progress check partway through and at the end, where you, not the coach, share what has changed.
If the coach or the company wants detailed session reports, that is performance management, not coaching. Push back.
When to start, and how long it takes
The best time is in your first three months as a manager, before habits set. The second-best time is when something isn’t working: a team member you can’t reach, a stakeholder who keeps escalating, or the feeling that you’re working harder than ever and getting less done. Many new managers start with 6 to 12 weeks of sessions every week or two, then decide whether to continue as their scope grows.
Key takeaways
- Look for engineering leadership experience plus a coaching credential. One without the other is half a coach.
- Check that they have coached first-time managers, and ask for specific examples of what changed.
- Agree on two or three written goals at the start and review them regularly.
- Settle confidentiality up front, especially when your company pays.
- Use the first call to test fit. If you can’t be honest with them, they can’t help you.
Frequently asked questions
Do new engineering managers really need an executive coach? Not everyone does, but the move from engineer to manager is the biggest role change most people in tech make, and most get no training for it. A coach shortens the trial-and-error period and gives you a confidential place to think through decisions you can’t discuss with your team.
What’s the difference between a coach and a mentor for a new manager? A mentor shares what worked in their own career. A coach works from your situation and goals and helps you decide what fits. Many new managers benefit from both. For a fuller comparison, see Tech Career Coach: What They Do and How to Find the Right One.
Should my coach have a technical background? It helps a lot. A coach who has led engineers understands your constraints and earns credibility with you quickly. A coaching credential matters too, because it shows they can coach and not just give advice.
How much does coaching for a new engineering manager cost? It varies with the coach’s experience, session frequency and engagement length. Many coaches, including me, offer a free first call where pricing is discussed openly. Ask whether your company has a learning and development budget that covers it.
Can coaching be done remotely? Yes. All of my coaching is remote, and video sessions make it easier to keep a regular rhythm around a busy schedule.
Talk it through
If you’re a new engineering manager, or you’re promoting someone into the role, tech leadership coaching gives you a confidential thinking partner who has led engineering teams himself. For a quick read on your strengths and gaps first, take the free Tech Leader Assessment. When you’re ready, book a free 30-minute discovery call and we’ll work out together whether coaching is the right step.