> 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.
Yes, GMail is absolutely terrible on that regard. I've been missing out on project mails from an UN organisation I have been working and exchanging emails with because of their aggressive and useless filters.
For me privately, switching to a better provider solved that.
But having >25% GMail customers and always landing in Spam is horrible. Pretty much any other provider likes our mail server, but GMail always says spam.
Then you're going double opt-ins but customers still mark mails as spam because unsubscribing is too hard. Thanks for nothing.
There is actually an industry in gaming GMails spam filter to somehow get into the inbox: some offer automated replies and unmarking spam, some manually run hundreds of mailboxes and don't do anything else all day than unmarking mails as spam.
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.