Engineering Manager Coaching for the IC You Just Promoted
Your best engineer now has a team. Ninety days of structured coaching to work out what they hand over, what they pick up, and which named person ends up holding the rest.
Engineering manager coaching is structured support for a newly promoted engineering manager, usually 90 days, that works through what the person stops owning as an individual contributor and who on the team receives each piece.
The promotion conversation almost never covers that part. Somebody gets told they are ready, they get the title, they get a heavier set of one-on-ones on the calendar, and then they go back to their desk and pick up the same ticket they would have picked up the week before. Nobody told them to stop. Nobody told them what to stop.
So they keep going. And they do it well, because they are good at it, which is the whole reason anybody promoted them, and six weeks later they are carrying two jobs and losing ground on both while their team quietly learns to wait for them. Nobody plans that.
That gap is what this page covers. We put a senior engineering leader alongside your new manager for a quarter, and the work is an inventory rather than a pep talk. What comes off the plate. What goes on it. Who catches the thing that came off. If the answer to that last one is nobody, the duty comes back inside a month, and that is the most reliable pattern Kris Drouet has watched across 25 years of running engineering organizations in fintech and mortgage tech.
KORE1 built the engagement around his framework because our engineering staffing desk kept getting the call a year late, after a good engineer had already been promoted, quietly ruined, and lost. His own write-up of the sit-down at the center of it is the coaching conversation that salvages a promoted IC. Worth reading first.
Nobody Fails at This Because They Lack the Skills
They fail because the reflexes that made them worth promoting are the same reflexes that now make them a bottleneck, and a reflex does not respond to a title change. A senior engineer sees a stuck build and fixes it. That is not a decision, it is a habit built over eight years of being correct. In week one it is still correct. By month four it is the reason two of their engineers have stopped trying. Nobody says so.
Kris puts it plainly. If you are the bottleneck, you are not leading, you are a senior IC with a calendar full of one-on-ones.
The tell shows up somewhere most directors never look. Not in velocity, not in a status report, but in who the team asks. When an engineer hits something ambiguous and their first move is to message the manager rather than the person who actually owns that surface, the handover never happened. It got announced. Those are different things, and an announcement is free while a handover costs a quarter of somebody’s attention and a fair amount of discomfort on all sides. Mostly theirs.
Four Things That Change Hands, and Who Ends Up Holding Them
This is the working document of the engagement. Every line is a pair, because you cannot put something down without deciding what replaces it, and you cannot hand something over without naming who caught it. We fill it in with your manager in week two and revisit it every session after that. Out loud, together.
Eight years of muscle memory says grab the stuck thing. It still works. That is the trap.
Receiver · the two engineers closest to that subsystemFixing the thing takes an hour. Making sure the next one gets fixed without you takes three weeks and nobody claps.
Taking it feels like leadership. It reads to the team as a vote of no confidence in whoever would have gotten it.
Receiver · your strongest senior IC, deliberatelyThere is exactly one every week, and it is the thing a new manager will find eleven reasons to postpone until Friday.
Why the retry logic is strange, which vendor call changed the schema, who signed off in 2023. All of it, undocumented.
Receiver · one document with one name on itA manager who is the only route to an answer has built a queue and called it being helpful.
This is the one that quietly wrecks people. They keep grading themselves on a test they no longer sit.
Receiver · nobody. This one just stops.Count the calls made in the last month that nobody reopened. That is the new number, and it is a slower one to watch.
The pairs are Kris’s, drawn from watching promoted engineers succeed and fail in regulated shops rather than from a curriculum anybody sells. He wrote the long version in the three skills a senior IC has to unlearn to lead, and the decision-rights half of it lives in decision ownership.
What Engineering Manager Coaching Actually Moves
Ninety days, biweekly, one hour. Six sessions and a written handover ledger that belongs to the manager rather than to us. Session one is an inventory of what they are still carrying, and it usually runs long, because the honest list embarrasses people a little. It should.
“Promoting your best IC into management without a real transition plan is how you ruin two careers simultaneously, theirs and whoever has to clean it up after.”
Every session after that names one line on the ledger, agrees the receiver out loud, and sets a date. Not a goal. A date. The check-in is the part that works, because a commitment with no date on it is a preference, and preferences lose to whatever is on fire that week.
A second track runs monthly with the director or VP above them, and we do not sell the coaching without it. Roughly half of what looks like a struggling manager is a mandate nobody wrote down, and coaching someone toward a target their own leadership has not defined is expensive theatre. If that is what is happening, we would rather find it in week three and say so. In writing.
What Sits Behind the Engagement
Retention and time to first submittal are KORE1’s own placement figures, trailing twelve months. The tenure figure is Kris Drouet’s own, and he is a real person with a bio on this site. For the wider picture of the role itself, the Bureau of Labor Statistics Occupational Outlook Handbook tracks computer and information systems managers, and the 2025 Stack Overflow Developer Survey is the widest public read on how engineers describe their own working conditions.
Three Ways Companies Buy This
Most start with the first. A few need the second running alongside it. We bring up the third only when the honest read says the seat needs somebody who has held it before.
Coach the Promotion Into Shape
Four weeks before the title changes. We write the mandate, the decision rights and the stop-doing list while everyone is still calm.
The promotion checklist →Ninety Days With the New Manager
Biweekly sessions against the handover ledger, plus a monthly track with the leader above them. This is the standard engagement.
If it is already wobbling →Hire Somebody Who Has Done It
Some seats need experience, not coaching. We say so in writing before you spend a quarter finding out the slow way.
Engineering manager staffing →
When Engineering Manager Coaching Is the Wrong Tool
Scoping calls go faster when the bad fits get named up front, so here are the four we redirect most often.
If the promotion happened a while ago and something already feels off, you are past the design window and into triage, which is a different engagement with a different clock. That one is engineering leadership transition coaching, and it starts by working out whether you are watching a wobble or a wash-out. If the whole team ships slowly and the new manager is only the most visible part of it, measure the team before you coach the person, either with the free engineering velocity assessment or the staffed engineering velocity diagnostic. Team first.
When several managers are struggling at once, that is not four coaching engagements. That is a structure producing this outcome on purpose, and it belongs to engineering org design advisory. And when the honest answer is that the seat needed somebody who had held it before, we open a search instead, whether that lands as engineering manager staffing, a level up at director of engineering or VP of engineering, or a fractional VP of engineering holding the seat while you decide. Then we fill it.
Kris Drouet on the Myth That Makes This Harder
Kris is VP of Engineering at a mortgage technology company and a contributor here. Twenty-five years of it, nearly all in regulated shops where an undocumented process eventually gets read back to you by an auditor with plenty of time. That world hires differently, which is why mortgage tech and fintech engineering staffing and fractional VP of engineering for regulated industries run as separate desks here.
The myth he pushes back on hardest is that good engineering leaders eventually stop being technical. He watched peers drift away from the craft and become dependent on their teams to tell them what was possible, and he made a different call. Stay close enough to the build that nobody can fool you. He still does. He argues it in full in why the best engineering leaders stay technical.
There is a real tension here worth naming rather than smoothing over, because the honest version of the advice is narrower than either side usually admits. Charity Majors makes the opposite case in The Engineer/Manager Pendulum, arguing you can only really improve at one of the two at a time and that a manager’s job is to get better at management. Both are right, and the line between them is the whole point. Stay fluent. Stop trying to improve as an IC. A new manager who tries to do both is the person we get called about in month seven.
Common Questions
What is engineering manager coaching?
Engineering manager coaching is structured support for a newly promoted engineering manager, normally 90 days of biweekly sessions, working through what they stop owning as an IC and who on the team receives each piece.
Six sessions. One written ledger. A parallel monthly track with the leader above them, because a manager can only hit a target somebody has actually defined. The output belongs to the manager, not to us.
Should we start before the promotion or after?
Before, if you have the choice. Four weeks ahead of the title change is the cheapest version, because the mandate, the decision rights and the stop-doing list get written while nobody is under pressure yet.
Week one after the announcement is nearly as good. Month five is not. What gets expensive is starting once something already looks wrong, which usually means month five, and by then the team has adjusted its own behavior around the gap and you are unwinding two problems instead of one.
Our new manager says they are doing fine. Do we still need this?
Ask their team instead, and ask it a specific way. When somebody hits an ambiguous call, who do they message first? If the answer is the manager rather than the person who owns that surface, the handover has not happened.
Most new managers genuinely believe they are fine at week six, and most of them are, on the half of the job they can still see. It is a good sign, not a warning. It just is not evidence.
Who gets coached, the manager or the person above them?
Both, on different cadences. The new manager works biweekly against the handover ledger. The director or VP above them gets a monthly session, and that track is not optional.
Roughly half of what presents as a struggling manager turns out to be an unwritten mandate, an undecided reporting line, or a set of decision rights nobody ever handed over on paper. None of that is fixable from below. Coaching a manager toward a target their own leadership has not set is how you burn a quarter and produce a very well-coached person who is still stuck. We have watched it.
How is this different from your leadership transition coaching?
This page is the design work, the inventory of what changes hands and who catches it. Our transition coaching engagement is the calendar, built for a promotion already in motion and possibly going sideways.
Same practice, same framework, different question. Ours asks what should move. That one asks whether it is still moving and how long you have. If you are at month four with a tight feeling in your chest, start with engineering leadership transition coaching instead. If the promotion is next month, start here.
Can a new engineering manager keep writing code?
Yes, with one condition. Nothing on the critical path. Small, unblocked, genuinely optional work keeps them fluent, and fluency is most of their credibility with the team.
The failure mode is not writing code. It is owning code somebody is waiting on, because the moment a manager’s week gets eaten by an incident their branch becomes the bottleneck and the team learns to route around the seat. We put a line in the ledger for it and the manager picks the boundary themselves, which they hold to far better than one we would hand them.
What if the coaching shows the promotion was a mistake?
We tell you in writing, and we say it to the manager first. Sometimes the honest read is that the seat needs somebody who has held it before, and stretching the engagement out does not change that.
It happens less often than people expect. When it does, the good outcome is usually a route back into senior IC work with the reputation intact, which is a real path and not a demotion if the company handles it like adults. Some do. The other version is a search, and we run those through engineering manager staffing as a direct hire, or as contract staffing if you want the seat covered while you decide.
Write the Handover Before the Title Lands
One call is enough to tell whether you are looking at a 90-day coaching engagement, a conversation with the layer above, or a search you should open this week.
Talk to an Engineering Recruiter →