CS Interview Coach
Start Free

By grade

Working Together SEO Example Answers (Civil Service)

Published

The Working Together answer that earns a 6 at HEO — one relationship built from cold, a wobble worked through, reciprocity you can point at — drifts to a 4 at SEO for a structural reason: it's bilateral. The SEO calibration of the shared descriptor band wants the plural everywhere the HEO version has a singular: relationships with a range of stakeholders, joined-up working within your own team and across other groups, and — the part that separates the grade — collaboration with genuine stakes in it, where the partners need things from each other that they're reluctant to give, where some of the friction is between them rather than with you, and where what you build has to survive the people who built it. At SEO you're not the counterpart in a partnership. You're increasingly its architect and, when it strains, its broker.

What SEO panels score on this behaviour

A network, not a dyad. Several parties — teams, organisations, professions — with different incentives, brought into something that delivers. The strongest evidence includes brokering between partners in tension with each other.

Stakes that make cooperation hard. Shared caseloads, pooled resources, data one side guards and the other needs. If nothing valuable changes hands, the collaboration was a meeting series.

Structures over rapport. Terms of reference, escalation routes, shared measures, agreed handoffs — the machinery that lets the partnership survive personnel churn. Rapport is how you build it; structure is what you leave.

Wellbeing, installed. At SEO the descriptor's put in place support means something structural: capacity protected, pressure routed somewhere, the partnership designed not to grind its people.

Questions this appears as

  • "Tell me about establishing joint working across teams or organisations."
  • "Describe a partnership you built that had to deliver something."
  • "Tell me about managing tensions between different parties you worked with."
  • "How have you created effective collaboration where it didn't exist?"

Probes to expect: "What did each party want?", "What happened when their interests clashed?", "What of this still exists now?"

Fail vs pass at SEO: the same caseload

FailVersion 1 — one good bilateral relationship, scores around 4/7 at SEO

"Part of my team's caseload involved vulnerable customers whose situations crossed into local authority responsibilities — housing, social care — and historically the interface was poor: cases bounced between us and councils with customers stuck in the middle. I built a strong working relationship with our largest local authority to fix this. I reached out to their service manager, and we set up monthly liaison meetings, agreed a named-contact arrangement for urgent cases, and developed a shared understanding of each organisation's remit so cases stopped being passed back and forth. The relationship became genuinely effective — urgent cases got resolved in days rather than weeks, both teams understood each other far better, and the council's manager described it as the best working relationship they had with a government department. Based on that success, my G7 asked me to look at how we might extend the approach to other authorities in our patch."

A genuinely good HEO answer — built from cold, structured, measurably better, with reciprocity implied. At SEO calibration, the caps are visible: it's one relationship, with the friendliest possible counterpart (they self-selected by engaging), no interests genuinely collided, nothing structural exists beyond two people's arrangement — and the tell is the final sentence, where the actual SEO-sized task (extend it across the patch) is where this story ends rather than begins. The panel scores the bilateral: a 4.

PassVersion 2 — the same caseload, around 6/7

"My team's vulnerable-customer caseload crossed into local authority territory — housing, social care — and the interface failed the same way across our whole patch: cases bouncing, customers stuck. A bilateral fix with one friendly council would have helped one corner of the problem, so I set out to build something that worked across all seven authorities we dealt with, which meant building a partnership between parties who wanted different things — including from each other. The interests genuinely conflicted: the large metropolitan councils wanted a dedicated named-contact route (they had volume to justify it), the small districts wanted anything but that (they couldn't staff it), our own operational teams wanted councils to stop referring cases that weren't ours, and every council wanted the same from us. Two of the councils also had history with each other over a boundary-case dispute and wouldn't initially sit in the same working group. I designed the collaboration around those conflicts rather than pretending them away. Instead of one model imposed on seven authorities, we agreed a two-tier structure: a named-contact route for the three high-volume councils, and a shared triage inbox with a 48-hour response standard for the four small ones — each tier getting what its scale actually needed. The referral friction I turned into the partnership's first joint product: a two-page 'whose case is it' guide drafted by one of my caseworkers with a council counterpart, which both sides had equal reason to want because both sides were drowning in each other's misdirected referrals. For the two feuding councils, I didn't try to fix their history — I structured around it, putting them in different tiers with no shared meetings, and let eighteen months of the arrangement working do what mediation wouldn't. The wellbeing piece I built in deliberately: the previous informal arrangements had run on individual goodwill — one named contact at a council going off sick had collapsed a whole route the year before — so every route in the new structure had a deputy, and the urgent-case escalation flowed to a rota, not a person. When our biggest partner council hit a budget crisis mid-year and their response times doubled, the structure earned its keep: rather than the relationship souring, the quarterly review surfaced it early, we flexed the standard for them for two quarters — openly, with the other six informed why — and they stayed in. Three years on, the two-tier model is still running, has survived complete personnel turnover on both sides including mine, was adopted by a neighbouring region, and cross-boundary case resolution went from a median of five weeks to nine days. The 'whose case is it' guide is on its fourth version — maintained by people I've never met, which is the outcome I'd argue matters most."

The annotation:

  1. The bilateral is explicitly declined. "A fix with one friendly council would have helped one corner" — the answer opens by rejecting Version 1's entire scope. That's the calibration difference stated in a sentence.
  2. The conflict map has partners clashing with each other. Big councils vs small on the contact model, mutual referral resentment, two councils feuding — friction the candidate must broker, not just absorb. This is the plural the SEO band wants.
  3. Design around conflict, not through it. The two-tier structure gives colliding interests different answers instead of one compromise nobody wanted; the feud is architected around rather than heroically mediated. Judgement about which fights to have is collaboration evidence.
  4. Reciprocity engineered as a product. The "whose case is it" guide works because both sides were drowning in each other's referrals — mutual interest located and built on, with a caseworker credited as co-author.
  5. Wellbeing as architecture. Deputies on every route, escalation to a rota not a person — the put in place support descriptor delivered structurally, with the previous collapse as the stated reason.
  6. The structure tested and durable. The budget-crisis quarter proves the machinery (early surfacing, open flexing, six partners informed); three years, full personnel turnover, regional adoption and a guide maintained by strangers prove the thing outlived its builder — the ultimate SEO collaboration mark.

Calibrating either side of SEO

At HEO, Version 1 — the bilateral built from cold with reciprocity and a wobble — is close to a 6. At G7, the network grows again: partnerships maintained across organisations to deliver shared objectives, assumptions challenged at senior tables, compromise deployed where it buys progress. Behaviour-wide guidance: the Working Together pillar.

SEO-specific mistakes on this behaviour

  1. The bilateral ceiling. One relationship, however good, answers the HEO calibration. Count the parties in your story.
  2. Frictionless partners. If every party wanted the collaboration equally, the collaboration proves little. Find the story where interests collided.
  3. Rapport as the deliverable. "The best relationship they had with a department" is lovely and dies when you change jobs. Show the structure.
  4. All friction pointing at you. Brokering between partners in tension with each other is the premium evidence — most candidates never think to claim it.
  5. Goodwill as infrastructure. Arrangements running on named individuals are outages waiting to happen — and saying so, with deputies and rotas built in, converts the wellbeing descriptor into structure.
  6. No survival test. "Still running, without me" is the strongest closing evidence this behaviour has. If it's true, say it.

If Working Together is on your SEO advert, count the parties and the stakes in your current answer — the AI coach scores it against the real descriptors at SEO calibration and tells you whether it's a network or a dyad. Three sessions free; the SEO Complete Guide runs every behaviour through the trade-off principle.

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