4 ms·

I really see both sides of this. It’s hard to get around the fact that OSS and GH activity really, truly, is a good hiring signal. It’s certainly one of many, a

I really see both sides of this. It’s hard to get around the fact that OSS and GH activity really, truly, is a good hiring signal. It’s certainly one of many, and it’s not (nor should it be) the be-all, end-all hiring signal. There are wizardly devs who stick to a strict 40 hour week. There are equally astounding devs who live, breath, and dream code all day every day. We’d all be lucky to work with both. I don’t see a way around the fact that a public resume is just an enormously strong and quantifiable signal for hiring managers.

ghaff 7y ago
On the one hand, it's hard to deny that a requirement (or strong preference) like this will often discriminate against some fairly large groups. And it feels cringe-y for that reason. But it's also hard to deny the value of a portfolio that's directly relevant to the job being hired for. And, if I'm being honest... I do a lot of writing as part of my job. If I'm hiring someone for a role like mine, you can be sure that I want to see some writing that they've done. If they don't have anything they can share? (Which seems a little off. But maybe it was all internal company communication stuff.) Well, they're going to have to write something because I'm not going to just take them at their word that they write well.
- ryandrake 7y ago
  Also keep in mind that while X could be a good hiring signal, that doesn’t mean that “lack of X” is necessarily a bad hiring signal. I’d be ok with using public projects / GitHub as a boost to get someone into the hiring funnel, but I’d never use “no GitHub profile” as a reason to filter a candidate out.