Application forms

An application form is a structured way to collect information from people applying for something specific. Unlike a generic contact form, an application form asks targeted questions that help you evaluate whether someone fits what you need.

Take any job posting and look at what hiring managers actually need before they schedule an interview. Not a life story. Not why the candidate wants the job. Not their entire work history. They need to know if this person has the basic qualifications to do the work, if they are available to start, and if they have proof they can do it. That is what an application form collects. The right questions, in the right format, so comparing applicants takes minutes instead of hours.

Most hiring teams skip the application form entirely. They use a contact form or they let people email resumes however they want. The result is chaos. One resume is a PDF. Another is a Google Doc. Someone sends a Word file. Resumes arrive in three different email threads. Some candidates include references, some do not. Some answer questions about salary, some refuse. You end up with 50 responses in 50 different formats. Comparing anyone feels impossible.

An application form stops that. Everyone fills out the same form. Everyone provides the same information in the same order. You spend less time organizing and more time evaluating who is actually qualified. The better your form, the better your hires because you get the right information upfront to make real decisions.

What fields matter in an application form

Most application forms have too many fields. Hiring managers think "I might want to know..." and then they ask about everything. The result is forms that take 20 minutes to complete and candidates abandon them halfway through. A well-designed application form asks only what you need to make a real decision.

Required identification fields

Name and email address. These tell you who the person is and how to contact them. Make both required. Do not ask for phone number unless you plan to call people. Typing a phone number into a form feels invasive when someone expects email communication. If phone is important, explain why next to the field. "We will call within 24 hours to schedule your interview."

Current role and years of relevant experience

What is their job title right now? How many years have they done this type of work? These two questions tell you if someone has a baseline level of experience. Do not ask for a detailed work history. You are screening, not interviewing. If they pass this question, you call them and ask about previous roles.

Availability to start

A dropdown with dates like "Immediately", "Two weeks", "One month", "Two months", "Flexible". This tells you if their timeline matches your needs. You can filter applications by start date. Some roles need someone right now. Some can wait. This field lets candidates self-select based on your needs.

Resume or portfolio link (optional or conditional)

A file upload field or a text field where they paste a link. Make it optional on the initial application. Or ask a qualifier first like "Do you have a portfolio or published work in this field?" and only show the upload field if they say yes. If you require a file upload on the first form, watch abandonment jump 20% to 30%.

One qualification question

A single open-ended text field where they answer one specific thing that matters for this role. For a designer, ask "Describe one design project you are proud of." For a marketer, ask "What is a campaign you ran that got measurable results?" For a developer, ask "What is a technical problem you solved?" One question. Not a 500-word essay but not a single sentence either. Two or three sentences tells you how they think.

Agreement to terms

A checkbox that says "I confirm the information I provided is accurate and I agree to the privacy policy." That is it. Do not ask candidates to opt into your newsletter or agree to multiple things. One checkbox. One agreement.

What you should never ask in an application form

These fields add friction without adding qualification value. They increase abandonment and do not help you evaluate anyone.

Phone number as required

Candidates expect email communication. Requiring a phone number makes the form feel invasive. They do not know if you plan to sell their number or call them at 6am. Make it optional.

References

Ask for references after someone passes your qualification screening. Not on the application form. If you ask for three references upfront, you lose candidates who do not want to give them until they know you are serious about hiring them.

Salary expectations

This belongs in an interview, not an application form. Salary is a negotiation. Most candidates will not put a number in writing until they know more about the role. If you need to filter by salary, do that with a quick phone call after reviewing their application.

Detailed work history

Do not ask for a resume embedded in the form. Do not ask them to list every job they have ever had. You want a resume link or file. That is enough. If their experience is relevant, you call them and talk through their background.

Personality tests or "why do you want this job" essays

These are interview questions, not application questions. An application form qualifies people. An interview explores if they are a culture fit. Do not mix the two. Keep the form focused on whether they can do the work.

Personal details that are not relevant

Do not ask about race, age, nationality, religion, disability, or marital status. Some of this is illegal to ask. All of it is unnecessary at application stage. You are screening for skills and fit. Personal details have nothing to do with either.

How to structure your application form for completion

An application form that looks short gets completed more than one that looks long. A form that is confusing gets abandoned. Structure matters.

