Job application form questions: what to ask, what to leave out

The US Equal Employment Opportunity Commission puts the principle plainly: information requested before hiring should be limited to what is essential for deciding whether someone is qualified for the job. Acas gives UK employers the same advice in different words: personal information on an application form should be relevant to the job or to running the recruitment. That gives you a simple filter for every question. Does it help you decide who to interview for this role?

The trap is collecting everything up front because it is convenient later. Bank details, emergency contacts, date of birth for payroll and ID documents all have a place in hiring, but that place is after an offer, in onboarding. Asking for them at the application stage makes the form longer, collects data on dozens of people you will not hire, and in some cases puts protected information in front of the people deciding who to shortlist.

Keep the form to what a hiring manager will actually read. For most roles, contact details, a CV upload, two or three role-specific questions and the availability and right-to-work questions come to eight to ten fields. That is enough to decide who to interview.

Knockout questions help when you get a lot of applications. A "Yes / No" on a genuine requirement (a driving licence, a specific certification, being able to work the advertised shifts) can route people who answer No to a polite ending screen. Use them only for requirements you really would not waive, and write the requirement into the job ad too, so nobody is surprised.

Federal law does not ban every sensitive question on paper. The EEOC's position is that questions about race, sex, national origin, age or religion may be used as evidence of an intent to discriminate unless a business purpose justifies them, so the safe practice is to leave them off. Disability is stricter: under the ADA, employers are explicitly prohibited from asking disability-related questions before an offer, though they may ask whether a candidate can perform specific job functions.

On criminal history, the EEOC's 2012 guidance recommends that employers not ask about convictions on job applications. Arrests are weaker still: the EEOC notes that an arrest is not proof that someone committed a crime. Many places go further. The National Employment Law Project's guide, last dated October 2021, counted 37 states and more than 150 cities and counties with ban-the-box policies, 15 of them states covering private employers. Federal agencies may not ask until after a conditional offer. Rules and timing differ by state and city, so check where each role is based.

Salary history is similar. HR Dive's running list, updated in April 2026, tracks roughly two dozen state-level laws plus local ones restricting pay-history questions, though some cover only public employers. Asking for salary expectations avoids the problem everywhere.

Section 60 of the Equality Act 2010 stops employers asking about an applicant's health or disability before offering them work, or before putting them in a pool of candidates to be offered work, except in narrow cases. Acas lists them: finding out whether someone needs adjustments for the recruitment process itself, equality monitoring, and a few specific exceptions. So "Do you need any adjustments for the interview?" is fine; "Do you have any health conditions?" is not.

Acas also says to ask about age only if a legal minimum age applies to the job, and to keep any equality monitoring form separate from the application and away from the people making the decision. For criminal records, applicants in England and Wales generally do not have to disclose spent convictions unless the role is eligible for a standard or enhanced DBS check. Right-to-work checks are a legal duty for UK employers, so ask whether the applicant has the right to work in the UK and check documents once you make an offer.

The GDPR applies to every applicant's data, not just to employees. Article 5 requires personal data to be adequate, relevant and limited to what is necessary, and kept no longer than needed, so set a retention period for unsuccessful applications and delete them when it ends. Article 9 prohibits processing health, religious, ethnic and sexual-orientation data unless an exception applies, and Article 10 allows criminal-conviction data only under official authority or where law authorises it. National employment law adds more, so check the rules in each country you hire in.

If you monitor diversity, and many employers do, keep it off the application form. Acas says the monitoring form should not ask for the applicant's name or anything that identifies them, and should be kept apart from the application and CV so decision-makers never see it. Every question on it should include "Prefer not to say".

The practical way to do this is two separate forms: the application, and a short optional monitoring survey linked from the application's thank-you screen, with no identifying fields. US employers subject to EEO-1 reporting or federal contractor rules have their own self-identification requirements, which are outside the scope of this guide.

Zunoform works for small teams that hire a few people a year and want a clean application form without an applicant tracking system. On every plan you get file upload for CVs (10 MB per file on Free), conditional logic for knockout questions and role-specific branches, a scheduler question for booking interviews, and responses sent to Google Sheets. One-response-per-person settings reduce duplicate applications. Anonymous mode, which stores no IP address or device details, suits a separate monitoring form.

It is not an applicant tracking system. There is no candidate pipeline, CV parsing, interview scorecards or job board posting. If you hire regularly, a dedicated ATS will serve you better. The Free plan also caps responses at 500 a month, which a popular role can pass. Google Forms and Tally have no response cap on their free plans.