liveBook · Manning

Career conversation

As explained in Think Like a Software Engineering Manager

A career conversation is a structured discussion about an employee’s motivations, aspirations, development, and career path.

An engineer may be delivering good work while feeling unsure about what comes next. A career conversation gives the manager and employee space to discuss motivations, aspirations, blockers, and opportunities for growth. It can happen during a private one-on-one or a performance review, but it should not be a one-time event. section 1.1.1 section 4.3.3

Keep the conversation supportive and useful:

  • Start with an open question such as “What’s top of mind for you?” Listen for the employee’s priorities rather than arriving with a path already chosen. section 3.1.1
  • Explore what motivates the employee, where they want to grow, and what might be blocking them. section 1.1.1
  • Discuss opportunities and actionable feedback. Use SMART as a flexible starting point for a goal that fits the individual, not as a rigid template. section 3.1.1
  • Return to the career road map in later conversations. A performance review can celebrate achievements and identify improvement areas, but it need not carry the whole discussion. section 4.3.3 section 3.1.1

Make a goal discussable

“Improve support” is difficult to assess. “Reduce trouble tickets by 20%” gives the pair a measurable result to discuss. They should also clarify who will act, what steps they will take, and what support is available, then check that the goal is realistic for this employee. section 3.1.1

Table 3.1 A competency matrix representing a sample gap analysis document
Competency
How do you demonstrate it?
Status (To do, In progress, Done)
Technical skills. Employee should be adept at coding and system design and have experience with large-scale system designs.
Situation 1—Dave was tasked with delivering a project to build a continuous data streaming service due to the missing mechanism.
Behavior—Dave stepped up to understand the problem statement and did a deep dive into the architecture design. He worked with senior engineers on the team and developed a technical design document detailing the pros and cons of each approach. Next, he implemented the project under a tight deadline.
Impact—His efforts led to a timely launch of the streaming service and helped reduce message latency by more than 80%.
Situation 2—<>
Behavior—<>
Impact—<>
Done
Participation in technical events.
Situation 1—<>
Behavior—<>
Impact—<>
In progress
Sharing learnings and expertise with cross-functional partners and having influence across teams.
Situation 1—<>
Behavior—<>
Impact—<>
In progress
Helping to improve operational excellence metrics for the team.
Situation 1—<>
Behavior—<>
Impact—<>
To do

A sample competency matrix shows how to record a skill, evidence of its demonstration, and a status such as to do, in progress, or done. It can make a development gap easier to discuss concretely. section 3.1.1

The aim is not to prescribe a promotion timetable. Ask what the employee wants to develop, agree on a useful next step, and revisit it with empathy and constructive feedback. section 3.1.1 section 2.5.9

How Think Like a Software Engineering Manager covers it

How deep it goes
Gives practical prompts and flexible SMART goal-setting guidance, while treating career planning as an ongoing conversation rather than a rigid template.
Examples
Uses an open one-on-one question, a measurable trouble-ticket goal, and a sample competency matrix.
What you can do after
Practice/perform career conversations using open questions, individualized goals, and recurring check-ins.
How it connects
Links career conversations to one-on-ones, performance reviews, coaching, mentoring, and constructive feedback.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.