20 communication skills interview questions and how to score them
"Are you a good communicator?" is the laziest question in interviewing. The 20 questions here actually evaluate the specific sub-skills that make someone communicate well at work.
The single most common interview question about communication is “are you a good communicator?” — and the second most common is “give me an example of when you communicated well.” Both questions evaluate exactly one sub-skill (the candidate’s ability to perform verbal confidence in the moment) and miss everything else that makes someone actually communicate well at work. The candidate who interviews smoothly is not always the candidate who writes a useful Slack message at 4pm on a deadline.
This post is the version that breaks communication into its four real sub-skills, asks questions that test each one, and scores them with a rubric that separates “I liked talking to them” from “they’d communicate well in this role.”
The four sub-skills
- Written precision. Can the candidate structure an argument for a reader who isn’t in the room — brief, accurate, and decision-ready?
- Verbal clarity under pressure. Can they explain a complex idea in real time, adjusting as the listener’s understanding changes?
- Listening as evaluation. Do they hear what’s actually being asked, including what’s not being said, and update their response accordingly?
- Stakeholder adaptation. Do they translate the same idea for different audiences — exec, peer, customer, junior teammate — at the level each needs?
Roles weight these differently. A remote IC engineer needs strong (1) and (3), modest (2) and (4). A field sales rep needs the inverse. A people manager needs all four roughly equally. The questions below let you score each separately and weight them to the role.
Sub-skill 1: Written precision
These work best as a short writing exercise after the interview, but you can probe verbally too.
1. Write me a 5-sentence Slack message to a peer explaining that a project you committed to is going to slip by two weeks. Include the reason and what you’re asking from them.
What good sounds like: Opens with the slip, not a preamble. Names the reason in one sentence. Names what they need from the peer specifically. Closes with a check-in or next step. No filler.
What weak sounds like: Buries the slip in paragraph three. Vague reason. Asks for “your input” without specifying what kind. Or apologizes for three sentences before getting to the point.
2. Walk me through how you’d structure a written update for your manager after a complicated week.
What good sounds like: Names a structure (TL;DR top, then specifics). Differentiates what the manager needs to act on versus what’s just FYI. Considers length — most managers don’t read past 200 words. Bonus for naming what they’d cut.
What weak sounds like: “I’d just summarize what happened.” No structure. No filtering for action.
3. What’s something you wrote at work in the last quarter that you’re proud of? Why?
What good sounds like: Specific document, specific reason. Connects the writing to a real outcome (a decision made, a process changed, a stakeholder aligned).
What weak sounds like: Generic “I write a lot of docs.” No specific example. No connection to outcome.
4. When you write something important, what’s your process between first draft and sending it?
What good sounds like: Names a real process (sleep on it, cut by 30%, run it past one specific person, read out loud). Shows self-awareness about what they tend to over- or under-do.
What weak sounds like: “I just proofread it.” No process.
5. Show me a piece of writing you’d want me to read to evaluate your writing.
What good sounds like: Picks something appropriate (not too long, relevant to the role). Can explain the audience and purpose. Acknowledges what they’d change in hindsight.
What weak sounds like: Picks the wrong sample (academic paper for an operations role). Can’t articulate why they chose it.
Sub-skill 2: Verbal clarity under pressure
These work in live interviews. Score on the structure of the explanation, not the warmth of the delivery.
6. Explain a technical concept from your work to me as if I have no background in your field.
What good sounds like: Asks one clarifying question about my background. Picks an analogy or framing. Pauses to check understanding. Adjusts when I push back.
What weak sounds like: Launches into the same explanation they’d give a peer. Doesn’t pause. Doesn’t adjust when I look confused.
7. Walk me through your reasoning on a recent decision you made at work.
What good sounds like: Frames the decision, names the trade-offs, makes the call, gives the reasoning. The structure is linear; the listener can follow.
What weak sounds like: Jumps around in time. Names the decision without framing the trade-offs. Skips the reasoning step.
8. Describe your current job to someone who’s never heard of your industry.
What good sounds like: Picks one or two analogies that map to common experience. Doesn’t use industry jargon without translation. Tests for whether I’m following.
What weak sounds like: Industry jargon. Long preamble. No analogies.
9. Tell me about a time you had to explain a setback to a senior stakeholder.
What good sounds like: Opens with the setback in their own words. Names the cause clearly. Says what they did about it and what’s next. Doesn’t over-apologize or under-account.
What weak sounds like: Long preamble. Blames others. Either over-apologizes or hides behind passive voice.
Sub-skill 3: Listening as evaluation
These are the questions candidates can’t pre-prep for, because they depend on a real-time read of the interviewer. Score on whether the candidate’s response actually engages with what you said.
10. (Mid-question reframe:) Hmm, that’s interesting but not quite what I was asking. Let me try again. [Reframe.] How does your answer change?
What good sounds like: Pauses. Restates the reframed question. Asks a clarifying question if needed. Gives a genuinely different answer.
What weak sounds like: Repeats the original answer with new packaging. Or defends the original answer instead of engaging with the reframe.
11. (After a strong answer:) That was a good answer. What part of it would you push back on if you heard a peer say it?
What good sounds like: Picks a real weakness — an assumption, a missing constraint, a context where it’d fail.
What weak sounds like: “I don’t see anything to push back on.” Or names a generic weakness that doesn’t fit the answer.
12. Tell me about a time you misunderstood what someone needed from you. How did you figure out you’d misunderstood, and what did you do?
What good sounds like: Real moment, specific signal that flipped them. Owns the misunderstanding. Names what they’d do differently to catch it earlier.
What weak sounds like: No specific moment. Either blames the other person for unclear ask, or makes the misunderstanding sound trivial.
13. (After they finish a long answer:) Can you summarize that in one sentence?
What good sounds like: Pauses, then gives a one-sentence summary that captures the actual point. Edits ruthlessly.
What weak sounds like: Repeats the long answer in slightly shorter form. Or summarizes around the point without naming it.
14. What’s a piece of feedback you got recently that you initially disagreed with but came around to?
What good sounds like: Real feedback, specific reason they initially disagreed, specific thing that made them update. Shows they actually heard the feedback rather than dismissing it.
What weak sounds like: Feedback that didn’t require any updating. Or “I just realized they were right” without the mechanism.
Sub-skill 4: Stakeholder adaptation
These probe whether the candidate can switch register for different audiences.
15. Pick a project you led. Now describe it to me three times: once for your CEO in 60 seconds, once for your engineering peer in 2 minutes, once for a new junior teammate in 3 minutes. What changes?
What good sounds like: Real differences across the three. CEO version is outcome-focused. Peer version is technically dense. Junior version teaches context. Each is appropriate for the audience.
What weak sounds like: The three versions are basically the same with minor edits. Or the candidate can’t articulate what they’d change.
16. Tell me about a time you had to explain the same decision to two different audiences. How was the explanation different?
What good sounds like: Specific decision, specific audiences, specific differences (different concerns surfaced, different language, different level of detail). Shows awareness of what each audience cared about.
What weak sounds like: “I just adjusted my language.” No engagement with what the audiences actually cared about.
17. How do you decide how much context to give in a message or meeting?
What good sounds like: A working heuristic (the listener’s familiarity with the topic, the decision they need to make, the time available). Examples of times they over- or under-contextualized.
What weak sounds like: “I try to be clear.” No heuristic.
18. Describe how you communicate with a manager who likes detail versus a manager who likes summaries.
What good sounds like: Names specific tactics for each (e.g., detail manager gets the full thread; summary manager gets the headline plus link). Acknowledges trade-offs (more prep time, harder to switch context).
What weak sounds like: “I just match their style.” No specifics.
19. When did you last get a communication style wrong with someone? What happened?
What good sounds like: Specific moment, specific person, specific recalibration. Shows learning.
What weak sounds like: “I usually get it right.” Or names a trivial misfire.
20. What’s the hardest audience for you to communicate with, and why?
What good sounds like: Names a real audience type (e.g., “executives who don’t have time for context, where I tend to over-explain”). Self-aware about the gap. Names what they’re doing about it.
What weak sounds like: “I get along with everyone.” Or names a fake hard audience (rude people).
The scoring rubric
For each sub-skill, 1-5 across the questions you used. Weight the sub-skills by the role.
| Score | Anchor |
|---|---|
| 5 | Strong evidence at a higher level than the role requires |
| 4 | Strong evidence at the level the role requires |
| 3 | Some evidence but inconsistent across questions |
| 2 | Mostly performative; doesn’t engage with specifics |
| 1 | Negative signal; the answer revealed a real gap |
Weighting examples by role:
- Remote IC engineer: Written 40%, Verbal 15%, Listening 25%, Stakeholder 20%
- Account executive: Written 15%, Verbal 35%, Listening 25%, Stakeholder 25%
- People manager: Written 25%, Verbal 25%, Listening 25%, Stakeholder 25%
- Customer success lead: Written 20%, Verbal 25%, Listening 30%, Stakeholder 25%
The candidate’s overall communication score is the weighted average. A 3+ is the threshold to advance; a 4+ is the threshold for senior roles where communication is the load-bearing skill.
Where async screening fits
Communication is one of the highest-leverage skills to evaluate in async one-way interviews. Three reasons:
The video format directly tests verbal clarity under pressure — same as a live interview, minus the social warmth that obscures the signal. A candidate who comes across as charming on Zoom but flounders explaining a concept on video is showing you something useful.
The structured question set tests listening differently. Each candidate gets the same questions in the same order; the variance you see across candidates is variance in how they engaged with the question, not in how the interviewer asked it. Truffle AI Match scores responses against criteria the recruiter sets — including communication-specific signals like “did they restate the question,” “did they structure the answer,” and “did they adjust the register for the implied audience.”
The shortlist review compresses the communication signal. Reviewing 8 candidates’ async answers in 12 minutes of Candidate Shorts — compared to 8 phone screens at 30 minutes each — means you see the communication signal more times in less time. The cross-candidate comparison is what makes the weaker communicators stand out.
The live round then probes the listening sub-skill more deeply with the mid-question reframes and the back-and-forth that async can’t capture. The two stages cover all four sub-skills cleanly.
Frequently asked questions about communication skills interview questions
What are good communication interview questions?
Good communication questions separate the four sub-skills: written precision, verbal clarity under pressure, listening-as-evaluation, and stakeholder adaptation. Each sub-skill has different signals and different ideal questions. Asking “are you a good communicator” evaluates none of them; asking “tell me about a time you explained X to Y” evaluates one. A useful interview covers at least three of the four with separate questions and scores each sub-skill independently rather than rolling them into one rating.
How do you evaluate communication skills in an interview?
Score against the four sub-skills, not against a generic “communication” rating. Use a 1-5 rubric on each sub-skill, evaluated through specific questions. The candidate’s overall communication score is the weighted average across sub-skills, with weights set by the role’s actual requirements. The most common interviewer error is conflating “I enjoyed talking to them” — which is mostly verbal warmth — with “they’d communicate well in this role” — which depends on what kind of communication the role actually requires.
What’s the difference between written and verbal communication in an interview?
Written communication is precision, brevity, and the ability to structure an argument for a reader who isn’t in the room. Verbal communication is clarity in real time, with feedback loops from the listener and the option to adjust. Roles weight them differently. A remote IC engineer needs strong written and modest verbal. A field sales rep needs the inverse. Interviewing for both as one trait misses the role’s actual requirement and produces hires who can do one well and the other not.
How important is listening in communication interviews?
Listening is the most under-evaluated communication sub-skill in interviews because it’s the hardest to surface with a question. Candidates can prep verbal and written examples; they can’t fake listening in the room. The strongest test is a mid-question reframe: change the question mid-stream and watch whether the candidate restates the new version before answering, or rolls their prepared answer over the top of it. The rolled-over answer is a clear signal of weak listening.
What’s a red flag in communication interview answers?
Three patterns. First: smooth answers that don’t actually answer the question — the candidate is performing verbal fluency without engaging with the specific ask. Second: every example is them explaining something successfully; no examples of explanations that didn’t land and what they did about it. Third: when asked about a communication failure, blaming the audience (“they just didn’t get it”). The first signals over-rehearsal, the second signals shallow self-awareness, and the third signals a real communication-skill ceiling.
