Your company might be benevolent, but it doubt most are, and when companies use information asymmetry to pay less, it hurts the very people they will turn around and pretend to care about, culture, "we're a family!", all the corporate platitudes we all know.
> At the end of the day, I really believe that the only person someone should compete against is himself.
This just isn't true. Should, in an ideal fantasy world, maybe. In the real, "I need to make money to eat and pay rent" world, you're competing with every other person applying for the same role. If you don't get a job, it's your life on the line. If a company misses out on a good applicant, well better luck next time, nothing really changes.
Bottom line, keeping pay bands secret/undisclosed only hurts individuals, and helps companies. Given the inherent power differential between the two, there's no good reason to tilt things even more in favor of employers.
This is repeated all over the thread, but makes little sense. You don't need to know this to come to agreement. All you need to know is what you want/expect to be paid, and the lowest number you're willing to accept. The company, in turn, doesn't know this information, and wants to discover it. You're equally matched. You both have exactly 50% of the information required to come to agreement.
Moreover, the company has invested a great deal of time and money to get you to the point in the negotiation where it actually matters what you're willing to accept. You have power!
The one thing that this does is (maybe) savesyou the effort of interviewing when your salary expectations are wildly out of line with the employer's willingness to pay. But that rarely happens, in practice. When it does happen, it's at senior levels, where your value to the company is disproportionately large. If you're at that level, you can usually tell going into the interview if the company has properly identified the value you believe you bring.
Stupid example: if you have 20 years of experience as a software engineering lead, manager, senior engineer, and so on, and you're interviewing for "Javascript Developer 1", then maybe you should be worried about pre-filtering on salary expectations.
Second, the big companies will (sometimes) pay for salary data, but this information falls in the "what the company is willing to pay" bucket. Again, that's 50% of the information to make a deal, and you don't need to know it. From your perspective, it doesn't matter if they got their salary band by consulting a survey or a magic 8 ball. Maybe it affects the level of faux outrage they show when you ask for more, but then you're just back to negotiation.
Said differently, if you know you're worth $X, and the company believes that the statistical average human cog in Barnsville, Nebrahoma is worth $Y, what do you care why they believe that? Your job is to find the highest number between $X and $Y that they will accept, based on your unique value. Their job is to convince you to join, and maybe get that number closer to $Y. Their justification for $Y is not your concern.
As an applicant, I understand that whatever you put at the low end is what you are going to want to offer me assuming I just minimally pass your bar. To get the higher end requires negotiation. However, if you are willing to pay my x+5, why bother with the games at all? Just make your best offer and let's get things off on the right foot. Why do we need to feel like we each "got the better out of each other?" It also levels the playing field for people that just aren't good at negotiating.
I'm an engineer, not a sales negotiator. What does my ability to argue for a higher salary have to do with my ability to build product. Probably nothing. And if you think this is some coded way of measuring ability to convince people in a discussion, maybe you should explicitly be asking that during your interview process instead.
Because both of you are parties in a deal and have your own best interests in mind
This is the heart of the matter. It's pretty well-studied that some less-represented groups are systematically underpaid for similar work than more-represented groups of employees. Empirically, that "worth" calculation is not objective.
> I then work out a range I'm comfortable offering
Employers frequently pretend they do not have a range in mind by saying comp is "DOE." But it usually isn't solely DOE, it's f(abstract role, person in role). So a entry-level data entry role isn't going to be worth $800k annually no matter how much experience. The employer has a range in mind before they see a single resume. I don't see the issue with publishing that range as part of the job description.
I actually think there will be a follow-on benefit to companies in reduced turnover (the hires that jump too soon because the job doesn't really pay enough but the candidate was too invested in the process to back out by the time comp was discussed) and reduced load on recruiters (by having people self-select out before the interview process). Every company aims to do these things when marketing offerings to its customers, I fail to see how it would be a bad thing to do when marketing to potential employees.
Can you imagine why many others cannot or do not want to negotiate like this?
Assuming that "screw over" includes staying within the bounds of the law, isn't this approximately correct? Companies try to maximize profits and not get in any legal trouble.
Having said all that, business does boil down to a lot more than just profits. Those are important but so is the livelihood of the employees, along with their expertise and tribal knowledge. I know those feed into profits, but I'm thinking beyond that. It's my job to ensure that my employees are able to take home the pay they've earned. Often, I have to put on more of a social worker hat and help out some of my employees with personal issues. That may be loaning a car at no charge, or giving a low interest loan to buy a house. In the past, I've paid for weddings and funerals. All of that goes with the job of being an employer. That doesn't mean every employer has to do those things. I'm fortunate to be in a position where I can help out in those ways, so I take advantage.
I think this highlights the point I'm trying to make: too many people focus on businesses trying to maximize profits and they push to enforce rules to help out the little guy. If businesses do that, then that's too bad. If you work for one of those businesses, then talk to your manager about it and if necessary, find a company that shares your outlook. Not all businesses are like that though - in fact, a lot of them aren't. Most businesses really do try to be fair and understand there's competition out there that may be trying to lure in some of your star employees.
In terms of what a person can do vs how they happened to interview - that's a fun challenge. I tend to be extremely honest with a candidate, letting him know exactly who we are, what we do, and what types of challenges to expect. As I'm talking through that, I can usually tell if they have that engineering spark. If I really have a tough time trying to decide if they know their stuff, I'll draw a problem on the board and see if they can solve it - usually a problem we've recently solved ourselves. I also call references, which sort of helps. Hiring is a gamble and fortunately in my case, it tends to work out. It's rare, but every so often I misread someone and find out after they start that they aren't as far along as I thought. When that happens, I provide them with a mentor or offer to be one myself - or I relearn their skillset and then write proposals that highlight their abilities. In the extremely rare cases an employee can't/won't grow, I'll have an honest and polite conversation with them and then part ways.
When an employee starts here, they join a "work family." We look out for one another and push each other to learn. I tend to focus on my employees interests and skillset, then design customer solutions around those. That has worked really well for decades now and customers keep coming back!
-> capitalist that wants to underpay people and justifies it through a lengthy verbose convoluted articulation
"It is difficult to get a man to understand something when his salary depends upon his not understanding it."
-Upton Sinclair
I then fully expect that person to counter, because I feel that it's on them to do the market research to determine how much they're worth. That's what I've done through my career and I've been happy with the result.
I see applying/hiring as a game where the company is trying to find a way to afford as much talent as possible AND ensuring they can continue to pay that rate when times get tough and projects are cancelled/postponed. I also factor in annual bonuses for other employees, R&D budgets, etc. At the same time, applicants should be prepared knowing what they're worth. That takes some research, but it's not overly difficult. As they determine what they're worth, they also gain an understanding of a skillset they can work toward to reach the next rung of the ladder.
At the end of the day, I really believe that the only person someone should compete against is himself. If comparing rates is THE issue, then I think the focus is misaligned. If rates are a concern, then start a dialog with your manager. Most managers are willing to go to bat to help out an employee if they really feel they deserve a higher wage. Just be prepared to make your case if you do that, explain WHY you deserve a higher rate - and it should be more than "well so and so is paid more than me." If in the end you're still unhappy with your rate/benefits, then consider a move, but be prepared to grow in your skillset if that's what's needed to reach your financial goals.
Handle it professionally and communicate... Those are my thoughts.