Should you answer the voluntary demographic questions?

There is no answer that helps you, and no answer that hurts you, that anyone can demonstrate. So the honest version is: this is a question about what you are comfortable with, not a tactic — and the most useful thing we can do is tell you exactly what the form is, since we read hundreds of them.

We are not lawyers and none of this is legal advice. Everything factual below is either something we measured in a live application payload or something the form itself says in its own preamble.

What the block is

At the end of most US application forms sit four questions: race and ethnicity, gender, protected veteran status, and disability status. They arrive in a separate section from the rest of the form — on Greenhouse, literally a separate array in the payload, either compliance or demographic_questions depending on the board — and they carry their own preamble written by the vendor or the government rather than by the employer.

Every one of the 36 live Greenhouse payloads we sampled that included a compliance section had the identical structure: a preamble block containing no questions at all, followed by four questions. That first block is the Paperwork Reduction Act statement, which is why it has nothing to fill in.

The block exists because some US employers — larger ones, and federal contractors — file periodic workforce demographic reports, and the numbers in those reports have to come from somewhere. That is what the preamble on the form says it is for, in more words.

Outside the US it is not the same instrument. Some European boards ask about gender as an ordinary form field with no compliance framing at all; Personio publishes a plain gender field on boards that use it. A question that looks like the US block is not automatically the US block.

Voluntary means voluntary — and blank is not the same as declining

Every one of these questions offers a way out. What surprised us is how much the wording varies, and that the variation has consequences.

The obvious phrasings are "Prefer not to say" and "Decline to self-identify". But GitLab's disability question, for instance, offers "I do not want to answer" and nothing else that declines. We found that the hard way: our own matcher only recognised the wish family of phrasings, so a user who had chosen "decline everywhere" got that one question left blank instead.

Blank and declined are different answers. Declining is a recorded response. Blank is a missing value, and on a required question it is also a form that will not submit.

If you are declining, decline explicitly, using whichever of that employer's options actually means it. It takes the same click.

What we can see, and what we cannot

We can see the questions, the options, the required flags, and whether the employer's board publishes the block at all. Mozilla's Greenhouse boards publish neither shape. Rippling does not put its equal-opportunity questionnaire in the payload at all — it adds it on its own page — so on a Rippling application you will meet those questions for the first time on their site, and no tool can show them to you in advance.

We cannot see what happens to the answers. Not whether they are stored apart from your application, not whether a hiring manager can see them, not whether an employer configured it either way. The form's statement that the answers will not be used in the hiring decision is the employer's statement about their own process, and there is no mechanism available to you or to us that verifies it. That is not an accusation. It is just the shape of the situation, and any article that tells you confidently which way it goes is guessing.

The case for answering

The numbers only exist if people supply them. A demographic report compiled from a self-selecting subset of applicants is a worse measurement than one compiled from most of them, and the people most likely to decline are frequently the people the measurement is meant to detect. If you think the reporting is worth doing, that argument is not nothing.

It is also, genuinely, four clicks.

The case for declining

You cannot verify the promise, the answers travel with an application that will be read by people you have not met, and "voluntary" is doing a lot of work in a document where every other field is a hiring decision. Declining is offered on every form for a reason, it is never held against you in any process we have seen described, and nothing downstream distinguishes a declined answer from a large pile of other declined answers.

If you are uneasy, that unease is a sufficient reason. This is one of the few boxes on an application where "I would rather not" is a listed option.

The disability question is not like the other three

Worth pulling out separately, because people click through it fast.

The US disability self-identification form is not a yes/no about a category you already think of yourself as being in. It names example conditions and asks whether you have, or have ever had, one of them — and the list is broader than most people expect, covering things many applicants have never once thought of as a disability. Whatever you decide, decide that one having read it, rather than by pattern-matching from the other three.

What Crossing does with all of this

Three rules, and they are in the code rather than in a policy page:

We never infer any of it. There is no path — not a weak one, not a guarded one, none — from your résumé, your name or your location to a demographic field. Any question we detect as demographic is answered from your own stored choice or not at all.

The default is "ask me". Not a stored answer, not a decline, not blank. If you would rather set it once, you can choose "decline everywhere" or store your own answers, and both are your choice made deliberately in one place.

The answers are never remembered from a form. Ordinary questions get filed under a key and reused at the next employer. Demographic keys are excluded from that store entirely, by prefix, so a future question we have not seen yet cannot leak into it. A demographic question we fail to recognise as one of the four standard ones is given no memory key at all — the failure mode is "ask again", never "reuse".

The reason for the third rule is specific. A demographic answer replayed across employers is not a convenience; it is a profile.

Our actual opinion

We do not have one about what you should answer, and we would be suspicious of a product that did.

We do have one about the mechanism: no software should ever fill these in for you, and no software should be able to guess them. Everything else here is genuinely yours to weigh — but that part is not a preference, it is a line, and it is why these four questions are the only fields in Crossing that our own automation is forbidden to touch.

The questions every job application asks covers the rest of the form. What we do with your résumé covers where the data goes.