I like your process, most of the time getting to know a designer isn't just about reading their résumé and looking at their portfolio. The thought process behind the design is super important as well.
Thanks for sharing, it was super insightful.
While some are good, most of the 17 exercises are too complex to solve under 60 minutes. Even the exercises that are easier than these would take about 15+ minutes just to understand and frame the problem. The better ones are the ones that are general and don't requires any domain knowledge such as your NYC Metrocard and Garbage exercises. Not everyone knows a lot about obesity or e-ink or audiobooks. And GoPro and Google Funnels? Unless they have worked on very similar products. It's one thing if you want to challenge the designers to solve problems in an unknown domain, but 60 minutes won't take you anywhere.
Also, all technologies must be viable for use today, isn't really a thoughtful constraint. More like the NYC Metro machine doesn't accept coins.
I agree, there are some exercises that might be more challenging for the 60-minutes framework. We preferred to share as many as possible so everyone can adjust it for her needs.
Broad exercises are used more indeed and they are working well for us so far :) However, I believe there is value in challenging designers with problems they are not necessarily having a domain knowledge in
Is the test run remotely? Are they getting paid for committing to a 90 min interview? I would expect that since these guys are investing so much of their time without even knowing if it's a good company to work for. And if they are supposed to come to your office, then it's even more than 90 minutes. During the course of the 90 minutes, I would also expect the manager who is interviewing to undergo some sort of testing, so that the candidate could see if he's dealing with a good functional team or not.
Those exersices are performed on-site and not remotely.
At this point candidates already know about the company and the specific department they are interviewed to.
They also meet their potential team mates before this exercise is performed, so they have context in order to decide if they are interested in being part of the team.
Wonderful, just what the design world needs more garbage solutions from the dev world just as people who hire devs are waking up to how awful whiteboarding is we get loudmouths from the design world championing it. Even with a sodding Traveling Salesman problem of all things...
Rather than angrily dismissing this, how about clarifying your comment by constructively suggesting a better alternative?
As a senior member of a product design team part of my job is to help evaluate new candidates and understand whether or not they will truly bring benefit to the team. I see plenty of polished CVs and portfolios that make candidates seem great on paper, but in real life they're often quite different.
One issue with relying solely on a traditional interview is that it's a weird environment to get to know someone. Clearly getting to know a person is a vital part of knowing if they're a good hire. Involving the candidate in more relaxed, informal discussions around a design problem can help everyone to relax and people's true personalities begin to shine through.
Also, I see plenty of candidates who talk well in an interview setting, but when presented with a design problem it becomes obvious that their interview comments are based on theory - not experience.
Surely it's much fairer to gain this deeper understanding of a candidate before offering them a position rather than hiring and only discovering the gaps in their knowledge when it's too late? In many product teams the designers are given huge amounts of responsibility and it seems only prudent to ensure that new hires are able to cope with that.