1:1s, feedback, and career conversations

The recurring meeting with your manager is the highest-leverage conversation you have, and most engineers spend it on the lowest-value content: status their manager could read in the tracker. This chapter is the language of using it properly, plus the adjacent genres nobody practices until the stakes are high: asking for feedback, giving it, asking for a promotion, and talking about money.

The 1:1 is your meeting

The near-universal convention: the report owns the agenda, the manager owns the safety of the room. Bring two or three topics, and say the shape out loud at the start:

"Quick status is in the tracker, so I'd rather spend the time on two things: the on-call load, and a career question."
"Nothing burning this week; can we do a longer-term topic? I've been thinking about where the platform work is heading."
"One sensitive thing this week; I'd like most of the time for it."

Topics that repay the slot: friction ("the review latency from platform is costing us days; can you help me route it?"), context ("what is the pressure behind the Q3 date? Knowing the why would change how I cut scope"), early warnings ("flagging that Ravi and I keep colliding on the API surface; nothing broken yet, but worth watching"), and growth (below). Topics that waste it: reciting the standup you already gave.

Disagreeing with your manager belongs here too, in private first, exactly per Chapter 5: "I want to push back on the staffing call before it's final. Can I make the case?" You get candor credit for the attempt even when you lose.

Asking for feedback

"Any feedback for me?" reliably produces "no, you're doing great", because the question is unanswerably broad and mildly dangerous to answer. Narrow it and it starts working:

"What's one thing about how I ran the design review that you'd change?"
"Was the incident update cadence right, or too noisy?"
"If I want to be trusted with the next migration, what would you need to see first?"

When feedback arrives vague ("be more strategic"), mine it politely for an instance: "Can you point me at a recent moment where I could have been more strategic? An example would help me aim." And when it stings, the professional move is the same as Chapter 5's: receive first, evaluate later. "That's useful and a little painful. Let me sit with it and come back Thursday with what I plan to change." Arguing with feedback in the moment teaches people to stop giving it to you, which is the actual career damage.

Giving feedback: SBI

The standard structure is SBI: Situation, Behavior, Impact. Anchor the moment, describe observable behavior (not character), state the effect:

Peer, corrective: "In yesterday's review (situation), you answered the first three questions before Priya finished asking them (behavior). She stopped contributing for the rest of the meeting, and we lost our storage expert's read (impact). I don't think you noticed, which is why I'm mentioning it."
Peer, positive, same structure: "In the incident (S), you posted updates every fifteen minutes even when nothing changed (B). Nobody pinged the channel asking for status even once (I). That's the standard now, as far as I'm concerned."
Upward: "When the priority changed on Tuesday (S), the team heard it from the PM before you (B), and it read like we were out of the loop on our own project (I). A two-line heads-up would fix it entirely."

Note what SBI removes: verdicts about the person ("you're dismissive", "you're disorganized") that trigger defense and carry no repro steps. It is Chapter 11's description formula applied to humans: observable, specific, scoped.

Don't be confused: a mentor and a sponsor are different assets. A mentor talks to you: advice, review of your plans, pattern matching from experience. A sponsor talks about you: says your name in rooms you are not in, puts you up for the visible project, spends their own credibility on your promotion. Mentors are easy to get and valuable; sponsors are hard to get and career-deciding. "Who is sponsoring this case?" is the real question behind most promotion outcomes, and cultivating a sponsor mostly means doing visible work and making it easy to retell (Chapter 2's credit mechanics, pointed at yourself for once).

The promotion conversation

The mistake is raising it as a verdict request ("do I get promoted this cycle?"), which invites a one-word answer. Raise it as a gap analysis, early, in writing-friendly form:

"I'd like to be a credible senior case within two cycles. Can we spend a 1:1 on what the gap looks like from your side?"
"What would a promotion packet for me be missing today? I'd rather hear it now than at calibration."
After the answer, convert it to record: "Summarizing what I heard: the gap is cross-team scope and a design doc with my name leading. I'll aim the queue-split work at exactly that; can we check the read in a month?"

Two supporting habits. Keep a brag document: a running file of outcomes with numbers and links ("led INC-214 response; wrote the postmortem; retry cap adopted org-wide"), updated monthly, because promotion packets and self-reviews are written from evidence and memory fabricates. And make your manager's job easy: "here are the six bullets for my packet, each with a link" beats "you know what I did."

The salary conversation runs on the same grammar, plus data and no bluffing: "I'd like to talk about compensation at our next 1:1, so flagging it now. My research puts the band for this role at X to Y; I'm at Z with two cycles of exceeds. What would it take to close that?" Never voice a leaving threat you are not prepared to execute; it converts the conversation from adjustment to countdown.

Self-reviews and interview stories

The self-review genre rewards exactly what the status chapter rewards: outcomes with numbers, claimed at the right size. "Led the retry redesign; checkout brownouts went from monthly to zero across two quarters" is a review bullet; "worked on reliability" is filler, and "singlehandedly saved checkout" invites your reviewers to correct you. Claim your real role with plain verbs: led, designed, shipped, unblocked, reviewed, mentored.

For behavioral interviews and review narratives alike, the standard container is STAR: Situation, Task, Action, Result. One tuned example: "Our checkout amplified a payment blip into a 40-minute brownout (S). I owned the fix under a two-week deadline (T). I capped retries behind a flag, replayed the incident traffic to prove it, and wrote the runbook (A). The next provider blip lasted 90 seconds and self-healed; the pattern was adopted by two other teams (R)." The most common failure is drowning in S; interviewers want A and R, told in "I" sentences, with honest edges ("what I'd do differently is flag it per-region from day one").

👉 Careers are the vertical human conversations; the horizontal ones are the social fabric around the work: joining a team, leaving one, congratulating, condoling, calling in sick, and handing over before vacation. Small genres, high stakes-per-word. On to Chapter 19.