How to Create a Job Application Form for Your Website

A job application form looks like a small piece of website plumbing and behaves like a hiring decision. It decides who finishes applying, what you know about them, and how quickly you can act, and most of the ones on small business websites are quietly losing candidates.

The usual failures are consistent. The form asks for things nobody will read. It demands a file upload from someone standing on a train. It arrives in an inbox where it sits for a week. Or it does not exist at all, and applications come in as unstructured emails that are impossible to compare.

This guide covers the whole thing: what to ask, what not to ask, how to handle CVs, what the law expects you to do with the data, and what has to happen after somebody presses submit.

What the Form Is Actually For

Three jobs, and being clear about them prevents most bad design decisions.

• Collect the same information from everyone. This is the real advantage over email applications. Comparable answers make a fair comparison possible, and remove the advantage that goes to whoever writes the most confident email.
• Filter lightly, not heavily. A form should screen out people who cannot do the job for a concrete reason, such as not being able to work where the work is. It should not try to rank candidates. That is what reading and interviewing are for.
• Not lose the good ones. The strongest candidates are the ones with other options and least patience for a twenty minute form. Every additional question costs you disproportionately at that end of the range.

Held against those three, most application forms are doing the second job too hard and the third one not at all.

The Fields Worth Having

A short form fills in more often. This is the set that earns its place for most roles.

• Name. One field, not three. Splitting names into first, middle and last is a small unkindness to a good part of the world.
• Email. The only contact detail you truly need. Phone can be optional.
• The role. Prefilled if the form sits on a specific job page, chosen from a list if one form serves several roles. Never a free text box, which produces titles you cannot filter.
• CV, or the same information as fields. Offer both routes.
• A link. Portfolio, repository, profile. One field, optional, and often the most useful thing on the form.
• Right to work, where it applies. A single yes or no about eligibility to work in the location, not a request for documents at this stage.
• Notice period or availability, if timing genuinely affects the decision.
• One role specific question. The most valuable field on the form, discussed below.

That is eight fields, most of them a single line, and it is enough to make a first decision about almost any role.

The Fields That Create Risk

Some questions are not merely unnecessary, they expose you. The specifics vary by country and this is not legal advice, but the direction of travel is the same nearly everywhere.

• Date of birth or age. Rarely relevant, frequently unlawful to use, and it invites a bias you cannot then prove you avoided.
• A photograph. Common in some countries and steadily disappearing, for the obvious reason.
• Marital status, family, dependants. None of it predicts anything about the work.
• Health, disability or sickness history. Adjustments for the process itself are a fair thing to offer, and a general health question is a different thing entirely.
• Nationality, ethnicity, religion, gender. If you run equal opportunities monitoring, it is a separate anonymous form, unlinked from the application and not seen by whoever decides.
• Current or previous salary. Banned in a growing number of places, and it perpetuates whatever unfairness the person arrived with. Ask what they are looking for instead, if you must ask at all.

The test that catches most of these: could you explain, to the person who did not get the job, why you asked. If not, take the field out.

CVs, Uploads and the Phone Problem

The upload field is where applications are abandoned, and the cause is almost always the same: someone is applying on a phone and the file is on a laptop at home.

Four settings make it survivable:

• Accept the formats people actually have, the common document and PDF types, and say which before the file picker opens.
• Set a size limit that fits a design portfolio, and state the number. A silent rejection after a slow upload is the worst experience on any form.
• Make the upload optional where a link or a few fields would do. A profile link plus three questions is a perfectly good first application.
• Let people finish later. Even a simple acknowledgement that they can reply to the confirmation email with their CV attached recovers candidates who would otherwise vanish.

On the storage side, uploaded CVs are personal data and should land somewhere access controlled, not in a shared mailbox that half the company can read. Decide who can see applications before you publish the form, not after the first one arrives.

The One Question Worth Asking

If you add a single thing beyond the basics, make it a specific question tied to the role, answered in a few sentences.

Good ones are concrete and cannot be answered from a template. What is the last thing you built that you were pleased with, and why. What would you check first if a customer said the site was down. Describe a time you had to say no to a client. The answers are short, comparable, and they separate candidates far better than a cover letter does.

