3 ms·
Imagine a junior developer asking your senior developer a question about how a relational database does something. There you go, now it's a work-sample for you
by chrisseaton 8y ago
Imagine a junior developer asking your senior developer a question about how a relational database does something.
There you go, now it's a work-sample for your senior developer.
- hinkley 8y agoI suspect a lot of my feeling of whether these people are good or crazy comes down to whether they can contextualize their questions. Most of the questions I get asked are for code I would veto in a PR because there are battle tested alternatives. I’ve been trying to do something about that when it’s my turn to ask interview questions. For instance, too many front end people struggle with basic data manipulation workflows. I want to virtue signal that it’s better to move this kind of logic to the backend, but I need to test them anyway. So I create a plausible scenario, maybe this is a POC to see if it’s worth sort or grouping functionality to the backend.
- tptacek 8y agoSure! It's an objective work-sample process if you can say these things about the challenge: * It's the same for all candidates. * It captures facets of the work as it is done on the actual job. * It's objectively evaluated (ideally, it has a rubric established a priori, such that results can be evaluated by someone other than the person who proctors the challenge). It's possible to devise work-sample challenges that assess communication skills. I have friends who've done it at their companies for customer service and sales roles. I'm saying, the process described in this blog post does not appear to be that.