Re:When hiring developers, have the candidate read existing ...
by michaelrhansen on Friday April 15, 2022 @09:24PM
(#31048177)
This is my standard practice - I give a real world data fix script that has been simplified to understand and comment on in 20 minutes. The interviewee is the code reviewer before it gets run in production. It covers things like performance, security, typical syntax mistakes, and working with sensitive data. The best part is actually not the script, but the stories it triggers about past challenges.
[ Parent
| on HN ]
Re:When hiring developers, have the candidate read existing ...
by lytefm on Saturday April 16, 2022 @04:00AM
(#31050542)
> The interviewee is the code reviewer before it gets run in production.
Yeah I've also been using this approach for Fullstack Devd: A small page with a bit of CRUD + a small ticket description of what the page is supposed to do.
The code contains various bugs or questionable implementations, the interviewee is supposed to analyze the code and to either fix the issues right away or to write comments.
Nobody is expected to get everything right within the time slot, but I've found it to be a great test on how a candidate might perform in their day to day work.
Re:When hiring developers, have the candidate read existing ...
by zeroonetwothree on Saturday April 16, 2022 @11:36AM
(#31053129)
I think itβs fine to have this as part of your interview but I would be worried to have it as the only thing.