Two rules keep it fair. Ask everyone the same question, and say roughly how long the answer should be, since an unbounded text box makes people write an essay out of anxiety. Around a hundred words is enough to see how someone thinks.

And read the answers before the CVs. It is the closest a form gets to an unbiased first impression, and several companies that have tried it never went back.

Where the Form Should Live

Placement affects volume more than any wording change.

• On the job page itself, below the description, with the role prefilled. Every extra navigation step between reading and applying costs applications.
• On a general careers page, for speculative applications. Worth having even when you are not hiring, as long as you say so honestly.
• Linked from wherever you advertised. If the advert is on a job board, the link should reach the form in one hop, not the homepage.
• Not behind a login. Account creation before applying is the single most effective way to reduce your applicant pool, and it filters for patience rather than ability.

If you list several roles, a job listings section that links each one to a prefilled form keeps the whole thing manageable. Our roundups of job application form widgets and general tips for effective website forms cover the tooling and the layout choices in more detail.

Data Protection Without a Legal Department

Applications are personal data, often including a CV with a home address on it. Where rules such as the GDPR apply, a few obligations follow, and they are manageable if you decide them in advance.

• Say what you collect and why, in plain language on the form itself, with a link to a privacy notice. One short paragraph is enough.
• Collect only what you use. Data minimisation is a principle rather than a preference, and it is set out among the principles in Article 5.
• Set a retention period and honour it. Six or twelve months after a hiring decision is a common choice. The point is that a period exists and something actually deletes.
• Ask separately about a talent pool. Keeping someone's details for future roles is a different purpose, so ask, and let them decline without affecting this application.
• Be able to find and delete one person's data. If applications are scattered across inboxes and drives, you cannot, and that is the practical reason to keep them in one place.
• Control access. Whoever needs to review applications, and nobody else.

None of this requires a policy document. It requires deciding where applications go, who can see them, and when they get deleted, then writing those three answers down.

Accessibility, Which Also Improves Completion

An inaccessible application form excludes candidates, and it does so invisibly: nobody emails to say they could not apply.

Label every field properly, with a real label rather than placeholder text that vanishes as soon as someone types. The WAI guidance on form labels covers this in a few minutes of reading.

Make errors specific and survivable. Say which field is wrong and what would be right, keep everything already entered, and put the message next to the field rather than only at the top.

Check it works with a keyboard alone. Tab through the entire form and submit it without touching a mouse. Anything you cannot reach is unreachable for a real candidate too.

Be careful with challenge tests. Image based checks defeat some disabled users entirely. If you need spam protection, prefer methods that do not require solving a puzzle.

Do not impose a time limit. A form that expires mid application is a bad experience for everyone and an impossible one for some.

One Form or One Per Role

Both work, and the choice depends on how often you hire rather than on how big you are.

One form for everything suits a business hiring a few times a year. The role is a dropdown, the fields are generic, and there is one place to check. The cost is that generic questions produce generic answers, and a candidate for a warehouse role and a candidate for a finance role are asked the same thing, which serves neither.

One form per role suits regular hiring. The role is prefilled, the specific question is genuinely specific, and applications arrive already sorted. The cost is maintenance: someone has to create the form and, more importantly, take it down when the role closes.

The middle path most companies land on is one base form with a role field and one question that changes per role. It keeps a single place to review from and still lets you ask something worth asking.

Whichever you choose, close applications properly when a role is filled. A form that keeps accepting applications for a job that no longer exists wastes people's time, and they remember. Replace it with a line saying the role is closed and, if you mean it, an invitation to be told about the next one.

Speculative Applications

Worth a form of its own, and worth being honest on it.

Some of the best hires arrive from people who liked the company and wrote in without a vacancy. A permanent, short speculative form costs nothing and catches them. What ruins it is pretending: a form that implies a role exists when nothing does produces disappointment and, quite reasonably, some anger.

So say plainly that there is no specific opening, that you keep details for a stated period, and how likely a reply is. Then ask three things: what kind of work they are looking for, a link, and anything they want you to see. That is enough to know whether to keep the conversation going.

