Promoted to Engineering Manager? Now What.

Here's how most new engineering managers get started.

You're an engineer. You're good at your job. You mentor a few junior developers. You speak up in planning meetings. You have opinions about process and culture. Someone notices.

So they promote you to engineering manager.

Congratulations. You now have direct reports, a calendar full of 1:1s, and a vague sense that you're supposed to "develop" people. But nobody gave you a playbook. Nobody trained you. Nobody even told you what success looks like in this role.

You're not alone. This is the most common origin story in engineering management, and it's broken.

Tools like a free Slack standup bot can help new managers get daily signal without adding meetings — but the bigger challenge runs deeper.

Why Companies Promote Great Engineers Into Management (and What Goes Wrong)

Companies pick future managers based on two things: leadership potential and communication skills. These are the right signals. If someone can't influence people or articulate ideas clearly, they'll struggle to manage.

But here's the disconnect: being good at leadership and communication as an IC is completely different from applying those skills as a manager.

As an IC, leadership means rallying a team around a technical decision. As a manager, it means navigating underperformance, giving difficult feedback, advocating for promotions, and making calls that affect someone's career.

As an IC, communication means writing clear PRs and explaining architecture decisions. As a manager, it means running productive 1:1s, translating executive priorities into team goals, and having conversations about growth that actually land.

The skills that got you promoted are necessary but nowhere near sufficient.

The Accidental Manager Problem: 82% Get No Training

Most companies invest heavily in hiring experienced engineering managers externally. Job descriptions list years of management experience, leadership frameworks, and coaching certifications.

But when they promote internally? The investment is usually a Slack message that says "congrats" and a link to an HR portal.

A 2024 study from the Chartered Management Institute found that 82% of new managers had no formal management training. They called them "accidental managers": first-time managers who landed in the role by circumstance rather than preparation.

The result is predictable. New managers:

Default to what they know: they keep coding, reviewing PRs, and solving technical problems instead of managing people
Wing their 1:1s: without structure, these meetings become status updates instead of coaching conversations
Avoid hard conversations: giving feedback on underperformance feels impossible when nobody taught you how
Burn out fast: they're doing their old job plus a new one, with no tools for either
Lose their best people: engineers who don't feel supported or developed will find a manager who does

What New Engineering Managers Actually Need to Succeed

The IC-to-manager transition isn't about reading a book on servant leadership (though that doesn't hurt). It's about three concrete things:

1. Context on your people

You can't develop someone you don't understand. What are they working on? How are they feeling? Where are they growing, and where are they stuck? As an IC, you knew your codebase inside and out. As a manager, your "codebase" is your team, and you need the same depth of understanding.

2. Structure for conversations

The best managers aren't the most charismatic. They're the most prepared. Walking into a 1:1 with talking points based on actual data, recent work, goal progress, sentiment signals, makes the conversation productive instead of performative.

3. A feedback loop

As an engineer, you had tests, CI/CD, and code review telling you whether your work was good. As a manager, you often get no signal at all until someone quits. New managers need leading indicators that tell them how their team is doing before problems become crises.

Why Most Management Tools Don't Help New Engineering Managers

When new managers look for help, they usually find two categories of tools:

Enterprise HR platforms (Lattice, Culture Amp, 15Five): these are built for HR teams running company-wide review cycles. They're process tools, not management tools. They'll help you fill out a performance review template, but they won't help you understand what to write in it.

Spreadsheets and docs: the fallback for every new manager. You create a Google Doc for each direct report, try to keep notes, and inevitably fall behind because there's no system pulling information together for you.

Neither category solves the core problem: new managers don't need more process, they need more context.

How Vereda AI Helps First-Time Engineering Managers Lead With Confidence

We built Vereda AI because we lived this IC-to-manager transition ourselves. We were engineers who got promoted, struggled through the same learning curve, and realized the tooling gap was the root cause.

Vereda AI is an AI-powered engineering management platform that gives new (and experienced) managers the context they need to lead effectively:

Async standups with AI analysis: instead of reading 8 standup responses and hoping you catch the important bits, Vereda AI identifies blockers, sentiment shifts, and engagement patterns automatically
1:1 prep that writes itself: before every 1:1, Vereda AI pulls together goal progress, recent activity, standup themes, and conversation history so you walk in prepared, not winging it
Career development context: see exactly what's expected at your engineer's current level and what they need for the next one, so career conversations are grounded in specifics
Early warning signals: risk analysis that flags engineers who might be struggling before it becomes a retention problem
Performance review prep: when review season comes, you have months of structured data instead of scrambling to remember what happened

The point isn't to replace the human judgment that makes great managers. It's to give new managers the same quality of information that experienced managers build up over years of pattern recognition.

Your First 90 Days as a New Engineering Manager

If you've recently been promoted to engineering manager, or you're about to be, here's what the first 90 days should look like:

Days 1-30: Listen and learn

Run 1:1s focused on understanding each person's goals, frustrations, and working style
Set up async standups so you have daily signal without daily meetings
Resist the urge to change processes immediately, earn trust first

Days 31-60: Build structure

Establish a consistent 1:1 cadence with prepared talking points
Start tracking goals and career development conversations
Identify your team's biggest risk: is it a delivery problem, a people problem, or a process problem?

Days 61-90: Start coaching

Give your first round of meaningful feedback based on patterns you've observed
Have your first career development conversation grounded in level expectations
Review your own effectiveness: are your 1:1s productive? Is your team more supported than they were 90 days ago?

The managers who nail this transition aren't the ones with natural talent. They're the ones with the right information at the right time.

Stop Promoting Engineers Into Failure

The IC-to-manager pipeline isn't going away. Engineering organizations will always need to grow leaders from within. That's a good thing, the best engineering managers understand the work because they've done it.

But promotion without support is a setup for failure. It burns out promising leaders, drives away the engineers they manage, and costs organizations far more than the training and tooling would have.

If you're a leader promoting ICs into management: give them real tools, not just a title change.

If you're a new manager reading this: you're not failing because you're bad at management. You're struggling because nobody gave you what you need to succeed. That's fixable.