Why Most Managers Avoid Them

Career conversations are uncomfortable in a specific way that most managers have not learned to manage. The discomfort is not about technical difficulty - most managers know enough about their engineers' work to have a useful conversation. The discomfort is about stakes and uncertainty.

When a manager sits down to talk about an engineer's career, several things can go wrong in ways that have real consequences. The engineer might want to go somewhere the organisation cannot take them. The manager might not know how to help. The engineer might be more ambitious than their current performance warrants, and acknowledging the ambition without validating it feels cruel. The engineer might want the manager's job. The engineer might want to leave, and asking the question feels like handing them the permission to do so.

These concerns are real. They are also, in aggregate, a reason why engineers rarely have the conversations that would most help them - and a reason why organisations lose people they did not need to lose.

The Silence Is Not Neutral

A manager who avoids career conversations is not preventing the engineer from having career ambitions. They are preventing themselves from knowing about those ambitions, influencing them, and creating the conditions that might satisfy them. The ambitions do not disappear because they are not discussed. They find other outlets - a LinkedIn message from a recruiter, a conversation at a conference, a growing sense of stagnation that becomes a resignation.

The data on this is consistent: engineers who feel their manager is invested in their career development are significantly more likely to stay. Not because the manager solved their career problems, but because the conversation itself signals investment. Most engineers do not expect their manager to have all the answers. They expect their manager to give a damn.

Conflating Career Conversations with Promotion Decisions

One reason managers avoid career conversations is that they conflate them with promotion decisions. In this conflation, asking "where do you want to go?" implies a commitment to help get them there - and if the organisation cannot currently offer a promotion, the manager does not want to raise expectations that cannot be met.

This is a category error. A career conversation is not a commitment. It is information-gathering and relationship-building. A manager who says "I can't promote you right now, but I'd like to understand what you're hoping for and what we can work on together in the meantime" is not raising false expectations. They are being honest about constraints while demonstrating genuine interest.

Treating career conversations as implicitly dangerous because they might surface unsatisfiable ambitions is letting the fear of an uncomfortable outcome prevent a necessary conversation. The outcome of not having the conversation is usually worse than the outcome of having it honestly.

The Three Career Conversation Types

Career conversations are not a single type of conversation. There are three distinct conversations, each serving a different purpose, and each needing to be its own dedicated time rather than a point on a 1:1 agenda.

Conversation 1: Where Are You Now?

This conversation is about honest, grounded assessment of the present. Where is the engineer in their career? What are they good at, and what do they know it? What are the gaps, and how aware of them are they? What is satisfying about the current work? What is frustrating? What are they not getting that they need?

The goal is to build an accurate shared picture of the current state. Not the official picture (title, level, salary) but the real picture (how they are experiencing the work, where they feel energised and where they feel flat, what they are learning and what has become routine).

The manager's role in this conversation is primarily to listen. To ask questions that invite honest reflection. To surface what has been implicit. Not to evaluate or assess - that is a different conversation - but to genuinely understand.

Useful questions for this conversation:

• "What kind of work have you been doing in the last six months that felt most engaging? What was it about that work?"
• "What have you been doing that has felt like a grind? What is it about that that's draining?"
• "What are you learning right now? What has become routine?"
• "When you're doing your best work - what does that look like? What are the conditions?"
• "What are you not getting from this role that you need?"

What this conversation is not: a performance review. The manager is not there to assess whether the engineer is doing their job well. They are there to understand how the engineer is experiencing their work. These are related but different things.

Conversation 2: Where Do You Want to Go?

This conversation is about the future - specifically, what the engineer wants from their career, not just from their current role. It is the conversation most managers find most uncomfortable, because the honest answer is sometimes "somewhere this organisation cannot take me" - and managing that information is genuinely difficult.

The goal is to understand the engineer's genuine ambitions and aspirations. Not their diplomatic answer ("I want to grow in my current role and contribute more") but their real answer, which usually requires more than one question to surface.

Useful questions for this conversation:

• "If you imagine yourself ten years from now, doing work that's genuinely meaningful and satisfying - what does that look like? What kind of problems are you working on?"
• "What kind of engineer do you want to be? What does excellent look like, in your mind?"
• "Is there a person in this organisation - or elsewhere - whose career or role you look at and think 'I want that'? What is it about what they do that appeals to you?"
• "If you had complete freedom to design your next two years, what would you prioritise?"
• "Are there things you want to do in your career that you're not currently doing - or not doing enough of?"

The manager's role in this conversation is to listen without editorialising. Not to immediately assess whether the ambition is realistic, not to immediately map it to what the organisation can offer, and not to discourage ambitions that feel misaligned with where the organisation is heading. Listen first. Understand first.

