Salary Transparency at Stack Overflow

We believe (and developers tell us) that job seekers should be empowered with as much information as possible when looking for a job – especially salary. So we ran an experiment on Stack Overflow Jobs to see if the evidence would support it.

Remarkably, we learned that job listings which include a salary range got 75% more clicks than job listings that don’t. With this experiment, we’re even more convinced that transparency isn’t just the right thing to do, it’s good for companies, too.

Along with much of the tech community, we were impressed with Buffer’s boldness and leadership in salary transparency. So…

Introducing the Stack Overflow salary calculator

We’ve created a salary and skills calculator for Stack Overflow’s engineering, design and product roles. This has been transparent internally for a while; now it’s transparent with you.

Try the salary calculator

Those who know Stack Overflow know that we work hard to work in public. This is a continuation of that tradition.

What we hope

We hope that moves like this will inspire other employers to greater transparency.

A lack of transparency is what economists call an information asymmetry: it’s in companies’ interests to keep these numbers close to the vest. Individuals are uncomfortable talking about salary sometimes, too.

We believe that conventions can change. If more companies become open on salary, perhaps openness will become expected.

Work in progress

Our salary calculator doesn’t cover every role at Stack Overflow. It doesn’t include equity, and only describes US salaries. (International employees use the same system but it’s not merely a currency conversion.) In the spirit of “default public”, we would rather share an incomplete system than not share at all.

The experimental details: 75% more clicks

(By David Robinson and Bret Copleland)

For our experiment, we redesigned the Stack Overflow Jobs ads to display salary ranges. We were curious: just how much effect does this information have?

We ran an A/B test, where for a random half of our users we hid the salary information from the ads they were shown, and measured the difference in clickthrough rate. Visually, it looked like this:

Job listings with and without salary

We expected to see an improvement, but we were surprised by the size: a 75% average increase in clickthrough rate (CTR) when we showed a job’s salary range.

What if a job has a relatively low salary – is it still worth showing? Generally speaking, yes: we found that showing any salary range led to an increase in CTR, though higher salaries led to a greater bump. For American jobs, we saw roughly a 60% increase for jobs with salary ranges centered below $100K, and about a 100% increase (doubling) for salaries above $100K.

Salary vs CTR

Is this just an effect of novelty, where users were surprised to see salary? Unlikely – we didn’t see any decline in the effect, and it has been consistent in the months since. We’ve tried many other changes to ads and have never seen anything this dramatic.

Clickthrough rate isn’t everything, but it’s an encouraging sign that advertising a salary range will help draw developers to a position.

Try the Stack Overflow salary calculator…

Further reading


Matt Sherman
Engineering Manager (former)
Matt speaks on engineering and engineering management. He specializes in recruiting, getting developers talking to salespeople, and the Go programming language. He is also the founder of Alikewise, a dating site based on books.

