By Mike Callen, President, TestGenius
About the author: Mike Callen is President of TestGenius, a pre-employment testing platform from Biddle Consulting Group, and co-host of the podcast Testing, Testing 1-2-3. This post is adapted from the episode "So, You Don't Test? A Closer Look at Why You Should." It's for general information and isn't legal advice.

Our team attends about forty-five conferences and trade shows a year, and one exchange happens more often than I can believe. An HR manager or recruiter walks past our booth, reads the word "testing" on the backdrop, and says, "Oh, we don't do that." Sometimes they add that they've been told they can't test, that it's risky, or even that it's illegal.
Here’s the reality. If your organization reviews resumes, conducts interviews, or decides which applicants move forward in the hiring process, you're already testing. You just might not call it that.
And that's an important distinction, because avoiding formal assessments doesn't necessarily eliminate the risks associated with hiring decisions. In some cases, it may actually make those decisions harder to explain or defend.
In 1971, the U.S. Supreme Court decided Griggs v. Duke Power. When Title VII of the Civil Rights Act took effect in July 1965, Duke Power began requiring employees who wanted to advance into its better-paying departments to pass two general aptitude tests, on top of a high school diploma requirement it already had. None of these requirements had been shown to relate to doing those jobs, and both screened out black workers at far higher rates than white workers.
The court ruled that practices, procedures, or tests (PPTs) can't stand if they aren't related to the job. Legally, a “test” isn't only a traditional test. It's any step that advances some applicants and not others.
Look at how many of those PPTs are already in a typical hiring process:
Nearly every employer uses at least three of these: a posting, an application, and an interview. So, the real question isn't whether you test; it's whether each step is job-related and consistent with business necessity, and whether you could verify that if someone asked.
A background check has people who pass and people who don't (based on the company’s criteria), so the same principles apply.
Apply them consistently. If you run checks on entry-level armed guards, run the same checks on the supervisors who carry the same responsibilities. People vying for the same role should go through the same process. This is no argument for screening less, it's an argument for screening in a way that's consistent, job-related, and documented. That's the same standard every other step in your process should meet.
Much of our work is with 911 and emergency dispatch centers. Over the years, many center directors have told me the same thing: "I can sit down with someone for five or ten minutes and know whether they'll make it on the job."
I believe them. They've been doing this a long time, and they know the work. But picture it from the applicant's side. They sat down, had a short conversation, and were told they're not a fit. But, there's no paper trail to explain why the decision was made.
The best of those directors finish the story like this: "But I don't do it that way." They don't want to spend their time interviewing people who lack the basic skills. So, they test first, and they save the interview (and background check, polygraph, psych eval, etc.) for candidates who have already shown they can do the core work.
A process applicants accept. If I take an Excel test for an office job and I struggle, I may be disappointed, but I'm not going to blame the employer. I know how well I did or didn’t do. Every organization recruits from its own community, customers, or market, and today any unhappy applicant will share their experiences online. You'll never please everyone, but a process that feels fair and job-related earns you the 99 good reviews that outweigh the one bad one.
A paper trail. Testing creates documentation at the step that often screens out the most applicants. That's exactly where you want your strongest records. When a client has told us a test is being challenged, our advice has been to send the validation report to the other side. More often than not, that ends the conversation.
One of our reps, Nick Brown, puts it simply at conferences. He asks whether anyone has hired a person whose resume listed “Excel experience”, only to watch them type numbers into cells and add them up on a calculator. Everyone laughs, and then everyone nods. You want to find that out before the offer, not after.
Whether or not you use formal tests today, you can start here:
Look again. Every step that determines who moves forward is part of your selection process, whether you call it a test or not. The goal should be to make better, more informed hiring decisions through practices that are job-related, consistently applied, and supported by evidence. Because the real risk isn't necessarily that you're testing candidates. It's that you may already be testing them without realizing it, or without being able to explain why.