What makes this conversation fail: the manager who responds to every expressed aspiration with "well, we don't really do that here" or "I'm not sure that's realistic given your current level." These responses shut down honesty. If an engineer has learned that expressing ambitions leads to being evaluated and managed, they will stop expressing them - and the manager will lose the information they need to be genuinely useful.

Conversation 3: How Do We Close the Gap?

The third conversation is where the first two come together. You have a clear picture of where the engineer is now. You have a genuine understanding of where they want to go. The third conversation is about the gap between those two things, and what can realistically be done about it.

This is the planning conversation. It should be the most concrete, the most specific, and the most action-oriented of the three. It should produce a development contract - specific, time-bound, honest about what the organisation can and cannot offer.

Useful framings for this conversation:

• "Based on what you've told me, here's how I understand the gap between where you are and where you want to go. Does that feel accurate?"
• "Here are three or four things I think would meaningfully close that gap over the next 12 months. What do you think?"
• "There are things on your list that we can address directly in your current role. There are things that would require a role change. And there are things that might require a different organisation. I want to be honest with you about which is which."
• "What do you need from me specifically? What can I do that would make the biggest difference?"

The development contract that comes out of this conversation should specify: what capability will be developed, through what mechanisms, over what timeframe, with what checkpoints, and with what organisational commitment from the manager.

How to Prepare

What the Manager Should Know Before the Conversation

A career conversation conducted without preparation is a conversation about nothing in particular. The manager who walks into a career conversation without having thought about it will fill the vacuum with well-intentioned but vague encouragement that does not actually help the engineer.

Know where the engineer is operating. Before the conversation, have a clear view of the engineer's current capability level, their recent track record, their strengths and their development areas. This is not about being prepared to assess - it is about being prepared to be honest when asked.

Know what opportunities are available. Career conversations quickly become frustrating when the manager cannot connect aspirations to actual opportunities. Know what stretch assignments are coming up in the next six months. Know what the headcount plan looks like. Know whether there are any cross-team opportunities that would suit the engineer's development needs.

Know the organisation's constraints. If the engineer wants to move into a leadership role and there are no leadership vacancies on the horizon, the manager needs to know this before the conversation, not halfway through it. Discovering mid-conversation that you cannot offer what the person wants leads to either false hope or an awkward retreat.

Have read back through any previous career conversations. If this is not the first career conversation, the manager should know what was discussed previously, what was agreed, and whether those agreements were honoured. Walking into a second career conversation without referencing the first signals that the first conversation was not taken seriously.

What the Engineer Should Reflect On

Career conversations work better when both parties have prepared. The manager should communicate that preparation is expected - and ideally provide specific reflection prompts in advance.

Useful reflection prompts for engineers:

• What has energised you in the past 12 months? What has drained you?
• What are you most proud of in your recent work? What do you wish had gone differently?
• Where do you feel confident in your capabilities? Where do you feel less certain?
• What would you like to be doing more of? Less of?
• If you think about the engineers you most respect or aspire to be like - what is it about them that you admire?
• What does success look like for you in two years' time?

Preparation is not about having the right answers. It is about creating the conditions for an honest conversation by having done the reflection beforehand rather than doing it in real time under the pressure of the conversation itself.

Listening for What's Not Said

Career conversations have two layers: what is said, and what is underneath what is said. A manager who is only listening to the surface layer is missing most of the information.

Boredom Disguised as Dissatisfaction

An engineer who expresses dissatisfaction with the team, the process, or the technology is sometimes communicating boredom. Dissatisfaction has an outward orientation - it is about what is wrong with things external to the engineer. Boredom has an inward orientation - it is about the absence of challenge or stimulation.

Engineers who are bored will frequently attribute their disengagement to external factors, not because they are dishonest but because boredom is sometimes difficult to recognise in oneself. "The retrospectives are a waste of time" may be true, but it may also be a proxy for "I am not being stretched and I have lost interest."

The question that surfaces this: "If we fixed everything you're frustrated about - the process, the technology choices, the team structure - would you feel genuinely satisfied in this role?" If the honest answer is no, there is something deeper to explore.

Ambition Disguised as Frustration

An engineer who is frustrated with decisions being made above them - technical decisions they disagree with, strategic direction they feel is wrong, management approaches they think are ineffective - is sometimes expressing ambition that has nowhere to go.

The frustration with others' decisions is sometimes a proxy for "I think I could make better decisions, and I have no way to do that from where I sit." This is not arrogance - it may be an accurate assessment. The productive response is not to defend the decisions being criticised but to explore what the engineer would do differently and why, and to use that conversation to understand their leadership ambitions.