The discipline this needs is the reply. A speculative form nobody answers is worse than no form, because it looks like an invitation. If you cannot commit to answering within a couple of weeks, offer a mailing list for new roles instead, which sets an expectation you can meet.

Reviewing What Arrives

A good form makes the reviewing quicker, and a small amount of structure makes it fairer at the same time.

• Decide what you are looking for before you read anything. Three or four things the person must be able to do. Written down, not held in someone's head, because the criteria drift as you read otherwise.
• Read the role question first, with names hidden if you can. It is the most comparable part of the application and the least loaded.
• Score against the criteria rather than ranking candidates against each other. Ranking rewards whoever wrote the most confident sentences.
• Timebox the first pass. A few minutes per application. If you cannot decide in that time, the answer is usually a short conversation rather than more reading.
• Have two people review the borderline ones, independently, before discussing. It is the cheapest bias control available.
• Note the reason for every no. One line. It makes rejections easy to write, and it shows you months later whether your criteria were sensible.

None of this requires software. It requires that the applications are in one place and in a comparable shape, which is the reason to have a form in the first place.

What Happens After Submit

The form is the visible part of a process, and the invisible part is what candidates actually judge you on.

1. Confirm immediately on screen. Not a page that looks like it might have worked. A clear message saying it arrived.
2. Send a confirmation email that repeats the role and says when they will hear back. Give a real timeframe, and one you can meet.
3. Notify a person, not a shared alias nobody owns. Applications die in unowned inboxes.
4. Write each application to one place where every reviewer can see it. A spreadsheet is a perfectly respectable answer at small volumes.
5. Reply to everyone. Including rejections, including a template, including the ones who were never close. It costs a few minutes and it is most of your reputation as an employer.

The last point is worth dwelling on. Candidates talk about the companies that never replied, and they apply again to the ones that did. A short honest rejection is worth more to your hiring than most of what you will spend on advertising.

Applying on a Phone

A large share of applications now start on a phone, often during a commute or a break, and a form designed on a desktop rarely survives the trip.

Test it on a real phone, not a narrowed browser window. Type into every field, attach a file, and submit. Most forms fail somewhere in that sequence, usually at the attachment.

Use the right keyboard. An email field should bring up the email keyboard and a phone field the number pad. It is one attribute per field and it removes a small friction from every application.

Keep fields full width and tappable. Two columns of inputs are a desktop idea. On a phone they produce targets people miss.

Do not lose what was typed. If a validation error reloads the page and empties the form, the application ends there. Test this deliberately by submitting with a field missing.

Expect the file not to exist. This is the phone specific problem and the reason the link field and the apply later route matter. A candidate who cannot attach a CV at that moment should still be able to reach you.

A form that works on a phone works everywhere. The reverse is not true, and the candidates you lose to a desktop only form are disproportionately the ones who were browsing rather than job hunting, which is a group worth having.

Problems and Their Fixes

• Applications stopped arriving. Test the form yourself end to end, including the email. The usual causes are a notification going to spam or a mail setting changed months ago.
• People start and do not finish. Count the fields, then count the required ones. The upload is the most common abandonment point.
• Every application is unsuitable. That is an advert problem, not a form problem. Say what the role needs and where it is based.
• Attachments never arrive. Check the file size limit and whether your email strips attachments. Storing the file and sending a link is more reliable than emailing it.
• Two people replied to the same candidate. Nobody owns the inbox. Give one person the job.
• Spam submissions. Expected on any public form. Use protection that does not punish real candidates, and never a puzzle as the only route.
• Old applications nobody deleted. Set the retention period now and do the first clear out today.

Getting Started

The short path. Eight fields, one of them a specific question about the role. An optional upload with a stated size limit, and a link field for people who would rather show than attach. One line saying what you do with the data, with a link to your privacy notice. A confirmation on screen and by email, with a real timeframe. One named person who reads them, and a retention date in the calendar.

If you would rather not build the uploads, the notifications and the validation yourself, a job application form widget gives you all of it on any careers page, styled to match your site, with the applications arriving somewhere you can actually work through them.

If you are building more than one form, creating a petition form covers the same ground for collecting names and consent at scale, where the volume rather than the comparison is the point.