Competency-based interview questions and example answers

Halfway through a system rollout I was coordinating, the supplier withdrew the version we had trained sixty staff on — their support deadline moved, and we had six weeks to switch to the newer version or run something unsupported.

I gave myself one afternoon to be annoyed, then treated it as a re-plan rather than a setback. I ran a gap analysis that evening: of our twelve training modules, seven were unchanged, three needed screenshots replacing, and two needed genuine redesign. That shrank the problem from 'retrain everyone' to 'redesign two modules' — and I communicated exactly that framing to the sixty staff, because the version they had heard was 'everything we learned is obsolete', and morale was becoming the bigger risk.

We converted the two modules into short floor-walking sessions in week one of go-live rather than classroom time before it, which people preferred anyway. Go-live happened inside the original window, the two redesigned areas generated the fewest support tickets of any module — attention follows redesign — and the gap-analysis habit became my standard first response to any imposed change: measure the delta before reacting to the drama.

A director wanted our supplier-performance figures in a stakeholder pack two days before the data cut-off that made them reliable — the early version would have flattered one supplier because their worst week fell just outside the window. He knew the pack's date; he didn't know the cut-off detail, and 'just use what we have' was said in the tone of a decision already made.

I didn't relitigate it in the meeting. I sent him a three-line note within the hour: the early figures would overstate one supplier's performance, here is the specific week that changes the picture, and here are two options — publish with a dated caveat, or hold that single table for two days while the rest of the pack goes out on time. I made the recommendation explicit: hold the table. Making it easy to choose right mattered more than being right.

He took the two-day option without comment, and the pack went out with accurate figures. Nothing dramatic happened — which is the point. Six months later his office started asking us for 'the cut-off check' on data requests, which told me the note had changed a habit, not just a table.

I organised the relocation of our 40-person office over a single weekend — the kind of project that is entirely logistics and entirely unforgiving, because Monday morning arrives whether you are ready or not.

I planned it backwards from Monday 8am. Working in reverse exposed the true dependencies: phones needed the network live, the network needed the comms room signed off, the comms room was the landlord's job and therefore my biggest risk — so I moved it to the front of the timeline and negotiated its completion a full week early, with a walkthrough test rather than a promise as the evidence. Everything movable got a numbered-zone system matching desks to crates, and I published one A4 page per team: your zone, your boxes, your Monday desk.

Two things still went wrong, as they do: a lift failed on Saturday morning, and one team's crates were double-numbered. The lift cost us ninety minutes against the four hours of slack I'd built into Saturday for exactly this category of surprise; the crate clash was resolved from the master list in twenty minutes. Monday 8am, 38 of 40 people worked normally; the last two were live by ten. The backwards plan and zone system were reused for the next office move after I'd left — by the colleague I'd walked through the method.

A customer rang about an application rejected for a missing document — the third rejection in a cycle, because each rejection letter restarted a process that took her weeks. Listening properly, the real problem surfaced: she was a carer, the document needed a counter-signature from a professional she could only reach at specific times, and our fourteen-day deadline kept expiring in exactly that gap.

The standard response was another letter. Instead I checked what the process actually allowed rather than what we usually did — and found the deadline was our convention, not a legal requirement. I extended her deadline to thirty days on a documented discretion, noted the reason on her file so the next colleague would not undo it, and completed the rest of her checks by phone in the same call so the counter-signature was the only outstanding item.

Her application completed eleven days later, at the third attempt becoming the last. Then I did the part that made it competency evidence rather than a good deed: I wrote up the case pattern — carers hitting the fourteen-day wall — and the team lead agreed a flagged extension option for carer cases, which used the discretion we had always had. Four similar cases used it in the following quarter, none of which required anyone to be lucky enough to reach me.