Live data from Hacker News

The Programmer Salary Taboo

thurn.ca

171–180 of 331 posts

Re: The Programmer Salary Taboo

#171

Earlier quoted context omitted.

Can someone please shed some light on what would be a good strategy to follow if you were in his position talking to HR, manager, CTO? What's the best way to save yourself once you've realized you're worth nearly double, triple, or quad your current comp pkg?

Honestly, the best way to obtain your newly-discovered market worth is to leave and find another job. In almost every job your only chance of negotiating a competitive salary is before you start. Sure, you can talk to HR and your manager and perhaps see some form of bump in salary, but if you're significantly underpaid then a) it's likely other people are too and they won't want to rock the boat, b) there's a decent…

Agreed. Not only that, but the less people pay for your services, the less they respect those services (it doesn't feel as earned as the next guy billing twice as much).

So you pretty much have to jump. Which is likely anyways since if you were being paid less than half than everyone else around you and doing the same or better work, you'd probably be more than a little annoyed.

Re: The Programmer Salary Taboo

#172

Earlier quoted context omitted.

As "bad" as 15%? Tax is at least 38% here in Au for that wage (was 60% not so long ago).

That's "only" for social security and medicare. You still pay federal income tax on top of that.

And on top of that the state income taxes in most states, and sales taxes that usually approach 8 or 9%, and property taxes on real estate (and autos where I live). Also if you manage to save anything after all that, you can look forward to paying dividend or capital gains taxes (a form of double taxation).

It is a myth that America is a low tax nation.

Re: The Programmer Salary Taboo

#173
post #2

I've always wanted to write exactly this blog post. Keeping your salary confidential is great for big companies, but it benefits you in no way. You should be making what your coworkers make. If you make less, you're being fucked, plain and simple. The sooner you realize that, the sooner you can remedy the situation. Sadly, some people go their whole careers without doing so. FWIW, my first programming job only paid $…

But it does benefit you, personally: by not having your information out there in public, you can claim whatever you want when you go into salary negotiations, and the hiring company has no way of knowing that you'd be perfectly happy with a significantly lower salary. Generally, whichever side has less information public about them is at an advantage in negotiations. Unfortunately, this leads to a prisoner's dilemma…

This argument is circular: "Keeping your salary private benefits you when negotiating a new salary"... which is difficult mainly because everyone's salary is private.

Re: The Programmer Salary Taboo

#174
One of my earliest memories of the Salary Taboo was at the first Java One I attended as a freshly-minted Silverstream "Field Application Engineer" (must have been '99)

Four of us in equivalent positions, including one woman got together in my room and started pounding down screwdrivers. After the fourth of fifth, we started talking salaries. All of the guys were making around $120k and the girl... (wait for it...)

$80k !!! Despite having more education and arguably better qualifications.

We had a big problem on our hands. I'll never forget we were in a room near the top of the tall St. Francis hotel tower and she was angrily threatening to jump out the window.

Re: The Programmer Salary Taboo

#175

Earlier quoted context omitted.

Another method I've heard: person 1 picks a large random number, adds their salary to it, writes down the resulting number, and passes it on to person 2. Person 2 adds their salary to the number, writes down the new sum, and passes it on to person 3. This continues until the result gets back to person 1. You end up with the large random number plus the sum of everyone's salary. Person 1 then subtracts the large rando…

This is better because it determines the average but not distribution. Imagine what would happen if there were five $70k salaries and one $165k salary for six people doing the same work. People would suddenly get very uncomfortable. One technical gripe: you forgot that the arithmetic needs to be modular to guarantee anonymity. Let's just say the large random number is chosen between 0 and 9,999,999. (You need a range…

I didn't worry about the technical details because I just figured that people would write down random strings of digits. But this is all true.

Re: The Programmer Salary Taboo

#176
post #62

Salaries never stay secrets forever. Hiding them only delays the inevitable. Last year we were having a discussion at lunch. Coworker was building a new house, and when it came to the numbers it was let loose that it was going to cost about $700K. This didn't seem like much, except to a young guy that joined the previous year and had done nothing but kick ass and take names. The new guy was arguably the most talented…

Can someone please shed some light on what would be a good strategy to follow if you were in his position talking to HR, manager, CTO? What's the best way to save yourself once you've realized you're worth nearly double, triple, or quad your current comp pkg?

Visit www.paynegotiation.com (disclosure this is my friends site!)

Re: The Programmer Salary Taboo

#177

Here's a trick I once heard to share salary with your coworkers without the uncomfortableness of finding out you are over or under-paid. Over beers with several of your coworkers, each write down your salary on a piece of paper and then mix them up. Randomly draw them out of a hat and then read them to each other. If you're all roughly peers, then you get all the benefit of knowing the salary range of the group, with…

We did this amongst ten of us, but as the beers flowed everybody kept asking about the numbers (one person was significantly higher than the others) and by the end everyone knew what each other was getting.

The bottom two people had left within a year... go figure!!

Re: The Programmer Salary Taboo

#178

Here's a trick I once heard to share salary with your coworkers without the uncomfortableness of finding out you are over or under-paid. Over beers with several of your coworkers, each write down your salary on a piece of paper and then mix them up. Randomly draw them out of a hat and then read them to each other. If you're all roughly peers, then you get all the benefit of knowing the salary range of the group, with…

We did this amongst ten of us, but as the beers flowed everybody kept asking about the numbers (one person was significantly higher than the others) and by the end everyone knew what each other was getting.

The bottom two people had left within a year... go figure!!

Re: The Programmer Salary Taboo

#179
post #29

Consider a hypothetical scenario for the person on the other side of the table: You are hiring up an engineering team and hope to hire up a team of 10 engineers paying 100k/yr each. So far you've hired 9 people at 100k and are working on filling that last slot. You find someone perfect but he has a competing job offer and is asking for 110k/yr instead of just 100. He's no better than the other 9 people you have alrea…

Here's what I though you were going to say: You're hiring up an engineering team. You have five slots. Four are filled at market salaries. The four people range in productivity from marginal to good-at-stuff-no-one-else-likes, but none of them are that great. You almost have to keep the four folks, because they're entrenched in deliverables and plus, they've shown their dedication to the company. In walks a candidate…

Why are you even interviewing if you can't afford to hire someone who asks for a reasonable salary comparable to your existing developers?
Post reply on HN