Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Your stance falls into the classic case of "understandable, but unacceptable".

What you are describing here is a situation that implicitly guarantees prejudice. You are looking for a near-guarantee that "it's going to work" - which is to say, you're going to implicitly exclude people who are unfamiliar to you.

This can play out in any direction - race, culture, religion, orientation, lifestyle.

To be blunt, it all comes to this: as a society we value inclusiveness and equality more than your right to a bit more peace of mind.

I don't doubt that you approach this with the best of intentions, Mr. Robinson, but FWIW I would never work for you so long as you demand the private details of your employees' lives.



Too many people have put too much stock in the fact Facebook was mentioned.

Let me rephrase it: I want to see HN, github, blogs, twitter feeds where they talk about tech and work and so on.

I'm not going to demand access to Facebook. I'm going to look at their public profile. If they add me on Google+ I'd expect to be in a circle for bosses/peers, and to see stuff that's pertinent, not pictures of their goldfish or what they had for dinner last night.

Is that still open to prejudice? Sure. Am I going to exclude people who are competent but I might not get on with? Possibly. But isn't that actually a good idea? Would it not be crueller for me to hire a waterfall tech who hates agile and who really wants to work in Enterprise IT rather than startup development, and for both us to be really miserable than for me to just realise early on that despite his CV scoring high on the startup development bullshit-bingo cards, they are simply not going to be a great fit?

I have never - and will never - hire/fire or select interview candidates based on religion, creed, gender or even necessarily experience. It's about ability, mindset and evidence of performance. Every time.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: