3 ms·

Not a recruiter, but I imagine there are at least 3 reasons for your repo to be ignored or deprioritized in favor of typical interview: - not everyone contribut

Not a recruiter, but I imagine there are at least 3 reasons for your repo to be ignored or deprioritized in favor of typical interview: - not everyone contributes to OSS - it’s easy to fake - it’s hard to assess within a short period of time This it seems to be hard to standardize and streamline candidates validation based on their oss repos. Also, afaik the goal of interview is to assess candidates thinking patterns, it’s hard to do quickly based on an arbitrary piece of code.

codr7 3y ago
Sure, it would take some more effort to dig into than checking boxes. But it would also provide more valuable feedback.
- tdudzik 3y ago
  How would you compare candidates that have some code in GitHub and those that don't ?
  - cinntaile 3y ago
    You can assess the ones that don't have code on GitHub in a different way, but there is no reason to ignore a possibly valuable datapoint.
    - tdudzik 3y ago
      But faang companies try to objectively compare all candidates. Also they have so many resumes that it doesn't seem feasible to review code on GitHub.
      - codr7 3y ago
        5 hours x 1/2 people checking boxes is energy that could be put to better use.