3 ms·

Well the .2 "Ask the interviewee for a git repository" can be a private repository. It is a very hard problem to solve if they have no visible code to show but

Well the .2 "Ask the interviewee for a git repository" can be a private repository. It is a very hard problem to solve if they have no visible code to show but it does happen in other areas. Imagine asking for a management candidate for the private e-mails he shared in certain tricky situations of previous jobs. Or even public e-mails. Or even to take 40 minutes to write in a whiteboard a team statement for a certain conflict scenario. Trust is entailed when recruiting in most areas. But in programming not as much.

jonathankoren 9y ago
> Well the .2 "Ask the interviewee for a git repository" can be a private repository. If someone shares a private git repo, they should not be hired, and in fact should be fired from their current job, and possibly sued. (Think Anthony Levandowski sharing Google lidar designs as an example of his work with Uber.) This isn't promoting trust. This is a violation of trust.
- HugoDaniel 9y ago
  Yes I agree with you but I was not making the point of sharing a repository you shouldn't share to a recruiter (I do own a few private repositories that I wouldn't mind sharing to recruiters). My point was that seeing code is not as mandatory for a recruitment as we currently make it so. I gave the comparison to management but it happens even in engineering areas. It is worth to know your candidate before asking to write a solution to an air conditioning problem in a whiteboard in 40 minutes when applying to a mechanical engineering position. Specially if your company never solves air conditioning problems.