TL;DR
A complete working process from role definition to reviewing outcomes, built for a small business.
How to read this guide
This guide is written for owners and managers who hire a few people a year and want a dependable way to compare applicants before spending hours in interviews. It moves from the basic question of what a pre-employment test is, through choosing and running one, to reviewing the results of your first round. Each section answers one question, so you can read it straight through or jump to the part you need today.
Keep one open vacancy in mind as you read. Abstract advice about assessment is easy to agree with and hard to apply, while a real role forces concrete choices about which skills matter, how long candidates should spend and who will look at the results. By the final section you should have a short written plan for that vacancy.
The examples are illustrative, and for legal questions specific to your location, take qualified advice. Where a topic needs more depth, we link to a dedicated article or guide rather than repeating it.
What is a pre-employment test?
A pre-employment test is a structured task that every applicant for a role completes under the same conditions, so the employer can compare people on job-relevant evidence. It may be a set of reasoning questions, a customer scenario with several possible responses, a spreadsheet exercise, a typing check or a short piece of code to read. What makes it a test, rather than a conversation, is that the questions, the time allowed and the scoring rules are fixed before anyone takes it.
People use several names for the same idea. A pre-employment assessment, a pre hire test, a pre hire assessment and an employment test usually describe the same step: evidence gathered after someone applies and before a final decision. Our glossary has short definitions of a pre-employment test and of the broader pre-hire stage if you need wording to share with colleagues. The label matters less than the design. A well-chosen ten-minute task can tell you more than an hour of loosely structured questions.
How is a test different from an interview or a background check?
An interview is a conversation that depends heavily on the interviewer, the order of questions and the rapport in the room. A structured interview narrows that variation, and our guide to structured interviews explains how. A test goes further: the content is identical for every applicant and the scoring does not depend on who is marking.
A background or reference check is different again. It verifies history, such as employment dates or qualifications, rather than measuring what someone can do now. A pre employment screening test sits between the application and the interview and answers a narrower question: can this person show the core skills the job needs today?
What are pre-employment tests used for?
Most small employers turn to testing for one of three reasons. They receive more applications than they can interview, the applications look increasingly alike, or a previous hire did not have a skill the CV seemed to promise. In each case the goal is the same: to replace a guess with a small amount of comparable evidence.
Testing also helps with consistency. When every candidate meets the same task, it becomes easier to explain why one person moved forward and another did not. That explanation is useful to the candidate, to colleagues who join the decision later and to you, months afterwards, when you wonder why a hire worked out.
When does a test help most?
A test earns its place when a role has a few clearly defined skills that can be shown in a short task, when you have more applicants than interview slots, and when the skill would be expensive to discover only after hiring. Customer support, administration, bookkeeping, data entry, junior analysis and junior development roles often fit that pattern well.
When is a test the wrong tool?
A test is a poor fit when you cannot name the skill you are measuring, when the job depends mainly on credentials that are better verified directly, or when the applicant pool is so small that a conversation with each person is quicker. It is also a poor fit when the task you have in mind would take candidates hours of unpaid work. In those cases, fix the role definition or the interview first.
What are the main types of pre-employment tests?
There are a handful of families, and most hiring needs only two or three of them. The detailed comparison, with an example question for each family, is in our guide to the types of pre-employment tests. Here is a brief map so the rest of this guide makes sense.
- Ability or reasoning tests ask candidates to work through unfamiliar problems, such as numerical, verbal or logical puzzles. See the cognitive ability tests.
- Job skills tests check a tool or task the role uses, such as spreadsheets, bookkeeping entries or data entry. See the practical skills tests.
- Language tests look at reading, grammar and written communication. See the language tests.
- Situational judgement tests present realistic workplace scenarios and ask for the most effective response. See the situational judgement tests.
- Technical tests check fundamentals such as reading code or writing a simple query. See the technical skills tests.
- Work samples ask for a small, realistic piece of the job and are usually kept for a shortlist.
Self-report questionnaires about personality or honesty are a separate category. They ask people to describe themselves rather than demonstrate a skill, which makes them harder to connect to a specific job task. If you are considering one, read the types guide first and be clear about what decision it would support.
How do I choose the right pre-employment test for a role?
Choosing a test is a matching exercise, not a shopping exercise. Start from the work, decide what evidence would convince you that someone can do it, and only then look for the shortest assessment that produces that evidence. Reversing the order, by browsing a catalogue and adding whatever looks relevant, produces long assessments that are hard to justify.
Start from a task list, not a job title
Write down the five or six tasks that fill most of the role's week. For each one, decide whether a new hire must be able to do it on day one or whether you can teach it during the first month. Only the day-one tasks are candidates for testing. Skills you will train are better discussed in the interview, where you can explore how quickly someone learns.
For a fuller method, including how to turn a vague person specification into concrete tasks, read our article on skills-based hiring without an HR team. It walks through separating essential requirements from preferences and writing a short scoring guide before you look at any results.
Map each task to one piece of evidence
Once you have the day-one tasks, pair each with a single way of observing it. The table below shows a hypothetical example for a small office.
| Day-one task | Evidence you need | A suitable method | | -------------------------------- | -------------------------------------- | -------------------------------- | | Reply to customer emails | Clear, accurate written English | A business writing test | | Keep the client spreadsheet tidy | Sorting, filtering and simple formulas | A basic Excel test | | Handle a frustrated caller | Sound judgement under mild pressure | A customer service scenario test | | Learn a new booking system | Ability to pick up unfamiliar rules | A short reasoning test |
Notice that each row produces one method, and that the list stops at four. If two tasks lead to the same method, you need only one test. If a task has no sensible short method, move it to the interview or a work sample rather than forcing it into a test.
Use a role bundle as a starting point
If you would rather not build the list from scratch, the role bundles group tests for common small-business roles. For example, the bundle for a customer support agent combines judgement, language and typing evidence, while the bookkeeper bundle leans on accounting knowledge and attention to detail. Treat a bundle as a draft: remove anything your version of the job does not need.
The full test library lists every HireValid test with its length, the skills it covers and a sample question. Reading the sample before you select a test is the quickest way to check that it matches your job rather than a similar-sounding one.
What do good pre-employment test questions look like?
Good pre employment test questions share a few traits. They describe a situation the candidate could plausibly face in the role, they have one answer that a competent person would clearly prefer, and the wrong options are tempting for understandable reasons rather than absurd. A question that only an insider could answer, or one that turns on trick wording, measures familiarity with tests more than ability.
When you review sample items, try answering them yourself and ask a colleague in the role to do the same. If either of you disagrees with the keyed answer, or finishes in a fraction of the allowed time, the item may not be doing the work you expect. Our article on situational judgement examples shows how to judge whether scenario options reveal a real difference in approach.
How long should the whole assessment be?
Add up the minutes across every test in the stage. For most early-stage screening, a total between twenty and forty-five minutes balances useful evidence against the risk of strong applicants giving up. Shorter is fine for high-volume roles; longer is only reasonable later in the process, when fewer people are involved and the task is closer to real work.
Are pre-employment tests legal?
In general, yes, when the test is related to the job, applied in the same way to every applicant, and offered with reasonable adjustments for disability. The details differ by country. The United States has federal guidance on employment tests and disparate impact, the United Kingdom applies the Equality Act 2010, and Canadian provinces have their own human rights legislation.
This guide does not try to restate those rules. Read are pre-employment tests legal? for country-by-country basics and links to the regulators, and take qualified advice for any specific question. The practical habits that support a defensible process are simple: write down why each test is relevant, keep conditions consistent, respond to accommodation requests promptly and keep records of what you decided and why.
How do you keep pre-employment testing fair?
Fairness is not a feature you switch on. It comes from choosing relevant content, applying it consistently and checking the results afterwards. A test that is perfectly fine for one role can be unfair for another if it measures something the job does not need, such as fast reading in a role that rarely involves reading.
Check for adverse impact after each round
Adverse impact describes a selection step that passes one group at a noticeably lower rate than another. A common first screen in the United States compares selection rates between groups and flags a concern when one group's rate falls below four-fifths of the highest group's rate. A flag is a prompt to investigate the process, not a finding of discrimination.
With small numbers, a single candidate can swing the ratio sharply, so treat each round as one data point and look for patterns across rounds. Our article on the four-fifths rule works through a hypothetical calculation and explains what to examine when a flag appears. HireValid's fairness reporting uses optional, consent-based demographic information kept separate from individual scores, so you can compare outcomes across groups without building a spreadsheet.
Set cut-off scores carefully
A cut-off score turns a continuous result into a pass or fail, and the choice of where to draw the line has real consequences. Set a minimum only for skills the job genuinely needs on day one, and prefer looking at the ranked results alongside other evidence over rejecting everyone below an arbitrary number.
Percentiles compare a candidate with a reference group, not with the requirements of your job. A result at the fortieth percentile may be entirely adequate for a role that needs only routine reasoning. Our help article on interpreting percentiles and the article on using cognitive ability tests fairly explain how to read these numbers without over-interpreting small differences.
Make adjustments easy to ask for
Some candidates need extra time, a screen reader friendly format, breaks or a different way to complete a task. Tell every applicant how to ask before the assessment starts, name a person who will respond, and decide in advance which adjustments you can make without changing what the test measures. The help article on requesting an accommodation shows the route a candidate sees.
How do you handle AI assistance in online tests?
Generative AI has made some traditional screening steps less informative. Polished cover letters are easy to produce, take-home tasks can be completed with heavy assistance, and some tools offer real-time suggestions during interviews. For an employer, the useful response is to design stages where independent work is clearly defined and outside help is less useful, then to confirm important results in person.
Practical measures include short time limits sized to the task, questions drawn from larger pools so candidates do not all see the same items, scenarios that depend on details supplied in the question, and a structured follow-up where the candidate explains their own answers. HireValid records integrity signals, such as focus changes, paste events and unusual timing, and combines them into an Integrity Score. Those signals are evidence for a person to review alongside context; they are never proof that someone cheated.
For an overview of the tools candidates may use and a five-step employer process, read the employer's guide to AI interview cheating tools. For assessment design in more depth, including how to write rules about permitted tools and how to review a concern without accusing anyone, read our guide on how to prevent cheating in online assessments.
What should the candidate experience look like?
Candidates judge your company by the process as much as by the job advert. An assessment that arrives without context, takes twice as long as promised or ends in silence costs you applicants and reputation. A clear one tells people what to expect, why each part matters and when they will hear back.
At a minimum, the invitation should state the purpose, the total time, the deadline, which tools are allowed, which integrity settings are switched on and how to request an adjustment. Candidates can try the format in advance with the free sample test, and the information for candidates page explains what happens during and after an assessment. Our guide to a candidate-friendly hiring process covers invitations, accessibility, timing and feedback in detail.
Is pre-employment testing worth the cost?
The direct cost of testing is usually a subscription or a per-candidate fee, plus the time candidates and reviewers spend. The cost it aims to reduce is a hire who cannot do the core tasks, which shows up as extra training, missed work, colleagues covering gaps and, sometimes, a second recruitment round. Neither side of that comparison has a universal figure, so estimate it for your own business.
The cost of a bad hire calculator lets you enter your own salary, recruiting and onboarding assumptions and see a range rather than a single headline number. Our article on the real cost of a bad hire explains which inputs matter most and why comparing scenarios is more honest than defending one estimate.
Billing structure matters too, especially if you hire in bursts. An annual contract can be good value when you test every month and poor value when you hire twice a year. The article on monthly versus annual hiring software shows how to sketch your hiring calendar before comparing plans, and the pricing page lists HireValid's monthly plans. If you are still deciding which kind of tool fits a small team, our overview of hiring software for small businesses explains what to look for beyond the price.
How do you roll out pre-employment testing, step by step?
The steps below assume one vacancy and a team without a dedicated HR function. They are ordered so that each decision is made before the one that depends on it. Expect the first round to take a little longer than later ones, because you are writing things down for the first time.
Step 1: Write the role in tasks
List the main tasks, mark which are needed on day one and note which can be trained. Keep the list on one page. If you cannot agree on the day-one tasks with whoever else is involved in the decision, resolve that disagreement before choosing any test.
Step 2: Choose the evidence and the stage
Decide which day-one tasks a short online test can show, which belong in a structured interview and which need a work sample with the shortlist. A common pattern is a short online assessment for everyone who meets the basic requirements, followed by an interview and a brief practical task for the top few.
Step 3: Select and preview the tests
Pick the tests that match your evidence list, then take each one yourself. Check the length, the language level and whether the questions resemble the work. Remove anything that measures a skill the job does not need, even if it seems interesting.
Step 4: Decide how results will be used
Before any candidate starts, write down whether you will use a minimum score, a ranked shortlist or a combination. Decide how many people you will interview and what you will do with close results. Deciding this afterwards invites the temptation to move the line for a favoured applicant.
Step 5: Prepare the invitation and the adjustment route
Draft the message candidates receive, with the time estimate, deadline, rules on tools and the name of a contact for adjustments. Ask someone outside the hiring decision to read it and tell you what is unclear. Make sure the contact person knows they are the contact.
Step 6: Run the round and review results with context
Send the invitations, answer questions promptly and give the same help to everyone who asks. When results arrive, read scores together with any integrity signals and their context. A low score or an unusual signal is a reason to look more closely, not an automatic rejection.
Step 7: Confirm skills in the next stage
Use the interview to explore the evidence the test produced. Ask candidates to talk through one of their answers, or to tackle a short variation of a task they found hard. Our interview templates include structured questions for each role so different interviewers ask comparable questions.
Step 8: Close the loop and review the process
Tell every candidate the outcome, including those who did not advance. Then look back at the round: did the instructions cause confusion, did anyone ask for an adjustment, how did selection rates compare across groups, and which test told you least? Record what you will change next time.
A worked example: a hypothetical first round
Imagine a small property management firm hiring an office administrator. The owner lists the day-one tasks as answering tenant emails, keeping a maintenance spreadsheet up to date and scheduling contractors. Learning the firm's accounting software is marked as trainable. From that list, the owner chooses a business writing test, a basic Excel test and a short time management scenario test, for a total of about thirty minutes.
The owner decides in advance to interview the top six candidates by combined result, provided no individual test falls below a modest minimum on the spreadsheet task. The invitation names the office manager as the contact for adjustments. One candidate asks for extra time because of a visual impairment, and the office manager agrees the same day.
After the round, two candidates have integrity signals for leaving the browser window. The owner notes these but does not reject anyone on that basis; instead, the interview includes a short spreadsheet task done on screen. One of the two explains that a phone notification interrupted them, and their on-screen work is consistent with their test result. Every applicant receives an outcome message within a week.
In the review, the owner notices that several people misread the deadline because it was given without a time zone, and adds one to the next invitation. That small change is exactly the kind of improvement a first round should produce.
Your first-round planning sheet
Before sending invitations, fill in a single page with the following headings. It does not need to be formal, but it should be complete enough that a colleague could run the round from it if you were away.
- Role and day-one tasks, with trainable tasks marked separately.
- Tests chosen, the task each one supports and the total candidate time.
- How results will be used: minimum scores, shortlist size and tie-breaking.
- Invitation text, deadline with time zone, permitted tools and integrity settings.
- Adjustment contact and the adjustments you can offer without changing what is measured.
- Who reviews results, and how integrity signals will be discussed.
- When and how every candidate will hear the outcome.
- What you will review after the round, including selection rates by group.
Questions to settle before your first invitation
- Can you explain, in one sentence each, why every test in the assessment is relevant to the job?
- Would a strong candidate with other offers think the total time is reasonable?
- Have you decided how scores will be used before seeing any of them?
- Does every applicant know how to ask for an adjustment, and does someone own that request?
- Will a person review any integrity signal in context before it affects a decision?
- Is there a date in your calendar to review the round and record changes?
When the answers are clear, you are ready to start. Browse the test library, pick a role bundle close to your vacancy and keep this guide open while you write your planning sheet.
| What it measures | Example roles | Typical length | At HireValid | |
|---|---|---|---|---|
| Cognitive ability | Reasoning, learning and problem solving | Most roles, especially fast-changing ones | 8 to 12 minutes | Reasoning, critical thinking, attention to detail |
| Job skills | Tools and tasks used in the job | Administrators, analysts, assistants | 8 to 15 minutes | Software skills such as Excel and Google Sheets |
| Language | Reading, grammar and written communication | Support, sales, marketing, remote roles | 12 minutes | English proficiency and other language tests |
| Situational judgement | Choices in realistic workplace scenarios | Customer service, sales, team roles | 8 to 10 minutes | Customer service, sales, time management and more |
| Typing and data entry | Speed and accuracy on the keyboard | Call centre, admin, data entry | 5 to 8 minutes | Typing and number entry |
| Coding | Reading, writing and fixing code | Junior developers and analysts | Up to 35 minutes | Programming tests and coding tasks graded on hidden test cases |
| Personality questionnaire | Self-described preferences and style | Used across many roles | Varies | Personality and working-style profiles, read as a profile, not a grade |
| Integrity questionnaire | Self-reported attitudes to rules and honesty | Retail, cash handling, security | Varies | Not offered |
| Work sample | A realistic piece of the job | Most roles, after a shortlist | 30 to 90 minutes | Templates for the interview stage |
Choosing from the types of tests
Most small businesses need two or three test types per role, not all of them; the guide to types of pre-employment tests explains each with an example. A sensible default is one reasoning test, one job-skill or judgement test and a language or typing check where the job needs it, usually in about 30 to 45 minutes. Our role bundles start from that pattern for eleven common roles, and the test library shows every test with its length and the skills it covers.
Personality and integrity questionnaires are a different kind of instrument: they ask candidates to describe themselves rather than show a skill. HireValid offers personality and working-style profiles, such as the Big Five Personality Profile and DISC Work Style, each shown as a profile, not a grade, with no right answers and no pass mark; it does not offer integrity or honesty questionnaires. Skills tests carry more job-relevant evidence, so if you use a profile, treat it as a conversation starter rather than a pass mark, and check that its use is job-related. Work samples are valuable but long, so most teams keep them for the shortlist; our interview templates help you score them consistently.
The cognitive ability tests page explains what reasoning tests measure and how to set fair cut-offs.
More on pre-employment testing
Types of pre-employment tests
Nine kinds of test, each with an example question and cautions.
ExploreAre pre-employment tests legal?
US, UK and Canada basics, with links to the regulators.
ExplorePre-employment testing software
Run tests on monthly plans with a free start.
ExploreSkills testing for small businesses
A short test before every interview, without an HR team.
ExploreBest pre-employment assessment tools
Ten tools grouped by type and compared on published terms.
ExploreSkills assessment tests for hiring
Tests in eight categories, with lengths and examples.
ExploreCognitive ability tests
What reasoning tests measure and how to use them fairly.
ExploreAI interview cheating tools
What employers can do about AI help in tests and interviews.
ExplorePre-employment testing in the AI era
AI has changed what a CV or a take-home task can tell you. Many applications now read equally well, and AI interview assistants can suggest answers during a video call. That makes a short, timed pre employment assessment more useful, not less: it gives evidence of how the candidate reasons and works under the same conditions as everyone else.
Design matters more than detection. Timed questions from randomised pools, scenarios that turn on specific details and a follow-up conversation about the candidate's own answers make outside help much less useful. Integrity signals, such as tab switches or unusual timing, help a person review results, but none of them is proof. The employer's guide to AI interview cheating tools covers the tools and a five-step process, and the integrity page explains HireValid's Integrity Score.
What pre-employment testing costs
A pre hire test costs money and candidate time, so compare both. On price, the main question is how often you hire. Many assessment platforms bill annually, which suits teams that test every month; HireValid is monthly by default, from $49 a month for 50 candidates, with a Free plan for three candidates and nothing to pay between rounds.
On candidate time, keep the whole pre employment screening test to about 30 to 45 minutes. Longer assessments lose good applicants who have other offers. The calculator below compares a year of HireValid, for your hiring months and candidate numbers, with the lowest published annual price of one widely used platform; the comparison hub covers others.
Run your first pre-employment test this week
Start free with three candidates. Pick a role bundle and send one link.
Legal and fairness basics
Any employment test should be job-related and applied consistently. In the United States, the EEOC's guidance on employment tests and selection procedures explains that tests must not discriminate and that employers must provide reasonable accommodations. The U.S. Office of Personnel Management notes that most assessment methods need measurement expertise to develop well, which is one reason small businesses use ready-made tests. In the UK, the CIPD's selection methods guidance recommends clear, objective and structured processes to reduce bias.
In practice: test only what the job needs, give everyone the same conditions, make accommodations easy to request and review selection rates across groups after each round. Our fairness approach and the glossary entry on the four-fifths rule explain the monitoring step. For more detail by country, read are pre-employment tests legal?.
Sources
- U.S. EEOC: Employment tests and selection procedures, checked 2026-10-01
- U.S. OPM: other assessment methods, checked 2026-10-02
- CIPD: selection methods, checked 2026-10-02
Can you still get hired if you fail an assessment test?+
Yes, often. Many employers use a test score to rank applicants alongside the CV, interview and references, not as a strict pass or fail, so a weaker result on one test can be outweighed by strong evidence elsewhere. Employers should design for that: set a minimum only for skills the job truly needs, never let one score decide alone, and review selection rates across groups after each round.
What is the pre-employment test?+
It is a short, structured assessment that applicants complete before an interview or offer, such as a reasoning test, a job-skill test or a typing check. Every applicant answers the same questions under the same conditions, so you can compare them on evidence rather than on CVs alone.
What are some examples of pre-employment tests?+
Common examples include cognitive ability tests, situational judgement scenarios for customer service or sales, Excel and Google Workspace tests, English and business writing tests, typing tests and programming or coding tests for developers. Work samples, such as a short task from the job, are often used later with a shortlist.
How long should a pre-employment test take?+
About 30 to 45 minutes for the whole assessment is a good target for most roles. That is long enough for reliable evidence and short enough that strong applicants finish. Most HireValid tests take 15 minutes or less, combined into role bundles.
Are pre-employment tests legal?+
Yes, when they are job-related, applied consistently and offered with reasonable accommodations. In the United States, the EEOC’s guidance on employment tests explains the basics. Employers remain responsible for their own decisions, so take qualified advice for specific legal questions.
What do pre-employment test questions look like?+
They depend on the test. A reasoning question might ask what must be true from two statements; a customer service scenario asks for the best next action; an Excel item asks what a formula returns. Each test page in our library shows a sample question.
When should a pre-employment test happen in the hiring process?+
Usually after a short application screen and before interviews. Testing early gives every applicant the same chance to show their skills, and it lets you spend interview time on the people whose results fit the job. Keep the test short at this stage and save longer work samples for the shortlist.
How do you choose a pass mark for a pre-employment test?+
Start from what the job needs, not a round number. Look at the score a person who can do the work well should reach, set the cut-off there, and review it after each hiring round. Check selection rates by group too, so the pass mark does not screen people out without a job-related reason.