What Is a Good Typing Speed for Programmers?
Benchmarks for developers — average WPM, what counts as fast, and why accuracy matters more than raw speed.
The numbers, without the inflation
The average adult types around 40 words per minute. Between 60 and 80 is genuinely good and puts you ahead of most people who use a keyboard professionally. From 90 to 110 is fast. Above 120 is the top few percent, and beyond 140 you are into competitive territory.
Treat online claims with suspicion. Scores get quoted without the accuracy that produced them, and a 120 WPM run at 88 percent accuracy is slower in practice than 95 WPM at 99 percent once you count the corrections.
Why developer numbers look lower
Programmers often test lower than their prose speed suggests, and it is not a skill gap. Code is dense with characters that sit outside the comfortable letter zone: brackets, underscores, angle brackets, semicolons, and the number row.
A developer typing 95 WPM on English words might manage 55 on real code. That gap is normal, and it is the more useful number, because it reflects the work you actually do.
What the number is measuring
A 'word' in every standard typing test is five characters, including spaces. This convention exists so that scores are comparable across languages and text types rather than being skewed by whether a passage happens to use long words.
So 60 WPM means 300 correct characters per minute. When a test reports both net and raw WPM, net counts only correct characters while raw counts everything you typed. The gap between them is the cost of your mistakes.
What speed is actually enough
For professional work, roughly 60 to 70 WPM with accuracy above 97 percent is the point where typing stops holding you back. Below about 40, typing genuinely interrupts thought — you lose the end of a sentence while hunting for a key.
Above 100, further gains are pleasant but rarely change your output. If you are already comfortably past that, your time is better spent on accuracy and consistency than on chasing a bigger headline number.
Speed by profession, roughly
Transcriptionists and court reporters work at 80 to 120 WPM on prose, because sustained speed is the job. Administrative and data-entry roles typically screen somewhere between 50 and 70. Software developers vary enormously, and the number is a poor predictor of anything, because code speed and prose speed diverge so sharply.
Treat published averages with suspicion generally. Most circulate without the accuracy figure that produced them, and a WPM number without an accuracy number is close to meaningless — you can inflate the first by sacrificing the second.
Comparing your own numbers honestly
Compare like with like. A words-mode run and a code run are different tests, and a 50-word passage and a 200-word passage measure different things — short tests reward a fast start, long ones expose stamina and concentration.
The only comparison that reliably means something is your own average against your own average on the same kind of material. Everything else, including a leaderboard, involves people typing different text under different conditions on different keyboards.
Put it into practice
Frequently asked questions
What is a good typing speed for a programmer?
Around 60 to 70 WPM with accuracy above 97 percent is comfortably sufficient for professional work. Expect your speed on real code to be meaningfully lower than on plain English — that gap is normal and reflects symbol density, not a lack of skill.
Why is a word counted as five characters?
It is the long-standing convention that makes scores comparable. Counting actual words would make your score depend on whether a passage used short or long ones, so every standard test counts five characters, spaces included, as one word.
Is 40 WPM slow?
It is about average for adults generally, but it is on the low side for anyone who writes for a living. Below roughly 40, typing starts to interrupt your thinking, which is the practical reason to improve rather than any target number.