Why this question matters
Washington lets an applicant or employee take a genetic information claim to court by one of two routes. Interviews drift into personal territory more often than most hiring teams realize. A hiring manager asks whether an applicant's parents had heart problems. A recruiter asks if anyone in the family has a condition that tends to run in families. The question sounds friendly and curious. To the applicant, it can look like a sign that genetic information is being gathered before any offer is made, and it is the kind of situation that chapter 49.44 RCW addresses.
This post covers two routes that an applicant or employee in Washington can use to bring a civil claim when they believe genetic information was sought or used in a way the law does not allow. It also explains how the statute defines genetic information, where the federal rules fit, and what you can do this week to lower your risk. It is general information, not legal advice. If a specific interview question or applicant concern is in front of you, bring it to employment counsel.
What the statute counts as genetic information
The chapter gives its own meaning to the term genetic information, and that meaning has exclusions that matter in everyday hiring. For purposes of the chapter, genetic information does not include routine physical measurements, including chemical, blood, and urine analysis, unless those measurements are conducted purposefully to diagnose genetic or inherited characteristics. The definition also excludes results from tests for abuse of alcohol or drugs. The exact wording is on the chapter 49.44 RCW page.
Read literally, that exclusion is narrow. A blood panel run as part of a routine physical is not automatically genetic information. A test designed to find out whether an applicant carries an inherited trait is a different matter, and the exclusion does not reach it. The drug and alcohol carve-out is also specific: it covers results from those tests, not every health question you might be tempted to ask. When in doubt, treat a question about a person's genes or inherited traits as sensitive, and avoid it.
The statute also says that the definitions in that subsection apply throughout chapter 155, Laws of 2002, unless the context clearly requires otherwise. In practice, that means you should not invent a looser meaning of genetic information for one form or one interview. Use the chapter's definition wherever it applies, and check the chapter 49.44 RCW text before you rewrite any policy.
Groups the 2002 session law does not change
The session law also carves out some groups. According to the text of chapter 155, Laws of 2002, the law does not modify any statute or policy regarding the employment of public employee retirees hired for postretirement employment under the specified retirement chapters, or public employee retirees who work as contractors. It also does not modify any statute or policy regarding the employment of enrolled students who receive employment as student employees or as part of their education or financial aid. If your organization hires any of these groups, confirm with counsel which rules apply before you change your process.
The federal baseline
Washington rules sit alongside federal law, and the federal agency's guidance is worth knowing. The U.S. Equal Employment Opportunity Commission states that, in general, you cannot request medical or genetic information from applicants. For employees, the agency says you may request medical or genetic information only in limited circumstances. Those two lines alone should change how interviewers prepare. A question that seems harmless in a first conversation can still fall within the request the EEOC describes. The EEOC's small business requirements page has the full text. For the employee side, see rules to verify before asking for employee medical records.
Route one: a civil action for an applicant
The first route is the one that most directly fits an applicant. The statute says that "an employee or applicant aggrieved by a violation of RCW 49.44.200 may bring a civil action in a court of competent jurisdiction." In plain words, an applicant who believes the employer violated that section can take the claim to court. The provision names applicants, not only employees. The complete wording is on the chapter 49.44 RCW page.
Three practical points follow from that wording. First, the remedy named here is a civil action in court, so a complaint can become a lawsuit and does not have to stay an internal HR matter. Second, the provision uses the word aggrieved, and what that word requires in a particular case is a question for a lawyer, not for this post. Third, the chapter has its own definition of genetic information, so the exclusions discussed above matter to any claim under this route.
Route two: a civil action for an employee
The second route comes from a different sentence in the same chapter. The statute says, in subsection (3), that an employee "deeming himself or herself harmed in violation of subsection (1) of this section may bring a civil action in a court of competent jurisdiction." Because this wording is written for an employee and points back to subsection (1), it is a separate route from the applicant language above. This route depends on the rules in subsection (1), so read the full chapter before you rely on it in any dispute.
For an applicant, the first route is likely the more direct fit, since it names applicants by word. For an employee, both routes may be relevant, and the difference between them is one reason a lawyer should review any claim. From a recruiter's point of view, the practical lesson is the same either way: a question that touches genetic information can lead to a court case, and it is usually easier to remove the question from your script than to defend it later.
Related guides: Hourly new hires: 3 Washington and New York checks · Washington discrimination hearings: 3 roles to know · Washington job postings: 2 pay disclosures to include.
Interview questions that cause trouble
Most problems start with a familiar question. Here are patterns to avoid in interviews, phone screens, and reference calls, because they tend to pull in family medical history or inherited traits:
- Does anyone in your family have a condition that runs in families?
- Has your family had a history of cancer or heart disease?
- Have you ever had a genetic test, or do you know if you carry any inherited condition?
- Can you tell me about your parents' health so we can plan your schedule?
Each of these questions asks about a relative or an inherited trait, so each one can bring genetic information into the room. The question does not have to be hostile to be a problem, and a friendly tone does not change what was asked. If you need to know whether an applicant can meet a schedule or a physical demand, describe the requirements of the role and ask whether they can meet them.
If an applicant volunteers family history or a genetic detail on their own, do not ask follow-up questions about it. Steer the conversation back to the job and bring the matter to HR or counsel rather than probing for more. Your interviewers should know this before they walk into the room.
What to change this week
A written checklist keeps interviews consistent. For one sample format, see the Interview Scorecard Example for Consistent Hiring Teams. Work through these steps with your HR lead or employment counsel:
- Remove family history and genetic questions from every interview guide, phone screen script, and application form.
- Brief every interviewer on the statute's definition of genetic information, including its exclusions for routine physical measurements and for results from alcohol or drug abuse tests.
- Teach interviewers to describe the job's requirements and ask whether the applicant can meet them, instead of asking about health or family.
- Confirm with counsel how the chapter 155 carve-outs apply to public employee retirees hired for postretirement employment, public employee retirees who work as contractors, or enrolled students who receive employment as student employees.
- Keep dated records of every change to your interview guides and forms, so you can show what your policy said and when it changed.
What a claim looks like from the applicant's side
Most applicants do not start with a legal theory. They start with a feeling that a question was wrong. An applicant may have been asked about a parent's illness, a sibling's diagnosis, or a test they took years ago. They may have left the interview feeling uneasy, then later realized the question was out of bounds. When that realization comes, the applicant may search for the statute, find the phrase about applicants, and decide to talk to a lawyer. That is why the wording of your interview practice matters as much as your intent.
Disputes like this often turn on the facts: what was asked, who asked it, what the applicant said in return, and what happened next. A question asked with good intentions can still be the question at the center of a claim.
Who asks these questions
Questions about genetic information rarely come from a written policy. They come from habit, from a manager who wants to be friendly, or from a recruiter who copies an old script. A hiring manager may think a question about family health is a kind way to get to know an applicant. A recruiter working from an old form may not notice that one line on it is a problem. The fix is not to blame individuals. It is to make the rules visible at the point where questions get asked.
Teams without a dedicated HR function face this risk in a sharper form. The person who runs the interview may also write the questions, so a single habit can repeat across every hire. If that describes your team, start with a review of recent interview notes. Look for any line about family, parents, relatives, or test results, and treat each one as a signal to fix the script.
When a concern comes in
If an applicant contacts you about a question they were asked, treat the message as a serious matter, even if it arrives as a casual email. Do not argue about the statute in your reply. Route it to counsel quickly, preserve the interview notes and any written materials, and avoid discussing the matter with other applicants. A short, calm response that says the company is reviewing the concern is usually better than a defensive one.
Keep the reply factual. Acknowledge the concern, confirm that the company takes questions about personal information seriously, and tell the applicant who will follow up. Avoid guessing about what the law means in their case, and avoid promising an outcome. Your counsel can decide how to answer the legal points.
Be careful with internal discussion. Messages among managers about an applicant's answer can become part of the record in a dispute. Keep them brief and factual, and do not speculate about an applicant's health or family. If you want to talk through the issue, do it with counsel, not in a group chat.
Better questions to ask instead
The goal is not to avoid hard conversations. It is to ask about the job, not the person's body or family. Consider the difference in these pairs:
- Instead of "Does anyone in your family have a condition that runs in families?" ask "This role involves standing for most of each shift. Can you meet that requirement?"
- Instead of "Has your family had a history of cancer or heart disease?" ask "What experience do you have with the work this position requires?"
- Instead of "Have you ever had a genetic test?" ask "Are you able to complete the certification this job requires, and when could you do it?"
- Instead of "Can you tell me about your parents' health so we can plan your schedule?" ask "Which shifts are you available for, and what dates work for a start?"
Notice that every replacement question is about the work, the schedule, or a requirement that applies to all applicants. That consistency is the point. When every applicant hears the same questions about the job, you have an easier time showing that your process is about the role, not about someone's family. For a method, see the same interview questions in a fixed order.
A short scenario
Consider a common case. A recruiter is on a phone screen with a strong applicant. Near the end of the call, the recruiter says, "Before we wrap up, is there anything in your family's medical history we should know about for the schedule?" The applicant pauses, then says their mother had a genetic condition and they had recently been tested. The recruiter thanks them and moves on to the next question.
In that moment, the recruiter has already asked the question, so the next move matters. The right response is to stop the line of questioning, avoid any follow-up about the mother's condition or the test, steer back to the role and its requirements, and flag the exchange to HR or counsel promptly.
Notice also what they did poorly: they asked the question in the first place, and the call had no clear script to fall back on. A short written script would have given the recruiter a safe next line, such as asking whether the applicant can meet the schedule for the role. The scenario shows why training matters as much as policy.
Common objections from managers
"We only want to know if the applicant is healthy enough to work." That concern is understandable, but the question about genetic information is still the wrong tool. Ask about the job's requirements and let the applicant answer about those. If a role has a specific requirement, write it down and apply it to every applicant in the same way.
"We are too small to worry about this." Size does not change the core question. A small team can repeat one habit across many interviews. Whether a particular company is covered by a particular rule is a question for counsel, but the practical fix, which is to keep family and genetic questions out of interviews, is inexpensive and works at any size.
Keep the policy current
A policy is only useful if people can find it. Put your interview guide, your list of prohibited topics, and your escalation path in one place that every interviewer can open. When the law or your practice changes, record what changed and when. If a claim comes later, that history shows what your team knew and what it did about it.
Review the policy regularly, and after any change in the statute or in your hiring process. A review does not need to be long. Walk through your forms, your scripts, and your job postings, and check for anything that asks about family history, inherited traits, or medical testing. Sign off on the review, even if nothing needs to change, so you can show it was done.
Where to read the primary sources
Chapter 49.44 RCW is available on the Washington State Legislature site, and the federal guidance on the EEOC's small business requirements page covers the general federal rule. Neither page replaces legal advice, and each may be updated after this post is published, so check the current version before you rely on it.
Bottom line
Washington law gives applicants a route to court when a violation of RCW 49.44.200 is alleged, and it gives employees a separate route under subsection (3), which covers harm from a violation of subsection (1). Its definition of genetic information excludes routine physical measurements and results from alcohol or drug abuse tests, but only within the limits described above. The EEOC says that, in general, you cannot request medical or genetic information from applicants. The safest policy is simple: keep family history and genetic questions out of every interview, and train your team to ask about the work instead.