Week one, midweek: glitches, mishearings, and the 1:1
Wednesday through Friday of week one. The scenarios in this chapter are the ones that make non-native speakers dread calls: broken audio in both directions, sentences that refuse to be understood in both directions, a tech talk with a question to ask, and the weekly 1:1. Watch how cheap the recoveries are when you have the words ready.
Wednesday, 10:00: his connection breaks (they can't hear him)
Design sync on the vault integration, eight people on the call. Alex is two sentences into his point when the chat lights up.
Sam (chat): Alex you're breaking up badly
Priya: Alex, we're getting every third word; you froze for
a second too.
Alex: Let me try once more... any better?
Priya: Worse, sorry.
Alex (chat): Dropping to rejoin. 60 seconds. Meanwhile my point,
short version: exchange tokens INSIDE the vault
boundary, so raw tokens never transit our service.
Sam, can you voice that if discussion moves on?
Sam: (aloud) Reading Alex's chat for him: exchange inside
the vault boundary, raw tokens never touch us. I
agree, for the record.
Alex: (rejoining) Back. Did the point land or should I
re-make it?
Priya: Landed, Sam voiced it. We're on the error path now.
The playbook when you are the broken one: try once (not five times), then switch channels without drama. Chat is your voice while audio is down; deputizing a colleague ("Sam, can you voice that?") keeps your point alive in the room while you rejoin. And on return: one line to resynchronize ("did it land or re-make it?"), no apology tour. Connection failures cost you nothing socially unless you spend five minutes narrating them.
Variations, from the speaker's side: "I'm told I'm robotic; switching to chat for a minute." / "My audio is unstable; I'll drop video, that sometimes saves it." / "If I freeze mid-sentence, the chat has my point; carry on and I'll rejoin."
Variations, from the listeners' side (kind versions): "Alex, you're breaking up; we lost everything after 'vault'." / "You cut out for ten seconds; can you repeat from the token part?" / "Your audio is choppy on my end; anyone else? OK, not just me." Note the kindness mechanics: say what was lost (so they repeat only that) and confirm it is not one listener's problem before making the speaker reconnect.
Wednesday, 10:20: the reverse (he can't hear them)
Same call, later. Priya is walking through rollout dates and her audio turns to gravel, but apparently only for Alex.
Alex: Priya, you're cutting out on my end; is that just me?
Ravi: You're clear for me.
Alex: Then it's my side. Priya, I lost the two dates you just
gave; could you drop them in the chat so I don't rebuild my
plan on a guess?
Priya (chat): Cutover 14th, freeze starts 21st.
Alex: Got it, thanks. I'll re-listen to the recording for the
rest; don't let me slow the call down.
The three moves: localize the problem before blaming anyone's setup ("is that just me?"), convert the load-bearing content to text (dates, numbers, and names never travel by damaged audio), and release the room ("don't let me slow the call down") while naming your own recovery plan (the recording). Never nod through content you did not hear; a guessed date is a bug you planted in your own calendar (Chapter 22).
Wednesday, 14:00: misunderstanding, in both directions
They don't understand him. Alex explains the design to Priya and watches the glaze form:
Alex: ...so the exchange is idempotent, which is what makes the
retry story safe.
Priya: (pause) Right.
Alex: Let me say that without the jargon, because it matters for
your rollout note: "idempotent" means running it twice is
harmless. So if the network hiccups and we retry, the
customer can't get double-charged. That's the sentence for
the release notes, actually.
Priya: THAT I can use. Why don't engineers open with that?
The skill is catching the silent non-understanding (the pause, the flat "right", the missing follow-up question) and taking the blame for it yourself: "let me say that without the jargon" rather than "do you understand?", which forces a confession (Chapter 25). Watch for your own tells being read the same way.
He doesn't understand them. An hour later, Ravi, who talks fast, explains the token fix:
Ravi: (rapid) ...so the refresh races the exchange unless you
pin the epoch before the call, that's the whole fix.
Alex: Slower for me, please; I want to actually get this. The
refresh races the exchange... and pinning the epoch does
what exactly?
Ravi: Freezes the token version, so the race has a winner.
Alex: Got it: pin first, race becomes harmless. Let me play the
whole thing back... (does) ...right?
Ravi: Exactly right.
"Slower for me, please" plus a targeted replay of the part that did not land, plus the final playback. Two clarifying passes on a technical point is normal engineering, not a language failure; senior native speakers do exactly this. The failure mode is the nod-and-hope, which converts a ten-second question into a Thursday-afternoon rework.
Don't be confused: the politeness ladder of mishearing. "What?" is abrupt in most professional rooms. "Sorry?" and "Say again?" are the friendly workhorses. "Pardon?" is fine, slightly formal. "Could you repeat that?" is neutral and complete. And the power move is none of these: it is the partial echo, "the exchange races the what?", which pinpoints the lost word so the speaker repeats three syllables instead of a paragraph. Reserve the theatrical "WHAT?!" for reacting to astonishing news, where it is not a mishearing at all but a compliment.
Thursday, 15:00: the tech talk, and asking the follow-up
Yuki gives a brown-bag on the vault redesign. Alex has a question, and a small disaster: the question gets half-answered by a slide he missed while reading chat.
Alex: Great walkthrough; the rotation story finally makes sense
to me. One question: what happens to in-flight exchanges
during a rotation? Do they fail, retry, or drain?
Yuki: Slide 14 covered the drain window, but the honest answer
is: drain works below one rotation per hour, and above
that we genuinely don't know yet.
Alex: I clearly blinked through slide 14, apologies; the
above-one-per-hour part is what I was really after. Is
"we don't know" scary or fine?
Yuki: Scary. It's on the risk list, want to poke at it with me?
Alex: Yes; I'll grab twenty minutes on your calendar.
The follow-up question kit: one sentence of specific appreciation (not flattery: "the rotation story finally makes sense" names something), then one question, phrased with its options ("fail, retry, or drain?" is easier to answer than "what happens?"). Missing a slide is a two-word recovery ("I blinked", "I missed that") followed by pushing to the part of your question that survives, and half the time the "answered" question has an unanswered core, as here. Never pretend the slide answered you if it did not.
Variations for asking in a talk: "Question when you reach a pause: ..." (chat, mid-talk) / "This might be slide-15 material, but: ..." (defuses the already-covered risk in advance) / "Naive question, and feel free to redirect me to the doc: ..." (Chapter 3; use sparingly). And afterward, the hallway follow-up beats the public marathon: "Your talk triggered three more questions; can I buy you a coffee for ten minutes instead of monopolizing the Q&A?"
Thursday, 16:00: the weekly 1:1
Dana's calendar, thirty minutes. Alex brings the agenda (Chapter 19):
Alex: Three things, smallest first: status is in the tracker, so
skip unless you have questions. Second, a friction: review
latency from the platform team is now my longest queue;
twice this week I sat a full day on small PRs. Third, five
minutes on the senior-engineer gap list we made last month.
Dana: Friction first. Is it their load or our asks?
Alex: Honestly, mixed. Our PRs arrive un-shrunk; their queue is
real. I can fix our side, splitting the reviews smaller.
The ask is you raising the SLA question with their EM,
manager to manager, so it doesn't read as me complaining.
Dana: Deal. And the gap list?
Alex: You said "lead a design end to end." The vault design is
that, if you agree it counts. I want it on the record
before calibration season, not after.
Dana: It counts if you run the review too, not just the doc.
Run it, and I'll write it down.
Notes: the friction arrives with Alex's own contribution named first (mixed cause, "I can fix our side"), which is what makes the escalation ask safe to grant. The career item is concrete, anchored to a prior agreement, and asks for the record, not a feeling. And the whole meeting fit in thirty minutes because status was pre-declared dead (Chapter 19).
Dana's closing question, and the upward-honesty answer:
Dana: Last thing, my question: how's the team feeling? I've been
heads-down in on-call.
Alex: Mostly good. Planning ran smoother than last sprint. One
watch item: Ravi is carrying the token mess alone and it's
the kind of thing that curdles quietly. A pairing nudge
from you would land better than one from me.
Answering "how's the team?" honestly without informing on anyone: observable load, no character commentary, and a concrete assist suggested. This is upward feedback in its most useful costume.
Friday, 12:45: the corridor ambush, and the weekend close
Alex is walking, with intent, toward the washroom. Ines materializes with a rolled-up architecture diagram.
Ines: Alex! Two minutes on the export format?
Alex: Genuinely mid-dash; find you in ten?
Ines: Ha, go. Ten minutes.
Alex: (ten minutes later, at her desk) You had a diagram for me?
Yes, you are allowed to say it. "Mid-dash", "on a mission", "catch you in ten, literally running an errand" all decline the ambush without explaining your bladder to a colleague. The only rule is the same as Monday's kitchen scene: the promised ten minutes must actually happen.
Friday, 17:20, the team channel:
Alex: Wrapping up. PR 519 is green and handed to Sam for Monday.
Have a great weekend, all; Yuki, good luck at the tournament!
Yuki: :badminton: thanks!
Sam: Enjoy, everyone. Off to lose a fight with my garden.
The Friday close: state of your work parked cleanly (so nobody pings you Saturday to ask), a general farewell, and, when you have one, a remembered detail aimed at a person. That last clause is the rapport ledger again; Yuki's tournament was mentioned once, on Tuesday, and Alex wrote it down.
👉 One week down. Week two opens with a weekend question that has a harder answer, a pairing session with a keyboard-grabber, a group lunch where the topics need steering, and Alex on the other side of the review table. On to Chapter 34.