The question that surfaces this: "What would you do differently if you were in that position? And is that something you'd want to be doing?"

Burnout Disguised as Disengagement

An engineer who seems disengaged - giving shorter answers, less enthusiasm, reduced initiative - may be describing burnout rather than genuine career dissatisfaction. Burnout and career dissatisfaction can look identical from the outside, but they have different root causes and different solutions.

The signals that point toward burnout rather than career dissatisfaction: the disengagement is relatively recent and represents a change from previous behaviour; the engineer used to be enthusiastic about work that is now described in flat or negative terms; there have been external stressors (sustained overwork, a difficult project, personal circumstances) that coincide with the change in energy.

The career conversation is not the venue for diagnosing burnout, but a manager who is alert to the distinction will avoid offering career development solutions to a problem that is actually about recovery and sustainability.

The question that surfaces this: "I notice things feel different from how they did six months ago. What's changed for you?"

The Answer That Is Too Clean

An engineer who gives a very polished, very reasonable-sounding answer to career questions - "I'm happy where I am, I just want to keep doing good work and develop my skills" - may be giving the answer they think the manager wants to hear, or the answer that feels safest.

The clean answer is not necessarily dishonest, but it is worth gently exploring. "That's a helpful start - can you tell me more about what 'developing my skills' looks like in your mind?" or "Is there anything you're not saying that you'd like to?" can invite more honesty without pressuring it.

Building a Development Contract

A development contract is the concrete outcome of a career conversation. It is not a development plan in the HR system sense - a list of training courses and competency targets. It is an agreement between the manager and the engineer about what will happen, who will do what, and what success looks like.

What a Good Development Contract Includes

The development goal: a one-sentence statement of the capability to be developed, connected to where the engineer wants to go. Not "improve communication skills" but "build the capability to lead cross-team technical initiatives independently, including stakeholder management and dependency coordination."

The organisational commitment: what the manager is committing to provide. A specific stretch assignment, access to a particular stakeholder, introductions to relevant senior engineers, time for a community of practice. The contract is bilateral - it is not just a set of expectations for the engineer.

The engineer's commitment: what the engineer is committing to do. The specific actions, the stretch they are taking on, the feedback they will seek. Not "try harder" but "lead the design of the authentication service refactor, produce a design document by end of Q1, and facilitate a design review with both engineering teams."

The evidence of success: how both parties will know the development is happening. What will be observable? What will have changed? What artefacts or outcomes will demonstrate progress?

The review cadence: when will progress be assessed? A development contract with no review mechanism is a document, not a contract.

The honest caveat about limitations: where the organisation cannot provide what the engineer wants, the contract should be honest about that. "I can create opportunities for you to develop leadership capability in your current role, and I'll advocate for you when leadership opportunities arise, but I can't promise a TTL role in the next 12 months because we don't currently have the headcount."

The Difference Between a Plan and a Promise

A development contract is a plan, not a promise. The manager is committing to create conditions and opportunities - not to guarantee outcomes. This distinction matters for two reasons.

First, circumstances change. A stretch assignment that was planned for Q2 may not survive a Q1 restructure. A leadership opportunity that was on the horizon may disappear when headcount plans change. A manager who has been explicit about the plan-not-promise nature of the contract can handle these changes without having broken a commitment. A manager who has been vague about this will be seen as having failed to deliver.

Second, outcomes depend on the engineer as well as the manager. The manager can create the stretch assignment. Whether the engineer develops the capability through it depends on how they approach it. A development contract that acknowledges this - "I'll create the opportunity; whether it develops the capability depends on how you engage with it" - is more honest and sets more appropriate expectations.

Frequency and Follow-through

How Often

Career conversations should happen three to four times a year, separate from 1:1s, performance reviews, and project retrospectives. The three types of career conversation (where are you now, where do you want to go, how do we close the gap) do not all need to happen at the same frequency or on the same schedule.

A useful cadence:

• Annual: a full "where are you now and where do you want to go" conversation, producing or updating the development contract
• Quarterly: a progress review against the development contract - what is working, what is not, what needs to change
• As needed: any conversation prompted by a significant career-relevant event (a promotion, a role change, a performance concern, a significant piece of work)

The annual cadence is a minimum, not an ideal. Engineers who are at a significant career inflection point - considering the IC/leadership fork, exploring a move to a different domain, navigating a promotion decision - need more frequent career conversation support, not less.

How to Track Progress

Development without tracking is aspiration. The manager needs a mechanism for monitoring whether the development contract is being executed.

