How this shows up in interviews — Communication craft: listening, writing and presence

Communication is the one competency an interviewer doesn't have to take your word for. Everything below is graded twice: once on the answer, once on the delivery.

"Tell me about yourself."

The most-failed question in sales interviewing, because most candidates narrate a CV chronologically and lose the room in twenty seconds. Use the pyramid: one top-line sentence saying who you are commercially and what you're moving towards, then three supports, then stop. Ninety seconds maximum, finishing cleanly rather than trailing into "…so, yeah". Rehearse the shape out loud; don't memorise the words, because memorised answers sound memorised.

"Run a mock discovery call — I'm a lab manager, and the last vendor was a disaster."

They are testing exactly the moment in this module's annotated example. Don't defend, don't stack questions, don't pitch. Mirror, hold the silence, label what you hear, ask "tell me more", summarise before you move on. Interviewers watch your talk ratio in real time: if you say under a hundred words in the first three minutes and the story keeps opening, you're passing.

"Here's a persona and a company — write us a cold email. Ten minutes."

Increasingly common, and a gift to a career-changer, because it's the exercise where inexperience is invisible. Subject line names their problem. First sentence is about them. One specific checkable claim, one question, one low-friction ask, under 120 words. Read it aloud before handing it over and cut anything you stumbled on.

"You're asked something on a customer call and you don't know. What do you do?"

Give the four-part answer: say you don't know plainly, say what you do know, commit to a named person and a date, then deliver by that date regardless of whether the answer helps you. Add the sector point about never guessing on regulatory status or data handling. If they follow up with a technical question you genuinely can't answer, use the same answer live — that's usually the real test.

"How do you know when a call is going badly?"

Name the signals rather than describing a feeling: sideways eye movement, camera off mid-call, delayed generic responses, several attendees disengaging at once, answers getting vaguer ("a bit of everything, I suppose"). Then name the response — stop talking and ask. Plenty of candidates claim to "read the room well"; almost none can list what they're reading.

"Present for five minutes on anything you like."

They're grading structure, pace and presence, not the topic. Pyramid and rule of three: conclusion in the first fifteen seconds, three supports, close by restating the conclusion. Slow down for numbers, get to a real example inside ninety seconds, look at the camera, and finish inside the time — running over is a mark against you that has nothing to do with content.

"How do you go about improving at something?"

A coachability question, and the deliberate-practice answer is very strong when it's true: one named observable behaviour a week, recorded evidence, review against a single measurable question, a written log. If you've run the four-week plan, say so with specifics — what you worked on in week one, what the recordings showed, what changed by week four. Concrete self-improvement machinery is rare, and it predicts what you'll do in month one of the job.

Cheat sheet

Listening. Levels: downloading (hears only confirmation) → factual → empathic (your working standard) → generative. Active listening = attending, following, reflecting, and not composing your reply. Nichols: average listening efficiency ~25%; listening is trainable.

Notes. Their words, not your summary. Nouns and numbers, not sentences. Announce it once. Look up for the important bits. Write up within ten minutes.

Silence. After your question, hold until they speak. After their answer, count two — the sentence starting "and honestly…" is the valuable one. Phone silence feels twice as long as it is.

Summarising. Vary the opener; compress rather than repeat; include something they didn't say; end on "what have I got wrong?" Do it after a developed pain, before changing topic, and before agreeing next steps.

Questions. Open to explore, closed to confirm and commit. Funnel broad → narrow → number, and don't leave a topic without a number or a dead end. Follow-ups: "tell me more" / "what happens when that goes wrong?" / "what's driving that?" / "can you give me an example?" / "what have you tried?" Mirror = last 1–3 words. Label = "it sounds like…". Leading-question tells: tag endings, your benefit named, you already know the answer you want. ~11–14 questions is the productive range.

Writing. One idea per paragraph. Short sentences. Delete your first two sentences. Concrete verbs. Their jargon, never yours. Every sentence passes "so what?". Subject line names their problem. One ask per email. Open on them, not you. Read it aloud; read it on a phone.

Presence. You're too fast, not too slow — slow further for numbers, names and objections. Watch for rising terminals and monotone. Fillers: substitute silence, slow down, count weekly; hedges ("does that make sense?", "I just wanted to") do more damage than "um". Smile — it's audible. Camera at eye level, light in front, head-and-shoulders, self-view off, wired headset. Nerves: reframe as excitement, slow exhale, first sentence written out, question ready.

Structure. 30-second version = who it's for → their problem → what you do → one proof. Pyramid: answer first, then support. Rule of three — a fourth reason undermines the first three. Story: setup → tension → resolution → point, 60–90 seconds, real numbers. Don't know? Say so → what you do know → named person and date → deliver.

Reading the room. Real signals cost the buyer something: specificity, obstacles raised, people introduced, future tense about themselves. Politeness: "looks great", "leave it with me", "send me some information". Stop talking after 90 seconds, after answering, after agreement, at any disengagement cue — and especially after making an ask. Bring in the silent participant by name, on their territory, inviting a concern.

Practice. One named observable behaviour per week. Record yourself; review against one measurable question. Ten minutes daily: read aloud → answer on camera → review → rewrite an email. Keep a one-line log and the recordings.

References & further reading

Are You Listening? — Ralph G. Nichols & Leonard A. Stevens (1957). The foundational listening research, from decades of studies at the University of Minnesota; source of the 25% listening-efficiency figure and of the insistence that listening is a trainable skill. Their Harvard Business Review article "Listening to People" (September 1957) is the short version and is still on hbr.org.
Time to Think: Listening to Ignite the Human Mind — Nancy Kline (1999). A British consultant's case that the quality of everything people do depends on the quality of their thinking, and that thinking depends on the quality of attention they receive. A useful counterweight to sales training's tendency to treat listening as an extraction technique.
Never Split the Difference — Chris Voss with Tahl Raz (2016). The practitioner source for mirroring, labelling and tactical empathy, from the FBI's former lead international kidnapping negotiator. Read it for the techniques; ignore the thriller packaging.
On Writing Well — William Zinsser (1976; 30th anniversary edition 2006). The standard guide to clear non-fiction prose and the fastest route to emails that get answered. Its chapters on clutter and simplicity are worth more to a new seller than any book about sales emails.
"Politics and the English Language" — George Orwell (1946). A short, free essay whose six rules still cover most of what goes wrong in business writing. Twenty minutes, and it changes how you read your own drafts.
The Pyramid Principle: Logic in Writing and Thinking — Barbara Minto (1987). The consulting world's structural bible: answer first, then supporting arguments, then evidence. Dry, and worth persisting with — it fixes rambling in speech as well as on the page.
Peak: Secrets from the New Science of Expertise — Anders Ericsson & Robert Pool (2016). The accessible account of deliberate practice: why repetition alone plateaus, and what makes practice actually produce improvement. The basis of this module's four-week plan.
"Nonverbal Overload: A Theoretical Argument for the Causes of Zoom Fatigue" — Jeremy N. Bailenson (2021), Technology, Mind, and Behavior. Open access, short, and the source of the video-call advice here — particularly the case for turning off self-view.

Also worth following: the Gong Labs blog, which publishes analyses of very large call-recording datasets on talk ratios, question counts, speaker switches and speaking rate. Treat the findings as correlations within their customer base rather than laws, but they are the closest thing the profession has to empirical data on how sales conversations behave.