Hardy's rule can be adapted to programming: to code it better, think it gooder. One big difference in productivity comes from making good design decisions early on and not taking shortcuts that weeks later turn into spaghetti hacks.
That's not what interview tests are for; they're for demonstrating a base level of competence and how you think about code during a discussion of the code. Also for acting as a catalyst for more discussion about programming.