For developers, we extract some production application code, remove some features, and give people relatively open ended "implement a feature to solve X problem" instructions. The criteria for those range from "idiomatic code" to "good enough to ship right now" to "good UX", depending on what specific type of dev we're after.
For support, we pull actual tickets and ask for responses + documentation. Criteria for those are things like "technically accurate" and "doesn't overpromise".
Others could be writing samples (we have a new feature, write a how-to) or even a marketing plan.
After the sample project, we do a "work day" in place of a series of interviews. These are typically continuations of what the sample project was, and involve a whole day on Slack / video / whatever with people they'd be working with.
This one's current, I don't know why but I'm vaguely weirded out about posting it here. It's already public on GH though so I guess I'll power through. :)
For developers, we extract some production application code, remove some features, and give people relatively open ended "implement a feature to solve X problem" instructions. The criteria for those range from "idiomatic code" to "good enough to ship right now" to "good UX", depending on what specific type of dev we're after.
For support, we pull actual tickets and ask for responses + documentation. Criteria for those are things like "technically accurate" and "doesn't overpromise".
Others could be writing samples (we have a new feature, write a how-to) or even a marketing plan.
After the sample project, we do a "work day" in place of a series of interviews. These are typically continuations of what the sample project was, and involve a whole day on Slack / video / whatever with people they'd be working with.