Nick Finck Profile picture
Nov 6, 2018 12 tweets 2 min read
Design hiring managers: Should you consider doing design challenges as part of your interview process it’s important to know how to properly execute them. Here are some tips to conducting effective design challenges:
1) Design challenges should not be be take-home work (paid or not!). A design challenge should occur during the on-site interview with the candidates in person (remote design challenges are not effective).
2) Design challenges should NEVER involve your company’s product, a problem the design team is currently dealing with, or anything even remotely in the realm the company does business. A design challenge should ALWAYS be on a generic/universal design problem.
3) Design challenges should always have a detailed rubric based on criteria for the role. You need to be able to objectively measure the results in a non-biased way that will be consistent criteria for all candidates.
4) Design challenges should be aimed to get signal on the candidate’s ability to do the job. They should never be given to candidates for roles that are not going to be executing design directly. Don’t waste the candidate’s time getting signal for something they won’t be doing.
5) Results from design challenges are not the only signal you should be collecting from a candidate in an on-site interview. The on-site should also include other separate sessions like 1:1 interviews, etc. that also collect signal.
6) Design challenges are not speed tests for performance, you won’t be able to effectively get signal on that until you hire the candidate. Expect candidates to not always end up with a fully complete and rigorously executed design. Don’t dock points based on design completion.
7) Design challenges are more about how someone works (granted, under stress) and how someone thinks when they are working. Design challenges are not about how perfectly square their boxes are on the whiteboard. You likely won’t be able to get to high fidelity designs.
8) Design challenges should not be impossible tasks. There should be several possible ways the candidates could tackle the problem. Just because the candidate didn’t approach the design challenge the way you think they should have doesn’t mean it’s wrong! Be open-minded.
9) Be considerate of candidates that may have special needs or health conditions that may prohibit them from participating. Don’t discount their ability to do the job based on their ability to do a design challenge. Find other ways to get signal on their ability to do the work.
10) Design challenges should be an activity not an interrogation. Interviewers should be able to answer questions and not penalize candidates for asking several questions when needed. Remember it’s also about signal on how they think when they design.
There are likely more tips I could add but didn’t include here. I choose to focus on the most common issues and misunderstandings that I’m seeing for design challenges. I hope you found them helpful.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Nick Finck

Nick Finck Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @nickf

Nov 23, 2019
People always get this quote wrong. The original quote from Louis Henry Sullivan goes, “Form ever follows function.” ...as in the two are inseparable (and unchanging) but the priority should always be the function (or purpose). Now chew on this for a second.
I believe we can learn something from architects if we take a moment and stop trying to simplify their message into something that serves our own purpose. Why the rush? I think design as a whole needs to take pause and look for a deeper understanding before charging ahead.
I’ve seen countless projects nearly go into full swing over a simple misunderstanding of a problem. Nothing a 15 minute meeting couldn’t solve if we all just slow the hell down. Stop trying to simplify the problem and rather really take the time to understand the problem.
Read 5 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(