The Case Against WPM in Job Adverts

Take a candidate who types the same passage twice and gets 72 and 58. Nothing about them changed. The first measurement counted only characters still wrong at the end; the second charged a penalty for every incorrect keystroke including the ones they fixed.

That is not an edge case. Both conventions are in wide use, sites rarely state which they apply, and the gap between them is routinely more than ten words a minute for a typist who corrects as they go. Add the difference between a fifteen-second and a three-minute window, and between prose and text containing numbers and proper nouns, and the same person can honestly report a range spanning thirty words a minute.

The mechanics are laid out in how WPM is calculated, and the summary is that a bare number is a measurement without units. An advert that specified a distance without saying whether it meant metres or yards would be recognised immediately as defective. This is the same defect and it goes unremarked.

In most postings, the figure is inherited. It appeared in a job description at some point, it has been copied forward through revisions, and nobody currently hiring can say what test it was calibrated against or who chose it.

Where it is not inherited, it is usually derived from the last person in the role — an observation about one individual generalised into a threshold. Which describes one individual's throughput and then dresses it up as a property of the job.

Occasionally it traces to a certification standard, which is the only case where the number means something specific. Those cases are rare and are usually accompanied by an actual test, because employers who genuinely depend on typing speed do not ask, they measure.

So the correlation is roughly inverse to what you would want: the adverts most likely to quote a precise figure are the ones least likely to have a reason for it.

Here is the substantive objection rather than the pedantic one. In nearly every role where a typing requirement appears, the thing that determines job performance is accuracy, not speed.

Data entry is the clearest case. A fast operator with a modest error rate creates work — records that are wrong, that nobody re-reads, that surface later as reconciliation problems. A slower operator who is reliably correct creates none. The employer's actual interest is entirely in the second, and the advert asks about the first, as typing for data entry sets out at length.

Support work is similar: a message sent with a wrong reference number costs more than a message sent thirty seconds later. Transcription is the one genuine exception, and even there sustained accuracy predicts output better than peak speed, because falling behind compounds.

So the number in the advert is not merely imprecise. It is pointed at the variable that matters less, in roles where the variable that matters more is easy to measure and rarely asked for.

Requirements have costs on the other side, and this one falls unevenly.

A candidate who has never taken a typing test does not know their number. If the advert asks for sixty and they have no idea whether they type sixty, the rational move is often not to apply — and that self-selection removes people who type perfectly well but have never had reason to measure.

It also filters on measurement literacy. A candidate who tested once on a short, forgiving test can honestly claim a high figure; one who tested on a strict, long one reports lower for identical typing. The advert rewards the first, which is not a property anyone intended to hire for.

And it interacts badly with anyone whose typing is fine but whose relationship with formal testing is not — which is a real category, and one that a demonstrated work sample would handle better than a threshold.

Three options, in ascending order of effort and usefulness.

The cheapest improvement is to state the convention: "60 net WPM over three minutes on general prose, 97% accuracy minimum, measured at interview." That takes one extra sentence, makes the requirement checkable, and lets a candidate arrive prepared for the format rather than for the number — which is the practical advice in typing tests in hiring.

Better is to specify accuracy as the binding constraint and speed as a floor. "Comfortable sustained typing with a low error rate" describes what the job needs. If a number is required, an error cap alongside a modest speed target is closer to the real requirement than a high speed target alone.

Best is a work sample. Give candidates the material they will actually handle — the forms, the record types, the audio — and measure the thing you care about on the thing they will do. This is more effort and it answers the question, which a proxy never does.

Ask, because the questions are short and most employers will answer them. The full list worth putting to a recruiter is in typing tests in hiring; the ones that change your preparation most are whether an accuracy minimum applies and whether the text is plain prose.

Those answers change how to prepare substantially. An error-capped test rewards treating the speed target as a floor and typing at the slowest pace that clears it — the opposite of the habit a speed-only test builds. A numeric or mixed-content test rewards practice on material ordinary prose does not contain.

If the requirement is above your current speed and the gap is small, accuracy is usually the faster route to closing it, for the arithmetic reason in accuracy versus speed: reducing errors raises the net figure with no increase in finger speed at all.

And if nobody at the company can answer the questions, you have learned something useful about how much the number really matters to them.