How to Answer "Why Do You Want This Job?" on an Application Form

"Why do you want this job?" is the most-asked written question on online application forms — and the one most candidates fail at. The reason is structural: the question feels open-ended, so candidates default to generic praise ("I'm passionate about your mission"), and reviewers reading 200 applications spot the pattern in two seconds. Specificity wins. This guide covers the structure, the worked example, and what to cut from the first draft.

Why this question is on every online application form

The hiring team uses "why do you want this job?" as a fit filter. They're not looking for enthusiasm — that's available from every applicant. They're looking for evidence that you've actually understood the role, the team, or the company well enough that your reasons hold up under scrutiny. A vague answer suggests you applied broadly without thinking. A specific answer signals retention probability — the most expensive metric in graduate and mid-level hiring.

Some application forms ask the question once. Others split it into "why this role?" and "why this company?" — sometimes "why this team?" too. The structure below works for any of them; you just adjust what each paragraph covers depending on which split the form uses.

How long should the answer be?

Most application forms cap this question at 250 or 500 words. Practical defaults:

• 250-word cap: aim for 200–240 words. Two short paragraphs is the right shape.
• 500-word cap: aim for 400–470 words. Three paragraphs.
• Under 60% of cap: looks lazy on a competitive role.
• Over cap: form blocks submission. Don't draft past it.

Reviewers read in chunks. A wall of text at the cap reads as worse than a tighter answer at 80% — even though more words could mean more evidence, in practice they usually mean more padding.

The two-reasons structure that scores well

The reliable shape:

1. One opening sentence that names what you're applying for and signals confidence (no warm-up, no "I am writing to apply for…").
2. Two specific reasons, each as a short paragraph. One about the role itself; one about the company or team. Each backed by one piece of evidence — a specific JD detail, a public company decision, a named team practice, or a named conversation.
3. One closing sentence that links your motivation to a concrete next step or scope of the role.

Two reasons beats four reasons. Four reasons signals hedging — you don't know which one matters. Two with evidence reads as someone who's thought about it.

Worked example: 250-word answer for a marketing exec role

I'm applying because the role's combination of full-funnel performance marketing and a real B2B audience matches what I want my next two years to look like.

What attracts me to the role specifically is the scope around the new self-serve product launch. The JD describes owning the paid-acquisition strategy from PMM brief through to post-launch optimisation, which is the breadth I haven't had in my current role at Linnet — there I run the paid-search channel in isolation while a separate team owns the strategy. Owning end-to-end is the experience I want before I move into a senior position, and it's rare on standalone-channel briefs in B2B at this stage.

What attracts me to your company specifically is the public commitment in your January investor update to triple self-serve revenue by 2027 — and the team's decision to build the acquisition function in-house rather than agency-led. I read your CMO's post on why the team chose the in-house route, and the trade-offs they accepted (slower at first, more durable later) match how I'd think about it. Speaking to one of your current performance marketers confirmed the team's actually structured this way in practice rather than on paper.

What I'd want to do in the first six months is bring my paid-search experience to the self-serve launch, and learn the upper-funnel craft from the rest of the team while I do.

That's 240 words for a 250-word cap. Two reasons (the work, the company), each with concrete evidence (the JD scope, the investor update, the CMO's post, the named conversation). One forward-looking closing sentence.

How "why this role?" differs from "why this company?"

When the form splits the question:

• "Why this role?" is about the work. Scope, technical surface, team you'd join, what you'd own day-to-day. Evidence comes from the JD, public engineering blogs, the team's product, or what you've heard from people in the role.
• "Why this company?" is about the organisation. Strategy, market position, recent decisions, mission, culture. Evidence comes from annual reports, press releases, the leadership's public commentary, or your read of the industry.

Don't repeat content. If you mention the JD's "self-serve launch scope" under "why this role?", don't bring it up again under "why this company?" — the reviewer will read both, and overlap reads as content-padding.

Common mistakes that get the answer scored down

• "Passion" as a substitute for reasons. "I'm passionate about your mission" is filler. Cut every instance and replace with a specific fact.
• Mission-statement quoting. Reading the company's own values back to it is the most-seen template move. It earns nothing.
• Negative framing of current role. "My current role doesn't give me the scope I need" reads as bitter. Frame everything towards the new role, not away from the current one.
• Generic praise. "You're a leader in the space" applies to a hundred companies. Test each reason: would this still be true if I changed the company name? If yes, cut or replace.
• Salary or career-ladder framing. "I'm looking for a more senior role" makes the reviewer feel like a stepping-stone. Reframe around what the role offers (the scope, the team, the technical surface), not what you want from it.
• No specific company evidence. At least one paragraph must cite something the company has actually done — a launch, a strategy decision, a published view, an organisational choice. Without that, the answer reads as if you applied without research.

If the slow part is starting from a blank box and getting the two-reasons structure right under a word cap, AI Job Answers' Application Question tool drafts a 250-word answer from your CV and the job description in seconds — leaving you the time to add the specific company-research detail that turns a generic answer into a scored one. The same shape underpins motivational questions on graduate scheme applications and civil service behaviour answers.