[toomuchtodo]

> These same employers may have a variety of software maintenance tasks that require recognizing a pattern of problem, knowing the appropriate algorithm from Ye Olde Textbook, and quickly applying it.

These edge cases might exist, although I argue the more likely problem is that hiring is hard, expectations can be unrealistic, and so it’s easier to fall back on puzzles and call them an objective measure of technical competency and soft skills. Project Euler is fun, but Stack Overflow is likely more relevant for your day to day for solving business problems with software.

[xapata]

I also measure my candidates' ability to fix bugs by learning the details of a language feature they're not familiar with, by finding examples and documentation.

I find that many junior-level candidates scrape by with Stack Overflow, but sadly have little competence when it comes to reading documentation. Candidates for more senior roles have a similar problem regarding systems design. They can find and parrot little statements they've seen on forums, but when you ask them to explain, their understanding turns out to be shallow.

I don't use programming exercises as a sufficient measure, but they are a necessary one.

Now I feel obligated to add that footer: We're hiring! ;-)

[vonmoltke]

> Now I feel obligated to add that footer: We're hiring! ;-)

Side note: you should put some contact info in your profile so people know who you are hiring for anf how to contact you. :)

[xapata]

I posted in the Who's Hiring thread non-pseudonymously.

[toomuchtodo]

I absolutely agree they’re necessary, but should be a realistic problem that needs solving (as you’re doing).