An application form has one job: make fifty candidates comparable. Not impressive, not welcoming, comparable. Everything else is decoration, and most of the decoration costs you applicants.
Here is the set of questions that earns its place, and the order to ask them in.
Ask the knock-outs first
Every role has one or two answers that end the conversation regardless of how good the rest is. Work authorisation. A required certification. A location or shift pattern that is not negotiable. An absolute salary floor.
Ask those in the first section, before anything else.
This is not about filtering people out efficiently. It is about not asking someone to spend twelve minutes on a form when the second question already decided the outcome. Putting knock-outs first is the single most respectful thing an application form can do.
Good knock-out questions:
- “Are you legally allowed to work in [country]?”: multiple choice
- “This role is on-site in Berlin four days a week. Does that work for you?”, multiple choice
- “Do you hold [required certification]?”: multiple choice
Keep them closed-set. A knock-out you have to interpret is not a knock-out.
Ask the role, then branch on it
If you have three vacancies open, you do not need three forms. Ask which role the candidate is applying for as a dropdown, then route each choice to a section with that role’s specific questions.
One URL to publish, one place to check applications, and no candidate ever sees a question meant for a different job. Per-answer branching is what makes this work, each option in the dropdown points at its own section.
Ask for the things you will actually compare
For each remaining question, ask yourself: will I line up all the answers to this and compare them? If not, cut it.
The questions that survive that test are usually:
Notice period. A dropdown of bands, not a text box. “Immediately / 2 weeks / 1 month / 3 months / Other.”
Salary expectation. Bands again. A free-text box gets you “negotiable”, “market rate”, and “£45k-ish”, none of which sort.
Tool or skill experience. A rating grid with one row per tool and a shared scale. Six data points, one screen, and every candidate rated on the same axis.
One short written answer. Exactly one. “Why this role, in three sentences?” is enough to hear a voice; anything more is an essay you will not read fifty of.
The CV. A file upload question, so it arrives attached to the application rather than in a separate email thread.
The questions to cut
“Tell us about yourself.” Nobody reads fifty of these, and the candidates who write the best ones are the ones with the most time, not the most skill.
A cover letter box. If you genuinely read them, ask for one. Almost nobody does, and it is a measurable drop in completed applications.
Full employment history retyped from the CV. You have the CV. Asking for the same information twice reads as indifference to the applicant’s time.
Date of birth, gender, nationality, photo. Do not ask unless you have a specific legal reason to, and if you do, ask separately for anonymised diversity monitoring rather than on the application itself.
“Where did you hear about us?” A fine question, but it is recruitment analytics, not assessment. Put it last, optional.
Order it like a funnel
- Knock-outs, the answers that end it
- Which role, the branching question
- Identity. Name, email, nothing more
- Role-specific screening, the comparable questions
- CV upload
- One written answer
- Optional extras, portfolio link, how they heard about you
Sections make this legible, and a progress bar makes an eight-question form feel like an eight-question form rather than an unknown quantity.
Score the screening questions
Give the closed-set screening questions point values, and every application arrives already scored. Our quiz scoring is the same mechanism. It does not care whether the “right answer” is a fact or a hiring criterion.
That gets you a shortlist before anyone reads a CV. Written answers still need a human, which is exactly right: the machine sorts on the criteria you can state, and the human reads the ones you cannot.
A word of caution: score the requirements, not the proxies. Points for a required certification is a criterion. Points for years of experience is usually a proxy, and it filters out the people who got good faster.
Tell them what happens next
The confirmation message is part of the form. Say when they will hear back, and from whom. Enable the emailed copy so they keep a record of what they submitted.
It costs one sentence and it is the difference between a candidate who waits and a candidate who assumes you are not serious.
Then delete it
An application round is personal data with an expiry date. When hiring closes, export what you need to keep and delete the rest: Questionful holds responses until you remove them, and self-service deletion is one click. Retention policies are much easier to honour when the data is not quietly accumulating in a form you forgot about.
The short version
- Knock-outs first, always.
- One form, branched by role.
- Only ask what you will line up and compare.
- Bands over text boxes for notice period and salary.
- One written answer, not three.
- Score the closed questions, read the open one.
- Say what happens next, then delete the round when it closes.
The job application form template is already in this shape, and the hiring use case covers the workflow around it: CV storage, notifications, and getting the round out to a CSV when it closes.