Policy

Ask What the Job Requires, Not What the Person Is

Federal law publishes no list of banned interview questions. A question is rarely the violation by itself: what is unlawful is using a protected characteristic in the decision, and a screening practice generally must be job related and consistent with business necessity. The ADA is the sharp exception, barring disability and medical inquiries before a conditional offer even when the answer is job related. Ask about performing the essential functions with or without reasonable accommodation, never about a condition. State and city law adds outright bans, salary history above all.

The takeThe training everyone runs targets the wrong surface. One interviewer's slip is a single event in one room; an application form's required field, a knockout question or a screening chatbot's script asks the same thing of every applicant and leaves a record proving it. So audit the automated question sets first, in every state each requisition is open in, and brief the panel second. The exposure has moved out of the room and into the script. Most compliance decks, I'd expect, have not followed it.

Where Olive fits

Open a role and see what the work shows

A hiring file that shows what was asked is also the cheapest evidence that nothing else was. Olive keeps its assessment record on the same footing: six findings written by a person, each carrying the timestamped excerpt it rests on, and every released report exporting with its rubric and item-bank versions attached.

Rank your shortlist

Which questions are actually illegal?

Almost none by name. Title VII, the ADEA and the ADA do not publish a list of forbidden sentences. All three make it unlawful to use a protected characteristic in the decision, and for a practice that screens people out Title VII's touchstone is business necessity, with any test required to measure "the person for the job and not the person in the abstract" 1. The ADA writes job-relatedness and business necessity into the statute itself 2.

Griggs is a 1971 case about a diploma requirement and two aptitude tests at one power plant. Its burden-shifting framework was narrowed by Wards Cove in 1989 and restored and modified by the Civil Rights Act of 1991, so read Griggs for the principle and that Act for the operative burdens. The ADEA runs on a separate track: the Supreme Court held in 2008 that the business necessity test has no place in ADEA disparate-impact cases, where the employer's defense is a reasonable factor other than age 7.

The ADA is the exception that behaves like a list. Under 42 U.S.C. 12112(d)(2)(A), an employer may not conduct a medical examination or ask a job applicant whether they have a disability, or about its nature or severity, before a conditional offer 2. The same subsection permits inquiries into the applicant's ability to perform job-related functions. That is why an interviewer may ask "can you perform the essential functions of this role, with or without reasonable accommodation?" before an offer. A kindly meant "do you have any conditions we should know about?" is barred at that stage.

So the practical list has to be derived. A question is a problem when it asks what a person *is* rather than what the job *requires*, and the familiar topics are familiar because they almost always do:

  • Age, graduation year, or how long someone plans to keep working.
  • National origin, accent, first language, citizenship beyond authorization to work.
  • Marital status, children, pregnancy, childcare or family plans.
  • Religion, observance, or which holidays someone takes.
  • Disability, health, medications, workers' compensation history, absence records.
  • Arrest history, and in many places conviction history before an offer.

This is US federal law as it stands in August 2026, stated as public legal fact. Any specific requisition belongs in front of counsel.

Replace each banned question with the one the job needs

For every question you are dropping, write the one that gets what the job actually needs. This is the step the list posts skip, and skipping it is why an interviewer either asks the banned question or asks nothing and loses real information. The substitute is almost always a plain statement of a requirement followed by a question about meeting it.

  • Instead of "do you have kids?" or "what does your partner do?" ask the schedule question directly: "This role is on call one weekend in four and the rota is published a month ahead. Does that work for you?" You wanted the availability, not the family.
  • Instead of "where are you from?" ask "are you authorized to work in the United States, and will you need sponsorship now or in the future?" Identity documents belong to the I-9, which comes after an offer.
  • Instead of "when did you graduate?" ask for the credential itself and for the work: "which degree, and what have you built with it since?" The year is a proxy for age and tells you nothing the transcript does not.
  • Instead of "any health issues that would get in the way?" ask "the role involves lifting to 20kg and two site visits a week. Can you perform those functions, with or without reasonable accommodation?" State the function, then ask about the function.
  • Instead of "have you ever been arrested?" ask nothing at this stage, and run whatever background check your jurisdiction permits at the point it permits it.
  • Instead of "what are you making now?" ask "here is the band for this role. Does that work?" Anchoring on your own band is better negotiating practice anyway.

