This seems pretty spammy for a top-10 slot on HN
Gitlab and remote work
31–40 of 214 posts
Re: Gitlab and remote work
#32Their pay was abysmally low last time I applied. The company seems cool but the salaries as a senior were honestly kind of silly in this market.
I think their remote pay is based on some kind of survey of local salaries? There's no tech jobs near me, so I guess they picked up the next-best-thing which was maybe like call centre workers or something? It was so low I wouldn't recommend to a new-grad, and this was for senior level. When you looked they also had these peculiar small islands of higher pay - so I guess it's really pay by what you can negotiate and they create an island for you if you're important enough?
Re: Gitlab and remote work
#33Earlier quoted context omitted.
You pay according to location for the same bottle of Coke? How is work pay different? Why shouldn't payment for work be tied to local price ranges and cost of living?
Because physical goods are subject to differently priced logistics and local ingridients and remote work is not? Seriously, how can you even compare?
in the tech job market generally, the value of the work to the company puts an upper bar on a salary, but competition with other employers for the same worker puts a lower bar on salary (obviously along with other factors like the company's reputation, mission, benefits). In practice all salaries are set by the latter rule, which means they depend on the job market, which varies by location. That salaries should not depend on location is a fantasy based on some weird idea of people getting "paid what they deserve"—a fallacious association between your salary and your worth as a person, which people would do well to get over.
Re: Gitlab and remote work
#34Still paying according to location for the same work?
You pay according to location for the same bottle of Coke? How is work pay different? Why shouldn't payment for work be tied to local price ranges and cost of living?
> Why shouldn't payment for work be tied to local price ranges and cost of living?
Why should it be? You pay someone enough to get them to work for you instead of someone else. That's the sole reason you pay someone anything at all. And there's no reason to pay them any more than that. How do local prices and cost of living fit into that equation?
Re: Gitlab and remote work
#35The comparation is great: https://about.gitlab.com/company/culture/all-remote/all-remo...
To elaborate, the above is a table highlighting all the benefits of Full Remote over Hybrid Remote.
Re: Gitlab and remote work
#36Earlier quoted context omitted.
You pay according to location for the same bottle of Coke? How is work pay different? Why shouldn't payment for work be tied to local price ranges and cost of living?
Because physical goods are subject to differently priced logistics and local ingridients and remote work is not? Seriously, how can you even compare?
The price of Coke is influenced by logistics but ultimately it's determined by the market (supply and demand), exactly the same as your work, that's capitalism.
What's the market in this context is of course the interesting question.
Re: Gitlab and remote work
#37Earlier quoted context omitted.
Who would you consider to be operationally and culturally superior in regards to remote work than Gitlab? Asking sincerely, because Gitlab is one of the first brands I think of when people mention "remote first culture".
Kraken has a few thousand employees, has been a remote first company for a decade, and pays the same no matter where you live.
Kraken operates in over 60 countries (according to their website). They pay the same amount across all those territories, including benefits etc.? I find that hard to believe.
Re: Gitlab and remote work
#38"They're the writers of their own press releases, Morty."
Re: Gitlab and remote work
#39Earlier quoted context omitted.
Because physical goods are subject to differently priced logistics and local ingridients and remote work is not? Seriously, how can you even compare?
in the tech job market generally, the value of the work to the company puts an upper bar on a salary, but competition with other employers for the same worker puts a lower bar on salary (obviously along with other factors like the company's reputation, mission, benefits). In practice all salaries are set by the latter rule, which means they depend on the job market, which varies by location. That salaries should not…
> which means they depend on the job market, which varies by location
Aren't you commenting on a post about remote work? Their job market is global (within limitations.)
Re: Gitlab and remote work
#40Earlier quoted context omitted.
You pay according to location for the same bottle of Coke? How is work pay different? Why shouldn't payment for work be tied to local price ranges and cost of living?
> Why shouldn't payment for work be tied to local price ranges and cost of living? Why should it be? You pay someone enough to get them to work for you instead of someone else. That's the sole reason you pay someone anything at all. And there's no reason to pay them any more than that. How do local prices and cost of living fit into that equation?
Presumably GitLab will stop using local prices and cost of living when continuing to use them gets in the way of hiring developers they'd like to hire. As of now, it seems that it's working for them.
If we enter a world where most SWEs work remotely and few other companies are paying location-based, we might see GitLab change their tune. For now, they're competing first and foremost against local jobs.