Interview questions for communication skills, with a scoring rubric
On this page
- What "communication skills" actually means for this role
- Ten questions, with strong answers, red flags and a follow-up
- A 1-4 rubric for communication skills
- Rehearsed versus real: how to tell the difference
- Which roles this matters most for
- Mistakes to avoid when scoring this
- A checklist before this interview
- Questions people ask
Interview questions for communication skills work only when they ask for a specific instance the candidate had to get someone else to understand, decide, or act — not for an opinion about how good a communicator they are. Below is a bank of ten questions built that way, each with what a strong answer sounds like, a red flag, and a follow-up probe, plus a rubric, a way to catch a rehearsed answer, and the roles where this competency decides more than the resume does.
This differs from how to assess soft skills in interviews, which covers the general method for any soft skill, and from behavioral interview questions with a scoring rubric, whose communication section is four questions inside a 24-question set spanning six competencies. This page is the full set for communication alone, with none of the same questions.
What "communication skills" actually means for this role
Before you ask anything, decide which of three separate things the job actually needs, because they do not travel together and a candidate can be strong in one and weak in another:
- Explaining. Making a message land with a specific audience: a customer, an executive, a junior teammate, a courtroom.
- Listening and adjusting. Picking up that the other person is confused, unconvinced or about to disengage, and changing course mid-conversation instead of finishing the planned script.
- Writing. Producing something — an email, a report, a set of instructions — that a reader can act on without a clarifying call back.
A sales role leans on explaining and listening; a support role leans on listening and writing; a policy or legal role leans on writing precision above the other two. Pick the one or two that matter and weight the questions below accordingly, rather than treating all three as one score.
Ten questions, with strong answers, red flags and a follow-up
| Question | What a strong answer sounds like | Red flags | Follow-up probe |
|---|---|---|---|
| Tell me about a time you had to explain something technical or complicated to someone who had none of the background. | Names the actual gap in the listener's knowledge, describes swapping jargon for an analogy or example from the listener's world, and checked understanding before moving on. | Describes the explanation itself but never mentions the listener's reaction, or admits the person "sort of" understood. | "How did you know they actually understood, rather than just nodded?" |
| Describe a message you had to send that you knew the recipient would not want to read. | States the bad news plainly and early in the message, gives the reason and the next step, and does not bury it under softening language. | The story is about delaying the message, or the message they describe still sounds vague when repeated back. | "What was the exact first sentence, as close as you can remember it?" |
| Tell me about a conversation where you realized partway through that the other person wasn't following you. | Names the specific signal that tipped them off — a question that missed the point, a blank expression, silence — and describes changing approach on the spot. | Claims they always notice immediately with no example, or the "fix" is just repeating the same explanation louder or slower. | "What did you change about how you explained it the second time?" |
| Give me an example of something you wrote that someone used to make a decision without calling you first. | Names the document, who read it, and that it stood on its own: the reader acted without a follow-up question. | No example, or the "written communication" example is really a verbal conversation they later summarized in an email. | "What would have happened if you had left out the part you're most proud of including?" |
| Tell me about a time you had to get buy-in from someone who reported to a different manager than you. | Describes framing the ask around what mattered to that person's own priorities, not just repeating the request more insistently. | The story is really about escalating to a manager to force compliance, not persuading the person directly. | "What did you know about their priorities going in, and how did you find that out?" |
| Describe a time you gave instructions and the result came back wrong. | Takes responsibility for the gap in the instructions, identifies exactly what was missing or ambiguous, and describes changing how they give instructions afterward. | Blames the other person's competence or attention with no reflection on what was unclear in the original message. | "If you gave the same instructions again today, what would you say differently?" |
| Tell me about presenting information to a group where people had very different levels of familiarity with the topic. | Describes layering the explanation — a plain summary up front, detail available for those who wanted it — rather than picking one level and losing part of the room. | Describes pitching to the most senior or most technical person in the room and ignoring the rest. | "How did you check that the least familiar person in the room was still following?" |
| Tell me about a time someone misunderstood something you said, and it caused a real problem. | Owns their share of the misunderstanding honestly, describes the actual consequence, and names a specific change to how they communicate now. | Frames it entirely as the other person's fault, or the "misunderstanding" was actually trivial. | "What exactly did you say, and what did they hear instead?" |
| Describe a time you had to deliver the same message to two very different audiences. | Names what stayed the same (the core facts) and what changed (the framing, the level of detail, the tone) between the two versions. | Delivered the identical message both times and considers that a strength ("I'm consistent"). | "What's one specific line that was different between the two versions?" |
| Tell me about a time you had to ask a clarifying question before you could do the work, when it would have been easier to just guess. | Describes a specific ambiguity, the exact question they asked, and how the answer changed what they did. | Cannot recall ever needing to ask, or the "clarifying question" was asked after the work was already wrong. | "What would you have built if you'd guessed instead of asking?" |
A 1-4 rubric for communication skills
| Dimension | 1 — Weak | 2 — Developing | 3 — Solid | 4 — Strong |
|---|---|---|---|---|
| Matching the message to the listener | Gives the same explanation regardless of who is listening | Adjusts wording a little but the structure and depth stay the same | Adjusts depth and framing to the listener's background | Same, plus checks understanding and adjusts again mid-conversation |
| Clarity under pressure or bad news | Buries the point, or avoids saying the hard part at all | Gets to the point eventually, after hedging | States the point plainly, with the reason and next step | Same, plus names the impact on the listener and offers a way forward |
| Listening and mid-course correction | No example of noticing confusion or disagreement in the moment | Notices eventually, after being told directly | Notices a specific signal and adjusts on the spot | Same, plus confirms the adjustment landed before moving on |
| Writing that stands on its own | No example, or written work always required a follow-up call to clarify | Written work mostly works, with occasional follow-up questions | A specific example of writing a reader acted on without a call | Same, plus can explain what they cut to keep it usable |
Rehearsed versus real: how to tell the difference
Communication is the competency candidates practice the most before an interview, because the interview itself is a communication exercise. That makes fluency the least reliable signal in the room. Three checks separate a rehearsed answer from a real one:
- Ask for the exact words. "What was the first sentence you actually said?" A real memory produces something close to a direct quote, even an imperfect one. A rehearsed answer stalls, or produces a sentence that sounds like a summary rather than something a person would say out loud.
- Ask what they cut. A candidate who really tailored a message to an audience can tell you what they left out and why. A candidate describing a generic "I'm a strong communicator" story usually cannot name anything they deliberately left out, because nothing was actually tailored.
- Watch this interview, not just the story. The single best evidence is happening in front of you: does this candidate check that you're following, adjust when you look confused, and answer the question you actually asked rather than the one they prepared for? A candidate who is fluent about communication but does not do these things in the room is describing a skill rather than showing it.
Which roles this matters most for
| Role type | What to weight most |
|---|---|
| Sales, account management, customer success | Explaining to a specific audience and listening for disengagement in real time |
| Support, help desk, client services | Writing that resolves an issue without a follow-up call, and clarity under a frustrated customer |
| Management and team leads | Delivering bad news plainly and adjusting instructions after a result comes back wrong |
| Technical roles working with non-technical stakeholders | Explaining technical work without jargon and checking understanding |
| Legal, compliance, policy, technical writing | Writing precision: a document that stands on its own with no ambiguity |
For a role with almost no cross-team or customer-facing communication, weight this competency low and spend the interview time elsewhere; scoring it heavily for a role that does not require it adds noise, not signal.
Mistakes to avoid when scoring this
| Mistake | What it costs you |
|---|---|
| Scoring how the candidate sounds in the interview itself as a proxy for the job | You hire for interview performance, which correlates with practice, not with the job's audience |
| Treating a quiet, plain-spoken candidate as weaker | You miss candidates who communicate clearly without performing confidence |
| Accepting "I'm a great communicator" without an example | You score a claim, not a behavior |
| Only asking about verbal explaining | You miss listening and writing, which fail separately and differently on the job |
A checklist before this interview
- You have decided which of explaining, listening or writing this role actually needs most.
- At least one question asks for a specific instance, not a general self-description.
- You are ready to ask for the exact words or the exact line that was cut, not just the summary.
- You are scoring what happens in this interview — whether the candidate checks understanding with you — alongside the stories they tell.
- Delivery nerves and content are scored separately.
Interview Signal builds the question guide from the job description and ticks off must-ask questions as they are covered, so a communication-skills question does not get skipped when the conversation runs long, and the scorecard carries the candidate's own words rather than a summary written from memory afterward.
Questions people ask
Is 'communication skills' too broad to interview for directly?
As a single label, yes. Break it into the three things that actually differ by role: explaining clearly to a specific audience, listening and adjusting mid-conversation, and writing that others can act on without a follow-up call. Score those separately rather than one vague impression.
Should I judge communication by how polished the candidate sounds?
No. Polish is stage presence and often correlates with interview practice, not job performance. Score whether the message was clear, organized and matched to the listener, which a plain-spoken candidate can do as well as a smooth one.
How do I score a candidate who is clearly nervous?
Separate delivery nerves from the content of the answer. A nervous candidate who still structures an answer logically and checks that you followed is showing the skill; a calm candidate who rambles without checking in is not, regardless of how comfortable they sound.
Can I test communication skills without a role-play?
Yes, with two changes to how you run the interview itself: ask the candidate to explain something to you as if you knew nothing about it, and ask them to summarize back what a stakeholder in the story wanted. Both give you live evidence, not a self-report.