Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gitlab and remote work

about.gitlab.com

Post reply on HN
Print view View original

41–50 of 214 posts

Re: Gitlab and remote work

#41

Post by mountainriver »

tapanjk wrote: post #18
mountainriver wrote: post #8

Earlier quoted context omitted.

Last I heard they were which makes them NOT a leader in remote work lol They underpay in general which is why their product is buggy

> They underpay in general which is why their product is buggy I understand the sentiment but I am not convinced that underpay is the cause of buggyness. They compete with a behemoth and it is quite a feat to stay in the game in spite of having a fraction of resources at their disposal compared to thier completion.

Yeah fair it's somewhat cultural, in that they are trying to roll out an insane number of features to best Github, but aren't building them with high quality

Re: Gitlab and remote work

#42

Post by somerandomqaguy »

cglan wrote: post #19

Their 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.

What pay was that? Last I checked Gitlab's pay for a junior QA/SDET positions was about $15,000 $30,000 more then most local Canadian tech companies pay for senior/staff level.

Re: Gitlab and remote work

#43

Post by lolinder »

arccy wrote: post #25
emerongi wrote: post #13

Earlier quoted context omitted.

It's in your own personal definition of remote work that people should be paid an universal salary. Gitlab might not be a world leader in salaries, but they might very well be a world leader in providing the best remote work environment to their employees.

can it really be "best" if you're treated unequally just because live somewhere different?

For some people, sure! There are dozens of other metrics that can be used to evaluate a remote work environment, and for a lot of people "my salary matches my coworkers" doesn't matter as long as it's a good wage relative to what they'd be able to get working in an office locally.

Re: Gitlab and remote work

#44

Post by b4je7d7wb »

lolinder wrote: post #40
chrisseaton wrote: post #34

Earlier quoted context omitted.

> 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.

Yes, but that is not a company that should be praised as world leader in remote work.

How do you expect to ever raise the standard of living in poor countries if you exploit their labor for pennies on the dollar. No different from apple and other who move manufacturing to cheap labor.

A real leader in remote work would try to be a part of the solution, not actively fight against it.

Re: Gitlab and remote work

#45

Post by b4je7d7wb »

detaro wrote: post #26
emerongi wrote: post #7

Earlier quoted context omitted.

What's the problem with that? If Gitlab is not paying top of the market salaries, then they're just going to miss out on top talent, and clearly they're fine with it. It's a free market after all, you don't have to join Gitlab.

From what I've seen the usual points of critique were/are: * "This person does the exact same work, obviously they need to be paid 30% more than you because they could afford to move close to an expensive city before applying" doesn't sound exactly fair * "We'll value your work less financially if you move somewhere cheaper (not the other way around though)" isn't particularly great * The message(s) of "You can work…

They have changed the areas to less specific. Like in Europe not individual countries and cities, but thigs like "nordic". Try paying a Norwegian and a Finn the same multiplier.

Imagine spending so much time and effort to justify paying your employees less. It makes financial sense for a public company with no soul, but I feel bad for gitlab employees.

Re: Gitlab and remote work

#46

Post by detaro »

b4je7d7wb wrote: post #45
detaro wrote: post #26

Earlier quoted context omitted.

From what I've seen the usual points of critique were/are: * "This person does the exact same work, obviously they need to be paid 30% more than you because they could afford to move close to an expensive city before applying" doesn't sound exactly fair * "We'll value your work less financially if you move somewhere cheaper (not the other way around though)" isn't particularly great * The message(s) of "You can work…

They have changed the areas to less specific. Like in Europe not individual countries and cities, but thigs like "nordic". Try paying a Norwegian and a Finn the same multiplier. Imagine spending so much time and effort to justify paying your employees less. It makes financial sense for a public company with no soul, but I feel bad for gitlab employees.

> They have changed the areas to less specific.

but with a rental-price index for local-ish area instead of trying to capture that in their regions? or total flat?!

Re: Gitlab and remote work

#47

Post by kirbypineapple »

andsoitis wrote: post #37
kirbypineapple wrote: post #22

Earlier quoted context omitted.

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.

For engineering/product etc. that's the case. Doesn't matter if you move from San Francisco to Thailand or some other low cost of living area, your pay remains the same.

Re: Gitlab and remote work

#48

Post by bastardoperator »

ROARosen wrote: post #21
belter wrote: post #2

Still 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 would you pay two people doing the same job vastly different salaries because one lives in A and the other lives in B? That's the better question to be answered. I am not bottle of coke, and neither are my colleagues, we're humans, so your analogy makes zero sense.

Re: Gitlab and remote work

#49

Post by onion2k »

kirbypineapple wrote: post #47
andsoitis wrote: post #37

Earlier quoted context omitted.

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.

For engineering/product etc. that's the case. Doesn't matter if you move from San Francisco to Thailand or some other low cost of living area, your pay remains the same.

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

Re: Gitlab and remote work

#50

Post by motoxpro »

mmaia wrote: post #30
ROARosen wrote: post #21

Earlier 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?

GitLab doesn't charge based on the location of their customers.

Never thought about this, but man, very much this.
Post reply on HN