4 ms·
>Surely this will filter out ~50% of people who are good but don’t have any public code? It then becomes a take home assignment where you get to pick the topic
by moonchrome 5y ago
>Surely this will filter out ~50% of people who are good but don’t have any public code?
It then becomes a take home assignment where you get to pick the topic.
Surely you wanted to protoype some tech but didn't have the opportunity at dayjob - so make that prototype and bring it to review.
Much higher interview value than take home assignment IMO, but you need to be competent as an interviewer to enter into a discussion on something you might not understand yourself.
And it's also higher value to the person applying because they get to protoype stuff they find interesting.
- EugeneOZ 5y agoWork created in 1-2 hours is very different from a work created in 1-2 months.
- brongondwana 5y agoYeah, but at this point you're not left with many other options other than sticking your finger in the air and hoping you can detect if they know how to write code.
- EugeneOZ 5y agoOnly if you are limiting yourself by the options mentioned by the top comment author :) I was interviewed many times without showing any of my code. The most effective way I saw: the interviewer gives you some code and asks you how you could refactor it, what parts you would implement differently.
- brongondwana 5y agoTo be fair, my "interview" for Fastmail was debugging a real production issue in realtime with one of the founders.
- moonchrome 5y agoI don't see myself reviewing your 2 months of work at an interview. Showing me a prototype of something you thought was interesting and walking me through, pitching the tech and debating pros and cons would be enough for me to estimate what it would be like to work with you and my estimate of your experience level.