How to Answer Online Job Application Questions

Online job application forms ask the same handful of questions, dressed up differently each time. Civil service behaviours, NHS Jobs supporting information, graduate scheme motivational answers, "why do you want to work here" textboxes on Greenhouse and Workday — once you spot the three patterns underneath, almost every online job application question gets faster to answer. This guide covers those patterns and the framework that handles competency-based answers in writing.

The 3 question types you'll see on every online application form

1. Identity questions — who you are, where you're heading. ("Tell us about yourself", "Why are you applying for this role?", "Why this organisation?")
2. Capability questions — what you can do, with evidence. ("What are your key strengths for this role?", "Describe a project you're proud of.")
3. Competency-based questions — what you've actually done in specific situations. ("Tell us about a time you handled a difficult stakeholder", "Describe an example of when you led a team through change.")

The first two are answered with structure and one specific example. The third — competency-based — is where the STAR framework earns its keep, especially in written form where you can't rely on tone or follow-up questions.

The STAR framework for written application answers

STAR = Situation, Task, Action, Result. It originated in behavioural interview prep, but it works just as well — arguably better — in a 250- or 500-word written application answer. The medium changes the cadence:

• Situation — the context in two or three sentences. You have more room in writing than in speech, so set the stage clearly.
• Task — what you specifically had to do. One paragraph.
• Action — the steps you took. This is the longest part, often two paragraphs of numbered detail.
• Result — what happened. Numbers if you have them.

Question (250-word answer): "Tell us about a time you had to influence someone without authority."

Last year I was leading a content strategy project for a B2B client. The design team was booked solid for the quarter and refused to take new briefs.

I needed three landing pages designed within four weeks to hit our launch date. I couldn't escalate above the design lead — that would have damaged the working relationship and slowed everything else down — so I had to find a path the team would say yes to.

I spent an hour pulling together a one-pager that estimated the design effort (six days), the revenue impact of hitting launch (£140k of contracted ARR at risk), and a proposal: their team would do the visual direction and final QA, my team would handle the wireframes and asset prep. I walked the design lead through it in person rather than over Slack, because the proposal involved a split of work that's easier to discuss than to read.

They agreed in the meeting, the work landed in the four-week window, and we shipped on time. We've used the same split twice since for similar deadline crunches.

Notice what's specific: the timeline, the revenue figure, the one-pager, the in-person conversation. Vague STAR answers ("I built rapport and aligned stakeholders") are worse than no answer because they signal you don't have a real example.

"Tell us about yourself" — what to actually write

The mistake is treating this as a biography question. It isn't. It's "give us the elevator argument for why you're the right person for this role, in writing."

Three short paragraphs in roughly 250 words:

1. Where you are now, framed for relevance to this role. ("I'm a senior backend engineer at Linnet, where I've spent the last three years building the payments infrastructure.")
2. One signature achievement that maps to what they're hiring for. ("Most recently I led the rebuild of our subscription billing system — it now handles 4x the volume on half the compute.")
3. Why this role, briefly. ("I'm looking to move into a staff role with broader scope, and your team's work on multi-region payments is exactly the technical surface I want to grow into.")

Do not open with university. Do not recite your CV chronologically. The application form already has your CV attached.

"Why do you want this job?" — how to make it specific in writing

Generic answer: "I'm passionate about your mission and excited to grow with the company."

Specific answer: "Two reasons. First, the JD mentions you're rebuilding the search infrastructure this year — that's the exact problem I worked on at Greybridge, and I'd like to get back to that depth of technical work. Second, three of the engineers I respect most have moved here in the last 18 months. That's not a coincidence I want to ignore."

The pattern: name two concrete things, one about the work itself and one about the people or environment. Both should reference something you actually know about the organisation, not generic praise. Written form gives you the advantage of being able to cite specifics from the JD directly — use it.

"What are your key strengths for this role?" — without the cliché

Pick two and back each with one sentence of evidence. Don't list five — it sounds like you're hedging, and reviewers reading 200 applications skim the first two anyway.

For weaknesses on the same form: do not write "I'm a perfectionist." Pick a real one, name what you're doing about it, and pick one that doesn't disqualify you for this specific role.

"I tend to commit to too much at once — I've had to consciously block out planning time at the start of each quarter and say no to anything that doesn't make the priority cut. Two years ago I would have said yes to everything and quietly dropped balls; three weeks ago I declined a tempting cross-functional project because it wasn't on the OKRs."

That answer is honest, shows self-awareness, names the system, and gives a recent example. It also fills the word count without padding.

Competency-based questions: the four families

Most competency-based application questions cluster into four families. Pick one rehearsed STAR story per family and you can adapt the same stories to most variants.

• Conflict / influence: a time you disagreed with a teammate or stakeholder.
• Failure / recovery: a time something went wrong on your watch, and what you did.
• Leadership / ownership: a time you took the lead without being asked.
• Ambiguity / decision: a time you had to make a call without enough information.

When the form asks "describe a time you handled a difficult customer", you reach for your conflict story and adapt the framing. You don't draft new content for every variant — you have four flexible written answers ready, and you tweak the opening and closing sentences to match the prompt.

If the slow part is starting from a blank textarea on the eighth supplementary question of a long online application form, AI Job Answers' Application Question tool lets you paste questions one at a time and get a 250- or 500-word answer that uses your CV, your voice, and the job description's specific language. Each answer stacks below the previous so you can work through the whole form in one session. Free, no signup.