Ask HN: What do you look for in an applicant's GitHub?
I'm a self-taught JavaScript guy / solo-preneur & have been thinking of seeking part-time / contract work.
Skill-wise I consider myself (FWIW) between 'mid-level' & 'experienced', but having never worked professionally as a dev, I'm uncertain about hiring expectations, particularly wrt code samples. Most of my code is closed source, so I'm looking to build-out my public stuff.
When you review an applicant's publicly available code, what's important for you to see? My assumption is that reviewing a repo is akin to reviewing a portfolio / resume (i.e., very quick), so how have applicants "wow'd" you in the past? (I mean short of obvious rockstar qualifications, like 'React core developer,' etc.)
Skill-wise I consider myself (FWIW) between 'mid-level' & 'experienced', but having never worked professionally as a dev, I'm uncertain about hiring expectations, particularly wrt code samples. Most of my code is closed source, so I'm looking to build-out my public stuff.
When you review an applicant's publicly available code, what's important for you to see? My assumption is that reviewing a repo is akin to reviewing a portfolio / resume (i.e., very quick), so how have applicants "wow'd" you in the past? (I mean short of obvious rockstar qualifications, like 'React core developer,' etc.)