I'm curious what you consider to be "cargo cult bad coding questions."
When I do phone screens, I generally do two coding questions, plus several other technical questions. The coding questions are a fizz-buzz level warmup question (not fizz-buzz itself, but something fairly trivial that any programmer should be able to do in 5 minutes), plus a more real-world question that requires walking over the filesystem, looking for particular things in particular files.
Beyond that, I do non-coding technical questions that are based on actual problems I've had to solve on the job, and actual technologies that we use every day like standard networking protocols (HTTP, TCP, DNS).
This seems like it would be fairly useful for my coding questions. So far I've done them in Etherpad or Google Docs, and told people not to worry about the precise syntax since that can be hard to do in such a different environment and without being able to run and test your code; then I inspect it manually and look for obvious logic errors. However, something like this would be fairly helpful in letting people write real code and run it.
When I do phone screens, I generally do two coding questions, plus several other technical questions. The coding questions are a fizz-buzz level warmup question (not fizz-buzz itself, but something fairly trivial that any programmer should be able to do in 5 minutes), plus a more real-world question that requires walking over the filesystem, looking for particular things in particular files.
Beyond that, I do non-coding technical questions that are based on actual problems I've had to solve on the job, and actual technologies that we use every day like standard networking protocols (HTTP, TCP, DNS).
This seems like it would be fairly useful for my coding questions. So far I've done them in Etherpad or Google Docs, and told people not to worry about the precise syntax since that can be hard to do in such a different environment and without being able to run and test your code; then I inspect it manually and look for obvious logic errors. However, something like this would be fairly helpful in letting people write real code and run it.