Related Articles


  1. Very interesting. I wonder if I can get more likes on Instagram by adding my salary to every photo. Will update.

    1. And compare it with adding how much you lift, to each photo XDXDXD
      pls update.

      1. umm… get a better salary?

    2. Jbal Tero says:

      LOL. Gold diggers will.

  2. The link you posted does not work for Also I think the skill # is very confusing, it needs a better explanation, the page it takes you to is choke full of content and text and hardly anyone would read it.

    1. Agree about the skill #. Would be neat if there was some kind of 10 minute test to quickly estimate this.

    2. Here’s the fixed link:

  3. Not surprised by this result. When you’re looking, you need to know if you’re looking at jobs in the right ballpark. There’s no way to know this until they tell you. The scenario involving it being hidden results in you not knowing until way down the line in the interview process which is a potential waste of time both for prospective employer and employee alike. Being up front about it saves everyone the hassle.

    1. It also means that listings with higher salaries get more clicks by default, which is clearly evident by the graph.

  4. Rudy Kroska says:

    Do you have data on how those clicks converted? Like – how many of the click throughs resulted in conversions on the advertiser’s page?

    I’m trying to figure out if this is lookie-loo traffic or actual conversion drivers.

  5. I would not even bother applying for a job without a ballpark salary figure. Waste of time.

  6. Rainier Wolfcastle says:

    The A/B test is interesting and relatively convincing. If I were evaluating this, I’d like to see a couple of other variants to get a better measure of the true effect.

    First, make the ads the same size whether or not the salary is displayed. The most obvious way would be to just leave whitespace where the salary would be shown. (There is undoubtedly some UI effect from just making the ad more noticeable by increasing the size alone.)

    Second, have an additional treatment where you keep the text color for the salary the same as the gray used for the company name and location. (The green is also a UI effect that will attract the eye regardless of what you put there, as will going from 5 figure salaries to 6, as the plot also seems to intimate.) Third, stratify users by some coarse geolocation data. Is the effect larger for higher salary ads when users are from areas not in the same geo region as the ad, but from one with a lower cost of living?

    Rudy Kroska’s comment is also one to pay attention to. There is, undoubtedly, a curiosity factor at play: “What does it take to make $120K+?” By giving the salary range upfront, you might reduce the quality of the traffic (e.g., in terms of the advertiser finding suitable candidates for every n resumes submitted).

    1. Dan Kaschel says:

      I agree. Measuring click-through without measuring conversion isn’t really that useful.

    2. Erwin Glassée says:

      Second that. Another interesting point is what happens when the salary is low or high compared with benchmarks for the jobs offered instead of merely in absolute numbers. An Angular.JS & Rails engineer in New York at 85 to 120 K may be lower or higher than expected for that job in that area. Comparing with external data from benchmarks could establish whether those numbers are average, below-33 percentile or above-66 percentile. Would love to see that graph, too. Otherwise, great post.

  7. que the incoming recruiter hate

  8. Listing the salary range saves us both time. I can filter out jobs I don’t want, because of low salary, or jobs I’m not qualified for, based on high salary. That way we don’t waste time just to find out that I don’t want an entry level position after being in the field for 10 years. If a salary is not listed I just assume it’s because it’s not competitive.

  9. Hillary Sanders says:

    Need a better y-axis on the last plot (you show the 0%, not clear the top of the chart = 100% or something else)
    Other than that great post!

  10. Dragonzord says:

    It’s pretty obvious. Secretively salaries are an old taboo. Most people are smart enough to know around what they can expect to make, so hiding that info just comes off as sleazy

  11. Agreed – Expecting someone to go through an entire recruiting process without a salary range will end up wasting time for both the company and the candidate if the salary doesn’t meet your minimum expectations.

    1. Which is why companies should ask you your salary expectations as part of the application process.

      1. Jamie Reeve says:

        And it would be a pretty bad negotiation move to answer that question 🙂

        1. Why? As a candidate applying for a job, you should have a figure or range you are happy with. If a company doesn’t have a salary range, but your expectation is above what the company is willing to pay, then the process stops there and no one’s time is wasted.

  12. This is a good A/B test!

    All companies with a web page to hire should heed your experiment conclusion.

  13. So you’re assuming a Dev with 0 experience and 0 skill is worth $86,000/year ? Please tell me where you guys live, I’m gonna pack my stuff now 🙂

    1. Wow me too, let’s do it and get a digs with 1gbps internet?
      To develop with of course 🙂

    2. Haha, was thinking the same 😉 Give me half and I am still theirs!!

  14. Why is the SRE pay scale different from the Developer pay scale? Why bother calling it SRE if its not equivalent to an engineering role?

  15. Samer Afach says:

    Why are the salaries calculated by the calculator for 0 years experience higher than the best salary advertised on Stackoverflow Jobs? All the jobs I see (I live in Germany) are like this!

    1. Bill the Lizard says:

      Because the calculator is for jobs *at* Stack Overflow. The salaries advertised on Stack Overflow Jobs are for other companies. There’s no reason to expect them to be the same.

  16. Константин says:

    Somebody from Russia, saw that kind of money?

    1. Alexey Filippov says:

      Not sure I understand your question. One’s origins are not relevant; the location is relevant indeed, but then the cost of living in Russia is much lower than it is in NYC or London.

      1. Not in Moscow though…

  17. Dániel Darabos says:

    Where do I put my rep score in the salary formula?

  18. There may still be a novelty effect. If each viewer is job-hunting across *many* sites, and not spending a large proportion of it on your site, your presentation of salaries is likely to be novel.

    1. Seems hardly any other job sites show a salary range, so…assuming other sites continue to *not* show them perhaps the novelty might stick around? I like it anyway 🙂

  19. For me employee welfare is more important then salary. I always feel uncomfortable on applying jobs that are not clear on Job security, vacation time, Health insurance etc.

    I would give 200% of my effort but will want to have enough security that the company won’t kick me out if I have a bad month due to personal reason.

    1. Do you have bad months very often?

      1. You could get sick, get depressed, whatever, and losing your job probably won’t help in getting back on your feet.

      2. Never a month but bad week perhaps but before you get a fulltime you need to make sure how they handle those situations.

  20. Any reason why Stackoverflow Jobs only have a few currencies to choose from when specifying the salary?

  21. Really cool. It lacks many countries though. Would love to see it expanded to Germany, Netherlands, Switzerland, Japan, etc too.

  22. Barbara Robson says:

    I always like to see salaries when considering job ads. It gives me a better idea of what level of experience and qualification they are expecting, whether it is worth me considering them, and whether they would be likely to consider me. It also reassures me that it won’t be an onerous negotiation task if I am offered the job.

  23. This is gonna be more fun than ever before

  24. Glen Thomas says:

    I’m a developer and If I see a job advertised without a salary or I am contacted by a recruiter about a position and salary range is not provided, I will more than likely not have any interest in it unless the job description sounds amazing and then I might consider asking what the salary is.

  25. This makes me a rather sad panda about how terrible salaries are in the UK

  26. Stefanos Ioannou says:

    Is this calculator for local jobs only?

    1. It’s only for jobs at Stack Overflow itself.

  27. Nick Iannone says:

    I’m in Milwaukee, and $70k for a year or so of experience at at skill level of 1 is pretty good. I am in consulting, though.

  28. PETER GREEN says:

    Why do you lump everything under $80K into one category?

  29. John Morrice says:

    UK salaries are like half to a third of what your calculator gives, and living here is very expensive too!

  30. Warren Dew says:

    You salary calculator calculates within 2% of my current salary. Pretty good!

  31. Can I sort jobs by salary DESC?

  32. […] Slack Sees 75% More Clicks on Job Descriptions with Salaries […]

  33. […] be ready to give good answers. One option here is to do what Stack Overflow did and create a pay calculator to determine everyone’s salary. Managers need only point to the calculator to explain […]

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.