I recently completed a series of interviews for a new job. Here are a couple of reminders of areas where I think I did well, and others where I could have done better.
Assemble a portfolio, even if they don't ask for it. Some companies may care a lot about your portfolio, and some may not even ask for one. Either way, it's always worth the effort to put together examples of your best work. The exercise will recall work stories you can speak to in the interview to sell your strengths.
Be honest ... Usability evaluations involve judgments. There's a temptation to try and "pass" the interview by saying what you think the interviewer wants to hear. If you can support your position with solid reasoning, though, a good boss-to-be shouldn't hold their disagreement against you.
If you're not honest, you're interviewing to be a approval-seeking flunkie. And if your interviewers are put off by your honesty, perhaps it's a sign of how it might be to work with them.
... But also be humble. It's easy to criticize someone else's effort when you don't know what kind of time, budget, or business constraints they were under. Don't be an arrogant outsider dismissing an interface that may have resulted from the hard word of the interviewer.
Prepare for the obvious questions, such as
- "What do you think of the usability of X?" Usually you can guess from tone how the interviewer already feels about product or website X. If you disagree, be ready to back up your opinion with some good supporting evidence.
- "Give me some examples of products and websites with good usability." This is a simple question to ask, but it deserves more than a quick answer. Prepare at least a couple of good examples, with explanations of what users the products are for, and why specifically they will find the product usable.
- "What is your working style?" Most employers are looking for excellent communicators, persuasive negotiators, and above all collaborative coworkers.
- "Do you think your background fits this position?" Once you've learned more about the position and the company, sell yourself as best you can, but be honest too. For example, if you are someone like me, with less of an academic background, you might not be happy on a team of all Ph.D. HCI experts.
When I interviewed at my current company, it was an arduous, all-day affair with an hour-long presentation to the whole UX team and one-on-one interviews with UXers, management, and some technical folks. In my last one-on-one of the day, the interviewer asked me how the day was going. I said it was going really well, and there had been a lot of interesting questions and discussions, as opposed to standard, boring interview questions. He asked for an example of a standard question. I said, "Oh, you know, like, 'Where do you want to be in five years?'". He paused, and completely deadpan asked, "Where do you expect to be in five years?" I found out later that he liked me and voted to hire me (and had an unusual sense of humor), but at the time I thought I'd blown the entire interview right there.
So there's another piece of interview advice -- don't get cocky! =)
BTW, that was a good link. I'm going to use some of those when I'm interviewing people in the future. I particularly liked, "How do you keep your knowledge of user experience design and usability up to date?" That's an interesting and telling question.
Posted by: Terry Bleizeffer | September 04, 2007 at 10:05 AM
I ask - Do you like Star Trek?... Seriously! I have done it twice in the last month and got a vehement no! I hired them too!
By asking that question, what I was looking for was a insight (from the potential employee) into how different people think. Empathy with others is critical to our work.
Actually, an understanding of our own habitual thought processes is really what I look for. That's where is all begins. If we can clearly understand our own experience then it allows us to put the shoe on the other foot and provide a client with useful critique of their technology from their customers point of view.
Posted by: Breezy | October 08, 2007 at 05:13 AM