| Well, there's a couple of reasons for it. The main reason is that there is this idea of equal pay for equal work which only works if your work is producing widgets per hour. That's fine on a manufacturing line, an hourly job, or a job where the variance in performance of a job isn't measurably valuable to a business. I've got a lot of experience as a programmer/devops guy, but if somebody hired me to setup Wordpress with a template for them I'm not really adding much more value than anybody else who could do the job. From the business perspective, they just want the site to be setup and look nice. If a company is looking to hire a developer who can both develop the application, help manage the infrastructure and identify programming decisions that are going to cause a negative impact down the line...I'm going to add a lot more value for that business. But...if my salary at that business was public and you could clearly see on paper that I made more money that another programmer on the team who really felt like he was contributing just as much it's going to cause resentment. The only way to clear up that resentment is for somebody to sit down with said guy and say, "Look, this guy does X, Y and Z and has experience and a track record of identifying problems and preventing us from making expensive mistakes. His salary is based on the value proposition. You are focussed on an area of programming for the app and you do a great job with it." There's no way to explain it without causing resentment, having another person constantly having to justify themselves, or backhandedly belittling the contributions of another person. This is essentially why people don't talk about it. Because nobody thinks their work isn't as valuable or their contributions are as valuable as the most valuable people at the company...and they have no way of understanding that without actually doing those people's jobs. There's not a PC way to say "there's no such thing as equal work" unless your job is so specific, so thoroughly defined and so repetitive that anybody can be plugged in to perform the tasks...and at that point your job doesn't have much value anyway. |
I'll give you an example. When we learnt a girl from finance owned her own horse, the gossip around the office was not how did she skrimp and save, but what she needed to do to whom to receive such an obviously large salary. I have no doubt she did just save her money well but thanks to keeping everyone's salary secret, we have vicious rumours instead of fact.
If you are really hiring people who honestly believe that everyone apart from them contribute little to the company, then you are hiring incredibly arrogant people. If you are really hiring people who honestly would be surprised that some people earn more than others, then you are hiring incredibly naive people.
fwiw, I earn £27,000 as a C#/Java developer in central London and I know I am extremely poor at salary negotiation so I expect I am grossly underpaid. This causes me resentment. Salary negotiations involve me having to justify myself or backhandedly belittling the contributions of my colleagues. ie. exactly the sorts of problems you believe that keeping salaries secret solves.
There is only one reason for keeping salaries secret, and that is to keep wages down. That benefits employers, and it benefits those who are great at negotiating.