One Job, One Pay – Globally

Re:One Job, One Pay – Globally by bombcar on Thursday June 02, 2022 @07:49PM (#31602142)

So is the pay such that everyone outside of SF should apply or is it such that nobody inside SF ever will?

[ Parent | on HN ]

Re:One Job, One Pay – Globally by deleted_account on Thursday June 02, 2022 @07:54PM (#31602192)

Hard to say, their job listings[1] don't include the salary. Their listings do say "All salaries are transparent within the company and are set above local market rates," so maybe all it takes is one high cost of living hire to raise the rates for all employees with the same title?

[1] https://jobs.lever.co/GraphCDN/33bc14f9-4671-4540-8862-7d358...

[ Parent | on HN ]

Re:One Job, One Pay – Globally by runnerup on Thursday June 02, 2022 @09:02PM (#31602873)

> set above local market rates

This wording seems philosophically incompatible with "One Job, One Pay" (OJOP), even if it's not actually logically inconsistent with OJOP "per se".

[ Parent | on HN ]

Re:One Job, One Pay – Globally by chris11 on Friday June 03, 2022 @12:55AM (#31604452)

> We are anchoring our pay to the 60th percentile of San Francisco

It works out as long as SF has the highest pay.

[ Parent | on HN ]

Re:One Job, One Pay – Globally by mxstbr on Friday June 03, 2022 @12:25AM (#31604285)

One of the easiest ways that we can hold ourselves accountable with minimum friction is through pay transparency. https://www.sueodio.com/pay-transparency/

We’re rolling it out in the next week 2 weeks. We will begin publishing salary bands on every job posting. Internally, we will publish levels and sub-levels for every job.

[ Parent | on HN ]

Re:One Job, One Pay – Globally by mattnewton on Thursday June 02, 2022 @09:41PM (#31603198)

It seems to me the way it would work in practice, is that they’ll probably have to give people in SF higher titles? Mostly hire people with senior pay bands in high CoL areas, and if those pay bands are competitive with the other offers they get (which may be less senior) then it works?

[ Parent | on HN ]

Re:One Job, One Pay – Globally by quickthrower2 on Friday June 03, 2022 @02:02AM (#31604785)

That would be the definition of it not working.

This HN post causing 1000 people around the globe to apply is what it means for it to work.

People in SF with high COL probably will not apply. Unless they intend to move as soon as they get the job.

[ Parent | on HN ]

Re:One Job, One Pay – Globally by mattnewton on Friday June 03, 2022 @02:23AM (#31604904)

I don’t disagree; just, I have seen talent hired at higher levels simply to justify the salary band and not because of the work and it seems like an easy escape hatch from this when recruiters want talent in competitive markets.

[ Parent | on HN ]

Re:One Job, One Pay – Globally by quickthrower2 on Saturday June 04, 2022 @06:35PM (#31625768)

Ah yes, introduce rules and people bend them to meet their targets.

[ Parent | on HN ]

Re:One Job, One Pay – Globally by mxstbr on Friday June 03, 2022 @12:19AM (#31604251)

We’ve already begun using this framework and have made offers to candidates with surprising non-obvious results. Here are some examples:

- We offered one person $27K more than their asking salary because the data showed that they were underestimating their market value.

- We offered someone 30K below what they were currently making

- We’ve made a comparable market offers

[ Parent | on HN ]