Illegal Interview Questions: What You Cannot Ask as an Employer

There is no federal list of interview questions that are illegal to say out loud. What federal law actually does is turn the answer into evidence. Title VII, the ADEA and GINA make it unlawful to base a hiring decision on race, color, religion, sex, national origin, age over 40, or genetic information, so asking about those topics creates a record that you held the information and then rejected the candidate. The one true prohibition on asking is disability: the ADA bars pre-offer inquiries outright. On top of that, roughly twenty states ban salary history questions, and a growing set of state rules reach further.

Most guidance on this subject is a list of forbidden phrases, which is a comforting format and a slightly misleading one. Interviewers who memorize the list still get into trouble, because the risk is not in the wording. It is in what you learned and what you did next.

What follows is how the rules are actually structured, the handful of questions that genuinely are prohibited to ask, and the practical part nobody writes down: what to do when an interviewer asks one by accident. This is general information for US hiring teams rather than legal advice, and anything multi-state is worth a short conversation with employment counsel.

What questions are illegal to ask in an interview?

Start with the distinction that makes the rest make sense. Federal anti-discrimination law is written about decisions, not about questions. Title VII does not say you may not ask someone their religion. It says you may not fail or refuse to hire someone because of their religion. The EEOC puts the practical consequence plainly: inquiries that are not themselves forbidden "may be used as evidence of an employer's intent to discriminate unless the questions asked can be justified by some business purpose."

So asking a candidate whether they have young children is not a crime. It is a question that hands the candidate's lawyer a fact, and leaves you explaining to a jury why the woman you asked about childcare was not the person you hired. The EEOC's own standard for the whole process is that the information requested "should be limited to those essential for determining if a person is qualified for the job," which is a better working rule than any list of banned phrases.

The exception, and the one place where the asking really is the violation, is disability. Everything else on the table below is a question that becomes dangerous through use.

Read the middle column as the useful one. In almost every row the legitimate business need behind the bad question has a clean, job-related version that gets you better information anyway. You do not actually want to know whether someone has children. You want to know whether they can work the shift.

Can you ask a candidate about a disability or a medical condition?

No, and this is the clearest prohibition in the whole area. The ADA states that an employer "shall not conduct a medical examination or make inquiries of a job applicant as to whether such applicant is an individual with a disability or as to the nature or severity of such disability." That is a rule against the question itself, before any offer exists, regardless of what you do with the answer.

The same statute tells you what remains open: "A covered entity may make preemployment inquiries into the ability of an applicant to perform job-related functions." So you can describe what the job physically and practically requires and ask whether the candidate can do it, with or without reasonable accommodation. You cannot work backwards from that to the diagnosis.

Two traps catch decent interviewers here. The first is the friendly follow-up: a candidate volunteers a condition unprompted, and the interviewer, trying to be human, asks about it. Sympathy is not a defense. Acknowledge it, note that accommodations can be discussed later, and return to the job. The second is attendance history, because asking how many sick days someone took is a medical inquiry wearing a scheduling costume.

Can you ask about salary history?

In much of the country, no. Salary history bans exist to stop pay gaps following people between employers, and they are state and local rather than federal. Counts published in 2026 range from about eighteen to twenty-two states depending on whether the source includes jurisdictions where the ban reaches only public sector employers by executive order, so treat any headline number with suspicion and verify your own states.

What these laws generally permit is asking about expectations. You may ask what a candidate is looking for; you may not ask what they currently earn, and in the stricter jurisdictions you also may not rely on the figure even if the candidate offers it unprompted. That last detail catches people out, because a volunteered number feels like fair game and often is not.

For a distributed team the practical answer is to stop asking everywhere. A single national script is easier to train and audit than a rule that changes by candidate location, and the expectations question is more useful in a negotiation anyway.

Are there questions that are legal federally but illegal in your state?

Yes, and this is where multi-state hiring gets genuinely difficult. State law is the fastest-moving part of this area and it consistently runs ahead of the federal floor. Illinois amended its Human Rights Act effective January 1, 2026 to address AI in hiring and named zip code specifically as an impermissible proxy for a protected class, which is a rule about inference rather than about questions. Illinois also requires notice, an explanation and consent before an AI-analyzed video interview. New York City requires an independent bias audit within the previous twelve months plus ten business days of notice to candidates before using an automated employment decision tool.

The rule that surprises remote-hiring teams most is jurisdictional. These duties generally follow the location of the job and the candidate, not your headquarters. A company in Texas hiring someone into a New York City role is inside the New York City rule. We keep a running breakdown in AI interview laws by state and a plain explanation of what counts as a regulated tool in what is an AEDT. When you need to see how a rule has actually been applied rather than how it reads, searching case law in plain English gets you to the decisions faster than working through a statute alone.

What happens if an interviewer asks an illegal question by accident?

Usually nothing, and the instinct to panic makes it worse. A single stray question is not automatically a lawsuit. What matters is whether the information influenced the decision and whether you can show it did not.

Three things help, in order. Document the job-related reason for the decision at the time you make it, not afterwards when you are reconstructing. Make sure the candidate was evaluated on the same criteria as everyone else in the pool. And do not compound it by treating the candidate differently from that point forward, because the retaliation claim is often easier to prove than the underlying one. If a candidate raises it directly, take it seriously and route it to HR rather than debating it in the room.

The prevention is duller and more effective: write the questions in advance and have interviewers ask those. Almost every problematic question in real hiring is improvised, asked in the loose small-talk minutes at the start or the end, by someone trying to build rapport. Unstructured conversation is where this risk lives, which is the same reason it produces weaker predictive signal, as we cover in structured vs unstructured interviews.

How do you stop it happening at all?

Fix the format rather than the people. An interview built from a fixed, reviewed question set, asked in the same order, scored against a written rubric, removes most of this exposure as a side effect of being a better interview. The questions were approved before anyone was in the room. The scoring is anchored to criteria you wrote down. And when someone later asks why a candidate did not advance, the answer is a rubric score against a job-related standard rather than a recollection.

That consistency is also what makes an audit survivable. If every candidate for a role got the same questions, you can demonstrate it. If each of six interviewers freestyled, you cannot, and the gap between what people believe they asked and what they actually asked is wide.

This is the strongest honest argument for running first-round screening through structured interview software or an AI interview assistant: not that software has better judgment than your recruiters, but that it asks the approved question, every time, to every candidate, and produces a transcript proving it. Ours follows up on what a candidate actually said rather than reading a fixed list, but the follow-ups are generated against your rubric and the whole exchange is recorded and scored, which is exactly the record you want if the process is ever questioned. Scoring mechanics are on candidate interview scoring, and the compliance posture on AI hiring compliance.

None of that removes the need for trained interviewers in later rounds, where conversation should be looser and a human is making a judgment call. It removes the risk from the round where you are talking to the most people and paying the least attention, which is where the accidents happen.