The practical guide to pre-employment testing

How to use this field guide

This guide organizes a practical assessment process into five chapters: defining the hiring decision, gathering skills evidence, understanding reasoning scores, reviewing selection outcomes and designing a customer service task. Each chapter addresses a different decision. Read them in order when preparing a first process, or use the table of contents when you need to revisit one part.

Start with one real vacancy and a blank decision record. Write the role, its three most important tasks, the evidence you want for each task and the person responsible for reviewing it. Do not begin by adding every available test. A smaller assessment with a clear purpose is easier to explain, maintain and improve than a large collection chosen because the software makes it possible.

The chapters are edited selections from the HireValid editorial library, linked at the start of each chapter. They are collected here so a small team can work through the whole process in one place. All examples are hypothetical. This draft has not received named expert or legal review. It is not a validated selection procedure or a guarantee of compliance.

Keep three records as you work: the candidate instructions, the reviewer rubric and the change log. The instructions explain the experience. The rubric explains the evidence. The change log explains why the process is different next time. These records do not need to be elaborate, but they should be specific enough that a colleague could understand the process without relying on your memory.

Before inviting candidates, check actual product availability. HireValid’s public catalog describes proposed tests and indicative durations; the website’s examples are practice tools. A live hiring round requires approved content, working candidate delivery, appropriate privacy arrangements and a review process owned by the employer.

Chapter 1: Pre-employment testing for a small business

Adapted from Pre-employment testing for a small business.

Begin with one hiring decision

A small business does not need a complicated assessment program to start collecting better evidence. It needs a clear answer to a narrower question: what must the next person be able to do, and what would demonstrate that ability? Start with the role you are hiring now. Avoid buying a library first and then looking for reasons to use as much of it as possible.

Write down the work in ordinary language. An office administrator may reconcile orders, coordinate calendars and answer routine questions. A support agent may interpret a policy, identify missing information and write a helpful reply. These tasks are more useful starting points than broad labels such as “smart,” “good communicator” or “culture fit.” The labels hide the behavior you need to observe.

Choose three or four essential requirements and separate them from things a new employee can learn. A familiar software package may be teachable. Careful checking of information may matter from the first week. This distinction helps you avoid excluding a capable candidate for not having worked in an identical environment. It also gives you a clearer explanation for why each assessment stage exists.

Match the evidence to the requirement

Different methods answer different questions. A reasoning test can show how someone works through unfamiliar information. A work sample can show how they apply a skill in a task similar to the job. A structured interview can explore decisions, communication and past experience. None of those methods provides a complete picture by itself, and adding more methods does not guarantee useful coverage.

For each requirement, name the evidence you want. If accuracy matters, ask candidates to compare two small records and explain any mismatch. If customer communication matters, ask for a reply using a supplied policy. If prioritization matters, provide competing requests with deadlines and enough context to choose a sensible order. The task should resemble the work without becoming unpaid commercial production.

The Attention to Detail test illustrates one narrow skill. It does not claim to predict every aspect of administrative performance. You could pair it with a short role-specific task and a conversation about checking work. This creates complementary evidence instead of repeating the same skill through several tests and mistaking repetition for confidence.

Keep the first assessment short

Long assessments impose a cost on candidates and reviewers. Before adding another test, ask what new decision-relevant information it contributes. If the answer is vague, leave it out of the first version. You can investigate a specific uncertainty later with a targeted follow-up rather than asking everyone to complete every possible exercise at the start.

Duration should reflect the purpose and the candidate’s stage in the process. A brief initial assessment may be reasonable before an interview. A substantial project without a clear commitment from the employer can feel disproportionate. Explain the expected time honestly, including instructions and practice. A label that says “ten minutes” but requires twenty minutes of setup undermines trust.

Use a role bundle as a starting point, then edit it. A generic bundle cannot know your exact responsibilities, language needs or accessibility requirements. Remove anything that does not connect to a real task. If a proposed test is a later-release capability, do not design your live hiring process around it until the product and content are actually available.

Explain the process before asking for work

