4 ms·
That might be good. I had thought a bit less involved process where I just show one of our simpler scripts and ask the candidate to comment to me everything fro
by beefield 9y ago
That might be good. I had thought a bit less involved process where I just show one of our simpler scripts and ask the candidate to comment to me everything from the workflow/tools he would use to develop/maintain the script to how and why s/he would write the actual code differently.
And this in two cases, first the theoretical case with unlimited time to make things perfectly, and the real world case when there are about a thousand other thing that you should do...
But here come my limitations. I know a good candidate should talk about version control and some testing, but I have never made a git pull request and I don't know if I knew a unit test if it came and bite me. Someone might lecture me about using more object-oriented approach and others keep on talking about how cool functional paradigm is. I just don't know how to evaluate these answers...
- JSeymourATL 9y agoIt's perfectly acceptable to tell the candidate that you're not a subject matter expert in a given area. Ask them to explain how they go about their work in layman's terms. If they can do that without a bunch of mumbo-jumbo; you'll likely have an acceptable hire. Imagine you were hiring a Chef-- can you tell me how you prepare Boeuf Bourguignon?