CS Interview Coach

Behaviours

Communicating and Influencing: Civil Service Examples and Interview Questions

Published


Communicating and Influencing appears in Civil Service job adverts at every grade, and it's the behaviour candidates most consistently misread. They prepare evidence of communicating — presenting clearly, keeping people informed, staying professional in difficult conversations. Panels score the second word: influencing. Did someone's position, behaviour or decision actually move because of what you did?

That gap is why pleasant, articulate candidates score 3s and 4s on this behaviour while feeling the interview went well. This article covers what panels actually score, the questions to expect, and a realistic answer rewritten from a borderline fail to a 6/7, annotated line by line.

What panels are actually scoring

Four things, in rough order of weight:

Movement. The single strongest signal: someone started at "no", "not like that", or "not my priority" — and ended somewhere else because of you. If everyone in your story agrees with you throughout, you've accidentally deleted your influencing evidence.

Deliberate choices about how. Why a conversation rather than an email. Why you led with their problem rather than your request. Why you took the difficult message in person. Choosing the channel and framing on purpose, with a "because", is descriptor-level evidence in one sentence.

Honesty under pressure. Delivering the unwelcome message yourself — clearly, with the reasons — rather than softening it into meaninglessness or passing it upward.

Audience adaptation. Technical content translated for non-specialists, or the same message framed differently for two different stakeholders, with the reasoning visible.

The questions panels actually ask

  • Tell me about a time you persuaded someone to change their approach or position.
  • Tell me about a difficult conversation you had to handle.
  • Give an example of delivering a message someone didn't want to hear.
  • Tell me about a stakeholder who was reluctant to engage — how did you bring them round?
  • Give an example of explaining something complex or technical to a non-specialist audience.
  • Tell me about a time you adapted your communication style for a particular person or situation.
  • Tell me about a time your communication approach didn't work — what did you change?

A real answer, rewritten: from 3–4/7 to 6/7

The question: "Tell me about a time you had to bring a reluctant stakeholder on board."

FailVersion 1 — scores around 3–4/7

"In my role I was rolling out a new request form that our team needed other teams to use, so that work arrived with the right information instead of us having to chase missing details. One team leader was reluctant — his team had their own way of sending requests and he didn't see why they should change.

I handled it professionally. I sent him a clear email explaining the benefits of the new form, including how it would ultimately save his team time as well as ours. I attached guidance I had written and offered to answer any questions. When he still seemed unconvinced, I arranged a meeting where I presented the reasons for the change and talked through the guidance step by step. I remained patient and polite throughout, listened to his concerns, and reassured him that the form was straightforward once you got used to it. I also kept my manager informed of the situation in case it needed escalating.

Eventually his team started using the form, and the quality of the requests we received improved. My manager was pleased with how I had handled a tricky stakeholder. It taught me the importance of clear communication and patience when introducing change."

Read it as a panel member. Every action is a broadcast: an email explaining benefits, a meeting presenting reasons, guidance talked through. The stakeholder's actual objection is never discovered — he's "reluctant", his concerns are "listened to" and then reassured away, and we never learn what they were. "Eventually his team started using the form" — was that the meeting, or attrition, or the manager quietly intervening after being "kept informed"? The panel can't tell, so they can't score it. Communication happened; influence was never demonstrated.

PassVersion 2 — scores around 6/7

"I was rolling out a new request form our team needed other teams to adopt — requests were arriving with missing information and the chasing was costing us hours a week. One team leader refused: his team had their own template and he saw the change as extra work imposed on them for our benefit.

My first move was to stop broadcasting and find out what the actual objection was. Rather than another email about benefits, I asked him for fifteen minutes and opened by asking how requests worked from his side — because 'reluctant' usually means a real cost I hadn't seen. There was one: his team submitted requests in bulk on Fridays, and my form forced them to be entered one at a time. The change genuinely was worse for him. That reframed the whole conversation — I acknowledged it directly, which changed his posture immediately, and I offered a trade: I'd build a bulk-upload version of the form for his team specifically, if he'd trial it for a month. I chose to concede the format rather than push compliance because I needed his requests' quality more than I needed uniformity — and because his team was the biggest submitter, so winning them won the rollout.

He agreed to the trial. Two weeks in, I sent him data comparing his team's query-rate before and after — down by two-thirds — because I judged evidence from his own team would persuade him where my assurances hadn't. He extended the trial himself, and then did something I hadn't asked for: recommended the form to the two remaining hold-out teams at their joint meeting.

Missing-information chasing dropped by around 70% across all submitting teams, and the bulk-upload option I'd built as a concession became the default version everyone preferred. What I took from it: influencing isn't explaining your case better — it's finding the other person's real cost, paying it where you can, and letting their own evidence do the persuading."

What changed:

  • The objection is discovered, not managed. Version 1 reassures away concerns it never identifies; Version 2 finds a real, legitimate cost — and the acknowledgement of it is the turning point.
  • A deliberate channel choice with a "because". Fifteen minutes in person instead of a third email, and the reasoning stated.
  • A concession, made strategically. Conceding the bulk format is judgement, not weakness — and the answer says why it was the right trade.
  • Evidence chosen for the audience. His own team's query-rate data, because "I judged evidence from his own team would persuade him where my assurances hadn't" — that sentence alone is descriptor language made concrete.
  • Movement you can verify. He goes from refusal, to trial, to extending it himself, to advocating unprompted. The panel can point to each step.

How Communicating and Influencing changes by grade

  • EO: handle the challenging conversation yourself — the unhappy customer, the colleague pushing back — with honesty about what can and can't be done, and adapt your communication to the person's needs. Pure de-escalation with the underlying problem untouched is the classic EO cap.
  • HEO: influence appears — someone's position moves because of you, and the difficult message is delivered by you rather than passed up. Channel choices become deliberate. The Version 2 answer above is pitched here.
  • SEO: the audience gets more senior and the stakes higher — delivering a message a senior stakeholder doesn't want to hear, moving someone who disagrees with you, translating technical material for decision-makers.
  • Grade 7: influence at organisational level — briefings and submissions that changed a senior decision, negotiating with other departments, holding a position under senior pressure while staying open to challenge.

Our complete grade guides (EO, HEO, SEO, Grade 7) cover this calibration across all nine behaviours, each with full worked examples at that grade.

Common mistakes that cap your score

  1. No resistance in the story — if nobody disagreed, nothing was influenced.
  2. Broadcasting harder as the strategy — more emails, longer meetings, clearer guidance. Influence starts with discovering the objection, not restating the case.
  3. The objection never identified — "I listened to his concerns and reassured him" without ever saying what the concerns were is unscoreable.
  4. Resolution by attrition or escalation — "eventually they came round" and "I kept my manager informed" both hand the influencing to someone or something else.
  5. Mood as the result — "they were happy with the update" is not movement. What did they do differently?

Every example here was written against the same 1–7 rubric your panel will use — see how Civil Service interviews are scored for the mechanics. To find out whether your own answers show influence or just communication, CS Interview Coach's AI scores them against grade-calibrated criteria instantly — try it free, or get every guide, the 250+ question bank and unlimited practice with Interview Sprint at £24.99/month.

Common questions

Practise before the real thing

Reading how panels score is step one. The candidates who pass are the ones who practised saying their answers out loud — and got scored feedback against the official Civil Service Behaviours framework before interview day.

Start Practising Free

3 free practice questions · No card needed · Cancel anytime