Typing speed for programmers

Almost no software job asks for a WPM figure. What slows developers down is symbols, brackets and navigation — so that is what is worth practising.

At a glance

Often askedUsually no WPM requirement in the advert
Measured asNot measured; speed shows in everyday work
What decides itAccuracy on symbols, brackets and shortcuts

The figures below are what job adverts commonly ask for, not a rule: employers differ, so always check the number in the advert you are answering.

Why raw WPM matters less

Code is mostly short names, symbols and navigation, and developers spend far more time reading and thinking than typing. A prose test at 100 WPM tells you little about how comfortably someone types brackets, quotes and operators.

What is worth practising

The symbol keys on the top row and the right-hand side, touch typing so you can look at the screen, and editor shortcuts. Fewer slips on brackets and quotes save more time than a higher WPM on words.

How to prepare

The code typing test lets you type real snippets in 13 programming languages and scores syntax accuracy. For the keys themselves, the free lessons include a symbols lesson and a keyboard shortcuts lesson.

Practise for it

Programmer typing speed — frequently asked questions

How fast should a programmer type?

There is no standard. Comfortable touch typing at an average speed or better is enough for most developers; accuracy on symbols matters more than WPM.

Does typing speed make you a better programmer?

Not by itself. It removes friction, so you can keep up with your thinking, but the quality of the code does not depend on it.

Which test suits programmers?

The code typing test, which uses real code in 13 languages and scores accuracy on the syntax you actually type.

Typing speed for other jobs