An invitation should tell candidates what the assessment is for, approximately how long it takes and what happens next. Include the deadline and the time zone. State the permitted tools, device requirements and any monitoring. Give a contact route for questions and accommodations. Candidates should not discover a camera requirement or an unexpected timed section after they have already started.

A useful invitation might say that the exercise covers written customer communication and checking order details, followed by a structured interview for shortlisted candidates. It can explain that the employer will review the answers and that a score is not the sole decision. Avoid promises about response dates that your team cannot reliably meet. If the schedule changes, send a clear update.

The invitation is also where you can reduce avoidable anxiety. Tell people whether practice questions are scored, whether they can return to earlier questions and what to do if the connection fails. These are not small details when someone is trying to perform under unfamiliar conditions. A respectful process makes the evidence easier to interpret because fewer surprises interfere with the task.

Chapter 2: Start skills-based hiring without an HR team

Adapted from Start skills-based hiring without an HR team.

Replace a vague profile with a useful task list

Skills-based hiring starts with the work, not with a new label on the same job advertisement. If a small business asks for a degree, several years of experience and a familiar job title without explaining the responsibilities, it may be filtering for background rather than capability. Some credentials are genuinely necessary. Others are habits inherited from an old template. Review each requirement instead of assuming it belongs.

Imagine hiring an office administrator. Begin with the tasks: reconcile order records, coordinate a shared calendar, respond to routine requests and flag exceptions. Ask which tasks need independent competence on arrival and which can be taught. This creates a more practical profile than “organized self-starter with excellent communication skills.” It also makes the eventual interview easier to prepare.

A useful task list names an action, an object and a standard. “Check daily order entries against the source record and escalate unexplained differences” tells a candidate more than “attention to detail.” You do not need a lengthy competency framework to write that sentence. A manager who knows the work can draft it, then ask a colleague to check whether it reflects the real role.

Separate essential requirements from preferences

An essential requirement should have a defensible connection to the job. A preference may make onboarding easier but should not quietly become a screening rule. List them separately. If your team can teach a particular software interface, say that equivalent experience is welcome. If a legal qualification is required, explain that clearly and verify it through an appropriate process.

Be careful with requirements that sound neutral but may be vague proxies. “Native speaker,” “young and energetic” or “a perfect cultural fit” can distract from the actual capability needed and create fairness concerns. Describe the communication task, working conditions and observable behavior instead. Obtain appropriate advice for employment wording in your location, especially where requirements might exclude protected groups.

The job description templates provide a structure with placeholders. They do not know your compensation, working hours or local obligations. Replace every placeholder and remove anything that does not apply. A template is useful when it prompts thought, not when it allows the employer to publish an unexamined list of demands.

Choose one direct demonstration per major skill

For each essential requirement, ask what a candidate could show in a reasonable amount of time. A brief record-checking exercise can reveal how someone handles mismatches. A scheduling scenario can reveal whether they notice dependencies and ask useful questions. A short written response can reveal clarity and tone. The demonstration should resemble the work without requiring confidential information or a lengthy unpaid project.

Use synthetic data and clearly fictional situations. Do not ask candidates to solve a live customer problem that your business can use commercially. Provide enough context to make the task fair to people who have not worked at your company. Explain any terms that are specific to your process. Hidden knowledge rewards familiarity rather than the intended skill.

A general assessment can complement a work sample, but it should not dominate the process merely because it produces an easy number. The Office Administrator bundle suggests several relevant areas. Review its scope against the task list. If the proposed bundle is longer than the decision requires, remove tests rather than treating the default as mandatory.

Write a small scoring guide before reviewing

A rubric turns an impression into a set of questions about evidence. For the record-checking exercise, you might consider whether the candidate found important mismatches, avoided inventing corrections and explained the next step. For a scheduling task, you might consider whether they recognized constraints and communicated a conflict. Keep each dimension distinct enough that reviewers can explain it.

Use plain descriptions for rating levels. A middle level might mean the answer is mostly correct but misses an important check. A stronger level might require accurate work plus a clear explanation of uncertainty. Avoid labels such as “excellent” without saying what makes the response excellent. The label adds confidence without helping someone apply the scale consistently.