Easy questions first, then harder questions

Start with name and email. Then ask current role. Then ask years of experience. Only after they have answered two simple things do you ask the harder question like "Describe a project you did." Someone who has filled out two fields is more likely to finish than someone who sees the hard question first.

Use a single-column layout

Do not put name and email side by side. Stack everything vertically in one column. Especially on mobile, side-by-side fields make people scroll horizontally and abandon. One column, top to bottom.

Use dropdowns instead of open text when possible

Years of experience. Use a dropdown with "0-2 years", "3-5 years", "6-10 years", "10+ years". Do not ask them to type a number. Availability to start. Use a dropdown with pre-set dates. Company size they have worked in. Use a dropdown. Dropdowns are faster to fill and reduce typos and variation.

Use conditional logic to hide irrelevant fields

If the role does not require a portfolio, ask "Do you have a portfolio?" first. If they say no, do not show a portfolio upload field. If they say yes, show it. Same form, different experience for different people. Perceived form length drops 30% or more.

Use a progress bar on longer applications

If your application has more than six fields, break it into pages. First page. Name, email, current role, years of experience. Shows "Step 1 of 2". Second page. Availability, resume link, one qualification question. Shows "Step 2 of 2". Psychologically, someone feels like they are committing to "just a few questions" not to a long form. Completion rate jumps.

Test on mobile first

Over half of job applicants apply on their phone during a lunch break or sitting at home in the evening. If your form is hard to use on mobile, you lose half your applicants. Large buttons. Large text fields. Mobile-friendly dropdowns. Date pickers that work on phones. Test your form on your phone before you launch it. If you would not fill it out, neither will your candidates.

How to reduce abandonment

If more than 40% of people who start your application do not finish it, your form is too long or too confusing.

Reduce field count first

If you have more than eight fields, cut it down to five or six. Remove your least important field. See if completion rate improves. If it does, you found friction. Keep it off. Test removing a different field next. Keep cutting until completion improves. Field count is almost always the problem.

Use heat mapping to find where people drop off

A heat map shows you which fields people skip and where they abandon the form. If everyone fills in the first four fields but nobody completes the resume upload, you found your problem. Move the resume field to a second page. Or make it conditional. Or remove it from the initial application. Heat mapping data tells you exactly where to improve.

Test removing or reordering fields

Remove the lowest-priority field and see if completion improves. Reorder fields. Sometimes moving a harder question to the end, after someone has committed to filling out the form, changes the completion dynamic entirely. Small changes compound.

Use multi-step forms to break up length

A 12-field application on one page feels daunting. Split it into two pages with 6 fields each and completion can jump 15% to 20%. The form is still 12 fields but the experience is "just six questions" per page. Psychological length matters more than actual length.

What happens after someone submits

The application arrives. Now what? Set clear expectations.

Show a thank you message immediately

After submission, show a message like "Thanks for applying. We will review your application and get back to you within 3 business days." Do not leave them wondering. Set a clear expectation. Then actually meet it. If you say 3 business days, respond in 3 business days.

Send a confirmation email automatically

Immediately after they submit, send a confirmation email. Include what they submitted. Include what comes next. Include a clear timeline. This tells them the form worked. It gives them a record. It builds confidence they were heard. Do not skip this.

Route applications to the right person

If you have multiple open roles, use conditional logic to route applications to the right hiring manager. Someone applying for a sales role goes to your sales manager. Someone applying for engineering goes to your CTO. Automatic routing. No applications get lost. No one ends up with the wrong hiring manager.

WEMASY application form features

WEMASY's form builder makes it easy to create application forms that get completed. Use conditional logic to show different fields based on answers. Use multi-step forms with progress bars for longer applications. Mobile design is automatic. Email confirmations go out automatically. Submissions appear in your dashboard organized and searchable. Integrations send applications directly to your CRM or email so you can manage candidates in one place. No coding required.

See what is included in each plan at /pricing.

FAQ

How many fields should an application form have?

Should I require a resume on my job application form?

Can I ask for references on the application form?

Should my application be one page or multiple pages?

What should I do if half my applicants abandon the form?

How do I know if someone started my application but did not finish?

DEVELOPMENT VERSION