News for hackers. Stuff that matters.

A comment on Things I Learned from a Job Hunt for a Senior Engineering Role. Parent comment

Re:Things I Learned from a Job Hunt for a Senior Engineering... by minimaxir on Tuesday April 24, 2018 @12:51PM (#16914301)
> but if I have an entire github of highly starred and heavily developed projects with reasonable commit histories... don't make me do your do damned homework or implement a toy BST.

Unfortunately, the current common argument from the hiring side is that GitHub profiles are not sufficient proof of skill since code can be copied (not fair) and GitHub projects bias toward people with extra free time (reasonable, but not enough to discount GitHubs completely IMO)

[ Parent | on HN ]
Re:Things I Learned from a Job Hunt for a Senior Engineering... by ryanianian on Tuesday April 24, 2018 @02:09PM (#16915056)
Right. Don't "require" a GH, but use it if it's there!

Yes, some of the code may not be original, but unless the repo is a fork you can pretty easily see if the code is organized in a coherent way that shows the committer knew how to decompose a problem well. If they solved /every/ piece of the problem themselves, it may be a sign of a different problem (and also copy/pasting without citing source is also telling!)

[ Parent | on HN ]