Try the rubric on two or three fictional answers before using it on candidates. Ask whether two reviewers identify similar evidence and whether disagreements reveal ambiguous wording. This is a calibration exercise, not a validation study. Its purpose is to make the process understandable and reduce avoidable inconsistency before real people are affected by it.

Chapter 3: Cognitive ability tests: what they measure and how to use them

Adapted from Cognitive ability tests: what they measure and how to use them.

Understand the question a reasoning test answers

A cognitive ability test is intended to gather evidence about reasoning, learning or solving unfamiliar problems. Depending on the design, it may include numerical information, written passages, visual patterns or a mixture of formats. A result tells you something about performance on those tasks under those conditions. It does not provide a complete measure of a person’s potential, character or suitability for every job.

That distinction matters because a single score can look more comprehensive than it is. A candidate may reason well in a visual format while finding a language-heavy format difficult. Another may understand the problem but work slowly under a strict time limit. Those differences deserve interpretation in relation to the role rather than a quick conclusion about who is “smartest.”

Start by asking why this kind of evidence belongs in the process. If the job involves learning new systems, interpreting unfamiliar information or comparing options, reasoning may be relevant. Document that connection. If the test is included merely because another employer uses it, you have not yet explained its purpose. A recognizable assessment name is not a substitute for a job analysis.

Separate reasoning from job knowledge

A reasoning task and a knowledge test measure different things. A person may know a spreadsheet shortcut because they have used a particular application for years. They may also be able to work out a new formula from documentation. Both can matter, but they are not interchangeable. Decide which ability is required immediately and which can be developed through onboarding.

For a junior analyst, a numerical reasoning question might reveal whether they interpret a percentage correctly. A SQL task might reveal whether they can filter rows or reason about a join. A short work sample could show whether they check missing values before explaining a result. These methods complement each other when each has a clear purpose. They become redundant when several versions merely reward the same familiarity.

The planned General Cognitive Ability test combines several reasoning areas. Its public sample is a practice illustration, not a validated instrument. The Junior Data Analyst bundle shows how reasoning can sit beside role-specific technical skills. The employer still needs to judge whether that proposed mix matches the actual work.

Interpret a percentile carefully

A percentile describes relative standing within a reference group. A result at the 75th percentile means the score is above 75% of that documented group under the relevant scoring convention. It does not mean 75% of questions were correct. It also does not mean a 75% probability of succeeding in the role. Those are different quantities that require different evidence.

Always look for the norm group, sample size, collection method and version. A broad working-population reference may answer a different question from a group of applicants for a specific role. If the reference sample is small or poorly matched, a precise-looking percentile can be misleading. Reports should explain those limitations instead of hiding them behind a confident visual.

Comparing scores across test versions also requires care. Changes to items, timing or scoring can alter interpretation. A useful report records the version used for the candidate’s attempt. If norms are updated later, the earlier report should remain understandable. HireValid’s benchmark page describes the intended documentation and explicitly notes that live norm data is pending validation.

Examine language and timing requirements

A reasoning question may contain a substantial reading component even when it is labeled numerical. Complex wording can turn a task about interpreting a table into a test of advanced language proficiency. Review the instructions and item text for unnecessary complexity. If the job requires plain workplace communication, use plain workplace communication in the assessment wherever possible.

Timing can also change the skill being observed. A strict limit may emphasize processing speed, familiarity with the format or comfort under pressure. That may be relevant in some contexts, but it should not be assumed. Tell candidates the timing in advance and explain whether practice is available. Consider appropriate accommodations rather than treating one clock setting as inherently fair for everyone.

Visual reasoning is not automatically free of barriers. Small shapes, low contrast or reliance on color can make a task inaccessible. A lower reading load does not establish cultural neutrality or universal accessibility. Evaluate each format on its own merits. The right question is whether the task offers an appropriate way to demonstrate the skill for the intended population.

Chapter 4: The four-fifths rule explained for small employers

Adapted from The four-fifths rule explained for small employers.

