The problem is that actual work experience doesn't give you this. The more experience you gain shipping working software, especially in a senior capacity, the l

The problem is that actual work experience doesn't give you this. The more experience you gain shipping working software, especially in a senior capacity, the less exposure you're likely to have to the skills tested for in the algorithm-based whiteboard interview. We don't write algorithms often, but based on this style of interview, you'd assume that's what we do primarily, or even mostly. Some of my time is spent putting together the solution to a business user's request. The rest is spent reading other peoples' code to figure out where I can safely add the new feature, writing the feature (which rarely involves algorithms), writing automated tests for the feature, and babysitting my PR to production. Asking a candidate to solve a gnarly merge conflict is more relevant than asking them to produce an algorithm on a whiteboard.