News for hackers. Stuff that matters.
Re:Open Salaries: Outcomes by marme on Thursday October 27, 2016 @02:26PM (#12807843)
no two employees with the exact same job title should have more than 10% difference in pay. If someone is making 40% more than others with same title then they should be promoted to higher title and if they dont deserve that title then why is the company paying them so much. It is one thing to want to minimize salary costs but another to disrespect employees with absurdly low salary.
Re:Open Salaries: Outcomes by DannyBee on Thursday October 27, 2016 @04:35PM (#12809761)
"no two employees with the exact same job title should have more than 10% difference in pay"

Meh, job titles are just buckets. Comp is also a bunch of buckets.

Why should these buckets be necessarily tied in size?

Lots of flatter organizations have a smaller number of titles but larger comp buckets.

There is nothing necessarily wrong with this.

Re:Open Salaries: Outcomes by 8ytecoder on Thursday October 27, 2016 @04:50PM (#12809953)
This is true even for bigger companies. As an example, let's say we classify engineers as SDE I,II and III and then have at least three sublevels within these which are not reflected in the titles. Engineers can negotiate on what level they think they should be based on their performance - as opposed to how much you should be making. Everybody at a sublevel makes the exact dollar amount +/- a performance bonus. I worked at a company that did that and I found it much less awkward to negotiate during performance reviews (aka pay-hike talks).
Re:Open Salaries: Outcomes by mason55 on Thursday October 27, 2016 @02:40PM (#12808089)
Doesn't the Peter Principle come into play here? What if we do the same job but I do it twice as fast? That doesn't mean I'd be a good fit for the next level up, it might just mean I'm really good at doing this specific job very quickly.
Re:Open Salaries: Outcomes by ellisv on Thursday October 27, 2016 @03:03PM (#12808505)
In my mind this is one of the cases where "Jr" and "Sr" titles can be useful.
Re:Open Salaries: Outcomes by jsprogrammer on Thursday October 27, 2016 @06:21PM (#12810828)
Or a 20 hour work-week with full salary.
Re:Open Salaries: Outcomes by mason55 on Friday October 28, 2016 @10:47AM (#12816408)
I suppose it's ambiguous but generally I feel like "senior" means "responsible for more pieces or higher level pieces" not just "faster at the simple stuff".
Re:Open Salaries: Outcomes by jonlucc on Thursday October 27, 2016 @03:40PM (#12809018)
Where I work, there are 4 levels of my job, none of which are management. That is to say that someone can work an entire career as a research associate and take on more responsibility, but not be forced up the org chart. This is very important because I look to the people in the higher levels for a lot of help (both organizational and technical), but we can do much of the same lab work.
Re:Open Salaries: Outcomes by rayvd on Thursday October 27, 2016 @03:15PM (#12808678)
No. An employee should make the salary he or she is willing to accept and an employer is willing to pay.
Re:Open Salaries: Outcomes by Joof on Thursday October 27, 2016 @02:32PM (#12807942)
What if they do different jobs? Is the title so important?
Re:Open Salaries: Outcomes by Salgat on Thursday October 27, 2016 @03:05PM (#12808539)
Agreed. Title doesn't really mean much, unless you force a ton of different titles.
Re:Open Salaries: Outcomes by morgante on Thursday October 27, 2016 @04:55PM (#12810015)
That only works if you come up with lots of different job titles, which is probably a good idea. It's just pretty hard to implement for many companies: most non-tech companies don't have 10 different levels of software engineers.

I've had plenty of experiences where people in equivalent job titles had vastly different productivity (and, justifiably, vastly different titles).

Re:Open Salaries: Outcomes by obstacle1 on Thursday October 27, 2016 @05:11PM (#12810196)
A job title is not an accurate reflection of an individual employee's value to the company. It would be insane to require that a 10x developer gets paid the same as colleagues just because they shared a job title.
Re:Open Salaries: Outcomes by stale2002 on Thursday October 27, 2016 @07:18PM (#12811323)
He is arguing that this 10x developer should get promoted to "senior principal engineer" or something like that.
Re:Open Salaries: Outcomes by baddox on Thursday October 27, 2016 @04:28PM (#12809653)
But titles are just arbitrary anyway. If you're saying that two people with the same role shouldn't have more than 10% difference in pay, that makes a bit more sense, although it's still quite difficult to define "role."
Re:Open Salaries: Outcomes by thedufer on Thursday October 27, 2016 @09:11PM (#12812073)
Are titles really that meaningful? I've never worked at a place that cared much about them.

Also, on a practical note, that would require 17 different titles for the same type of job if you have a 5x variation in compensation. That seems kinda crazy.

Re:Open Salaries: Outcomes by exclusiv on Friday October 28, 2016 @12:32AM (#12813115)
Employees care about them because getting a new title is an official recognition of their accomplishments to themselves and their coworkers, it looks good on a resume, and can definitely be meaningful for optics with clients.

I really don't care that much about them myself. I do use a few different titles depending on the client however.

Re:Open Salaries: Outcomes by plicense on Thursday October 27, 2016 @04:03PM (#12809329)
LOL, genuinely laughed. A developer with a title a level below mine makes more than me - I was recently promoted but the raise I got with the promotion didn't match his salary without the promotion!
Re:Open Salaries: Outcomes by smsm42 on Friday October 28, 2016 @02:20AM (#12813543)
OK, next thing there's 9000 job titles. Where's a win in this? If it just salary levels, then why bother with titles? Call it just "salary level N+1" and that's it.