Why this test matters
Engineers who type 30 WPM and engineers who type 100 WPM are equally capable architects, but the 100 WPM engineer is meaningfully more productive across the long tail of work: PR descriptions, code reviews, design docs, async chat, debugging notes, commit messages. None of these are typing-bottlenecked individually, but in aggregate they consume 30–50% of an engineer's day. A 70+ WPM baseline with strong code-mode speed (typically 30–40% slower than prose) makes async-first remote workflows feel natural rather than painful. Higher than 100 WPM stops mattering — at that point your bottleneck is thinking, not typing. The 1-minute prose test below is the right warm-up; if you want a code-specific benchmark, switch to a code-mode test once those ship. Many engineering teams that explicitly value WPM (Northgate Dev, several remote-first SaaS companies) cite 70 WPM as the floor, with 90+ on code-specific tests as the strong-pair-programmer threshold.