Hacker News new | past | comments | ask | show | jobs | submit login

All five of them may feel cheated. The best compensated one may consider themselves as more than that much better than the other four.

But, abstractly, maybe four of them are getting cheated. Shouldn't they be told?




Why is it person A’s business what anyone else is paid? IMO, they’re only getting cheated if they’re being paid worse than as agreed.


I remember accidentally finding out a coworker (with about half my experience by the way) was being paid 50% more than me, and yea it totally felt like I was being cheated. Likely just because he was a smooth talker and not from any real technical talent. All hat and no cattle, as they say. Next review time I hinted that I thought there was a lot of upward room in the salary band for my experience level, but the conversation went nowhere so I quit and got a significant bump elsewhere.


This only works if both sides have access to all the info. The employer has all the info, but the employee had no info. They may agree to a lower wage because they think it is the best they can get. But with more info up front they may not have made that agreement.


What's the harm to person B of person A getting to know person B's salary?

In a more general sense, more information makes for better decisions.


What’s the harm to any person if private information of theirs is shared?

Person B should be (and is) free to tell person A their salary iff they want. If they don’t want to share that private information with A, no else should either.


You're thinking about an individual supply of information between two actors, not a sea-change by making it common knowledge among all market participants.


I wonder if you’re carefully thinking through the privacy concerns. Share anonymized (and non-de-anonymizable) information all you want. Don’t share private, individual information without that individual’s affirmative consent.

Same reason that it’s OK and informative to share how many people in your state have +COVID or +STD tests, but not how many in your household do.


I'm honestly not sure how I feel about the privacy concerns.

On the one hand I do very much support privacy in many areas. Facebook is a cancer that seeks to spy on me every second of the day and needs to be regulated for that reason. People need privacy for a lot of very important reasons.

On the other, I'm not sure how I feel about privacy in financial matters. Do people's salaries need to be secret? Yes, having other people's financial information is an advantage in negotiations, but wouldn't that even out if you both knew more about each other's finances? And make lots of other negotiations easier too.

Edit: I'm actually not sure it's a valid privacy state to conceal how many people have COVID in your household. It think that information being public has a lot of value and I don't know if I support privacy in that case. Where they were when the caught it is a dangerous thing to leak. But I don't see any reason to conceal it. Certainly, I wouldn't want COVID+ people around me, and I wouldn't want them hiding their status to sneak back to work and continue the pandemic either. "I am currently under quarantine" seems like an important message that needs to be broadcasted.


I couldn't care less what anyone else at my company makes for any practical reason. In the best case, I know I'm the highest paid person in circumstances X. In the worst case, I get jealous or enraged that someone else is either making more for the same contribution or making the same and contributing less (in my estimation).

I think it's pretty clear we just have different views on privacy. I view health and financial information as being nobody else's business, except as required disclosures to the government and those disclosures should be minimal so as to serve a valid government purpose and not be disclosed to random members of the public. Sure, the IRS needs to know how much I made last year. My neighbor or my non-supervisory, non-payroll, non-HR co-worker has no business knowing it.

Likewise, if there are quarantine restrictions for people with +CV19 test results, I support the government having enough information to enforce their quarantine restrictions, but not for the local Nosy Upinmybusiness to have that information.


> I think it's pretty clear we just have different views on privacy.

I'm not sure we do. I'm normally on the pro-privacy reflexive side. But the best way to test your beliefs is to have a discussion. I was hoping to take the opposite side on a few issues I'm more ambivalent about and clarify my own position.

In the case of "person X needs to be quarantined", I find myself leaning away from privacy by default because it interferes with people's ability to protect themselves. That's not suggesting I would be okay with knowing other people's cancer diagnoses or blood pressure.

Similarly, I'm not sure of the downside of your coworkers knowing what you make. It seems that openness will lead to everyone making more money. Possibly except the company, but honestly they may make more than enough extra revenue to make up for slightly higher salaries with more motivated workers.

> if there are quarantine restrictions for people with +CV19 test results, I support the government having enough information to enforce their quarantine restrictions,

Pragmatically, there just isn't sufficient government surveillance (thank goodness) for the government to enforce quarantine restrictions without the population's cooperation. That's why it's so scary to be in pockets of anti-maskers. It's also why I feel safe knowing that it's hard for the government to enforce similar measures outside of a pandemic.


It's possible to tell the four being cheated without telling them the fifths salary.


How do you determine that any are “being cheated”?

