I'm sure I'd feel pretty bad too if I was in her place. I hope she can get through it and learn and grow from the experience.
I'm sure I'd feel pretty bad too if I was in her place. I hope she can get through it and learn and grow from the experience.
http://www.indeed.com/salary?q1=User+experience+designer&l1=...
Having recently hired both designers and engineers, I can say with confidence that the pay differential is a hell of a lot more than 7%. Double is absolutely plausible.
"You see, it's not that women get paid less than men... it's that women are designers, and men are programmers, and programmers make more than designers!"
It does sound as bad. The lack of appreciation for 'non-technical' employees labor is pretty sad. I am highly technical, and the designers on my team are the most valuable ones in my eyes... they can do something I can't.
All roles help build the company.
The issue really needs to be addressed earlier - at the high school, and college level, when girls start to drop out of technical course work.
We, socially, consider 'women's work' to be less valuable then men. Hence, positions that have a gendered connotation have a difference in salary.
Your (1) should mean that their salary is way _higher_ than programmers. Supply and demand, no? I also don't know if what you say is true.
I definitely agree with this when we're talking about teachers, nurses, librarians, etc. but I don't think web/product/UX designer is a particularly gendered role. It just looks that way because there are so few working women programmers (in comparison to their solid majority of the population) and the sex ratio for designers is more even.
We consider designers to be less valuable than programmers because there are 5 times as many of them than there are programmers.
Of course designers do something that you can't, and if programmers were common, the designers would be calling the shots. Architects do something you can't, too, and they make a lot less than you do - because there's more of them than we need.
What I meant was there are fewer designers on staff because there's a need for them, but a much lower need for designer man-hours than coder man-hours.
Your average web/software startup can be served by one or two designers while the coding team scales up to 10+ times that number. Maybe that's different in video games or other design-heavy areas but consumer and business products don't seem to have as much demand for designers.
Designers work tends to be in much more of a winner-take-all star system, where a celebrity with a track record like Johnny Ives, Karim Rashid, or Phillipe Starck can make millions, while your 'average' designer makes very little. In contrast, it's probably a flatter distribution for software engineers.
This is true, but rightly or wrongly roles are compensated very differently. A successful tech company probably needs programmers, designers, testers, customer support, managers, ops, etc. It would be an odd company (though not necessarily a bad one) that paid all those employees the same. Remember that the wage paid to a person is somewhere between 'what I must pay to hire a decent candidate' and 'how much value they actually add', and usually skews towards the former.