TL;DR
The right pre-employment tests start with the job's real tasks, not a generic test bundle. This guide shows small businesses how to choose a short, fair mix of tests for each role and how to weigh the results.
Pre-employment testing for small business works best when every test matches a task the job actually requires. List the role's core tasks, choose two to four short tests that measure those tasks, keep the assessment brief enough that strong candidates finish it, and treat scores as one input a person weighs alongside interviews and references.
That sounds simple. In practice, many small employers either skip testing entirely or send every applicant a long, generic battery that measures little of what the role needs. Neither approach helps you hire well.
This guide gives you a repeatable method for any role. You will learn how to turn a job into a short task list and how to map tasks to skills, cognitive and situational judgment tests. You will also see how long an assessment should take, how to read results fairly, and which US rules shape employment testing.
What pre-employment testing means for a small business
Pre-employment testing is the use of standardized tasks or questions to measure whether a candidate has the skills, reasoning ability or work behaviors a job requires. A good test gives every candidate the same chance to show what they can do, so you rely less on resumes and gut feel.
For a small business, the stakes of a single hire are high. One wrong hire on a team of eight affects customers, coworkers and the owner's time far more than it would at a large company. Testing will not remove that risk. A well-chosen test does give you evidence you would otherwise lack.
The main types of pre-employment tests
Each test type answers a different question about a candidate. The table below summarizes what each type measures and where it fits.
| Test type | What it measures | Best used for | Main limitation |
|---|---|---|---|
| Job skills test | Specific, learnable skills such as bookkeeping, spreadsheets or coding | Roles where a skill is needed from day one | Says little about how fast someone learns new skills |
| Cognitive ability test | Reasoning: numerical, verbal, abstract, problem solving, attention to detail | Roles with changing problems and frequent learning | Can show group differences in scores, so fairness monitoring matters |
| Situational judgment test (SJT) | Choices in realistic work scenarios | Customer-facing, team and supervisory roles | Measures judgment about scenarios, not actual behavior |
| Language proficiency test | Reading, writing and comprehension in a work language | Roles with heavy written or spoken communication | Results are estimates of level, not a formal credential |
| Typing test | Speed and accuracy | Data entry, transcription, high-volume chat support | Narrow; rarely enough on its own |
| Personality profile | Work-style preferences | Structuring interviews and onboarding | A profile describes tendencies; it is not a pass or fail grade |
| Custom questions | Your company's specific knowledge or scenarios | Filling gaps no standard test covers | Quality depends on how carefully you write them |
How to choose pre-employment tests for a role: a five-step method
To choose pre-employment tests, start from the job's real tasks, rank them by importance, and select only the tests that measure the top-ranked tasks. Most small-business roles need two to four tests. Then try the assessment yourself, or with a current employee, before sending it to candidates.
- List the role's core tasks. Write down the eight to twelve things the person will actually do each week. Use verbs: reconcile invoices, answer billing questions by email, schedule technicians, build monthly sales reports. If you are unsure, the U.S. Department of Labor's O*NET OnLine database lists typical tasks and skills for hundreds of occupations, which makes a useful starting checklist.
- Rank tasks by frequency and cost of error. Mark each task as daily, weekly or occasional, and note what a mistake costs. A bookkeeper who miscodes expenses creates tax problems. A receptionist who misfiles a brochure creates almost none. Your top three to five tasks are what the assessment should measure.
- Map each top task to a test type. Ask what a candidate must know or do to perform the task. Building reports maps to a spreadsheet skills test. Calming an upset customer maps to a situational judgment test. Catching errors in purchase orders maps to an attention to detail test.
- Choose a short mix, usually two to four tests. Combine one or two job skills tests with one test of general reasoning or judgment. Drop any test you cannot connect to a ranked task. A test that measures nothing the job needs adds candidate time and legal risk without adding insight.
- Pilot the assessment before launch. Take the assessment yourself, or ask a solid current employee to try it. Check the total time, whether instructions are clear, and whether the questions feel related to the job. If your best employee struggles with a section, that section may measure the wrong thing.
The written task list is worth keeping. It documents why you chose each test, which supports the job-related standard US regulators look for, and it gives you a ready outline for interview questions.
Which pre-employment tests to use for common small-business jobs
The right pre-employment tests for a job depend on its core tasks, but common roles follow recognizable patterns. Treat the examples below as starting points to adjust against your own task list, not fixed recipes.
| Role | Suggested tests | Why |
|---|---|---|
| Office administrator | Spreadsheet tasks, attention to detail, written English | Scheduling, records and correspondence reward accuracy and clear writing |
| Bookkeeper or accounting assistant | Bookkeeping skills, numerical reasoning, attention to detail | Daily work involves numbers where small errors compound |
| Customer service representative | Situational judgment, written English, typing | Tone, judgment and response speed drive customer experience |
| Sales associate | Situational judgment, verbal reasoning | Reading customer needs and explaining products clearly |
| Junior developer | Coding test, problem solving | Hands-on coding shows ability better than a resume list of languages |
| Shift or team supervisor | Situational judgment, problem solving, custom scenarios | Supervisors handle conflicts, scheduling and judgment calls |
| Marketing coordinator | Written English, spreadsheet tasks, custom questions on your channels | Writing and basic reporting are core; your channels are specific |
Consider a small dental practice hiring a front desk coordinator. The task list shows insurance verification, appointment scheduling, patient phone calls and payment posting. A sensible assessment pairs an attention to detail test, a short situational judgment test about patient interactions, and two custom questions about the practice's scheduling rules. A coding test or an abstract reasoning section would add time and measure nothing on that list.
When does a cognitive ability test for hiring make sense?
A cognitive ability test for hiring makes sense when a role involves learning new systems, solving unfamiliar problems or handling complex information. Cognitive ability tests measure reasoning skills such as numerical, verbal and abstract reasoning, which helps you assess candidates who will grow into a job rather than repeat one fixed task.
Research on personnel selection has long found that general cognitive ability predicts job performance across many occupations. The best-known summary is a 1998 meta-analysis by Frank Schmidt and John Hunter in Psychological Bulletin. A 2022 reanalysis by Paul Sackett and colleagues in the Journal of Applied Psychology revisited those estimates. It concluded that earlier figures for cognitive tests were likely overstated, and it ranked structured interviews among the strongest predictors.
The practical lesson for a small business is balance. A cognitive test is useful evidence, but it works best combined with job-specific skills tests and a structured interview.
Cognitive tests also call for care on fairness. Cognitive ability measures can produce score differences between demographic groups. For that reason, choose cognitive sections only when the role clearly requires the reasoning they measure, and monitor your outcomes, as covered in the fairness section below.
How long should a pre-employment test be?
A pre-employment test should be as short as possible while still measuring the role's top tasks. For most small-business roles, a total of roughly 30 to 45 minutes is a sensible target. Entry-level and high-volume roles benefit from staying nearer 20 to 30 minutes, while senior or technical roles can justify somewhat longer.
Those ranges are practical guidance, not a research-based rule. The reasoning behind them is straightforward. Strong candidates often have other options, and a long assessment early in the process asks a lot from someone who has not yet spoken to you. Length should grow as the candidate's investment in your opening grows.
How to budget assessment time
Start with a total time budget, then divide it among tests by importance. For example, a 35-minute customer service assessment might allocate 15 minutes to situational judgment, 12 minutes to written English and 8 minutes to typing. If a test does not fit the budget, ask whether it measures a top-ranked task. If it does not, cut it.
A few habits keep completion rates healthy:
- Tell candidates the total time and the number of sections in the invitation.
- Send the assessment after a quick screen of basic requirements, not before.
- Make sure the assessment works on a phone where possible, since many hourly applicants apply from mobile devices.
- Save long work samples or take-home projects for finalists, and keep them proportionate to the role.
Treat scores as one input, not an automatic cutoff
Test scores should inform a hiring decision, never make it alone. A score shows how a candidate performed on specific tasks on one day. Interviews, work history and references add context that a test cannot capture, such as motivation, reliability and fit with how your team works.
Rigid cutoffs create two problems. They can screen out capable people who had a bad day, needed an accommodation or approach problems differently. And a cutoff that is not clearly tied to job requirements can raise fairness concerns under federal guidance. A better approach is to use scores to decide whom to look at more closely and what to ask about.
Building a simple decision record
For each finalist, write a short record with four parts:
- Test evidence: overall and sub-skill scores, with notes on strengths and gaps.
- Interview evidence: answers to the same structured questions you asked every candidate.
- Reference evidence: what former managers said about the top-ranked tasks.
- Decision and reason: who was hired and why, in two or three sentences.
Suppose a bookkeeping candidate scores lower on numerical reasoning but very high on bookkeeping skills, and two references confirm years of accurate month-end work. The record lets you weigh that full picture, and it shows a consistent, job-related process if a decision is ever questioned.
Fairness and legal basics for US small businesses
US employment testing is governed mainly by federal anti-discrimination laws enforced by the U.S. Equal Employment Opportunity Commission (EEOC). The core expectation is that tests are job-related and consistent with business necessity, applied consistently, and adjusted for candidates who need accommodations.
The key rules in general terms:
- Title VII of the Civil Rights Act of 1964 prohibits employment discrimination based on race, color, religion, sex and national origin. It applies to employers with 15 or more employees. A neutral test can still be a problem if it disproportionately screens out a protected group and is not job-related.
- The Americans with Disabilities Act (ADA) requires reasonable accommodations, such as extra time, for qualified candidates with disabilities, and also covers employers with 15 or more employees.
- The Age Discrimination in Employment Act (ADEA) protects applicants aged 40 and older and applies to employers with 20 or more employees.
- The Uniform Guidelines on Employee Selection Procedures (29 CFR Part 1607) describe the four-fifths rule. Under that rule, a selection rate for any group below 80 percent of the rate for the highest group is generally treated as evidence of possible adverse impact worth examining.
The EEOC's guidance page on employment tests and selection procedures explains these principles in plain language. Many states and cities add their own rules, including some on automated tools in hiring. Smaller employers below the federal thresholds may still be covered by state law. For your specific situation, speak with a qualified employment attorney or HR advisor.
Handling AI assistance during online tests
AI cheating is now a common search topic among employers, because chatbots can answer many standard test questions in seconds. The sensible response is to choose tests designed to resist AI help and to treat any integrity signals as evidence for a person to review, never as proof.
Useful design features include timed questions served one at a time, a different question set for each candidate, and recorded signals such as tab switches or pasted text. On HireValid, for example, those signals feed an Integrity Score and an evidence timeline that summarize what was observed. A person then reviews them alongside everything else.
If something looks unusual, do not draw conclusions. Ask the candidate to walk through an answer in the interview. A short follow-up conversation is fair to the candidate and usually tells you more than any single signal.
Common mistakes when choosing tests
Small employers tend to repeat a handful of avoidable mistakes:
- Testing everything. A long battery tires candidates and buries the useful signal.
- Testing traits instead of tasks. Choose tests from the task list, not from a general idea of a great employee.
- Using a personality profile as a grade. Profiles describe work-style preferences and are best used to shape interview questions.
- Skipping the pilot. Unclear instructions or a mismatched section are easy to catch before launch and costly to fix after.
- Ignoring accommodations. Tell candidates how to request extra time or other adjustments, and grant reasonable requests.
- Never reviewing outcomes. After a few hiring rounds, check whether test results matched later job performance and whether any group passed at notably lower rates.
For more on building assessments, see our other assessment design guides on the blog.
Frequently asked questions
Are pre-employment tests legal for small businesses?
Yes, pre-employment tests are generally legal in the United States when they are job-related, applied consistently to all candidates for a role, and offered with reasonable accommodations for people with disabilities. Federal laws such as Title VII and the ADA, enforced by the EEOC, apply above certain employee counts, and state laws may add requirements. A qualified advisor can confirm your obligations.
Should every applicant take the test?
Not always. Many small businesses send the assessment after a quick screen for basic requirements such as work authorization, schedule availability or required licenses. Testing everyone who applies can waste candidates' time and yours. Whatever point you choose, apply it consistently, so every candidate who reaches that stage of the process takes the same assessment.
How many tests should one assessment include?
Most small-business roles need two to four tests. A typical mix is one or two job skills tests plus one test of reasoning or judgment, such as a cognitive ability or situational judgment test. If you cannot connect a test to one of the role's top-ranked tasks, remove it. Fewer, well-chosen tests usually produce clearer evidence.
Can I write my own test questions?
Yes. Custom questions are useful for company-specific knowledge, such as your products, scheduling rules or common customer scenarios. Write them carefully: each question should relate to a real task, have a clear correct answer or scoring rubric, and avoid trivia or assumptions about background. Pilot custom questions with a current employee before using them with candidates.
Is a personality test a good way to screen candidates?
A personality profile describes work-style tendencies, not ability, so it should not be used as a pass or fail screen. Profiles work best for preparing interview questions and planning onboarding. For example, a profile suggesting a preference for independent work could prompt a question about how the candidate handles close collaboration.
How do I handle a candidate who asks for extra time?
Treat the request as a normal part of the process. Under the ADA, employers covered by the law must provide reasonable accommodations, such as extra time, to qualified candidates with disabilities. Explain in your invitation how to request an adjustment, respond promptly, and apply the accommodation without asking for more personal detail than you need.
Do test results predict who will succeed in the job?
Test results are evidence, not a guarantee. Research on personnel selection shows that job-related tests and structured interviews predict performance better than unstructured judgment, but no single method is reliable on its own. Combining test scores, structured interviews and references gives you the most complete picture for each finalist.
Conclusion
Choosing pre-employment tests is less about finding the perfect test and more about discipline. Start from a short, ranked task list, and map only the top tasks to tests. Keep the assessment brief, and pilot it before candidates see it. Then let scores guide where you look closer, while interviews, references and your own judgment complete the decision. Monitor fairness over time, document your reasoning, and get advice when a legal question arises.
If you want to put this method into practice, HireValid offers skills, cognitive, situational judgment, language and custom tests that you can combine into one short assessment per job. You can browse the English test library index or, if you hire Spanish-speaking candidates, the Spanish test library index. Try HireValid free with three candidates, or compare the monthly plans on the pricing page at hirevalid.com/pricing.
Does a low Integrity Score reject a candidate?+
No. Integrity signals may have innocent explanations, including connection issues or accessibility needs. A person should review the evidence and speak with the candidate before deciding.
What will candidates need?+
A browser and a reliable connection. Typing, spreadsheets and code tasks are intended for desktop. If an employer enables camera checks, candidates must receive a clear notice and a route to request an alternative.
Are the scores official qualifications?+
No. These are tools for hiring decisions. English results are CEFR-aligned level estimates, not official certificates. Cognitive scores are not clinical IQ results.