Hacker News new | ask | show | jobs
by onetimeusename 4357 days ago
I object to the part about gender coding the language. I think people should be able to speak and write the way it comes naturally to them. It gets to a point where being friendly to women is so strenuous that it becomes hostile to men. Apart from that, the "better" descriptions were vague and unclear as to what the focus was. "understanding the engineer sector intimately" sounds like it is actually NOT an engineering position.
3 comments

I'm a man, I support having more women in tech (thought I don't agree it is the companies responsibilities for this) but I can honestly say, her rewritten job descriptions would make me NOT want to apply (maybe that is the goal?).

1) 'We are a dominant engineering firm that boasts many leading clients'

2) 'We are a community of engineers who have effective relationships with many satisfied clients'

First one makes me think of a solid company with many clients, second one just makes me think they are a hippie community living in the woods foraging for food and no showering while coding.

The problem is that social activists have discovered computing. Now they are trying to force their world view into the tech domain because they have failed to impart change in the real world.

Hence the faux moral outrage over gendered words.

Hence the hounding of Brendan Eich for his personal views which had no bearing on his technical competency.

Hence the Gnome foundation running out of money because they diverted all their funds to a women's outreach program instead of focusing on software development.

Right now, in the real world, scantily-clad women in bikins are draped across magazine covers, sporting events segregate the sexes, and in many Islamic countries women are treated like slaves... yet somehow “The tech industry may have a problem with women"?

The process has to start somewhere. People in tech like to call themselves egalitarian and progressive, so they should be open to encouraging more people from different backgrounds to enter the pipeline.
i replied to a few threads about this re: "re-evaluate your job post descriptions" - i did not draft those descriptions, they are linked to the actual original content by ERE. everything on the site is not original content. i find the descriptions could use some work, but do a decent job of illustrating the point that language matters, especially when the goal is simply to expand the pool of people that respond positively to your post.
I'm not trolling and I actually hoping for a positive discussion, but when you put those excerpts on a site you made (even if taken from ERE) promoting more women in tech and editorialise them (the ERE sites mentions Masculine and Feminine descriptions, you wrote Average and Better), it does make people feel queasy (affirmative action queasy). If you state the feminine descriptions are 'better', you will be alienating the men, which in many cases are the decision makers on hiring.

If I was in part of the hiring process, and someone told me I had to write in a job description 'We are committed to understanding the engineer sector intimately.' to attract more women, I think I would be biased against women in my process, both consciously (I don't want 'intimacy' of any kind at a place of business) and probably unconsciously as well.

nobody is telling you you "have" to write things that alienate men, and i guarantee that some of the overly "masculine/average" descriptions repel many men from these positions as well. if you feel you would be biased against women in your hiring process, you should probably remove yourself from said hiring process. if you don't like the ERE descriptions, that's cool, simply write better ones (i don't think ERE is the authority here) - the aim is to be more conscious of the difference language makes.
>"understanding the engineer sector intimately" sounds like it is actually NOT an engineering position.

This particular language was for describing the company as a whole, rather than a position.

To me, this phrasing sounds like the firm differentiates itself based on having a better understanding of its customers, which is a useful thing for consultancies.

You are right, I read it and went back and took a quote from the wrong place after getting a bad impression from the entire section. Consider this though,

Proficient oral and written communications skills. Collaborates well in a team environment. Sensitive to clients’ needs, can develop warm client relationships

Does that sound like a qualification for an engineer? I suppose it could but I am used to engineering qualifications being specifically about engineering, if I had to guess, I would assume this was a sales job or sales oriented and would not apply.

I still hold that I shouldn't have to filter all the language I use to be nontoxic to women. I am not a woman, so I cannot judge what is toxic to them and would prefer to function as normal.

> It gets to a point where being friendly to women is so strenuous that it becomes hostile to men.

This is a good point. If you get to the point where people are scared of expressing their thoughts for fear of offending someone who took them the wrong way, you have a serious problem. Most people are not going to put in the effort; they're just going to keep their mouths closed and dodge the confrontation entirely. This leads to bad ideas winning.

Sure, it's one thing about posting a job description. But if you're going to apply that mindset to your job description, you're probably going to apply it to everything from water cooler conversation to official meetings to emails.

And yes, it's important that people are respectful and make your environment a great place to work. But it's a really bad idea to go over the top in welcoming 10% of your workforce and alienating the other 90%.