If the job actually requires typing quickly like a Court Recorder then there is a basis to require typing quickly. If the job doesn’t actually require it, like for example a programmer then enforcing the requirement anyway is discrimination.
Most jobs that involve typing benefit from being able to type quickly.
For example, I am a frequent customer of U-Haul. I learned to not use the branch that’s closest to me, because some employees there are really slow with computers, which makes checking out equipment very slow, and frequently results in a long line of waiting customers. Driving 5 extra minutes saves me 20 minutes of waiting for employees to type in everything and click through the system.
And this is freaking uhaul. If you’re a software engineer, slow typing is also a productivity drain: a 3 minutes email becomes 6 minutes one, a 20 minutes slack conversation becomes 30 minutes etc. It all adds up.
Small productivity drains on minority portions of the task are not a requirement of doing the job. Software developers generally spend more time thinking than typing. Typing is not the bottleneck of the job (at least for the vast majority of roles).
Sure, of course typing is not the biggest bottleneck in software engineer job. That doesn’t mean it’s irrelevant for productivity.
Consider another example: police officers need to do a lot of typing to create reports. A fast typing officer can spend less time writing up reports, and more time responding to calls. That makes him more productive, all else being equal. Of course it would be silly to consider typing speed as a sole qualification for a job of police officer (or, for that matter, a software engineer), but it is in no way unreasonable to take it into account when hiring.
> Most jobs that involve typing benefit from being able to type quickly.
Maybe. If you type 10,000 words per minute but your entire module gets refactored out of the codebase next week, is your productivity anything higher than 0?
Multiple times in my career, months or even years worth of my team's work was tossed in the trash because some middle manager decided to change directions. A friend of mine is about ready to quit at AMZN because the product he was supposed to launch last year keeps getting delayed so they can rewrite pieces of it. Maybe some people should have thought more and typed less.
> Maybe. If you type 10,000 words per minute but your entire module gets refactored out of the codebase next week, is your productivity anything higher than 0?
If you spent less time typing that module that later went to trash, you are, in aggregate, more productive than someone who spent more time typing the same module.
This sort of argument only makes sense if you assume that there is some sort of correlation, where people who are slower at typing are more likely to make better design or business decisions, all else being equal. I certainly have no reason to believe it to be true. Remember we are talking about the issue in context of someone who is slow at typing because of arthritis. Does arthritis make people better at software design, or communication? I don’t think so.
