Why Do Job Applications Ask Demographic Questions?

You upload your resume, type your name, retype half the information that was already on your resume because we’re still doing that in 2026, and then you get to those questions at the end of the application.

What is your race?

What is your gender?

Are you a protected veteran?

Do you have a disability?

It’s stressful no matter your answers because why exactly does a company need to know any of that before they’ve even decided to interview you.

Especially when we’re constantly told that employers aren’t supposed to make hiring decisions based on those things.

So… why are they asking? Will this influence the decision after all?

Why Ask Demographic Questions at All?

There are a few different reasons, and this is where things get a little more complicated than “the government makes them do it.”

In the US, the Equal Employment Opportunity Commission, or EEOC, is the federal agency responsible for enforcing federal laws against employment discrimination. For certain employers, it also collects demographic information about their workforce.

For example, private employers with 100 or more employees generally have to submit an annual EEO-1 report containing workforce information broken down by job category, race or ethnicity, and sex.

Notice I said workforce there.

The EEO-1 itself isn’t a report of everyone who applied to the company.

So why collect demographic information during the application?

Because companies may also want, or in some cases need, to track what their applicant pool looks like. The EEOC specifically recognizes applicant-flow tracking as a legitimate reason for collecting race information, as long as that information is kept separate from what is being used to actually make the hiring decision.

That can tell a company something that employee demographics alone can’t.

Let’s say 40% of the people applying for a company’s jobs belong to a particular demographic, but only 5% of the people making it through the hiring process do. That’s something worth looking into.

You can’t identify that gap if you only start collecting demographic information after someone is hired.

Then There Are Federal Contractors

This is another reason these questions show up on applications, particularly the question about protected veteran status.

Certain federal contractors have additional obligations under laws like the Vietnam Era Veterans’ Readjustment Assistance Act, better known as VEVRAA.

Covered contractors are required to give applicants an opportunity to voluntarily self-identify as protected veterans. That information helps them measure whether their veteran recruiting and hiring efforts are actually working.

Disability self-identification has also historically been part of federal-contractor compliance under Section 503 of the Rehabilitation Act, although those rules changed very recently. The Department of Labor discontinued its federal disability self-identification form effective September 21, 2026.

So if you’ve been applying for jobs for a while and feel like you’ve seen these questions approximately 900 times, you’re not imagining things. Some of the rules surrounding them are also actively changing.

What About Those Tax-Credit Questions?

This is actually a separate thing.

For years, employers could potentially receive the federal Work Opportunity Tax Credit, or WOTC, for hiring people who belonged to certain groups that faced barriers to employment.

That included some veterans, people receiving SNAP or certain other forms of public assistance, people experiencing long-term unemployment, formerly incarcerated people, and several other specific groups.

That program required employers to screen for eligibility around the time of hire, which is one reason candidates sometimes encountered questions that seemed VERY personal for a job application.

But as of 2026, this is outdated information.

The federal WOTC currently does not apply to employees who begin work after December 31, 2025, and the IRS says the Form 8850 previously used for that screening is no longer in use.

So if we’re talking specifically about those standard race, sex, veteran, and disability questions you see on applications today, “the company gets a tax break for hiring diverse people” is not a good explanation for them.

Why Not Just Ask After Someone Is Hired?

For some information, they absolutely can.

If the company only needs demographic information about its employees, collecting it during onboarding makes the most sense.

Applicant demographics are different, though, and waiting until onboarding completely changes what you’re measuring.

You would know who the company hired but you wouldn’t know who applied.

That makes it much harder to spot whether something weird is happening somewhere between application and hire.

The company may have a recruiting problem and isn’t reaching a very diverse group of applicants in the first place. Maybe plenty of people from an underrepresented group are applying, but they’re disproportionately dropping out at another stage of the hiring process.

Those are two very different problems and you need applicant data to be able to see it and investigate appropriately.

There Is Still a Candidate-Experience Problem Here

Just because we understand why companies collect the information doesn’t change the fact that applicants don’t like being asked for it.

You’re applying for a job and suddenly being asked about your race, gender, veteran status, or other personal information by a company you have absolutely no relationship with yet.

Even when there’s a perfectly legitimate reason behind the questions, it can feel like you’re giving the hiring team information they’re not supposed to use.

Then there’s the application itself.

Every additional page and question is another thing standing between someone finding your job and actually submitting an application. There’s plenty of reason for employers to pay attention to application abandonment and remove questions they don’t actually need.

That doesn’t automatically mean demographic questions themselves are causing applicants to leave, but it is worth considering.

Can Recruiters See Your Answers?

This is the part candidates are usually actually worried about.

And the frustrating answer is: it depends on the system and how the company has configured it.

These questions are supposed to be separate from the information being used to evaluate your qualifications. The EEOC has specifically recommended separating demographic information from the application so it isn’t used in selection decisions.

In the recruiting systems I’ve worked in, I have not been sitting there looking at someone’s race, gender, disability status, or other EEO answers while deciding whether to interview them.

That doesn’t mean I can promise you that no recruiter anywhere can access demographic data in their system. There are far too many ATS platforms and configurations for me to make that claim.

But the entire point of separating this information is that it should not be part of the recruiter’s decision about whether you’re qualified for the job.

And legally, an employer cannot make hiring decisions because of protected characteristics like race, color, religion, sex, national origin, age 40 or older, disability, or genetic information.

Do You Have to Answer?

For these voluntary self-identification questions? Nope 🙂

Many demographic self-identification questions are voluntary and include something along the lines of “I don’t wish to answer.”

If you don’t feel comfortable sharing the information, you can choose that option when it’s available.

I’ve never looked at someone’s EEO information to decide whether I wanted to interview them, and I don’t assume another recruiter is secretly sitting behind their computer going, “Aha! Gotcha!” every time someone fills one out.

I Don’t Think There Is a Perfect Answer Here

Collecting applicant demographic information can help companies figure out whether their recruiting and hiring processes are actually reaching and advancing different groups of people.

Candidates can also reasonably look at a question asking about their race before they’ve even spoken to another human being and think, “Why do you need to know that?”

Removing the questions entirely might make some candidates more comfortable and shorten the application, but could also mean losing information that could reveal disparities in who applies and who ultimately gets hired.

Keeping them gives companies more data, but only works if candidates understand why they’re being asked and trust that the information isn’t being used against them.

And I think that’s the key piece that employers miss when evaluating whether or not to keep them in.

If you’re going to ask people for sensitive information before they’ve even met you, explaining why you’re collecting it and clearly telling them whether answering is voluntary goes a long way.

“Don’t worry about it, it’s for EEO” isn’t particularly comforting to someone who doesn’t spend their life swimming in HR acronyms.

At the end of the day, all you can do is trust your gut and know that if a company is using that against you, it’s not only illegal, but just straight up a company you don’t want to work for.

Like what you just read?

I write about hiring, content creation, internet culture, and whatever else I can’t stop thinking about that week.

Subscribe to Said & Dunn to get new articles sent straight to your inbox. No algorithm required.