Ask HN: Culture dilemma, customers r parents, should my team be all parents too?

Besides possible legal issues (depending on your location, there may be a problem of discrimination) I think it' not a best idea.The culture fit you have described is just one aspect of competencies you need (attitude, values etc.) which isn't neither the only nor the most critical requirement to get the job done right. And btw you can find non-parents who will have enough empathy and adequate mindset to fit to your culture and vision. Just look at other industries - Medical companies do not select the candidates by their diseases ;)

I'll take the opposite tack. If you're just starting out or hiring your core team, having people who empathize with your vision is much more valuable.<p>This is the stage where if you're following "lean" principles, you're listening to customers. Strictly from a cost perspective, having customers in the house (as part of your team) is cheaper and you can iterate faster.<p>Constituting your team this way will lead to a much bigger interest in dogfooding your app once you've built a prototype. And your team will deeply and personally care about the product it is building.<p>But what I'll point out is that your culture will grow organically based on your team - you can't impose a culture, even if it's something as benign as "family first" - in a company of your size, anything imposed is a (forced) process and not a culture.

Make your product people parents. For engineers (backend and such), it will matter less.