The career conversation that most managers have sounds something like this: a direct report doesn’t get the promotion they expected, or they get it but felt the process was opaque, or they come in and say they’ve accepted a role somewhere else. And then the manager has a very intense, very real conversation about what that person actually wants from their career, what they see as their next step, whether there’s something that could have been done differently.
It’s a useful conversation. But it’s almost always happening too late, under conditions that make honesty harder on both sides and action nearly impossible.
I’ve been thinking about this for a while, and what I’ve come to believe is that timing is a symptom, not the root cause. The deeper problem is organizational: most engineering teams don’t treat career conversations as a structured, recurring manager function. They’re not on a calendar. They’re not expected at set frequencies. They happen reactively — triggered by a promotion cycle, a departure signal, or a visible drop in engagement — rather than proactively, as part of how the team operates. That’s an organizational maturity problem, not just an individual manager failure. Mature engineering organizations build career conversation cadences into their operating model the way they build performance cycles or sprint reviews. They treat it as infrastructure, not improvisation. When it’s left to individual initiative, it happens unevenly — reliably on the teams that need it least, sporadically everywhere else.
What a career conversation is not
The thing that passes for career conversation in most 1:1s is status-and-growth-flavored check-in. “How are you feeling? What’s your biggest challenge? Is there anything you want to work on?” These are fine questions. They’re not career questions. Career questions are more specific and often harder to ask, because they require you to go somewhere the person might not be ready to go, or where you might not like what you hear.
What I actually ask in a career conversation — one I’ve deliberately framed as distinct from our regular 1:1 — is something like: Where do you want to be in three years? Not in terms of title (though that’s part of it), but in terms of the work you want to be doing and the problems you want to be working on. What’s the thing you’re most energized by right now? What’s the thing you’re least energized by? If you imagine yourself still here two years from now, what would need to be true for that to feel like the right choice?
That last question is the one that tends to open things up. People have usually thought about this more than they let on. They have an answer. The question gives them permission to say it.
The trap of assumed ambitions
One of the most consistent mistakes I’ve seen managers make — and I’ve made it myself — is assuming they know what someone wants. This person is great technically, so obviously they want to move into a principal engineer role. That person has been managing for two years, so obviously they want to manage a bigger team. These assumptions feel reasonable from the outside, and they’re often wrong.
I’ve had engineers tell me, when I finally asked directly, that they had no interest in becoming principal engineers — they wanted to move into product or into people management, and they’d been quietly trying to figure out how to bring that up. I’ve had managers tell me they’d love to move back to being individual contributors, that they’d tried management and it wasn’t what they expected, and they’d been afraid to say so because they thought it would look like failure.
None of this came out in regular 1:1s. It came out when I explicitly created space for it and made clear I wasn’t going to be alarmed by the answer. The explicit framing matters: “I want to understand what you actually want, not what you think I want to hear.”
The conversation I wish had happened earlier
A few years ago, I watched someone on a team I was close to leave a role that, in retrospect, they’d been trying to leave for over a year. Not the company — just the specific function. They wanted to move into a different area. They’d mentioned it once or twice in passing, but it never got picked up as a serious conversation item. Their manager assumed they were happy where they were, largely because they were performing well.
By the time it became explicit, the person had already mentally moved on. The conversation that happened then was good, but it was about managing a transition, not about designing a path. The version of that conversation that could have happened a year and a half earlier might have actually changed the outcome — not by keeping them in the role, but by creating a real path into the area they wanted to move into, within the organization that was trying to keep them.
I think about that one a lot. The conversation wasn’t hard. The manager wasn’t malicious or even particularly inattentive. It just never got scheduled, never got made explicit, and by the time it did, the opportunity had passed.
Schedule the career conversation before you need to. Put it on the calendar with enough lead time that neither of you is there because something is wrong. You’ll be surprised how much you learn, and how much easier it is to actually help.
And if you’re in an organization where this isn’t a top-down expectation — where recurring career conversations aren’t mandated, trained for, or built into how managers operate — don’t just do it quietly in your own team and call it done. Push for the change organizationally. Raise it in leadership forums. Make the case that this is an organizational capability gap, not a personal style preference. The managers who care about this tend to do it regardless of whether the org requires it. That’s not enough. The ones who don’t care, or don’t know better, are running teams around yours, and their engineers are the ones who will leave before anyone understands why.