What does the rule compare?

The four-fifths rule compares selection rates between groups. A selection rate is the number of people selected divided by the number considered in a defined group and stage. The screening ratio divides one group’s selection rate by the highest group selection rate. A ratio below 0.80 can flag a difference that deserves investigation. It does not, by itself, explain the cause of that difference or determine whether a selection process is lawful.

The distinction between a flag and a conclusion is essential. A dashboard can make a ratio look authoritative because the arithmetic is precise. The interpretation is more complicated. You need to understand the population, the stage, the sample size, the quality of the data and the relevance of the selection method. A ratio above the threshold is not a certificate of fairness, and one below it is not a complete legal finding.

The U.S. EEOC guidance on employment tests and selection procedures is a primary source for the broader legal context of employment testing. This article is an educational explanation of a screening calculation. It does not replace advice about a particular employer, jurisdiction or hiring decision.

Work through a hypothetical example

Suppose a clearly defined assessment stage includes two hypothetical groups. In Group A, 20 of 40 applicants advance, giving a selection rate of 50%. In Group B, 8 of 20 advance, giving a selection rate of 40%. Dividing 40% by 50% gives 0.80, or 80%. The example sits exactly at the conventional screening threshold. These numbers are invented for explanation; they are not HireValid customer outcomes.

Now suppose only 6 of the 20 applicants in Group B advance. Its selection rate becomes 30%. Dividing 30% by 50% gives 0.60. That ratio is below four-fifths and would prompt closer review. The calculation still does not identify whether the difference arose from the test, a prior screening stage, an inconsistent review practice, missing data or another factor.

Keep the denominator and stage consistent. If one group’s denominator includes everyone who applied while another includes only people who completed a test, the comparison is not measuring the same thing. Label the population and time period explicitly. A useful report should allow a reviewer to understand where each count came from rather than displaying a ratio with no underlying numbers.

Why small samples need care

In a small hiring round, one person can move a rate substantially. If a group contains five people, changing one outcome changes the selection rate by twenty percentage points. That does not mean the person’s experience is unimportant. It means the number is unstable and should not support broad conclusions without context. A responsible review treats uncertainty as part of the result.

Do not combine unrelated roles or periods simply to make the sample bigger. Different jobs may have different requirements and selection stages. Combining them can hide an important difference or create a misleading one. If you aggregate data, explain why the populations and processes are comparable. Keep the underlying views available to appropriately authorized reviewers.

A group with no applicants or a comparison group with no selections can also create undefined or uninformative ratios. Software should not quietly turn these into zero, a pass indicator or a confident warning. Show the actual counts and explain that the ratio cannot be interpreted in the usual way. A clear limitation is more useful than a tidy but misleading status badge.

Protect the information used in analysis

Demographic information can be sensitive. Decide whether collecting it is appropriate and lawful, how participation is explained and who can access the results. Voluntary responses may be incomplete, and missingness can affect interpretation. Do not infer protected characteristics from names, photographs or other proxies merely to populate a chart. That creates additional risks and can make the analysis less trustworthy.

The HireValid brief proposes optional, consent-based demographic collection stored separately from individual candidate scores. Fairness reporting is a later-release plan, not a live feature established by this website. The intention is to support aggregate review without presenting demographic attributes beside an individual’s assessment result to the hiring manager.

Before implementation, define access permissions, retention and minimum reporting conditions. Small groups may be identifiable even in a summary table. The person reviewing aggregate outcomes does not necessarily need access to every candidate’s sensitive information. Legal and privacy review should address the actual collection and reporting workflow rather than relying on the reassuring name of a feature.

Chapter 5: Build a useful customer service assessment

Adapted from Build a useful customer service assessment.

Start with the service your team actually provides

Customer service work varies. A person handling delivery questions needs different context from someone supporting a technical product or resolving billing disputes. Before building an assessment, identify the situations the new hire will encounter most often and the decisions they are authorized to make. A generic test of being friendly does not capture the practical boundaries of the role.

