[andrewstuart]

>> Well, it does. It says he doesn't have a portfolio for some reason.

No, you do not have to have a "reason" for not having a public portfolio. Not having a public portfolio doesn't say anything at all about someone's competence.

>> if the candidate makes it difficult for recruiters and interviewers to get an objective way to corroborate his claims regarding his level of expertise

Public code is not the only way to assess skills, indeed as I mentioned elsewhere in this thread its actually a pretty bad way to assess skills. If the best tools you have for assessing competence is github then your recruiting process is lacking.

>> It would be better to cut him out of the shortlist for further interviews.

I can imagine employers with this attitude lamenting how hard it is to find good people.