Live data from Hacker News

Gitlab and remote work

about.gitlab.com

161–170 of 214 posts

Re: Gitlab and remote work

#161
post #89

I appreciate a lot of what Gitlab has done, but as someone who has been permanently remote for nearly a decade, I don't really consider them to be a leader in remote work. One of my biggest issues with Gitlab is that they pay based on locality, many other fully remote companies pay below Bay Area salaries, but they pay flat globally, meaning you can be location-independent without a pay-cut and it helps to bring in h…

I don't really understand appealing to the concept of "fair" regarding salary. I guess I'm showing some assumptions about labor being a free market, but isn't your salary by definition acceptable to both you and the employer?

You could exchange "fair" for "reasonable" (as in "buying at a fair value"). I think OP's point is not on justice, but more on how acceptable of a trade-off it is.

Either way I think Gitlab will be paying different taxes and other fees depending on where the employee is registered, so IMO it kinda comes down to the message they want to send to their employees.

Re: Gitlab and remote work

#162
post #89

I appreciate a lot of what Gitlab has done, but as someone who has been permanently remote for nearly a decade, I don't really consider them to be a leader in remote work. One of my biggest issues with Gitlab is that they pay based on locality, many other fully remote companies pay below Bay Area salaries, but they pay flat globally, meaning you can be location-independent without a pay-cut and it helps to bring in h…

I don't really understand appealing to the concept of "fair" regarding salary. I guess I'm showing some assumptions about labor being a free market, but isn't your salary by definition acceptable to both you and the employer?

The point is it isn't acceptable, since I wouldn't apply to GitLab.

They could attract a more good people if they paid globally consistent wages.

Re: Gitlab and remote work

#163
post #116
post #89

I appreciate a lot of what Gitlab has done, but as someone who has been permanently remote for nearly a decade, I don't really consider them to be a leader in remote work. One of my biggest issues with Gitlab is that they pay based on locality, many other fully remote companies pay below Bay Area salaries, but they pay flat globally, meaning you can be location-independent without a pay-cut and it helps to bring in h…

I hate that as well, but from the point of view of the employer it makes sense no? They are supposed to pay as little as they can afford, and location impacts that.

"as little as they can afford" is still completely subjective, as they will pay more for an employee that is better valued on the market for any specific reason, regardless of the actual results once they join Gitlab.

If tomorrow they declared they "need" to pay their employees 2x more to hire "A players" and get an edge on their competitors, we probably would have to take their word for it.

Re: Gitlab and remote work

#164
post #100

Earlier quoted context omitted.

>I care what the company is earning from my labor and getting my fair share. I have no problem extorting more from a company that has no problem extorting more from me. This just feels naive to me. You aren't being paid based on what your labor is earning your company. That number is totally irrelevant in a world in which businesses can run on VC money instead of actual revenue. You are paid based of both yours and y…

> You aren't being paid based on what your labor is earning your company. I've managed P&L at multiple companies. Salaries are inevitably influenced by cash flow projections and revenues, and are absolutely aligned in multiple dimensions to revenues. > cost of living shouldn't matter and maybe pay everyone $110k No, they're going to pay whatever their margins can tolerate while competing for labor. If Google can mana…

You get paid a fixed salary, that fact alone means it has nothing to do with the income you bring into the company, it's perfectly fine and is the norm. It's always about what number would make you happy, not what is fair, nor that "being fair" is well defined.

Re: Gitlab and remote work

#165
post #89

I appreciate a lot of what Gitlab has done, but as someone who has been permanently remote for nearly a decade, I don't really consider them to be a leader in remote work. One of my biggest issues with Gitlab is that they pay based on locality, many other fully remote companies pay below Bay Area salaries, but they pay flat globally, meaning you can be location-independent without a pay-cut and it helps to bring in h…

Locally-adjusted pay is a fluke if revenues are not locally constrained (like a coffee shop). It's just another way employers try and nickle and dime workers, and it's sad that a large class of workers have been brainwashed to support it because somehow they're more upset at the other workers making more, than the company trying to pull a fast on on them. "But you would make so much more than your neighbors!". Fuck o…

This applies whether you work remotely or on site, actually.

The difference is that without remote opportunities people are constrained to their local area so companies can indeed pay, say, an engineer in India much less than one in Silicon Valley although output for company may be very similar.

Re: Gitlab and remote work

#166

Earlier quoted context omitted.

Locally-adjusted pay is a fluke if revenues are not locally constrained (like a coffee shop). It's just another way employers try and nickle and dime workers, and it's sad that a large class of workers have been brainwashed to support it because somehow they're more upset at the other workers making more, than the company trying to pull a fast on on them. "But you would make so much more than your neighbors!". Fuck o…

>Locally-adjusted pay is a fluke if revenues are not locally constrained You don't get paid based on company revenue, you get paid based on the lowest amount you (or someone you're competing with) are willing to agree to sell your labour for. That amount is going to be lower if your cost of living is lower. People earning less if they work remotely in Podunk, Idaho compared to SF is no different from someone earning…

Absolutely true in labor markets where supply exceeds demand, but tech is not currently one of them.

Re: Gitlab and remote work

#167

Gitlab's company handbook is absolutely amazing if you haven't read it: https://about.gitlab.com/handbook/ Every company should be handbook-driven.

Handbook-driven is a lot better than location-based pay. So at least they've got one solid thing going for them.

Re: Gitlab and remote work

#168
post #95

Earlier quoted context omitted.

> You also won't see this for senior management. As a VP/C-level, I've never had a potential employer put pressure on salary during a negotiation because of my location (though it's always been domestic). It's never even come up besides relocation discussions. This is absolutely true and it's because executives usually have spent at least some amount of time doing "sales" type roles where they learn what value sellin…

> This is absolutely true and it's because executives usually have spent at least some amount of time doing "sales" type roles where they learn what value selling is. or because there are two orders of magnitude fewer VPs/C-levels than line workers. an extra +100k for a single unicorn employee is easier to justify than +20k comp x 100 replaceable employees

[deleted]

Re: Gitlab and remote work

#169
post #49

Earlier quoted context omitted.

Not cutting someone's pay when they move is very different to hiring someone in Thailand on a Bay Area salary.

Why? If both do the same work in the same location, why would one get more than the other. Either you don't adjust the pay when they move because you are already paying everyone an equal salary. Or you adjust it and pay everyone a local salary. Gitlab does the latter.

If both do the same work in the same location, why would one get more than the other.

I totally agree. But kirbypineapple's point was about someone's salary not being cut when they move. That's much less interesting than someone in Thailand getting the Bay Area salary when they're hired.

If Kraken pays the same salary for a role regardless of location when they're hiring then that's awesome. I would find that incredibly surprising though, if only because advertising a role on 50* the typical local salary would make hiring really hard because you'd be swamped with low quality applications.

Post reply on HN