Write down the essential behaviors. These might include listening to the concern, checking the relevant record, applying a policy accurately, explaining the next step and escalating when necessary. Separate behaviors from outcomes the candidate cannot control. An agent may handle a difficult interaction well even when the requested refund is not permitted. The assessment should not reward a promise that breaks policy merely because it sounds pleasing.

Use a small set of realistic situations rather than an exhaustive simulation of every possible complaint. You want enough evidence to guide a hiring conversation without turning the assessment into unpaid training. The Customer Support Agent bundle is a proposed starting point. Its relevance depends on whether the tests match the work and communication channels in your team.

Give the candidate enough context

A situational question should supply the policy, the customer’s concern and the agent’s authority. If the best answer depends on an internal rule the candidate has never seen, the question rewards familiarity with your organization rather than service judgement. Keep the scenario concise, but do not remove information needed for a defensible response.

For example, describe a delayed order, the latest tracking event and the available resolution options. State whether the agent can issue a refund or must request approval. Ask for the next action and a short explanation. A strong response should use the supplied facts rather than inventing a policy or promising an outcome outside the agent’s control.

Avoid unnecessary emotional drama. A realistic frustrated customer can reveal how a candidate balances empathy and accuracy. An extreme or humiliating scenario may measure comfort with the assessment rather than normal service work. Keep the wording respectful and explain any industry-specific terms. The goal is to observe useful reasoning, not to surprise or embarrass the person taking the test.

Assess empathy and accuracy together

Empathy matters, but it should not be reduced to a list of approved phrases. A candidate can acknowledge a customer’s inconvenience in several reasonable ways. Score whether the response recognizes the issue and communicates respectfully. Do not require the candidate to imitate one reviewer’s preferred style when another clear, appropriate style would work just as well.

Accuracy matters at the same time. A warm message that gives the wrong policy or exposes another customer’s information is not a strong service response. The rubric should separate tone from factual correctness so reviewers can identify the actual strength or gap. A single overall impression can hide this distinction and reward polished writing over a useful answer.

Consider a hypothetical duplicate-charge complaint. A sensible first step is to acknowledge the concern and check the billing record. Immediately promising a refund may sound helpful but could be premature. Telling the customer to contact someone else without investigating may be unhelpful. The reasoning behind the choice is more informative than whether the candidate includes a particular stock apology.

Build a short written work sample

A written task can reveal how the candidate translates a decision into a message. Provide a short policy and ask for a reply of a reasonable length. Explain the audience and the communication channel. A chat response may need a different structure from an email, so do not score both as though they were the same task.

Use synthetic customer details. Do not expose actual support tickets or personal information without a lawful, appropriate basis. Remove company-specific knowledge that a new hire would learn during onboarding. If a tool or template is normally available in the job, decide whether the assessment permits it and say so. Tool rules should reflect the skill you are trying to observe.

A practical rubric might consider whether the reply identifies the issue, states the correct next step, avoids unsupported promises and remains easy to understand. Ask for a brief explanation if you need to see why a choice was made. Keep the task proportionate, and do not use candidate responses as free commercial support content.

Your first-round worksheet

Write a one-page plan before sending invitations. Name the role and list the essential tasks. Beside each task, identify the evidence you need and the assessment method that could provide it. Mark requirements that can be taught during onboarding so they do not become unnecessary entry barriers.

Next, draft the invitation and the rubric together. If you cannot explain a task to a candidate in plain language, examine whether its purpose is clear. If a reviewer cannot explain a rating using observable details, revise the rubric. Try the instructions with someone unfamiliar with your internal process.

After the round, review unclear instructions, estimated duration, accommodations and reviewer disagreements. Record the changes you intend to make and why. Keep the scope of your conclusions modest: a first round can reveal workflow problems, but it cannot establish broad predictive validity.

Final decision questions

• Does each stage connect to an essential requirement?
• Is the candidate’s total time proportionate?
• Are tools, timing and monitoring explained before the start?
• Can reviewers distinguish evidence from assumptions?
• Who handles questions, accommodations and data requests?
• What will you review after the hiring round?

Continue with the test library, role bundles and template collection.