The simplest mechanism: a standing item in the monthly 1:1 agenda that asks one question: "How is your development plan going?" This takes five minutes and ensures the conversation happens regularly. The development contract itself should be a living document - updated when circumstances change, not left static until the next formal review.

The manager should also track their own commitments. If the development contract includes "manager will introduce engineer to the platform team's technical lead by end of Q1," that needs to be in the manager's own action items, not just the engineer's. A development contract where the engineer fulfils their commitments and the manager does not fulfil theirs is a trust-breaking event.

The "We Talked About It Once" Failure Mode

The most common failure in career conversations is the conversation that happens once - a genuine, honest exchange about where the engineer wants to go - and then is never referenced again. The engineer remembers it. The manager does not. Six months later, the engineer is still waiting for the stretch assignment that was discussed. The manager has moved on and forgotten the conversation ever happened.

The fix is simple: write it down, share it, and schedule the follow-up in the same conversation. "Here's what I'm hearing from you. I'm going to write up a summary of what we've agreed and share it with you by end of week. I'll also put a 30-minute check-in in the diary for the end of next quarter so we can assess how it's going." Then do those things.

When the Answer is "Not Here"

The hardest career conversation is the one where honest engagement leads to the conclusion that what the engineer wants is not available at the current organisation. They want to lead a team and there are no leadership openings. They want to build ML infrastructure and the organisation does not do that work. They want to work on problems at a scale the organisation will not reach in the timeframe that matters to them.

Most managers handle this situation by avoiding the honest conclusion - by promising that things might change, by redirecting toward what is available rather than what the engineer wants, or by letting the conversation go quiet. The result is that the engineer eventually leaves anyway, but later, after a period of growing frustration and declining engagement.

How to Have the Honest Conversation

The honest conversation is better for the engineer and, counterintuitively, often better for the organisation.

Name what you are hearing. "What I'm hearing is that you want to be doing X, and I don't think I can provide that in the current role or team. Let me be straight about that rather than pretending otherwise."

Acknowledge the constraint without apologising for the organisation. The constraint is real. It is not a failure of the organisation or the manager - it is a mismatch between what the engineer wants and what is currently available. Acknowledging it clearly is more respectful than managing it evasively.

Explore the partial fit. Sometimes the engineer wants something the organisation cannot fully provide but can partially provide. "We can't give you a leadership role right now, but we can give you a meaningful amount of leadership experience through mentoring, project leadership, and cross-team initiative ownership. Would that be sufficient for now, or is the full role what you need?"

Be honest about the timeline. If the thing the engineer wants is genuinely unavailable for the next two years, say so. "The honest answer is that we're not planning to hire another EM until we grow the team significantly, and that's 18 to 24 months away if everything goes well. I want you to make an informed decision about whether that timeline works for you."

Offer to support the transition. This is the part most managers least want to say, but it is often the most powerful thing they can offer. "If you decide that this organisation isn't the right place for the next stage of your career, I will be honest about that and I will support you in making the best move for you - including giving you an honest reference and helping you think through what the right next role looks like." A manager who says this and means it earns enormous trust - and often retains the engineer longer than if they had been evasive.

What You Often Gain

The engineering organisation that is honest about what it can and cannot offer, and that supports engineers in making good career decisions even when that means leaving, is an organisation people want to work for. The engineers who stay will know they have chosen to stay with full information. The engineers who leave will speak well of the organisation. The alumni network is one of the highest-quality talent pipelines available - and it is built on honest relationships, not management of information.

Connection to Your Operating Model

Career conversations are the human mechanism through which the rest of the career and capability system becomes real.

Career pathways describe the landscape of possible progression. Career conversations are how individual engineers navigate that landscape with the support of someone who knows both the terrain and the person. Without the conversation, the pathway is a document the engineer reads alone and tries to apply without context.

Capability frameworks provide the language for honest assessment. A manager who has a career conversation and says "at the ISE level, what I'm looking for in delivery capability is..." is using the framework as a tool rather than as bureaucracy. Without the framework, the conversation is vague. Without the conversation, the framework is academic.

Learning and development is what the career conversation produces. The development contract is the bridge from conversation to action. A career conversation that does not produce a specific development plan has created clarity but not progress.

Promotion and levelling decisions should be anticipated and unsurprising as a result of regular career conversations. An engineer who receives a promotion should already know, from career conversations, that they are operating at the next level and that a strong case exists. An engineer who does not receive a promotion should already know, from career conversations, where the gap is and what is needed to close it. Both outcomes should have been discussed before they happen, not announced after.

The career conversation is not a separate element from the rest of the operating model. It is the connective tissue - the mechanism through which individual engineers engage with the system, and through which managers translate policy and framework into genuine human support.