1. Before the interview
Be clear about your expectations. You should be clear about which gap in your team you’re trying to fill, what type of experience you think would be valuable and what skills you feel might be needed to do the job.
I like to be able to explain the role & expectations in one line — “A junior designer who knows the basics of visual design & is willing to learn under a mentor to deliver user interfaces” or, “A designer with 2 – 3 years of experience in delivering projects with regular user testing exercises”.
This will help you explain the role to the candidate when you meet them.
Also:
- Have a clear budget in mind.
- Keep the interview within a max of 90 mins.
2. Introduce yourself
Remember that the candidate is also trying to vet you & the company. Start by introducing yourself. Then talk in detail about the company – pitch your company. I like to give a bit of history to explain how we turned from a small app development team to a design fronted client servicing studio.
Take your time, make sure you don’t rush. Set the tone for a relaxed, informal & detailed chat. (Just like a project kickoff meeting – but that’s another story).
3. Have a chat
Try to stay away from the Q&A format. Start a conversation. I usually lead with:
“Tell me how you got into design – start from when you were a kid.”
Pick on as many details as you want, and don’t be afraid to lead the conversation away from work once in a while — it will help the candidate open up and give you both a deeper insight into whether you are a good match. If you’re curious about that little town they grew up in, ask more about it. Tell them about your background as well—it could help them open up. Again, remember you’re also being evaluated by the candidate — give them all the info they need to feel comfortable & connected with you.
This is also when you can get into as much of the nerdy design details as you like. I like to find out what their strengths are and how they developed these. I’m a “design process” nerd, so I love talking in detail about their design process:
- “Can you walk me through your design process?”
- “That’s an interesting choice of typefaces, how did you decide on the typefaces for that project?”
- “How did you set up that type scale?”
- “Where do you look for inspiration?”
- “Give me some pointers on how to ask better questions during user testing!”
- “Did you work best early in the morning or late at night?”
- “Thoughts on afternoon naps?”
4. Have a checklist
I end each interview with a chat about things which are relevant to the job and may not have been touched on in the initial conversation — for example; any special needs or requirements, design tools that the team is using at the moment, salary expectations, etc.
At time when you’ve had a really good chat, it’s easy to forget to talk about these. So, I keep a list of these handy to make sure I cover the important stuff.
5. Test
If I have a good feeling about the candidate, the next step is a short design exercise followed by a design review with the entire team. My standard exercise is:
“Redesign the ‘Phone’ app.”
The requirements are:
- Don’t put in more than a day’s worth of effort into this
- Making it “pixel perfect” won’t get you extra points
- Whenever you’re ready, you’ll present it to the entire team for a design review (max of 20mins).
I always hope I get asked for more constraints.
6. Follow up
Always follow up, even if you’re not hiring the candidate. It is common courtesy — that is all. I’ve had a number of candidates come back after the interview, asking for general feedback, advice or just to talk more about design — I love these chats.
7. Offer
If you’re interviewing for your team, you should be the one to send the offer letter. Write the letter yourself, make it personal and show your enthusiasm. There’s no excuse not to write a personal offer letter — trust me, you don’t end up writing a lot of these.