Career conversations with your manager are discussions about where you want your working life to go and how that direction fits with your role. They are not automatically requests for promotion. Nor are they a reason to pretend promotions do not matter. The starting point is understanding what you actually want, rather than borrowing someone else's definition of success.
Most people I work with actively seek promotion or career advancement. That is my experience, not a measured statistic about engineers. It matters to take those ambitions seriously. It also matters not to assume that every person wants more responsibility at every point in their life.
An employee and a manager can both care about the person's future while picturing different destinations. Useful career conversations make those differences visible. The aim is not to settle your entire career in a single one-on-one, but to understand your interests, the expectations you need to meet, and the possibilities worth exploring together.
Start Career Conversations With the Work You Want
A title can be a meaningful goal, but it leaves important questions unanswered. What attracts you to it? The kinds of decisions you would make? Greater influence over a product? More recognition for your contribution? Those motivations may overlap, but they are not interchangeable.
In my discussion about not constantly chasing promotions, I explain that my own motivations are not superior to someone else's. Being excited about broader responsibility does not make that the correct ambition for every engineer.
Try describing the substance of the future you want. You might be interested in understanding customers better, becoming more capable in a particular domain, or taking responsibility for decisions that cross team boundaries. You do not need a perfectly named destination to explain an interest.
These distinctions help your manager understand what an opportunity would actually do for you:
- An interest identifies something you want to understand or contribute to.
- A desired responsibility identifies something you want to own.
- A promotion goal identifies a formal outcome you want to pursue.
None of those is a substitute for the others. A project might satisfy your curiosity without changing your responsibilities. Another might expand your responsibilities without matching your interests. Saying which part matters gives the discussion something more useful than an assumed preference for whatever comes next.
This is also why lessons from earlier career experiences can be useful context without becoming instructions to copy another person's path. Someone else's lessons may help you notice a question you had not considered. They cannot decide what you should value.
Separate Desired Responsibility From More Work
Wanting broader responsibility is not the same as wanting a larger pile of assignments. An engineer might want to make decisions about a problem rather than complete more tasks selected by someone else. Another might want deeper technical work rather than more coordination.
For a hypothetical example, imagine an engineer who enjoys understanding complicated failures. They are interested in developing stronger judgment about reliability, but not in managing a group. Giving them more routine tickets does not necessarily serve that interest. Neither does assuming they should pursue management because they are doing well.
Career conversations can examine what a responsibility involves before treating it as attractive. Ownership might include ambiguous decisions, explaining tradeoffs, coordinating with others, or staying accountable after an initial delivery. Those parts can be interesting, challenging, or unwanted. It helps to understand the combination.
Consider the responsibility from more than one angle:
- What decisions would you be expected to make?
- Who would depend on your work or judgment?
- What support would help you take it on?
- What existing work would need to change?
These are considerations, not a required questionnaire. The point is to understand the work behind the label. Wanting an opportunity does not mean agreeing to unlimited additional work, and offering an opportunity does not remove the manager's responsibility to clarify priorities.
When broader influence does interest you, informal leadership in software engineering is one relevant direction to explore. It should be connected to your interests and the team's needs, not presented as the inevitable next move for every capable engineer.
Keep Career Conversations Connected to Role Expectations
Personal goals matter, but they do not replace the responsibilities of your current job. Being less interested in promotion does not mean you can ignore expectations about quality, collaboration, delivery, or developing the capabilities your role requires.
The same applies when you are eager for advancement. An appealing future assignment does not automatically outrank the work the company needs you to do. Career conversations need to connect your desired direction with actual priorities rather than treat them as separate worlds.
This creates two related questions: what is expected of you in the role you hold, and what would you like to explore beyond it? Keeping them distinct prevents a preference from being mistaken for a performance expectation, or an expectation from being mistaken for an optional interest.
My earlier article about job titles and responsibilities provides historical context for why a label alone is not enough. For your own situation, ask your manager to explain the responsibilities and expectations that apply. Do not infer them from another company's titles.
There can be a genuine mismatch. You may prefer a kind of work that the team has little need for, or want to avoid something essential to the role. Naming that mismatch is more useful than assuming either side can wish it away.
The manager should explain constraints clearly, including what is fixed and what can be discussed. The employee can explain preferences and ask about alternatives. Alignment does not require identical ambitions, but it does require an honest understanding of the working arrangement.
Not Wanting More Responsibility Is Different From Not Caring
An employee can care deeply about doing good work without wanting every available increase in responsibility. In my mentoring discussion about individual goals, I acknowledge that some people do not want additional responsibilities even when they come with more money. That is a legitimate preference, not a description of my own motivation.
It would be equally unhelpful to turn that observation into an argument that promotions are unimportant. For someone who wants advancement, formal progression can matter a great deal. The manager needs to understand that ambition rather than redirect it into a conversation the employee did not ask for.
Career conversations should leave room for both positions. Someone may want to become more effective in their existing responsibilities. Someone else may want to expand their scope substantially. Both still need clarity about what the organization expects from them.
A person who does not want a particular responsibility can be specific about the work they do want to contribute. That gives the manager more to understand than a broad refusal of development. It also avoids making the employee defend a private explanation for their preferences.
You do not have to disclose personal circumstances to make a professional preference legitimate. If you choose to share context, that information should be treated as private. The useful discussion can remain about responsibilities, interests, and the support you need.
Uncertainty Is a Starting Point, Not a Missing Qualification
You might know what you enjoy without knowing what that means for your career. You might also have several interests that do not point toward one obvious role. Career conversations can help you investigate those questions rather than demand that you arrive with a completed plan.
In that mentoring discussion, I talk about helping people identify directions when they are already productive but do not know what they want to focus on. Being independent at work does not prove that you have no further interests or needs. It means the manager or mentor may need to look beyond fixing an immediate problem.
Employee agency still matters. Reflecting on what you find engaging, difficult, or worth understanding gives another person something to work with. But reflection is not the same as knowing all the steps. A manager should not respond to uncertainty by withdrawing support.
Possible starting points include:
- Work you would like to understand more deeply.
- Decisions you want to become more confident making.
- Responsibilities you would like to try before committing to them.
- Parts of an opportunity that make you hesitant.
You can bring an incomplete observation and develop it together. The manager can offer context you do not have, notice patterns, and suggest possibilities. That is different from assigning you a destination because it is convenient for them.
The mentoring discussion also emphasizes that direction can become clearer through experience. Trying something may help you discover an interest you could not confidently name beforehand. Uncertainty can narrow over time without being treated as a failure at the beginning.
Look for Timely Opportunities, Not a Universal Roadmap
Once an interest is clearer, career conversations can connect it to work that is actually available. An opportunity is more useful when both people understand why it fits than when it is presented as an unexplained test.
Imagine a hypothetical engineer interested in learning more about how product decisions are made. There may be an upcoming planning discussion where their technical perspective would be useful. Participating could help them understand that work while contributing to a real need. It does not automatically imply a new role or a promised promotion.
The manager should explain the intended responsibility and the support available. The employee can ask what participation would involve and how it fits with existing priorities. Learning through work is relevant here: development can be discussed through real responsibilities, not only as extra study outside working hours.
There may not be a suitable opening. A team's priorities and the employee's readiness can limit what is possible. That does not invalidate the interest, but it means the conversation needs a truthful answer about feasibility rather than encouragement that sounds like a commitment.
If a mentor is involved, keep the guidance connected to the manager's expectations. In that discussion, I also explain why conflicting guidance can leave someone caught between a mentor and their manager. An employee should not have to guess which direction matters when one person encourages work that another considers off-priority.
This is where hands-on management connects to career support: understand enough to help clarify an opportunity without making the employee's thinking irrelevant. Support can include context, introductions, and feedback. It is not a guarantee of the eventual outcome.
Revisit Direction When There Is Something to Learn
Goals can change. A responsibility may look appealing until you experience its less visible parts. An unfamiliar area may become compelling after you work in it. Career conversations need to make room for that information rather than hold you permanently to an earlier preference.
Changing direction does not mean every assignment can be dropped immediately. You still need to discuss commitments, the team's needs, and what a workable adjustment would involve. An honest update is the start of alignment, not an exemption from accountability.
There is no need for a constant overall progress verdict. If the question is whether a kind of work interests you, useful follow-up may come after you have had enough exposure to form a view. If an opportunity is approaching, discussing it before decisions are made can matter more than waiting for a recurring career slot.
Follow-up can focus on:
- What the experience clarified about your interests.
- What was different from your expectations.
- What support or context is still missing.
- Whether the desired direction has changed.
These questions do not require a rigid monthly schedule or a formal tracking system. I recommend returning to those interests periodically, without prescribing a particular interval. Agree on a useful reason to revisit the subject instead of making every meeting another verdict.
Manager follow-through matters as well. If you agreed to investigate an opportunity or clarify an expectation, return with what you learned, including limitations. Career conversations lose continuity when a promising discussion is silently forgotten, even if the original interest remains.
Frequently Asked Questions
The questions below address direction and expectations, not a promotion formula. Different answers can be reasonable for different people.
What are career conversations with your manager for?
They help you understand how your desired future direction relates to your work, responsibilities, and opportunities. Promotion can be part of that discussion when you want it, but it should not be assumed to be the only purpose.
Do I need to know my long-term career goal before discussing it?
No. Interests, uncertainties, and responsibilities you might like to explore are useful starting points. Reflect on your experience and bring what you can identify. Your manager should help clarify possibilities rather than require a finished plan before supporting you.
Is it wrong to want promotion?
No. Most people I work with seek advancement, and that ambition deserves attention. Explain what matters to you about it so the conversation does not rely on assumptions. Respecting other goals does not mean dismissing promotion as unimportant.
Can I prefer my current responsibilities without ignoring expectations?
Yes, but preferences and role expectations need to be discussed separately. Not wanting additional responsibility does not remove the requirement to do your job effectively or develop capabilities the role requires. Ask which expectations apply to your current role and discuss how your preferred responsibilities fit them.
How often should we have career conversations?
Revisit them when new experience, an approaching opportunity, or changing interests gives you something useful to discuss. Do not require an overall career verdict in every one-on-one. The appropriate interval depends on the subject and what both people need to understand.
What if my goals change after I try an opportunity?
Explain what you learned and how your preference has changed. Discuss existing commitments and team priorities before making adjustments. Discovering that a responsibility does not fit can be useful information without making the original exploration a mistake.
Shared Understanding Does Not Require Identical Ambitions
Career conversations are useful when they make your direction clearer without pretending your manager can choose it for you. Interests, responsibility, and formal advancement belong in the discussion, but their importance differs from person to person.
Start with what matters to you, understand what your role requires, and stay open to what experience teaches you. The manager's responsibility is to listen, clarify, support, and follow through. Together, you can understand a possible direction without promising an outcome or assuming that the same destination suits everyone.