STAR Method Communication Examples (2026): 3 Worked Answers

Got an interview coming up?

Get my STAR action plan - Free • 30 seconds • No signup required

Why Communication Questions Are Sneakier Than They Look

Communication shows up in more than 70% of behavioural rounds and scores the lowest average of any STAR category in 2026 recruiter rubrics. Most candidates write a generic answer to "tell me about a time you communicated effectively." They describe a presentation, say it went well, and stop. That answer scores in the bottom quartile every time. A weak communication story is the most cited reason senior candidates lose offers to less experienced rivals in director-level interviews. Recruiters are not measuring whether you can talk. They are measuring three specific things:

1. Audience calibration — did you change your message for who was listening?

2. Outcome tied to a decision — did the listener actually do something different because of what you said?

3. Self-awareness about what didn't work — did you adjust mid-conversation when the message wasn't landing?

The STAR method (Situation, Task, Action, Result) fits communication questions perfectly because the Action section forces you to name the specific moves you made: the slide you cut, the doc you rewrote, the pushback you absorbed. Vague claims like "I explained clearly" do not survive a follow-up. For the parent framework, see the STAR method interview examples guide.

Three worked answers below. Each ~75 seconds spoken, each from a different communication mode interviewers actually probe: technical-to-non-technical, difficult-conversation, and async written.

Example 1: Translating Technical Complexity for a Non-Technical Audience

Question: "Tell me about a time you had to explain a complex technical topic to a non-technical audience."

Situation: Six months into my senior engineer role at a mid-market SaaS, our CFO asked me to justify a £180K spend on a database migration. The exec team had heard the engineering case three times already from my tech lead and rejected it twice. I had thirty minutes on the calendar and one slide.

Task: Convince the CFO and COO that the migration was a cost-saving decision, not a cost. Get a sign-off in the same meeting. A fourth rejection would have killed the project and locked us into a vendor we needed off.

Action: I dropped every architecture diagram from the deck. The two previous attempts had leaned on schema visuals and the exec team had glazed within four minutes. I had watched it happen. Instead I built one slide with three numbers: current monthly vendor cost (£18K), projected cost after migration (£4K), and break-even month (month nine). I added a single sentence on risk: "If we don't migrate by Q4, the vendor's renewal terms increase the £18K to £29K (that is in their proposal on file)." Then I rehearsed the talk track twice the night before. In the meeting I led with the £29K renewal number (the one that hit their P&L directly) and only mentioned the technical reason ("our query patterns no longer fit their pricing model") when the CFO asked. The COO interrupted at minute eleven to ask what I needed to start; I had the answer ready: a one-page approval form, pre-filled.

Result: Approved in twenty-three minutes. The migration shipped on schedule and saved £168K in the first twelve months versus the renewal trajectory. The CFO asked me to present the rollout retrospective at the quarterly board meeting. It was the first time an IC at my level had been invited.

Example 2: Delivering Difficult News and Holding the Line

Question: "Tell me about a time you had to deliver difficult news or push back on a stakeholder."

Situation: Two weeks before a major product launch I owned the analytics integration. The marketing director walked into our planning standup and added three new tracking events to the launch scope. That was the kind of work that would have pushed our launch date by ten days. The CMO was already telling the press that the launch date was fixed.

Task: Tell the marketing director, politely but unambiguously, that the new scope was not landing in the launch. Keep the relationship intact for the next six quarters of work we had together. Avoid the easy out of dumping the decision on my engineering manager.

Action: I asked the marketing director for fifteen minutes that afternoon, in person, not in Slack. I opened with what I could deliver: two of the three events, ready in time, because they shared infrastructure with the launch path I had already built. I named the third event specifically (the one tied to a brand-new attribution model) and walked her through the engineering work it actually required (a new data pipeline, two integration tests, a vendor onboarding). I gave her a date: ten working days after launch. I asked her to tell me what would change in her quarterly plan if we shipped the third event on that date rather than launch day, which made her own the trade-off rather than absorbing it for her. She wrote back two hours later proposing exactly that compromise. I followed up the same evening with a one-paragraph decision log to my manager, our PM, and the marketing director, so the scope cut had a paper trail and nobody was surprised at launch.

Result: Launch shipped on the original date with the two events live. The third event shipped on day nine, one day ahead of my commitment. The marketing director cited the conversation in my next 360 review as the example of "clear communication under pressure." We worked on three more launches that year without a single late scope change — she sent her additions during planning instead of standup.

Example 3: Async Written Communication That Prevented a Week of Confusion

Question: "Tell me about a time your written communication had a measurable impact."

Situation: I was leading a four-engineer team through a quarterly OKR replan after our scope shifted mid-quarter. The team was split across two time zones with only two overlap hours a day, and we had spent the entire previous quarter chasing each other through Slack threads that lost context every twelve hours.

Task: Replan the quarter and communicate the new commitments in a way that did not require a single synchronous meeting in week one. The calendar was full, and I wanted to test whether async-first could actually scale for this team.

Action: I drafted a single decision document with five sections: what changed, what we kept, what we cut, what was new, and who owned each new item. I wrote it in plain English (no engineering jargon) because the document was going to my PM and director too. Every commitment had a name next to it. Every cut had one line explaining why. I posted it in our team channel with a deadline: "Add comments by end of day Friday or it ships as written." I tagged each engineer individually for the items where their input mattered most. I deliberately did not call a meeting. By Friday I had eleven comments, eight of which improved the doc; I resolved each comment publicly so the trail was visible. I shipped the final version Monday morning. I then re-pinned the doc weekly with a one-line status update (owner, percent complete, next milestone) so anyone could check progress without asking.

Result: The team hit 100% of the replanned scope for the first time in three quarters. Slack volume on planning topics dropped by roughly 70% (I counted before and after). My director adopted the same document template for two adjacent teams the following quarter. In my next performance review the line cited was "raised the communication bar for the whole org."

The Five-Minute Communication Story Tune-Up

Before any behavioural round, run each communication story through this filter:

1. Name the audience and what they cared about. Generic "stakeholders" loses points; "the CFO, whose KPI was operating margin" wins.

2. Name the change you made to your message. Did you cut a slide, switch from Slack to in-person, rewrite a doc? The specific move is the answer.

3. Tie the result to a decision the listener made. "They understood" is weak. "They approved £180K the same meeting" is the story.

4. Acknowledge what didn't land. Even one sentence on a piece of feedback you absorbed makes the answer credible.

5. Time it to 75 seconds. Communication answers run long because the temptation to over-explain is the strongest of any STAR category.

Want a faster version? ApplyArc's interview prep generator takes your CV plus the job description and writes draft STAR answers tagged to the specific competencies a role is screening for, so you walk in with rehearsed examples for each audience type the interviewer is likely to probe.

For more sibling examples on adjacent competencies see the STAR teamwork examples and STAR adaptability examples guides.

The One Thing That Separates a Top Communication Answer

It is not eloquence. It is the named move. The slide you cut, the meeting you turned into a doc, the doc you turned into a meeting, the pushback you absorbed before it hardened. Interviewers can hear the difference between someone who communicates by default and someone who communicates by choice. The named move is the proof.