One more substitution worth planning, because it is now asked badly more often than any of these: how a candidate uses AI in their work. There is a job-related version and a version that drifts toward monitoring, and whether you can legally ask candidates how they use AI separates them.

Where does state and city law go further?

Further in several directions, and the law that applies is the one where the requisition is open rather than where the company sits. Labor Code 432.3, in the version effective January 1, 2026, bars a California employer from seeking an applicant's salary history at all, personally or through an agent, and from relying on it in an offer decision, unless the applicant volunteered it unprompted 3. A remote requisition open in eight states is subject to eight sets of rules.

Criminal-history timing is the second layer, and it is a rule about when a question may be asked. Fair-chance laws set that timing and they do not all set it the same way, so the thing to check is which of a requisition's states and cities have one and what each of them requires. Counsel in each jurisdiction is the cheaper version of that check.

The third layer is newer and specific to how the question is asked. The Illinois Artificial Intelligence Video Interview Act, in force since 2020, requires an employer using AI to analyze recorded video interviews for Illinois-based positions to notify the applicant beforehand, explain how the analysis works and what general types of characteristics it evaluates, obtain consent, and delete the video within 30 days of a request 4. Its practical bite is limited: it names no penalty and no private right of action, and it covers only AI analysis of applicant-submitted video, saying nothing about resume screeners or chat-based screens.

The operating rule that falls out of all three: build one question set per role, then check it against the states the requisition is open in before it goes live. A loop checked only against the company's home state is compliant in exactly one of them.

Audit the automated question sets before you retrain the panel

Start with the surfaces that ask the same question of every applicant. Those surfaces also keep the receipt: a form field, a knockout rule and a chatbot branch each leave a stored record of exactly what was asked and of whom. The EEOC settled a case in which tutoring companies had programmed their tutor application software to automatically reject female applicants aged 55 or older and male applicants aged 60 or older 5.

That settlement was $365,000, covering more than 200 qualified US-based applicants rejected because of their age, and it resolved the case with no admission of liability. Commentary routinely calls it the first AI hiring settlement. The EEOC's own description is narrower: a date-of-birth cutoff somebody wrote into the software, which is the more useful lesson. A rule you can read in a config file is easier to find than a model's behavior and just as capable of doing the damage, so the audit starts with the fields, not the algorithms.

None of these surfaces sits outside federal selection law: the 1978 Uniform Guidelines reach informal or casual interviews and unscored application forms 6, so a knockout field is the same category of thing as a test.

What to open, in order:

1. The application form. Every required field, especially date of birth, graduation year, salary expectations, and anything marked optional that the form will not submit without. 2. Knockout questions. Each one, with the reason it exists written next to it. A knockout with no stated job-relatedness is a filter nobody owns. 3. The screening chatbot's script, in full, including the fallback branches that only fire on unusual answers. Those are the ones nobody has read since launch. 4. The interview guide, last, because a human can correct that one in the moment.

Then keep the interview record as evidence. Scorecards and a transcript turn what was asked into something a third party can read a year later, which is the whole point of keeping them. That record has rules of its own: what an AI notetaker's summary can and cannot go into the hiring file is the question that arrives the week after you start recording, and how ADA accommodations apply to an AI-based assessment is the one that arrives with the first request.

Read the evidence

Common questions

Is there an official list of illegal interview questions?

No federal statute publishes one. Title VII, the ADEA and the ADA all prohibit using a protected characteristic in an employment decision, and Title VII and the ADA apply a job-relatedness and business-necessity test to practices that screen people out, which is a standard rather than a list. The ADA comes closest to a bare prohibition, barring disability and medical inquiries before a conditional offer. State and local law adds specific bans, notably on salary history. The published lists you find are practitioner summaries of that structure, which is why they disagree with each other at the edges.

Can I ask whether someone needs an accommodation for the interview itself?

Yes, and telling candidates what the process involves while inviting accommodation requests is normal practice. The line is between the process and the person: describing the assessment and asking whether anyone needs an adjustment is fine, while asking about a condition, a diagnosis or a medical history before a conditional offer is not. Design the request route so nobody has to disclose a diagnosis to use it, and make sure a request counts wherever it lands, including when it reaches a recruiter or a vendor's chatbot.

