What's the difference between a competency-based question and a behavioural question?

They're effectively the same thing. "Competency-based" is the term used by HR and structured-hiring frameworks (civil service Success Profiles, NHS, graduate schemes); "behavioural" is the term most often used in interview prep. Both ask you to evidence a specific skill area through a real example, and STAR works for both. The difference is the medium — written competency answers have a word cap and no follow-up question.

How long should a written competency-based answer be?

Most online application forms cap competency answers at 250 words; civil service caps are 250 standard, 500 for senior grades; graduate schemes vary from 250 to 400. Use 80–95% of whatever cap is set. Anything under 70% scores lower because you haven't given the panel enough evidence to mark.

Can I use a university or volunteer example in a written competency answer?

Yes, when you have nothing stronger from work and the example is genuinely substantive. Final-year projects, society leadership, and structured volunteering all work. A university example with a real outcome and named contributions beats a vague work example. Don't reach back further than that — A-level examples on a graduate application read as thin.

How do I find what competencies are being assessed before I write?

Read the job description carefully — it usually names the competencies explicitly ("working together", "delivering at pace", "making effective decisions") or implies them through the role description. For civil service campaigns, the candidate pack lists the named behaviours. For NHS, the person specification's skills section maps directly. If it's not named, the question itself is the clue ("tell us about a time you handled conflict" → influencing/conflict competency).

Should each competency answer use a different example?

Aim for distinct examples per competency where possible. Sift panels notice repetition, and unless each answer extracts a different facet of the work, the second use of the same example scores lower. Have at least four distinct STAR stories prepared before you start drafting — one each for conflict/influence, failure/recovery, leadership/ownership, and ambiguity/decision.

Competency-Based Application Questions: Written Answer Templates

Most online job application forms include at least one competency-based question, and senior-grade applications usually have three or four. The question feels open-ended ("tell us about a time you led a team through change") but it is scored against a defined competency on a structured rubric — not against your writing ability. Get the structure right and you score well; treat it as a personal essay and you score below threshold. This guide gives you the templates, the worked example, and the mistakes that keep otherwise-strong candidates out at sift.

What is a competency-based application question?

A competency-based application question asks you to give one specific real example that evidences a defined skill area. The phrasing is consistent across forms:

"Tell us about a time you…"
"Describe an example of when you…"
"Give an example of how you have…"

The competency is named explicitly in some frameworks (civil service Success Profiles, large corporate ATS templates) and implied in others (most graduate scheme questions, NHS Jobs supporting information sub-questions). Either way, the panel has a defined rubric for what a "good" answer looks like at the level of the role.

The 6 most common written competency areas

Across civil service, NHS, graduate schemes, and corporate ATS forms, the same six competency areas come up repeatedly:

Working together / teamwork — collaboration with people you don't manage.
Communicating and influencing — landing a message, changing a mind without authority.
Delivering at pace / managing your work — hitting a deadline under constraint.
Making effective decisions — judgement under incomplete information.
Leading and managing — directing others (formal authority or informal).
Changing and improving / problem-solving — making something better than you found it.

Each form will use slightly different language — civil service "behaviours", NHS "person spec criteria", corporate "competency frameworks" — but the underlying skill areas are recognisable across all of them.

STAR template that fits a 250-word box

For a 250-word cap, the proven distribution:

Situation (35–50 words) — one sentence on context, one on what made it tricky.
Task (25–40 words) — what you specifically had to do. Use "I", not "we".
Action (130–160 words) — the bulk of the answer. This is where the marks live. Numbered or short-paragraph detail of what you did, why, and what you considered.
Result (35–50 words) — what happened. At least one number where possible.

The most common scoring failure is spending 100 words on Situation and Task (low-scoring) and only 80 on Action (high-scoring). Flip that ratio in every answer.

Worked example: "Tell us about a time you had to deal with conflict"

Competency: Working Together / Communicating and Influencing.

Situation. As project lead on a six-month CRM migration, I clashed with the head of sales over the cutover date. He wanted to delay by three weeks to protect quarter-end forecasting; I wanted to keep the date to avoid a six-month overshoot.

Task. I had to either find a path he'd agree to or escalate, but escalation would have damaged the working relationship and slowed the next phase of the project.

Action. I spent a morning building a one-page risk comparison: what we'd lose by delaying (six weeks of finance team time on parallel reconciliation, deferred cost savings of around £42k a month) versus what we'd lose by holding the date (a higher-risk forecast for Q4 because the new pipeline reports would be unfamiliar to his team for two weeks). I proposed a compromise: hold the date, but add a one-week shadow-running period where his team could use both the old and new reports side by side. I walked him through the comparison in a 30-minute meeting rather than on Slack, because the trade-off involved trust as much as numbers, and asked him to push back on any of the figures he disagreed with before we agreed.

Result. He accepted the compromise; we hit the original cutover date; the shadow-running period was used by 9 of his 12 team members in the first three days. We've used the same conflict-resolution shape twice since on different cross-functional decisions.

That's 235 words for a 250-word cap. Specific numbers (£42k, 9 of 12, three weeks, six months), named action (the one-page comparison, the 30-minute meeting), specific outcome. The question's competency (handling conflict, influencing without authority) is evidenced through the actions, not asserted in the opening.

How written competency questions differ from interview competency questions

The same STAR framework works for both, but the medium changes the cadence:

Written: word-capped, no follow-up. Pack more numbered detail into Action; spend less on rapport-building openers.
Interview: time-bound (~2 minutes spoken), follow-up likely. Spend more on Situation/Task to let the interviewer ask probing questions; Action is shorter because depth comes from the follow-up.

Written answers can carry more density per word because the panel reads at their own pace, and you have no chance to clarify. That's why the "fewer words on Situation, more on Action" rule matters more in writing than in speech.

How to build 4 reusable STAR stories before drafting

Most candidates draft each competency answer from scratch and panic when the form asks for four. Better approach: build a four-story library before opening the form.

Story 1: Conflict / influence — disagreement with stakeholder, persuasion without authority.
Story 2: Failure / recovery — something went wrong on your watch; what you did about it.
Story 3: Leadership / ownership — taking the lead without being asked.
Story 4: Ambiguity / decision — making a call without enough information.

Most competency questions on online application forms map onto one of these four. Have each story rehearsed in 250-word and 500-word versions, then adapt the opening and closing sentences to match the specific competency phrasing. This is faster, and it forces you to use distinct examples rather than reusing one across four answers.

Common mistakes that score low

Vague Action paragraph. "I worked with the team to align on a path forward" earns nothing. Specifics in the Action paragraph carry the mark.
"We" instead of "I". Panels are alert to team-level credit. Use "I" generously and name the specific decisions or actions you owned.
No numbers in Result. "Stakeholders were happy" is unscored. "Pipeline accuracy improved by 14% in the first quarter post-cutover" is scored.
Reused example across answers. Allowed but penalised. Aim for four distinct stories.
Topic sentence that doesn't mirror the competency. If the question is about working together, your opening sentence should signal collaboration explicitly. Don't make the panel infer.

If the slow part is starting from a blank box on the third or fourth competency question of an application, AI Job Answers' Application Question tool drafts a 250-word STAR answer from your CV and the job description in seconds, with the structure already shaped to score. Edit each answer for the specific competency and named example; the framework guide on online job application questions covers the patterns underneath competency, motivational, and identity questions across all four written-application surfaces.