3 ms·

I often ask for them to version control and send me a zip of the git repo, so I can look at commit histories. Yes, they can fake that, sure, but I can normally

I often ask for them to version control and send me a zip of the git repo, so I can look at commit histories. Yes, they can fake that, sure, but I can normally tell a lot about a dev from that, and actually if I see 4-5 commits over an hour perhaps with some wrong turns, that pushes the candidate up in my estimation than somebody with 1-2 commits that don't tell a story, but does show a complete solution - which is most likely what would happen if you edited history a bit.

kaashif 3y ago
When I'm actually writing code and hashing out a solution over the course of a single hour in my job, I'm not going to commit the wrong turns. What you're really asking for is a candidate to spend extra time inventing a convincing git history. I really think the only way this actually works is if the problem is on a page which you can only view after you start a timer or something. Or do it on site and watch them. This is all high pressure but if you really want to time box, there can't be a way around it.