Rimu's blog

I've had a lot of work interviews or interview-type meetings in my life, but there have only been two or three which I felt really assessed me well, technically. I enjoyed those very much, because just by the questions they asked they demonstrated that they could understand any answer I could throw (back) at them. There was a sense that I was getting a fair trial, and so was everyone else.

"Where do you want to be in 5 years?" or "Give an example of a situation you handled well/badly" are too easy to have pat answers for.

Here are a few things I would appreciate being asked and which I think the ask-er would gain a lot from. If they lack the understanding to interpret the answers then they should delegate the technical aspects of the interview to someone who does.

• Program your way out of a paper bag. Be creative.
  Imagine if you employed someone who can't program their way out of a paper bag. Or someone who took this question literally! Ideally they'll whip up a few lines or code that would never successfully execute/compile but that is humorous or clever, in a geeky way.
• Write a program on the whiteboard that prints out the words FLIP then FLOP on seperate lines, for 100 lines. Every 5 lines, print out BOUNCE instead. Use any language.
  Tests elementary problem solving skills and ability to code without support from an IDE or the internet. Their code won't be perfect, but they should have a good stab at it and demonstrate that they are able to reason through a fairly efficient way of solving the problem.
• This is a lift (show a photo or physically go to one). Design a better user experience on the whiteboard.
  This is a chance to demonstrate understanding of various non-obvious stakeholders (maintenance worker, building owner, etc) while applying basic UI design skills in a unusual setting. Look for extra buttons they add, access panels, touch screens or even things which make the lift much more than just a lift. Massage chairs would be nice. You're looking for vision, creativity and originality.
• What is your favourite programming language(s). Why?
  Watch for passion and interest levels, rather than judging them on their choice. An indifferent programmer is often a bad one.
• What is the coolest app you made in your spare time?
  The answer is nearly irrellivant, unless they haven't made any cool apps in their spare time, which is what you're checking for. They don't need to have made anything particularly 'cool', but a programmer who never makes any programming for fun is probably not going to be that into their work. Again, a chance for the programmer to demonstrate passion and interest in their field.
• Have you attempted to start your own online business? What is different about it?
  Few will have, but those that have will probably have learnt lessons that you can't buy anywhere.
• When was the last time you had a great (or average) idea for a online business/website?
  Programmers who think about their work a lot should have a 'great idea' every once in a while. It's not important how good that idea is or even how frequently they come, but if they never have any ideas then there is something lacking.
• Why didn't you build it?
  Other than 'not enough spare time', ideally... Awareness of their own limitations and how difficult it is to succeed will hopefully be demonstrated.
• FOSS. Thoughts?
  They need to have an opinion, at least. Ideally a well thought out one with an example or two, but any opinion is better than none.

Of course you'd still want to ask the normal stuff around what technologies and methodologies they've used and for how long, but hopefully some of the above questions will have given you a few ideas.