News for hackers. Stuff that matters.
Re:Gitlab's Guide to All-Remote by alkonaut on Thursday March 12, 2020 @05:59AM (#22555226)
They buy your skill at the market rate, and sell the product at the market rate in a different market.
Re:Gitlab's Guide to All-Remote by flyingfences on Thursday March 12, 2020 @08:58AM (#22556304)
For an all-remote, international company, "the market" at both ends of that process is "the world".
Re:Gitlab's Guide to All-Remote by alkonaut on Thursday March 12, 2020 @11:08AM (#22557623)
The fact that I make X here while pay is 4X in SF is the only proof needed to show job markets and pay levels are local.

If a SF company wants to hire me remotely, I'll take the job at 1.5X, so they won't pay more than that. The simple reason is this: If I don't want the job at 1.5X the local pay, I my neighbor does, and he's every bit as good an engineer as I am. When they do hire me at 1.5X my current pay, they have bought my skill at the local market rate.

Re:Gitlab's Guide to All-Remote by rizz0 on Saturday March 14, 2020 @02:11PM (#22577294)
You make a good point: as an employee you are not the product, you are part of a team — and the team is just one ingredient in the manufacturing of a product. An important ingredient, but not the whole story nonetheless.

Taking that further: as a human you are also part of the physical community that you live in. A developer in a small town might help out the local library, whereas a developer in a big city might organize tech meet-ups to help their peers.

I'm not saying one situation is better than the other, but I can imagine not just different price points, but also different valuations for equal skill depending on location.