[fifilura]

Does that mean you will not hire anyone without a public portfolio?

[Pooge]

I thought that meant what you typically write in the "Experience" section. GP, am I wrong?

Is everyone writing a "Projects" section by rewording what they wrote in "Experience"?! For me, "Projects" should strictly be personal projects. If not, maybe that's what I'm missing.

[sshine]

Projects are personal projects, or at least projects in which you did a distinguishable effort.

They don't have to be public to the whole world, you can have links that are only in your resume.

But if they're on GitHub, they have to be public, since there aren't unlisted repositories.

[mdaniel]

I actually believe that it would be possible to provide a read only clone url in a resume link but I don't know if a way to make a link to a browsable version (short of having a proxy server type setup, or, of course, a slim server protected by http basic)

[Dwedit]

Github does allow private repositories.

[sshine]

Yes, but you'd have to invite each interviewer by their GitHub handle.

An unlisted repository would be one that is public to those who know the URL.

[MacsHeadroom]

I'm saying the sections of the resume don't matter at all. The resume is basically ignored. You either have public code you can point to on Github or you aren't ever hearing from us.

[joshdavham]

I’m curious to hear a bit more about your rationale for this. Is it because trust is otherwise hard to establish between you and the candidate? Is it like “if we can’t see the candidate’s code then we have no evidence they can code”?

[MacsHeadroom]

Essentially, yes. Public portfolios come in different flavors though. Most often it's code. But sometimes it's research, a blog, transcripts of talks ripped from YouTube.