What happens if an interviewer asks one of these by accident?

Nothing automatically, but do not treat it as nothing. Under federal law the question is generally evidence rather than a standalone violation, and what matters is whether the answer affected the decision. Have the interviewer note what was asked, exclude the information from the scorecard explicitly, and let the panel see that it was excluded. Then fix the guide. If the answer plausibly reached the decision, take it to counsel before the panel meets again. The correction is what a transcript read a year later will show.

Do these rules apply to a screening chatbot or an automated questionnaire?

Yes. Under the 1978 Uniform Guidelines a selection procedure is anything used as a basis for an employment decision, a definition that reaches unscored application forms and casual interviews 6, so a question does not become safe by being asked by software. The practical difference cuts against automation: a chatbot asks its script identically of every applicant and logs it, which turns one interviewer's lapse into a documented pattern across thousands of people. Read the whole script, including the branches that only fire on unusual answers, and check it against every state the requisition is open in.

Can I ask a candidate how they used AI on a take-home?

Generally yes, and asking is better than guessing. The job-related version asks what the person delegated, what they checked, and what they rejected, all of which are questions about the work. The version to avoid asks about tools as a proxy for something else, or pairs the question with monitoring the candidate did not agree to. Set the rule before the exercise, apply it to everyone, and record the answer as evidence rather than as a judgment about honesty.

References

  1. 1. Griggs v. Duke Power Co., 401 U.S. 424 (1971) Supreme Court of the United States, via Cornell Legal Information Institute, 1971. law.cornell.edu Supports the claim that the federal frame is job-relatedness and business necessity rather than a fixed banned list, and the quoted requirement to measure the person for the job.
  2. 2. 42 U.S.C. 12112 - Discrimination Office of the Law Revision Counsel, United States Code (prelim), 1990. uscode.house.gov Supports the ADA's pre-offer bar on disability and medical inquiries and the permitted inquiry into ability to perform job-related functions, which is the substitution this article recommends.
  3. 3. California Labor Code Section 432.3 California Legislative Information (leginfo.legislature.ca.gov), 2026. leginfo.legislature.ca.gov Supports the claim that California bars an employer from seeking an applicant's salary history and from relying on it in an offer decision, together with the voluntary-disclosure carve-out at subdivision (i). Fetched and read against the version the page displays as effective January 1, 2026.
  4. 4. Artificial Intelligence Video Interview Act, 820 ILCS 42 Illinois General Assembly, Illinois Compiled Statutes, 2020. ilga.gov Supports the Illinois notice, explanation, consent and 30-day deletion duties for AI analysis of recorded video interviews, and the limits of that Act's scope.
  5. 5. iTutorGroup to Pay $365,000 to Settle EEOC Discriminatory Hiring Suit U.S. Equal Employment Opportunity Commission, Newsroom press release, 2023. eeoc.gov Supports the example of a programmed age cutoff inside application software producing federal enforcement, cited as a settlement with no admission of liability.
  6. 6. 29 CFR Part 1607 - Uniform Guidelines on Employee Selection Procedures (1978), sections 1607.16(Q) and 1607.3(A) U.S. Government Publishing Office, Code of Federal Regulations (Title 29, Vol. 4, 2023 edition), 1978. govinfo.gov Supports the FAQ claim that federal selection law defines a selection procedure to cover the full range of assessment techniques, including informal or casual interviews and unscored application forms, which is why a question does not leave that frame by being asked by software.
  7. 7. Meacham v. Knolls Atomic Power Laboratory (2008), No. 06-1505, syllabus Supreme Court of the United States, via Cornell Legal Information Institute, 2008. law.cornell.edu Supports the limit placed on the Griggs frame in this article: the business necessity test has no place in ADEA disparate-impact cases, where the employer carries a reasonable-factor-other-than-age defense instead.

7 sources, numbered by first appearance. How Olive sources claims

General guidance, not legal advice. Hiring rules differ by state and country and change often; check anything here against your own counsel before you act on it.

Olive assesses how a person works with AI. It does not detect AI-written documents, and it never produces a score, a ranking, or a match percentage for a person. Candidates read the same report the employer reads.

Back to answers

Open your first role Ten attempts a month against a live item bank, with a human-written report on every one.