Regarding point 1, remember that there are no salary negotiations at Stack Overflow. No one gets a raise because they ask. People get raises because they demonstrate skills, increase experience, etc... A candidate will have an initial skill evaluation they might not like, but they are pretty much guaranteed to have a much better one after one year, and if it is a big positive correction, then be it! There are no negative corrections btw - previous years salaries are at least maintained.
Secondly, I sincerely doubt we'd make an offer to a candidate that assumes their skills are all at the top of the range. "Fives" are extraordinarily rare, most employees have no fives, and the ones that do have one five.
Regarding point 2, as an employee I am not concerned with the salary of others per se. I know that they have the salary which corresponds to their perceived skills. It's likely that I would object to some evaluations of skills if I saw them, but that's an order of magnitude healthier than having salary envy. In fact, keeping evaluations fair and in check is a very good thing for the company.
I don't understand the rationality behind this. Why have (nearly) impossible to reach ratings? I mean, by this logic, the most talented people will only ever be a 4, yes? So make 4 the limit. You just came off of saying you'd never make an offer to an 80K candidate who thinks they're worth 100K[0]. Yet, you're telling your very best that they'll never be _the_ very best because basically nobody is a "five".
[0] It's what you were basically responding to.
Edit: for clarification.
I don't think anyone can be _the_ very best and I think that's not a reasonable or attainable goal.
We value T shaped developers, and our salary matrix values both spreading breadth (e.g. as a mobile dev if I up my skills in sysadmin or data science) or depth (which is a bit harder to do if you're already experienced) which fits into that nicely.
> I don't think anyone can be _the_ very best and I think that's not a reasonable or attainable goal.
... kinda proves my point of not needing a "five" rating.
You are confusing 2 things. The salary is (effectively) determined by the average skill rating of a person. The single skills can and do go up to AAA+++, and this raises the average and thus the salary.
While having an average of 5 is very difficult, having a super high maximum is actually meaningful. Some people are special in some area and we recognize that.
EDIT: clarified terms (see https://stackoverflow.com/company/salary/skills/web-develope... for the formulas)
My reference to negotiations was mostly for a negotiation upon hire. A job is advertised at a certain range, and the applicant expects the top of that range. I know that Stack Overflow's process might be a bit more evolved, but most companies that advertise a range probably leave a little wiggle room at the top and don't expect to be negotiating with candidates asking the minimum.
>Secondly, I sincerely doubt we'd make an offer to a candidate that assumes their skills are all at the top of the range.
This comes across more like assessing candidates for hire based on ego or confidence rather than actual skills. Of course, companies don't want to hire people with inflated beliefs about their own abilities - those who "don't know what they don't know".
If you would object to the skills evaluations, and if we assume some of those people are earning more than you, how is that different than "salary envy"? I'm not disagreeing with you, I'm just not sure I understand the thought process.
Our hire/no-hire policy is only based on competence, however true competence includes the capacity for realistic self-assessment. Keep in mind that our skill scale, especially for core skills, goes from "I could be better" to "I am world famous for this skill", so it's fairly easy to prove or disprove whether someone is at the top of the ladder.
> If you would object to the skills evaluations, and if we assume some of those people are earning more than you, how is that different than "salary envy"?
Big caveat: this works for us, but of course each company is different.
Our skills are based on measurable stuff and generally do not represent a "career achievement". An employee can't say "I'm better than Marco, so I should be paid more". An employee might say "This year I've done better than Marco at SQL, but Marco has a better score in it, can you review mine?". In most cases, we simply look at the evidence: has the employee actually been better than Marco in the last year in doing SQL?
Also keep in mind that there's a huge gap between categories. We've four, B, A, A+, A+++. They start at "B" which means that someone did not do much on that skill in the past year. For example, I've got a B in sysadmin stuff which I never need to do. In order to get an "A" one needs to be completely proficient in the skill, no obvious gaps, so for example I've (IIRC) an A in SQL, which means I can do SQL as well as anyone else in the team. In order to be "A+" one needs to be really good at the skill, someone that is recognized in the team for it, if I were to get it for SQL I'd need to go above and beyond the average. Patrol SQL for misbehaving query plans. Perform DBA tasks. Et cetera. An A+++ means that one is actually famous for the skill, for example a Microsoft MVP, or a famous blogger, etc. A guru level of skill is needed in SQL. Probably something which would take me 10 years to achieve.
One nice thing about being transparent and consistent with salaries is that you can have an objective conversation with someone about the reasons that they're making less, versus having to rely on vague, irrelevant, or harmful explanations like "he was making more at another company," or "he negotiated harder." If someone thinks they should be making what another developer is being paid, they need to make the case based on clearly laid out criteria.
There's no compensation system that makes everyone happy, and there shouldn't be. You want a system that leaves people knowing where they stand, what it takes for them to make more, and management that encourages them to grow into that amount.
Those objective conversations are a great benefit to salary transparency in theory, and I can't imagine you can open up your numbers without being at least somewhat prepared for those conversations to take place. I would be curious if companies that provide salary transparency wouldn't be scurrying to make some salary adjustments in the days before the data becomes public.
The issue lies in the fact that developer contribution is more than just commits and LOC stats, and it's tough to measure objectively. You're likely to get into some rather vague explanations, even if they aren't as nefarious as negotiating ability or salary history.
It's a step in the right direction, though until we have clear and widely accepted methods of measuring contribution we'll still have disagreements on individual employee value.
And sometimes comparing people and their skill sets is really apples to oranges. If one guy is an expert on some very specific top, and thats important for your business (and is therefore an expensive hire) - it doesn't mean you should create an incentive for other employees to learn his skill set (maybe you only need one statistician or expert in COBOL or whatever)
"There's no compensation system that makes everyone happy"
Sure, pay people way above market rate and don't allow them to compare wages. They will not feel ripped off and they don't develop a sense on inadequacy
That sounds illegal. Can you really not allow your employees to compare wages?
The National Labor Relations Act of 1935 is what you're looking for here - it provides employee protections for such discussions.
Why is this wrong? The labor market should strive to be efficient, no?
Some of those issues will be related to things like confidence, willingness to speak out, and the ability to honestly recognize your ability.
When asked in this context (as it relates to pay), most people may think they are at least above average. Obviously that can't be true. It's not easy to determine contributions in most cases, so value (and relative worth) can be ambiguous.
As for people being unable to judge and compare the price value of their contribution, because of the lack of public salary data, they've had no practice at the exercise. After a short adjustment period I'm sure people would develop the tools and attitudes to navigate a marketplace where they have way more information available.
I wasn't referring to the inability to compare price value of contribution as related to public salary data, but rather for internal comparisons. Not market rate across the entire market, but value compared directly with a co-worker. These should be related, but transparency within one organization is easier to assess.
If we have two programmers working on the same code base building the same product, how easy or difficult is it to determine who is contributing more and therefore worth more to the company? There are several factors at play, not to mention intangibles (catalysts, morale, leadership), and it's incredibly complex to say EMPLOYEE1 is 'more valuable' than EMPLOYEE2.
And then, requests for reducing salary will be weighed against the sacrifices the superiors are making, not about whether the kid brought in to fix the issue is getting paid more or less.
1. This generally means it's easy to filter out candidates who aren't a fit for your organization. In my experience, most employers would love to have employees where the salary is not the first (or even top 3) factors in their decision to take a job. (Rare, I know.)
2a. That seems like a good tail into #1. The employees who aren't in it for the team/company/career filter themselves out. 2b. Or, it's used as a comparison for employees to better themselves. "I want Job xyz because I can make an additional $20k/year. How do I improve myself to get it?"
If "fit" for an organization means not caring (as much) about money, that almost always indicates the organization is paying below market rate. I have clients that pay below market rate, and candidates who value money above other things will filter themselves out when they discover the ranges being paid.
Not sure I follow the second point. My example would be if Jane sees herself as a top contributor and earns 100K and she learns that Joe (who she feels is not a top contributor) earns 120K, Jane won't be happy. I don't think Jane will think "what can I do to earn what Joe does?", because she already feels she's doing more than Joe.
I might have misunderstood your point, but wanted to clarify my post.
Regarding the second point, I guess my point was: if the argument is that employees “value” is shown by salary and Jane is unhappy based on her perception of contribution, isn’t that a fault with management for not recognizing that and fixing accordingly?
I think we're assuming Jane to be a rational actor with perfect information. Jane makes less than Joe and feels she does more than Joe. Management feels Joe does more. Theoretically, management can tell Jane that Joe is paid more because his contribution is valued more, but Jane's unhappiness only exists because she disagrees with this valuation.
Either Jane convinces management that her self-evaluation is accurate, management convinces Jane she is being paid what she's worth, or Jane updates her resume.
On a practical note: I definitely perform better if I know that I am paid well. Money is the ultimate indicator of respect.
There have been many good articles on HN about salary negotiation, setting freelance rate, and seeing through the "one day you'll be a billionaire because of these options if you work for almost-free" and the kind of nonsense your touting does nothing but set the conversation back.
Non-profits are the obvious example where the business typically just can't afford to pay market, but employees accept sub-market pay because they place value on the opportunity to (hopefully) help others.
Companies that offer extraordinary benefits to the employee that may or may not have direct cash value and are often not included when applicants consider "total compensation". Training and learning opportunities are an example of this. Short term loss as investment towards long term gain.
I said that most employers would love to have employees where the salary is not the first (or even top 3) factors in their decision to take a job.
In other words, employees who actually want to be there are far more valuable than those just looking for a high paycheck.
Sure, and most employees would love to have an employer who isn't trying to pay them the minimum possible. The idea that it's a bad sign for employees to try to maximize their salaries while it's okay for employers to try to minimize them is an absurd double-standard.
In any publicly traded company, this is an unacceptable viewpoint.
How is it in any way reasonable for an employer (who has a fiduciary responsibility to return maximum value for its shareholders) to take this stance and then admonish their at-will employees for it?
That said, salary ranges and transparency can create two obvious issues.
1. Negotiations - I can tell you from vast past experience that when you tell an applicant "the salary range for this position is 80-100K", in almost every case any offer below 100K is considered a slight regardless of the experience of the candidate. "...but I thought you said the position paid 100K?" is a common thing to hear. Candidates hear the top of the range, and apply/interview with that expectation.
This is only an issue when a candidate's true market rate is at the bottom of a range. A minimally qualified candidate doesn't typically see himself/herself as 'minimally qualified'. So even if 80K is true fair market rate for this candidate, and 80K is offered, the offer still has a good chance of being rejected simply because of the emotional attachment to the higher number and the feeling of "leaving money on the table".
2. Internal employees - Stack Overflow said this has been available internally for a bit, but when employees find out what others are making they are inclined to compare their own efforts/abilities vs others. It can lead to people either asking for raises to match their co-workers, or perhaps feeling slighted and seeking other employers.
Being that it's not easy to truly measure productivity in most environments - other than perhaps consulting (billable hours) this is likely to cause issues. The next step is being prepared for how to handle those issues when they arise.