How Many Fields Should a Job Application Form Have So Candidates Don't Quit

You posted the job, paid to promote it, people land on the page and… they don't apply. Most of the time the problem isn't the ad — it's the form. A job application form that's too long is like a long queue at the checkout: the person is interested, but gives up halfway because they don't feel like going through all of it.

The good news is you don't have to guess. There's a simple logic behind forms that actually get completed: you ask only enough to be able to call the person, and you learn the rest at the interview. In this article I'll show you exactly how many fields to use, which ones help, and which ones drive candidates away without you realizing it.

The core rule: ask only enough to call the candidate

A job application form isn't an HR file. It's not the place to collect everything about a person before you've even met them. Its only job is to give you enough to decide whether they're worth a phone call.

Ask yourself at every field: "Do I need this to call the person, or can I learn it at the interview?" If the answer is "I can learn it at the interview," cut it. Date of birth, full address, ID number, a written motivation — you learn all of that in five minutes of conversation. You don't need it upfront.

Good candidates often apply from their phone, on a break, between other jobs they're browsing. If the form asks for ten minutes and a CV they don't have on hand, you lose them — and often the best ones, because they have options.

The minimal set that works

For most jobs at small and mid-sized companies, you need very little to start a conversation. A set that fills out in under a minute:

• Name (one field, not separate "first name" + "last name")
• Phone — the channel people respond to fastest
• Which role they're applying for (if you have several openings)
• One free, optional field: "Tell us briefly about your experience," or attach a CV

That's it. You can make email optional, because many field-work candidates don't check email often but reply on the phone or WhatsApp within minutes.

If you feel the urge to add something, add it as optional and put it at the end. A short form with one open question brings you more quality people than a long one that scares everyone off from the start.

The fields that quietly drive candidates away

Some fields look useful but actually cut into your applications without anyone telling you why they quit:

• Mandatory CV: the biggest involuntary filter. The person applies from their phone and doesn't have the CV there. Make it optional and offer an alternative (a text field).
• Written motivation ("Why do you want to work with us?"): few people stop to write an essay for a job they're not even sure about yet. Ask at the interview.
• Desired salary upfront: it puts people on the defensive and makes you lose good conversations before they start.
• ID number, full address, date of birth: you don't need them to call someone, and on the data-protection side you're creating obligations for nothing.

The simple rule: every extra mandatory field is one more reason to abandon. Keep only the ones you genuinely can't continue without.

Required vs. optional: this is where you lose the most people

The difference between a required field and an optional one is huge in practice. An optional field sits there for whoever wants to fill it; a required one, with a red asterisk, blocks submission until it's filled — and that's where people quit.

The rule worth keeping: required = only what you need to make contact (name + phone). Everything else, optional.

Watch out for overly aggressive validation too. A phone field that rejects the number because the person added a space or a country prefix is a real cause of abandonment, and the most frustrating one, because the person genuinely wanted to apply. Accept common formats and don't make the candidate guess exactly how you want the number written.

The real battle is on the phone

Most candidates reach the form from a phone, not a laptop. If the form isn't built for a phone, you lose them no matter how short it is:

• Fields need to be large, easy to tap with a finger
• The right keyboard: numeric for phone, with @ for email — not the standard keyboard on a phone-number field
• Browser autofill should work (name and phone fill themselves)
• No pinching to zoom or struggling to hit the submit button

A form that works perfectly on a laptop can be a nightmare on a phone. It's worth testing it yourself, from your own phone, exactly the way a candidate does. More often than not, that's where you discover why nobody applies.

What happens after "Submit" matters just as much

A candidate who hits "Submit" and sees nothing clear immediately wonders whether it went through. Put a clear message: "We got your application, we'll call you within two days." Simple and reassuring.

And more importantly: call fast. A good candidate applies to several places at once. Whoever calls first often wins. A short form does nothing if you reply a week later.

At MPO Web Studio we build exactly this kind of form — short, built for phones, with applications landing straight with you, not in an inbox you never check. We can prepare a ready-made demo of your hiring page so you can see how it looks before deciding anything, and we work remotely across the whole country. If you'd like to see what it would look like for your business, message us on WhatsApp and we'll show you.