4 ms·
To add to what I think have been many other good comments, in my experience the productivity differentials between individuals in the same job can easily be vas
by hn_throwaway_99 5y ago
To add to what I think have been many other good comments, in my experience the productivity differentials between individuals in the same job can easily be vastly greater than the upper and lower bounds of that job's payscale.
I can recount cases where I've worked with relatively new engineers (a couple years out of college) who were easily 3-4x as productive as some of their peers. Of course, the pay scale for "Software Engineer" usually only has a band width of about 15-20%. Yes, the better programmer would get promoted faster, but still I've nearly always seen that there is more variance in "creative"-type jobs than pay scales will allow.
So for these types of jobs, posting a payscale is nearly always a bad idea, because it can further compress what is already a "too compressed" payscale.
- itsgrimetime 5y agoWhy not just list that entire “wider” band? How would doing that “compress” the payscale further?
- hn_throwaway_99 5y agoBecause when you list the entire band, people naturally will demand being at the top of the band, of be insulted if you offer them salary at the bottom of the band, even if it is warranted.
- pydry 5y agoIME it's usually because they'd be prepared to accept less not because they're actually less productive.
- lotsofpulp 5y agoSo? That sounds like the applicant's problem if they do not want to accept the buyer's offer.
- thebean11 5y agoJust list the lower end of the band as 20% less than the actual lowest offers. Does the law prevent that?