|
|
|
|
|
by UncleMeat
2217 days ago
|
|
> why not just keep salaries the same and then you select from a larger pool of candidates (this should give you a pretty good pick, but you're still limited by when waking hours overlap). Because you make less profit if you pay the outrageously high SF salaries. Bay Area salaries are incredibly high because there is outrageous competition for the top engineers and there are a lot of rich companies local to the region who can afford high salaries. They aren't able to hire a bay area engineer at 2/3 pay because that hire can go somewhere else. If you are one of the early ones to the remote-game then you aren't competing with other bay area companies for an engineer in Tulsa. You are competing with local Tulsa businesses, which don't tend to make the gazillions in profit or VC money needed to afford to pay engineers 300k+. So you don't lose as many candidates when you say now you are paying 150k. So you make more money. Over time this difference could even out as more and more companies become remote-friendly or remote-first and there are no more local job markets. But this isn't going to end with bay area salaries for the whole world outside of a very very small number of companies and very top performers who can command high pay. |
|