2 ms·
Throw out everything else you are doing in those 45 minutes and just look at their repo and make a decision based on that. You'll get better results. (Maybe s
by jimbokun 7y ago
Throw out everything else you are doing in those 45 minutes and just look at their repo and make a decision based on that. You'll get better results.
(Maybe spend a few minutes on the phone just to verify they are really the person who wrote all that code.)
- grogenaut 7y agoGuess you missed what I meant. The manager/recruiter covers that. If it's substantial then I would likely get called in to review it. The on site interviews are checking for things like communications, soft skill, design, etc. Things that don't fully come across in a code repo and are hard to verify who did what. We have tons of people who try and misrepresent themselves. It would be a waste of time for the 6 people on a loop to all read the repo. It would also be bad if we didn't cover the things we cover in the on-sites. We are also required to keep loops the same for all candidates. So giving an offer to one candidates because they have a GitHub repo and a phone call and the rest don't and therefore have to come in is a no-no. Therefore they all come in.