A role goes live, the link goes out, and for the first three days everything looks fine. By the second week the picture has changed. Some applications are sitting in a shared inbox, some are rows in a spreadsheet, two were forwarded to a manager who has not opened them, and nobody can say out loud who is waiting on a reply. The form itself is not the problem. The form worked. What broke is everything that happens in the twenty minutes after each submission lands.
That is worth saying plainly, because most advice about an online job application form stops at the questions. Questions are the easy part. The hard part is that a hiring intake is a queue with a service level, and a queue needs an owner, a state, and a record of what was said. This article covers both halves: what to ask, and what the form has to hand you once the answers arrive.
A job application form is an intake queue, not a survey
A survey is finished when the responses are in. A hiring form is barely started. Every submission opens a small case that stays open until the applicant is either hired or told no. That case has a state at all times, and somebody is accountable for moving it.
The practical consequence is that the tool you pick is judged on two different things. The first is whether it can collect what you need without losing people on the way. The second is whether the response list can carry work. Can two people look at the same list and see who has already screened which application? Can you tell at a glance which four candidates have been waiting eight days for an answer? Can you find, six weeks later, what was actually sent to a particular person and when?
Most form builders were designed for the first thing. A spreadsheet export is treated as the finish line, because for a customer satisfaction survey it is. For hiring it is the point where the work moves off the tool and into a set of manual habits that hold up for about thirty applications.
There is a simple test for this. Take the tool you are considering and ask where the sentence "Sam is reviewing this one, and the reply went out on Tuesday" is stored. If the honest answer is a spreadsheet column that someone remembers to fill in, or a message in a chat channel, the tool is handling half the job. That is not a reason to reject it. Small intakes run fine on habits. It is a reason to know in advance which part of the process you are carrying yourself, so that you notice when the volume outgrows it.
The fields that earn their place
Every extra question costs you applicants. Long application forms are abandoned, and the people most likely to abandon are the ones with options. The discipline is to ask only what changes a decision you are about to make.
Identity and contact
Name and email address are the only two that are never in question. Email is the field to get right, because it becomes the key that ties this person to every later message. Make it a proper email field so that typos are caught at entry rather than discovered when a reply bounces. Phone number is worth asking only if you actually call candidates at the screening stage.
The role and the terms
If you are hiring for more than one position, a single choice field for the role is worth more than a free text box, because it is the field you will filter the list by every day. Add start availability and the working pattern only when they can disqualify somebody. Asking about salary expectations at this stage is a judgement call and in some jurisdictions a legal one, so check before adding it.
The documents
A resume or CV upload, and a portfolio link where the role warrants one. Be specific about accepted file types in the question text, because the alternative is a folder of files nobody can open. The next section covers why this field causes more trouble than any other.
The questions only this role can ask
Two or three short written answers, each tied to something you will genuinely screen on. A single well chosen question of about 150 words tells you more than five generic ones and costs the applicant a fraction of the effort. Mark them as required only if an empty answer really would end the application.
What to leave out: anything you could ask at interview, anything you are collecting because the last form had it, and any field whose answer would not change what you do next. A form that takes six minutes will finish; a form that takes twenty will not.
Where to build the form
The realistic shortlist splits into tools you already pay for and tools built for intake. The figures below were taken from each vendor's own pricing and documentation pages.
| Tool | Free plan ceiling | File uploads from outside applicants | Seats on paid plans |
|---|---|---|---|
| Google Forms | Free with a Google account | Applicant must sign in to a Google Account | Sharing is by Drive permission |
| Microsoft Forms | Free with a work or school account, up to 400 forms per user | Only when responses are restricted to the organisation | Sharing is by Microsoft 365 permission |
| Jotform | 5 forms, 100 submissions a month, 100 MB | Yes | Starter through Gold are single user; Enterprise is the multiuser plan |
| Tally | Unlimited forms and submissions under a fair use policy | Yes, 10 MB per file on the free plan | Pro at 29 USD a month, unlimited members |
| Fillout | 1,000 responses a month | Yes | Unlimited seats on every plan, Starter from 15 USD a month billed annually |
| Cognito Forms | 100 entries a month, 1 user | Yes | Pro at 19 USD a month billed annually, 2 users |
| Typeform | Basic from 28 USD a month billed annually, 100 responses a month | Yes | Basic 1 user, Plus 3 users, Business 5 users |
Two things fall out of that table that matter more than the headline prices.
The first is that seat counts, not response counts, are what usually bite a hiring team. Jotform's own pricing describes Enterprise as the only multiuser plan, which means a Bronze, Silver or Gold subscription is a single login. Typeform's Basic plan is one user and Plus is three. If four people need to see the applications, check the seat line before the submission line.
The second is that free tiers on the volume based tools are sized for a trickle. A hundred submissions a month is a perfectly normal single job posting. Once you are running two or three openings at once, the free tier on a metered tool is a countdown, whereas Google Forms, Microsoft Forms and Tally do not meter submissions in the same way. Tools that price by the number of people using them rather than by the number of responses arriving remove that particular anxiety entirely, which is the trade you are making when you compare pricing models.
File uploads are where most application forms break
This is the single most common failure in a job application form, and it is almost always discovered after the posting has gone live.
Google Forms supports a file upload question, and the documentation is explicit about the cost: to answer that question, responders need to sign in to a Google Account. Uploaded files land in a folder on the form owner's Drive. For an internal process that is fine. For a public job posting it means every applicant without a Google account, or signed into a personal account they would rather not attach to a job application, hits a wall at the one question that matters most.
Microsoft Forms is stricter still. The file upload question is only available when the form is restricted to people inside the organisation, either everyone in it or a named list, and those settings require the respondent to sign in with a work or school account. That makes it a good tool for internal transfers and a poor one for external hiring.
The practical options are three. Accept the sign-in requirement, which is reasonable if you are hiring internally. Drop the upload and ask for a link instead, which shifts the problem onto applicants who then have to make a document publicly shareable. Or use a form tool where the upload question works for anonymous respondents, which every dedicated form builder in the table above supports.
If you take the third route, check two details before you launch. Where the files are stored and who can download them, since a resume is personal data and a guessable file URL is a real exposure. And what the per file size limit is, because a designer's portfolio PDF will be larger than you expect. Tally's free plan, for example, caps file uploads at 10 MB each and lifts that on Pro.
Give every application an owner and a stage
Once the applications are arriving, the question stops being "did it submit" and becomes "who has this one, and where is it".
A stage is a short list of states every application passes through: received, screening, interview, offer, declined. Five is usually enough and more than seven becomes decorative. The point is not process theatre. The point is that a list you can filter by stage answers the only question that actually causes damage when it goes unanswered, which is which applications have been sitting untouched.
An owner is the second half. Without one, an application that two people have glanced at is an application nobody has screened. Assigning a name to each submission as it arrives takes seconds and removes the entire category of silent drops.
Then there are the fields your team fills in after the fact, which are not questions on the form at all: interview date, who conducted it, the screening score, whether a reference has come back. These belong next to the application rather than in a separate document, because the separate document is the thing that goes stale. A response list that lets you define internal columns keeps the applicant's answers and your notes in one row, and exports them that way too.
Finally, keep the history. Six weeks after the fact, the useful record is not the current state but the sequence: when it arrived, when it was picked up, what was sent, when the stage changed. That sequence is what you need when a candidate asks where things stand, and what protects you when a decision is questioned. Tools built around response management keep it automatically; a spreadsheet will not.
Replying is part of the form, not a separate job
Two failures account for most of the complaints candidates make about application processes, and both are mechanical rather than attitudinal.
The first is silence at the start. An automatic acknowledgement sent the moment the form is submitted, containing a copy of what the applicant wrote, costs nothing and removes the "did that go through" email entirely. Include a realistic timeframe. A stated two weeks that you hit beats an unstated week that you miss.
The second is the reply that never goes out, or goes out twice. Rejections are the messages most likely to be forgotten, because nothing external pushes them. If the reply is sent from a personal mailbox, nobody else can see that it went, and the second person to look at the application sends it again. Sending from the same place the application lives fixes this, because the send is recorded against the record and visible to everyone.
For volume rejections, selecting several applications and sending one templated message with the candidate's name merged in is both faster and more consistent than writing each one. Keep the template honest and short. Candidates do not need a paragraph of praise; they need a clear answer and a date.
What applicants are owed about their data
A job application is a concentrated bundle of personal data: name, contact details, employment history, sometimes a photograph, occasionally more. Three decisions are worth making before the posting goes live rather than after.
Say how long you will keep it. Unsuccessful applications do not need to live forever, and an unbounded pile of resumes is a liability with no upside. Pick a retention period, write it on the form, and hold to it.
Control who can open the files. Uploaded documents should require a sign-in to download and should not sit behind a URL that can be guessed. Check this in whatever tool you choose; the difference between tools here is real.
Know where the data is stored. If your organisation has a policy about data leaving a particular jurisdiction, the form tool is part of that policy whether or not anyone has looked at it. Vendors state their storage location, and it is a two minute check.
None of this requires a legal review for a small team. It requires a sentence on the form and a decision you can point to later. The questions people ask about a tool's storage and access model are usually answered on the vendor's own site.
What to change first
Pick the one thing that has actually cost you a candidate and fix that. If applications are getting stuck, add an owner and a stage before adding a single new question. If people are dropping at the upload, move to a form that accepts files without asking applicants to sign in. When the answers and the replies need to sit in the same place, Halict shows what that looks like on a real intake.
Q1. How many questions should an online job application form have?
Enough to make the screening decision you are about to make, and no more. For most roles that is a name, an email address, the position, a document upload, and two or three short written answers. Anything that could be asked at interview should be asked at interview, because each extra field costs you applicants.
Q2. Can applicants upload a resume to a Google Form without a Google account?
No. Google's documentation states that to answer a file upload question, responders need to sign in to a Google Account. For an internal process that is usually acceptable. For a public posting it turns away anyone who does not have an account or does not want to link a personal one to a job application.
Q3. What is the difference between a contact form and a job application form?
A contact form is finished when the message arrives. A job application opens a case that stays open until the person is hired or told no, which means it needs a state, an owner, and a record of what was sent. The fields are the smaller difference; the handling afterwards is the larger one.
Q4. How long should unsuccessful applications be kept?
Long enough to answer a query or fill a similar role, and not indefinitely. Decide on a period, state it on the form so applicants know, and delete on schedule. An unbounded archive of resumes carries risk without adding value, and candidates increasingly ask.
Q5. Is a free form builder enough for hiring?
For a single opening with one person handling it, usually yes. The two limits that tend to arrive first are seats, since several free and low tier plans are single user, and monthly submission caps, which a normal job posting can reach on its own. Check both lines before the posting goes live rather than after.