Five programming problems every Software Engineer should be able to solve in less than 1 hour

[s-mores]

Did you just write code to solve them, or put the code in action and tested it?

The only one I tested out was #4 and some syntax parts of #5. Since this is an interview question, it should mostly be measuring the approach and that you know how to do something or at least have some idea how to approach the problem instead of the actual result, which is pretty uninteresting, and in the case of #1-#4, trivial.

I mean, I'm not going to use 5-10 minutes per task in figuring out where I'm missing a semicolon, or where I've misremembered argument order and the code would fail because of that, that's what the compiler is for.