Once you do, how do you share the salary information of five people such that four of them working together can’t de-anonymize the fifth? (I’m facing this exact issue at work; I do want to publish more info about salaries without risking even the slightest possibility to expose private information of any of our employees.)


Two options spring to mind:

1. Don't worry about that failure mode. There will always be ways for collusion among employees to gain salary information.

2. Publish the methodology by which compensation is calculated. That is, it is presumably some combination of algorithm based on location and role, performance, and discretion. Make the calculation methodology transparent (internally). This will also set a range you can publish externally.

This allows people to ask informed questions ("why is my perceived performance not being rewarded") instead of being completely baffled by numberwang. Transparency about the process and forces the company to do better, which is a good thing.


Re: 1. I don’t view it as my place to disclose (or allow to be disclosed) any information that any of my employees would reasonably consider private.

They can choose disclose it. I will not decide to do so on their behalf.


Then don't. But publishing aggregate salary information is not that. You're making an excuse to avoid sharing information that would help your employees.

You might, for example, try asking them, and seeing how many feel that their privacy would be violated by publishing aggregate anonymous salary data. The answer will be 0.

Keep in mind if you have a reasonable belief that all but one of your employees will collaborate to unmask another's salary, they have ample support to form a union and require internal transparency in the contract. Your threat model is illegitimate.


It depends on how you're aggregating, of course. If I publish an indicative range, I agree that I'm not divulging any private information. (That also happens to be exactly what I'm personally fighting HR/comp in order to be able to do. I want my employees to have this information, but I want that less than I want to protect the privacy of employees who have not chosen to share their information on their own.)

If I publish a names-redacted list of everyone's salary and track/level/job code, or a mean & std-deviation per track/level/job code, I am almost certain to divulge private information of at least one employee. I have spoken with employees on this topic. Publishing their data, even inadvertently (as in the Netflix contest example), does not have anywhere near 100% support.


Why do you care if four people can unmask the fifth? Isn't allowing them to figure out the range part of the impetus to share the data? Do you feel that one person is dramatically over/under paid? Is there a reason you wouldn't want to just put all that information in a spreadsheet with people's names and publish it?

But that failure mode seems pretty similar to the failure mode where all 5 share their salary. At least in my mind.

To really answer your question, I ask wonder what your goal is? Because that determines how to set up your information publishing.


My goal is to publish something that addresses questions roughly of the form: "Where am I in the overall salary range for my current role?", "Where would my current comp be relative to the next most likely role for me?" (to know if I "have room" in the current level or if the only large raise is to get a promotion/change role/change company), and [if possible] "How wide is the current band/are the bands in general? Are people paid within 10% of each other or 100% of each other?"

It's not a failure mode if all 5 people volunteer to share their salary information with each other. It is a failure mode if one of their salaries is exposed against their willing participation in the sharing.

I believe we are paying people fairly. (That specifically does not mean paying people equally, because the scope and value of their contributions to the company differ.)


On your last point, the biggest reason I can see not to share salary information (unless you want to take advantage of people) is that everyone tends to overvalue their own contributions.

Almost any aggregate statistics can be reversed by N-1 datapoints. Even something like Mean and Std. Deviation have a unique solution for the missing datapoint. Even just a band fails in the case that the missing person is one of the two extremes.

If that's the information you want to provide, does it matter how much the data directly reflects reality? Is there a reason to provide an actually min-max band as opposed to your budgeted min-max band (except that basing it on actual data keeps you honest and makes your employees trust the numbers more.)


That’s likely the solution we’re going to go with. If the scatter plot of actual salaries is $190-280K, I think saying “anywhere from $180-300K” or “$200-275K with rare outliers” or “centers around $240K, typically within 20%” would all be fine and would communicate more than nothing.

If the employees don’t trust the numbers unless you give them to the penny, why would they trust anything we said? If you don’t trust any of your employer’s statements, you should probably find another employer.


I wasn't talking about trusting your word if you're rounding or otherwise tweaking real numbers. I was talking about the tendency to lie to yourself (universally, not about you specifically) if you were trying to come up with a "reasonable" range. As in "sure, we never gave someone $385,000 for this position, but of course we would if a sufficiently good candidate arrived or when one of employees improves enough" with your 190-280k range you quoted.

Honestly, I think if you're going to do that to give me some idea of what the future holds (and it's not too much work) tell me how likely I am (individually) to move up in the band. It can be part of the annual review, or something as general as "we typically move people who are developing on track 15% of the way up the band as they progress from bottom to top". It gives a picture going forward and, if an employee doesn't advance, sends a powerful signal that they need to improve.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: