News for hackers. Stuff that matters.
Re:GitLab acquires Gitter, will open-source the code by hamandcheese on Wednesday March 15, 2017 @02:50PM (#13878678)
Somewhat off topic, but I was once very interested in working for GitLab. According to their compensation calculator, though, I'd be making less than half what I make now (also working remotely). They ding me for living in a comparatively low cost area.

I'm surprised they are able to attract talent to achieve what they have done so far. It makes me worry somewhat about my future prospects in an increasingly globalized talent pool.

Re:GitLab acquires Gitter, will open-source the code by matthewvincent on Wednesday March 15, 2017 @03:32PM (#13879044)
I had an interesting interview with one of their recruiters in which within the first 5 minutes I was asked to agree to compensation below what their calculator (which was a part of the job posting) indicated was their pay scale for my location and that position. I was told my resume wouldn't be passed to an engineering lead until I had (in writing) agreed to the lower salary range. Liiike why even...

Edit: Didn't intend to make a scene or put anyone on blast here. Just thought the calculator was a little silly. Thanks for the responses gitlab staff.

Re:GitLab acquires Gitter, will open-source the code by sashagitlab on Wednesday March 15, 2017 @04:58PM (#13879721)
Hi Matt, I am the recruiter at GL, I've reviewed your case, and I wanted to follow up personally. I'd like to address your concern and explain our process. Since the time of your interview, we have changed the process of discussing compensation within the first 15 minutes of a conversation to the end of a phone call. We understand it's uncomfortable and sometimes awkward to talk pay when you've just met someone. Hopefully this improvement will prevent misunderstandings in the future. Secondly, we never would ask you to agree to something that is below the calculators suggestion, however your expectations based on Level, Experience, or Location may differ from the recruiter or hiring managers' assessments. We do talk about compensation early and upfront with every candidate, because we use it to guide our offers. I'm very sorry that your experience was less than ideal, and I apologize for any miscommunication that happened as a result! We are always striving to improve our process so any more details/feedback you'd like to share about your specific situation would be appreciated so our PeopleOps team can ensure this mistake isn't repeated.
Re:GitLab acquires Gitter, will open-source the code by aldarn on Wednesday March 15, 2017 @05:32PM (#13880005)
I'm not sure this really addresses the issue? Personally I actually would appreciate the upfront salary discussion as it could potentially save a lot of wasted time.

It seems to me the issue is more there was a difference in expectations between what the candidate perceived was their situation and what the recruiter believed. This is of course not uncommon, however from the sounds of it the candidate was not given an opportunity to reason their position. It could be that GitLab is simply not offering competitive renumeration based on what the candidate believed they could achieve in the same market. It could also be that GitLab undervalued the particular skill sets of the candidate. Of course the opposite may also be true.

Clearly there were differences in opinions, however by asking the candidate to sign an agreement to a specific salary based on no discussion is only going to cause issues for everyone. Either the candidate agrees, goes through the interview and decides "it's not worth it, and now there's no flexibility", they disagree and a potentially good candidate is immediately lost or they agree, take the job and feel like they are not being fairly compensated, which can have all sorts of consequences.

This is usually why the discussion happens at the end of an interview process, after the candidate has had the opportunity to demonstrate their skills and experience. Then if there is still a perception of a mismatch this can be reasoned with respect to what has previously been discussed.

> Secondly, we never would ask you to agree to something that is below the calculators suggestion, however your expectations based on Level, Experience, or Location may differ from the recruiter or hiring managers' assessments.

The candidate has clearly stated they were offered less than what the calculator suggested. It was your recruiters opinion that they did not meet the parameters entered into the calculator, however clearly the candidate believed that they did. In this case the recruiter must judge the cause of the disparity through discussion with the candidate and set expectations in terms of the results of this discussion. Again, simply telling a candidate "this is our opinion, you must agree to it" is not going to benefit anyone.

Re:GitLab acquires Gitter, will open-source the code by ernstvn on Wednesday March 15, 2017 @06:27PM (#13880461)
Just to be clear: the calculator takes Level, Experience, and Location into account. If the candidate and recruiter arrive at different numbers while typing into the calculator, then there is apparently miscommunication about one or more of those factors. But being asked to agree to something that is lower than what comes out of the calculator is just not something we do at GitLab. If it came across that way then something got lost in the communication.

Matt, since I deal with the comp calculator every now and then, if you'd like to provide more specifics of your situation, can you please email me on [email protected] ?

Re:GitLab acquires Gitter, will open-source the code by sytse on Wednesday March 15, 2017 @06:38PM (#13880540)
I want to second this, we should never ask people to agree to something below the calculator. But of course the applicant and the interviewer might disagree about the appropriate title and experience factor for a candidate.

We have to decline 200 applicants a week at GitLab. We realize that interviewing is very stressful. We send a survey afterwards to get a net promoter score. The current average is 4.2 out of 5 for people that did not sign with us. Most applicants don't fill out the survey, we're not sure how that influences results.

Re:GitLab acquires Gitter, will open-source the code by hartator on Wednesday March 15, 2017 @07:08PM (#13880781)
You are saying most people don't do the survey and I think also most would think it matters how they rate the company for their own future prospects. 4.2 is actually pretty low considering this.
Re:GitLab acquires Gitter, will open-source the code by heliostatic on Wednesday March 15, 2017 @11:41PM (#13882306)
If you're actually calculating an NPS, the non-respondents should be considered detractors for a more accurate rating. Happy to talk more if you're interested (have done a lot of this as a user researcher).
Re:GitLab acquires Gitter, will open-source the code by sytse on Thursday March 16, 2017 @12:42AM (#13882559)
Cool! Thanks for the offer for help. Can you maybe reach out to [email protected]?
Re:GitLab acquires Gitter, will open-source the code by anilgulecha on Thursday March 16, 2017 @01:18AM (#13882726)
Your calculator would probably need to be updated? I just tried it out and the difference between the locations Mumbai and Bangalore, the latter is close to 2.5x less than Mumbai (0.08 vs 0.20).

Your data-source for this is very clearly wrong.. any income/cost-of-living report for India will show that the cost of living is the same for these 2 cities.

Just FYI.

Re:GitLab acquires Gitter, will open-source the code by developer2 on Thursday March 16, 2017 @01:23AM (#13882738)
Holy crap, you've just done your company - or if you are an external recruiter, your client - a huge disservice by posting this reply. You've done nothing to assuage future candidates' concerns. You've merely confirmed that your compensation offers, and likely the entire hiring process, is driven by undesirable corporate metrics. This makes GitLab sounds seem like a company that only knows how to regurgitate HR 101 tactics. No thanks.

GitLab, diversify/improve your recruitment strategy. Why you only have "the recruiter", aka a single person heading your recruitment, rather than a group of competent personnel, is concerning. Your public image is of a medium-sized company which is already established, not a tiny startup outfit wherein all hires rely on a sole (apparently inadequate) person vetting each potential employee.

Re:GitLab acquires Gitter, will open-source the code by Perihelion on Thursday March 16, 2017 @02:04AM (#13882885)
Since the first part of your comment is addressed to Sasha I'll let her reply to it, but to address the second part:

There are multiple people involved in the hiring process here at GitLab, specifically several people who handle phone screens and resumes. The responsibility of vetting doesn't rest solely on one person and is actually a pretty collaborative process in my experience. As an example, I was able to vet every single candidate's resume myself for roles I was involved in hiring for.

Re:GitLab acquires Gitter, will open-source the code by developer2 on Thursday March 16, 2017 @02:07AM (#13882904)
With all due respect, the parent to my comment - an apparent employee at GitLab - said "I am the recruiter at GL". "The recruiter", not "a recruiter" How else is that to be interpreted? With whom does the candidate discuss compensation? This one single recruiter, or the manager of the team with whom the employee would be placed? Why does GitLab have a "recruiter", rather than an "HR employee" or "hiring manager"? The term "recruiter" generally means an external non-employee who is financially compensated for each new hire brought on board. "HR" or "hiring managers" are company employees, given a flat salary irrespective of the number or quality of hires. Which do you have?

Either way, the parent comment is full of language that raises red flags to competent developers. Personally, my first thought is "oh hell no!". It's possible that their comment is not representative of the company's effective policies, but when one perceives this kind of reply as an official stance of the company's standpoint, it is difficult to retract.

Re:GitLab acquires Gitter, will open-source the code by jabl on Thursday March 16, 2017 @03:51AM (#13883280)
> With all due respect, the parent to my comment - an apparent employee at GitLab - said "I am the recruiter at GL". "The recruiter", not "a recruiter" How else is that to be interpreted?

The way I understood it, at least, was 'the recruiter who handled the interview with "matthewvincent"'. Doesn't imply that there are, or are not, other recruiters at gitlab.

And if so, at least to me it seems honest for said recruiter to come forwards personally, instead of some feel-good mumbo-jumbo from the PR department.

Re:GitLab acquires Gitter, will open-source the code by jospoortvliet on Monday March 27, 2017 @02:16PM (#13970245)
I'd LOVE to hear what red flags are in the comment from the recruiter or the other person - whom I guess is a manager. I've re-read it a few times but I see nothing but reasonableness. Then again, I'm neither a developer myself (does that make a difference) nor a recruiter...
Re:GitLab acquires Gitter, will open-source the code by bartread on Friday March 17, 2017 @05:07AM (#13892573)
Speaking from the candidate's perspective, I tend to avoid companies where money is discussed upfront. I want to be able to demonstrate the value I can add, and then have a negotiation about remuneration based on that value.

Bluntly, yes, it does put the candidate in a much stronger negotiating position but, hey, if you really want to hire good people then I'm afraid it's hard cheese. Conversely talking about remuneration upfront puts the candidate on the back foot because there's substantially less of a basis for convincing negotiation, so it really becomes about cutting costs for the company.

Unless you absolutely have to - sometimes you might not have any other option, and you shouldn't let pride blind you to that reality when you're facing it - I'd always recommend you avoid working for anyone where you've had to discuss money first.

Re:GitLab acquires Gitter, will open-source the code by developer2 on Saturday March 18, 2017 @01:15AM (#13900016)
The discussion of compensation is an extremely simple concept: you wait for the candidate to bring it up, and you discuss it only at that point in time. The interviewer should never bring up compensation before the candidate does, unless the potential employee is so shy that they are waiting for the employer to do so first. The moment an employer tries to pre-emptively bring up the topic of money before it makes sense, it shows their true colors - they care far too much about the money rather than the talent they are hiring.

It really is that basic. When the company cares more about the money than what the employee can bring, they've shown their company cares more about their internal politics then they do about their future success. Simple as that.

Re:GitLab acquires Gitter, will open-source the code by paulddraper on Wednesday March 15, 2017 @10:32PM (#13881930)
I don't understand. Why does Location matter? Does it matter if have 10 kids, or a lease on a Porsche, or 2 alimonies, or live in a McMansion, or my kid has cancer? Are those factors relevant? What makes Location special?
Re:GitLab acquires Gitter, will open-source the code by hisham_hm on Thursday March 16, 2017 @12:07AM (#13882410)
Because not all jobs are remote, so local jobs make up for a considerable amount of the job pool. For this reason, it's easier to get another job at your current location, so that's the competition the employer is faced with. If you live in an expensive area they're not paying you more to help you, they're paying you more to be more competitive with other companies in your area.
Re:GitLab acquires Gitter, will open-source the code by segmondy on Thursday March 16, 2017 @12:30AM (#13882512)
This line of argument is ridiculous. Are software companies pricing their computer programs based on location? Do folks in Ohio get to pay less than folks in New York?

What if you hire a great remote developer who lives in San-Jose, then she moves to Kentucky 6 months later, and their contribution is still the same. Why should their pay be adjusted?

Re:GitLab acquires Gitter, will open-source the code by fatal510 on Thursday March 16, 2017 @12:57AM (#13882636)
Because a huge factor of pay is cost of living. The only reason people in San Jose are getting paid so much is because they are in San Jose and could not survive otherwise.

> Are software companies pricing their computer programs based on location? Do folks in Ohio get to pay less than folks in New York?

Yes?

Re:GitLab acquires Gitter, will open-source the code by a_imho on Thursday March 16, 2017 @04:57AM (#13883526)
I would like to repeat this comment here:

This is the sentiment I usually see but how are one's expenses or expected living standard is relevant regarding compensation for work? Imo it is very hard to argue against equal work => equal pay. At least from a moral pov.

Btw that is a lot of incorrect assumptions about expenses, including where someone's children might want to go to college, globally fixed costs like work equipment and cloud services, not to mention goods which are actually cheaper in the US.

Re:GitLab acquires Gitter, will open-source the code by stephenr on Thursday March 16, 2017 @08:23AM (#13884407)
> Yes?

Since when? I'm pretty sure I've never seen any variation in software prices except international variances, which are most often a case of with/without tax and currency fluctuations.

Re:GitLab acquires Gitter, will open-source the code by 59nadir on Thursday March 16, 2017 @10:22AM (#13885214)
I think he simply read that as "Do they pay less (for living)?" and not that they pay less for software. No one could seriously think that you pay less for software based on your location, compared to other people in the same region/country.
Re:GitLab acquires Gitter, will open-source the code by stephenr on Thursday March 16, 2017 @11:38AM (#13885897)
S/He quoted the whole thing:

> > Are software companies pricing their computer programs based on location? Do folks in Ohio get to pay less than folks in New York?

> Yes?

Re:GitLab acquires Gitter, will open-source the code by storafrid on Saturday March 18, 2017 @06:16AM (#13900678)
Yes, he did, unfortunately. Gasp. The humanity. Now get over it. You understand that he meant paying less for a flat, not for an OS. So stop pretending and go on with replying that you still think it's wrong to base the compensation on the location's living expenses, for whatever other new reason that you now need to come up with.
Re:GitLab acquires Gitter, will open-source the code by stephenr on Saturday March 18, 2017 @06:57AM (#13900760)
> You understand that he meant paying less for a flat

No. If I understood that, I wouldn't have replied as I did, would I now?

> go on with replying that you still think it's wrong to base the compensation on the location's living expenses

But why is it a location's living expenses? If a company is paying people to work remotely, location should have zero impact on remuneration: they aren't asking you to live anywhere specific, so there is no business reason to use location as a cost factor.

Re:GitLab acquires Gitter, will open-source the code by storafrid on Saturday March 18, 2017 @05:03PM (#13903512)
I'm not hearing a counter-argument. The company needs to get good people to work for them. And this is a way of getting someone from a high-cost location to work for them. If the location's higher living expenses aren't covered for, the person would be unable to take the job. I don't know if you mean that the company should adjust their lowest pay according to the world's most expensive location, but that would probably not sustain the business.
Re:GitLab acquires Gitter, will open-source the code by stephenr on Sunday March 19, 2017 @11:37AM (#13907710)
> this is a way of getting someone from a high-cost location to work for them

Why is that a requirement? Do you somehow think the Bay Area has a monopoly on good developers?

Re:GitLab acquires Gitter, will open-source the code by storafrid on Tuesday March 21, 2017 @10:45AM (#13922591)
If the company finds a person that they want to recruit, and that person happen to live in a high-cost location, they will need to pay up in order for the recruitment to happen. The only alternative would be to offer relocation to a lower-cost region. It doesn't have anything to do with any requirement. It's just a result from the way the world works.
Re:GitLab acquires Gitter, will open-source the code by stephenr on Tuesday March 21, 2017 @11:10AM (#13922853)
Given that most people aren't hired that way, it's more like:

If a person wants to work for the company but their offered salary isn't high enough to sustain a high cost of living environment, the person will need to either move or find another job.

The company has literally the entire world to find staff - that's the whole point of remote workers.

Re:GitLab acquires Gitter, will open-source the code by jospoortvliet on Monday March 27, 2017 @02:42PM (#13970488)
True. Still, I think most companies will take cost of living in the area where the potential employee lives into account. When thinking about it it seems odd, indeed. I guess it is kind of normal and expected. But entirely rational it is not.
Re:GitLab acquires Gitter, will open-source the code by paulddraper on Thursday March 16, 2017 @01:02AM (#13882657)
GitLab has made a big deal about working remotely; I thought that's what they did. https://about.gitlab.com/2015/04/08/the-remote-manifesto/
Re:GitLab acquires Gitter, will open-source the code by stephenr on Thursday March 16, 2017 @08:02AM (#13884292)
> not all jobs are remote

GitLab claims to be "Remote Only": https://about.gitlab.com/jobs/

Re:GitLab acquires Gitter, will open-source the code by jobvandervoort on Thursday March 16, 2017 @08:15AM (#13884371)
That's correct. We don't have any offices. You're free to work from home, a coworking space (by our expense) or anywhere else, but there's no GitLab office.

We have a 'headquarters', which is also where Sytse (CEO) lives, where there are a number of desks available for special occasions, but no one is ever required to work from a particular place.

Re:GitLab acquires Gitter, will open-source the code by stephenr on Thursday March 16, 2017 @08:21AM (#13884398)
So, to quote the original post that prompted the theory about "not all jobs are remote", which I then replied to:

> Why does Location matter? Does it matter if have 10 kids, or a lease on a Porsche, or 2 alimonies, or live in a McMansion, or my kid has cancer? Are those factors relevant? What makes Location special?

Re:GitLab acquires Gitter, will open-source the code by a_imho on Thursday March 16, 2017 @04:28AM (#13883412)
It does not matter how big you are on equal opportunities, work and compensation, when you can use your (cherrypicked) metrics to point your fingers at the market regarding salary discrimination, it would be irresponsible not to do so. Put it another way, if it was legal to discriminate against <underprivileged group> companies would be all over it.

PS it is not about GitLab, I like their service (even better than GitHub) and it is great they are transparent about compensations. IMO if they were to eliminate location from their calculator they could get the cream of a very big talent pool.

Re:GitLab acquires Gitter, will open-source the code by methyl on Wednesday March 15, 2017 @11:33PM (#13882262)
Especially for remote position when you can live wherever you can imagine.
Re:GitLab acquires Gitter, will open-source the code by chejazi on Wednesday March 15, 2017 @05:38PM (#13880050)
This response is quite in the style of the Yelp/TripAdvisor response to a negative review. A thin veneer of consolation around an attempt to save face.
Re:GitLab acquires Gitter, will open-source the code by scrollaway on Wednesday March 15, 2017 @06:33PM (#13880506)
It looks like a perfectly reasonable response to me. What face is there to save? The fact that this was brought up "within the first five minutes" is far better than "after a plethora of interviews".

I had an interview with Parsely a few years back. Took over 3 weeks of back & forth before they rejected me with a reason that should have been squashed the first hour of the interview.

Re:GitLab acquires Gitter, will open-source the code by ianleeclark on Wednesday March 15, 2017 @05:47PM (#13880123)
Agreed, the underlying process is still there.
Re:GitLab acquires Gitter, will open-source the code by Cpoll on Thursday March 16, 2017 @10:23AM (#13885227)
> Since the time of your interview, we have changed the process of discussing compensation within the first 15 minutes of a conversation to the end of a phone call.

Cynical read: We discovered people are more likely to compromise on the salary if they've already committed their time to the interview.

Re:GitLab acquires Gitter, will open-source the code by connorshea on Wednesday March 15, 2017 @04:02PM (#13879287)
Sorry this happened to you, I’ve brought it up with our PeopleOps team and we’re looking into it. Something like this absolutely shouldn’t be happening.

If you have any more information you can share, it'd be great if you could send it to peopleops at gitlab.com.

Re:GitLab acquires Gitter, will open-source the code by s_kilk on Wednesday March 15, 2017 @03:46PM (#13879165)
That all sounds kinda weird and sketchy, like the recruiter had a strange hidden motive.
Re:GitLab acquires Gitter, will open-source the code by rixrix on Wednesday March 15, 2017 @04:41PM (#13879575)
be nice this is my first comment in Hacker News :D

Interestingly issues gets noticed here!, there was a posting yesterday about FB hiring issue.

Re:GitLab acquires Gitter, will open-source the code by ezekg on Wednesday March 15, 2017 @03:43PM (#13879132)
Agreed. I actually had a good time interviewing with them. I'm not sure if it was normal, but it was essentially a 2 week email thread with a few GitLab devs asking me to explain various architectural parts of their system. I had fun diving into their system and getting to know it, including a few of their Go projects like workhorse, but I stopped the process after being told I couldn't ask for more than $60,000 for the position. Cool company, but the pay is just too low.
Re:GitLab acquires Gitter, will open-source the code by ianbicking on Wednesday March 15, 2017 @07:42PM (#13881004)
I feel a little bad contributing to such a very off-topic thread, but...

I'm familiar with how compensation is determined at Mozilla, and we use something similar but with different inputs. GitLab seems to be using rents as their determiner with New York as a baseline, which means way underpaying people in most markets. If they adjusted those numbers by the average percentage of income applied to rent (I believe a readily available number) then the numbers might be more reasonable.

At Mozilla we have a smaller number of regions, I think it's each nation plus three tiers in the U.S.: Bay Area/New York, Chicago/Seattle (not sure what all is in this bucket), and the rest of the country. Then we get data from some company that provides us with market rates for different given titles. We target salaries at the top 25th percentile (not a 25% bump like GitLab).

So given a title, people's compensation is figured as somewhere between 0.8x and 1.2x that market rate, depending where you are in your career. Each level bump is about 1.2x the previous level. So typically you might enter a Senior Engineer role at maybe 0.85x the compensation, and as you grow into the role you get to 1.0, and as you are approaching the next level you get into the 1.1s.

I think it's a pretty fair process. Especially internationally you can't relate salaries to each other well given different labor laws and taxes. Assuming our input numbers are right, our compensation is by definition competitive across markets – though in practice all sorts of weird things can happen over an employment history, like when a person moves.

All that said, it's clear we get a better value from people in cheaper markets, even while those people in practice also get a better value in terms of compensation. So far that hasn't been met with any adjustment in compensation, but instead some acknowledgement of the dynamic during recruitment.

Re:GitLab acquires Gitter, will open-source the code by kilroy123 on Wednesday March 15, 2017 @02:52PM (#13878701)
I'm also turned off by remote companies that do the same. I work remote and moved to a very low-cost area. That doesn't mean I want a massive pay cut.
Re:GitLab acquires Gitter, will open-source the code by usrusr on Wednesday March 15, 2017 @05:40PM (#13880069)
I guess if you are a remote friendly employer, you'd want to avoid both cutting yourself off from talent that happens to live in a high-cost area and getting completely overrun by applications from low-cost areas. And that could be reason enough even before applying the most obvious rule of acquisition, "don't pay more than you need".

But yeah, the outcome, remoters from Cheaptown effectively subsidizing their coworkers from Glitter City is incredibly ugly. One should at least hope that the decisionmaking processes at the employer do not completely isolate the one deciding on a hire from the cost difference, so that flyover guy could at least enjoy an increased chance of getting the job.

Re:GitLab acquires Gitter, will open-source the code by duncan_bayne on Wednesday March 15, 2017 @04:39PM (#13879555)
"From each according to his ability, to each according to his need" is a bad principle to run both countries and companies.
Re:GitLab acquires Gitter, will open-source the code by Yahivin on Wednesday March 15, 2017 @05:08PM (#13879801)
Why should we run countries like companies?
Re:GitLab acquires Gitter, will open-source the code by Ellahn on Wednesday March 15, 2017 @05:29PM (#13879967)
That was never said, we obviously shouldn't.

Finding something that applies to both (Or in this case something that works in neither, which makes it even clearer) is not the same as treating both as requiring the same solutions.

Re:GitLab acquires Gitter, will open-source the code by megablast on Wednesday March 15, 2017 @08:23PM (#13881238)
What is the advantage to the company in hiring remote workers then?

You want your cake and to eat it too?

Re:GitLab acquires Gitter, will open-source the code by stonith on Wednesday March 15, 2017 @10:25PM (#13881889)
Access to talent in locations where there aren't offices + access to talent who only work remotely.
Re:GitLab acquires Gitter, will open-source the code by onion2k on Thursday March 16, 2017 @11:24AM (#13885751)
So you seem to think a Bay Area company should pay it's remote workers Bay Area money. That'd be lovely, but we should explore what it infers. Let's assume that Gitlab will open a Mumbai office in a month's time. Would you expect the people there to get typical Mumbai wages, or typical Bay Area wages?

Assuming you don't think it's Bay Area wages (because that's crazy), why do you think going to an office in your location means you ought to be paid a lot less?

Re:GitLab acquires Gitter, will open-source the code by jsudhams on Thursday March 16, 2017 @12:23PM (#13886301)
Some of us get Bay Area salary in hyderabad and bangalore. Why should we not get bay area salary when we deliver the same or better. I have no control over my cost of living but i do control what i will work for. No matter where.
Re:GitLab acquires Gitter, will open-source the code by stephenr on Thursday March 16, 2017 @08:05AM (#13884306)
Getting the best staff and not having to provide an office?
Re:GitLab acquires Gitter, will open-source the code by yellowapple on Thursday March 16, 2017 @02:08AM (#13882909)
Not having to deal with operating a physical office (beyond the bare minimum necessary to e.g. be served with a subpoena)?
Re:GitLab acquires Gitter, will open-source the code by fbuilesv on Wednesday March 15, 2017 @08:26PM (#13881259)
Using the GitLab calculator: If you are a developer in Medellín you are paid 3x less than if you are living in the Bay Area. If you are a customer in Medellín you pay the same as a customer in the Bay Area. In this case, "cost of living"[0] only applies to employees and not customers, which in my opinion says a lot about how much the company values their staff.

I appreciate the openness from GitLab on this matter though, they're pretty up-front about it so if you don't like it don't apply.

[0] When the word "cost of living" is mentioned but it's not reflected in the price for final users then you know you're about to get fucked.

Re:GitLab acquires Gitter, will open-source the code by webo on Wednesday March 15, 2017 @03:20PM (#13878936)
Senior Backend Engineer shows 85-95k in Chicago, which is below average. It shows 45-55k for Fayetteville -- most junior guys/gals start around 75k in Fayetteville at mediocre companies.
Re:GitLab acquires Gitter, will open-source the code by graton on Wednesday March 15, 2017 @04:32PM (#13879509)
Yeah, similar for me. In my geo it shows ~87-98K, but if I moved to San Francisco it is ~173-189K. Which seems foolish. They should incentivize people to move to the lower costs geos, not penalize them.

And the listed salary for my geo is about 2/3 to 3/4 of my current base pay before any bonuses. The idea of the company sounds good, but the pay is a deal breaker for me. I wouldn't like feeling like I'm providing the company more value but because the person lives in San Francisco they get twice as much pay. Maybe that is me being petty?

Re:GitLab acquires Gitter, will open-source the code by ghostly_s on Wednesday March 15, 2017 @07:25PM (#13880897)
They're not trying to incentivize people to move to SF; they're trying to maintain a competitive hold on the market of talent which is already there, as the realities of our current climate are that many of the highest-talent candidates are to be found in that pool.
Re:GitLab acquires Gitter, will open-source the code by majormajor on Wednesday March 15, 2017 @07:35PM (#13880958)
If they're ok with people working remotely, they'd do much better to pay everyone as if they lived in a very expensive area, and attract all the people who don't want to give up a lot of the flexibility of a large paycheck but would love to be able to save even more of it by living somewhere cheaper.

(Their calculator also seems somewhat bonkers (on the extremely low side) compared to the local market where I live. It seems based on a somewhat-arbitrary, quick-and-dirty-wild-guess estimate formula vs what real, on-the-ground competitor companies in those areas are paying.)

EDIT: there seems to be a small trend emerging where every company I've seen with fully-public payscales/pay calculators wildly comes in below what I'm currently making, and what I've heard from local competitors. And I'm not in SF. Wonder if there's some causality there, though it's still just a handful.

Also it's amusing to get a downvote for offering up the info that Gitlab would want me to take a pretty substantial ~30% haircut in base pay based on where I live. What would be attractive to me would be "we'll give you 80% of your current take-home, but you get to live wherever you want," but this is basically the opposite.

Re:GitLab acquires Gitter, will open-source the code by onion2k on Thursday March 16, 2017 @11:26AM (#13885772)
I get $45k - $48k which would actually be about a 50% pay rise for me. UK wages outside of London really do suck.
Re:GitLab acquires Gitter, will open-source the code by guitarsteve on Wednesday March 15, 2017 @03:32PM (#13879047)
So you could get double your pay by moving from Chicago to San Francisco, or multiply by 6 if you move from Fayetteville to San Francisco.

Seems backwards to have such a large incentive to live somewhere more expensive.

Re:GitLab acquires Gitter, will open-source the code by lrem on Thursday March 16, 2017 @06:30AM (#13883909)
Unfortunately, this is the common practice - offer salaries adjusted for the local market. I could keep my current job and move to an office 1500km closer to my parents, but my salary would be slashed in half, because market. But it's pretty funny for remote workers: what if you get hired in SF, but then move to Fayetteville without telling anyone?
Re:GitLab acquires Gitter, will open-source the code by webo on Thursday March 16, 2017 @11:02AM (#13885540)
As long as you keep paying taxes in CA, I imagine this is not an uncommon practice.
Re:GitLab acquires Gitter, will open-source the code by ravitation on Wednesday March 15, 2017 @03:41PM (#13879119)
Yep, this seems to be a major flaw in their compensation calculator. If you don't live in a high rent, hot bed, you end up with a compensation package that is very (i.e. laughably) low.

A lead (maximum seniority), with high (maximum) experience, in Fayetteville, AR makes less than most junior developers (60k-68k)...

Re:GitLab acquires Gitter, will open-source the code by godelski on Wednesday March 15, 2017 @06:59PM (#13880723)
I used a cost of living calculator[1] and compared it to theirs. Found the numbers don't match up. Just matched Nashville vs SF and the low end of Nashville was higher than the low end of SF (-3000 SF dollars) but the high end of Nashville was lower than the high end of SF (+3000 SF dollars).

[1] I've found this calculator to be decently accurate http://www.bankrate.com/calculators/savings/moving-cost-of-l...

Re:GitLab acquires Gitter, will open-source the code by mbesto on Wednesday March 15, 2017 @11:22PM (#13882217)
Simple solution. Don't work there. If they can attract talent at that price then good for them.
Re:GitLab acquires Gitter, will open-source the code by yellowapple on Thursday March 16, 2017 @01:57PM (#13887245)
Same deal in Sacramento; it'd be more cost-effective (even factoring in time and cost of transportation) to just commute to the Bay Area, which quite a few people already do.
Re:GitLab acquires Gitter, will open-source the code by Lazare on Wednesday March 15, 2017 @07:03PM (#13880746)
The concept of the calculator is very strong, but I don't think they've implemented it well.

It seems obvious to me that they should be paying relatively more to people in cheap locations than expensive ones. That saves Gitlab money, biases their hiring to people in cheaper areas, incentivizes people to move to cheaper areas, helps cool down the overheated housing markets in expensive areas.

I can see drawbacks to paying a strict flat amount regardless of local cost of living; some adjustments probably make sense. But Gitlab seems to be doing the opposite. I don't get it.

Re:GitLab acquires Gitter, will open-source the code by gedrap on Thursday March 16, 2017 @07:31AM (#13884145)
The problem with GitLab's calculator is that it's simply... too ambitious. They try to calculate the salary for pretty much every somewhat major city in the world and it's simply impossible. You can't capture the details of so many different local economies.

For example, when I lived in England, the difference between rent for a room in a shared house outside city center and a 1 bedroom apartment in the city center was usually at most 100% (excluding the very top and very bottom of the ranges). Meanwhile in Lithuania, where I live at the moment, the difference is about 6 times. You can't capture this in a calculator with such broad coverage.

Approach by mozilla (https://news.ycombinator.com/item?id=13881004) seems much more reasonable to me, to be honest.

Re:GitLab acquires Gitter, will open-source the code by cookiecaper on Wednesday March 15, 2017 @03:11PM (#13878868)
They're not really able to attract much talent. Look through the LinkedIn of some of the GitLab people. A lot of them are very junior (this is the first "real job" for one guy I looked up), and they, rather clearly, have an amateur leadership team, as exhibited by their recent spectacular failures, their underwhelming commentary on remote team management, their naive idealistic implementation of "radical transparency", and their grossly inadequate compensation calculator.

Most likely, one of their founders is technically adept, there are a small number of other experienced people onboard because they incidentally live in areas where the compensation calculator doesn't screw them, and most others are riding on those coattails.

GitLab is really a sad story of lost potential. Most of the time, you can't fix these kinds of problems, because they start at the top and flow down (and you usually can't replace the top). A well-engineered GitLab alternative would be welcome.

Re:GitLab acquires Gitter, will open-source the code by utku_karatas2 on Wednesday March 15, 2017 @05:43PM (#13880088)
That's one hell of a pessimistic view if I've ever seen one.

What I see is an brilliantly managed company despite having a globally distributed team, which has a great pace of development, which is carving a nice market share in an extremely tough market (developers) and against a fierce competitor (Github), let alone the other multibillion company backed Bitbucket.

And their radical transparency, as you put it, is a fascinating thing in and of itself. If anything it makes me feel intimate with the company. Hard to put it in words, maybe because I was a rather early adopter but if you follow them closely it's a like you're there on their board with spectator mode on. That's some invaluable experience for HN crowd.

Are we even talking about the same company?!

Re:GitLab acquires Gitter, will open-source the code by cookiecaper on Wednesday March 15, 2017 @07:40PM (#13880988)
Is the company "brilliantly managed" because they still exist? What is an example of this management brilliance? At this point, all the company has proven is that it is able to convince investors to give it money. I see a bloated company with over 100 underpaid junior-level engineers putting out subpar software.

The radical transparency may be a fun experiment and it may provide a lot of interesting data to parse, but it's not a good way to run a real company. It screams of impractical idealism. A lot of companies are bad, but GitLab wants to make sure that you know they're bad from a distance. In theory this is all great and nice. In practice, it hurts the company in both commerce and recruiting.

Re:GitLab acquires Gitter, will open-source the code by aaron-lebo on Wednesday March 15, 2017 @06:11PM (#13880332)
The truth is probably somewhere in the middle.

How do you get "brilliantly managed company" when they just had a massive data loss? How can you say that honestly?

Re:GitLab acquires Gitter, will open-source the code by lox on Wednesday March 15, 2017 @06:41PM (#13880564)
Is there a strong correlation between company management and ops practice?
Re:GitLab acquires Gitter, will open-source the code by aaron-lebo on Wednesday March 15, 2017 @06:43PM (#13880583)
Especially for small companies, I'd hope so. If management isn't even aware that they've got data backup issues, they're missing valuable information, yeah?

My boss makes sure I backup stuff...and we're not taking on millions of dollars in funding and customers.

Re:GitLab acquires Gitter, will open-source the code by the_common_man on Wednesday March 15, 2017 @03:35PM (#13879076)
Not sure I entirely agree but I do feel GitLab is caught up now in the hyper-growth circle like every other startup :/ If the enterprise angle does not work out, there is no backup plan. They compete against GitHub and Atlassian in this space and can only grow so much (but VCs was never ending growth).
Re:GitLab acquires Gitter, will open-source the code by elygre on Wednesday March 15, 2017 @05:29PM (#13879968)
I can't be bothered to bother that GitLab has junior people, even to the extend that it's the first "real job" for some of them. We hire people for their first "real job" all the time -- someone has to!
Re:GitLab acquires Gitter, will open-source the code by cookiecaper on Wednesday March 15, 2017 @05:50PM (#13880149)
Of course, the problem is not that some people are junior. The problem is that most people are junior, because, ironically, unless you live in one of the most expensive cities on the planet, their compensation is not commensurate with what an experienced developer can make in any first-world market.

When you have an inexperienced crew running your tech, you get a lot of very preventable issues, which sometimes approach apocalyptic scale (like GitLab's February data loss). That's fine for some businesses, but it shouldn't be fine for something as important as GitLab.

Re:GitLab acquires Gitter, will open-source the code by yuhong on Wednesday March 15, 2017 @03:17PM (#13878915)
Are there evidence that the founders are not willing to learn or something like that.
Re:GitLab acquires Gitter, will open-source the code by cookiecaper on Wednesday March 15, 2017 @07:56PM (#13881076)
Just the fact that they've been around a long time now, and are still like they are.
Re:GitLab acquires Gitter, will open-source the code by ultimatejs on Wednesday March 15, 2017 @05:49PM (#13880144)
Um ok. What's actually wrong with the product? Why is it not "well-engineered"? All the things you said could be true, yet their product is amazing. I haven't used it, but I like what I'm seeing.

So what if a smart experienced developer (their CTO) is able to get good prices on what he/she wants done through remote work? The point you're making is negativity for no reason without evidence on how it's not working, i.e. what's wrong with their product.

Re:GitLab acquires Gitter, will open-source the code by cookiecaper on Wednesday March 15, 2017 @07:49PM (#13881035)
It doesn't take much investigation to start seeing problems, or to see major lapses in engineering from both a concrete (e.g., bugs) and a process (e.g., data loss) perspective. The data loss event that made it clear that GitLab a) never tested its backups b) didn't have a real monitoring/alarming system to inform its employees when things broke c) did not have processes enforcing clear separation between production environments and d) did not know how to configure a PostgreSQL cluster, among many other basic flaws, is just one recent example. The postmortem for that event included the accidental disclosure of a serious DoS exploit, itself the symptom of poor engineering practice (hard-deleting all content flagged as spam, making it impossible to redeem erroneously targeted content; a user could maliciously trigger such deletes with minor effort), which was live on the site until a couple of hours after that disclosure was discussed on HN. As I understand the ticket explaining this, the entire spam cleanup system was shut off until they could teach it not to hard delete anymore. Many other junior-level mistakes are regularly discovered and discussed, both on their bug tracker and elsewhere.

Other than that, GitLab is a beast to install and navigate and it requires a lot of resources. Rails is slow. The UI is weird (frequently end up not finding the repo I want due to the way the "trending" tab works). There are other issues. I'm not a GitLab contributor so I don't really have more technical detail, I just use it sometimes.

It seems like you're just assuming they're a great company with a well-engineered product because you like the corporate image they project.

I don't know of anything about them that makes either themselves or their product "amazing". It is somewhat usable, which is good; I'm not trying to besmirch the earnest efforts of people to make something that works, and indeed there are some uses for something like GitLab. That doesn't mean that GitLab is "amazing" or that their product is flawless or even good.

The most exciting thing about GitLab to me is remotely distributed teams, which I usually love seeing, but I think they've gone about it all wrong.

Re:GitLab acquires Gitter, will open-source the code by aaron-lebo on Wednesday March 15, 2017 @06:14PM (#13880355)
Shouldn't you use the software before calling it amazing?

Your reflexive defense isn't any more useful than extreme criticism.

Re:GitLab acquires Gitter, will open-source the code by ultimatejs on Wednesday March 15, 2017 @06:22PM (#13880415)
I didn't say it was amazing. Perhaps you are the one being reflexive.

I wrote:

"All the things you said could be true, yet their product [could be] amazing."

Grammatically, it's called "elliptical." I then immediately say: "I haven't used it, but I like what I'm seeing"--so what I meant should be quite obvious.

What value are you adding with your criticism of what--in my case--at least has a question:

"What's actually wrong with the product? Why is it not 'well-engineered'?"

My point was extremely clear--his post needed to have evidence of how their processes results in bad product. And I asked that as a question--perhaps you know? Something tells me you even do (perhaps you're a Gitlab user), yet you're choosing to take an unproductive meta route of criticizing my partial criticism with no actual goal. What do you expect to accomplish with that?

I presume you got stuck on one word ("amazing"), made up your mind and didn't read the rest. My bad, i could have been more clear. However, the essence of what I was saying was straightforward, but you chose to see the forrest instead of the trees. A common reason people take that route is because there is something else you wished to express, but didn't--perhaps you have real experience with gitlab in one way or another that resonates more with the person's viewpoint I replied to. I'm not saying he's wrong--I just would like to hear the full reasoning behind that perspective.

I'd love to hear what that actual perspective is. Gitlab is an interesting product I haven't spent much time reviewing until today. Maybe you can provide the evidence to back up the original poster's point??

Re:GitLab acquires Gitter, will open-source the code by aaron-lebo on Wednesday March 15, 2017 @06:40PM (#13880554)
You can find out if their product is amazing by creating an account and using the software. It takes ten minutes, less time than it takes for you to type up that post. The original poster shouldn't have to explain to you how good the software is when you can try it. If you haven't used it his criticisms of the product aren't going to be useful to you anyway.

I haven't used it, but I like what I'm seeing

If you're just talking about what you're seeing, you have the same vantage point as everyone else and the original poster made a number of obvious and valid criticisms - data loss is one, they are selling software and a service.

It probably is trolling on my part, but as harsh as the original poster's words were, he's got some points.

Re:GitLab acquires Gitter, will open-source the code by ultimatejs on Wednesday March 15, 2017 @06:57PM (#13880702)
The data loss event that happened--to me--isn't enough to describe the quality of their product. I could go try it, but it's a few hours in (if not a weekend) to really get answers that someone experienced could provide in 3-5 bullet points.

I guess we have one bullet point, do we have more?

Re:GitLab acquires Gitter, will open-source the code by was_boring on Wednesday March 15, 2017 @10:08PM (#13881796)
I'm happy this comes up in every thread about gitlab, and that they appear to read them. I'm hoping one day someone on the team says "you know, they're right, we should do something about this."

Just to throw my example in, they would want to pay me at least 20% less than what I currently make -- and I'm already a 100% remote employee working for a financially stable startup. What they offer is simply not even close to market value -- yet they claim it is. In this case it's the D.C. area.

Re:GitLab acquires Gitter, will open-source the code by tedmiston on Wednesday March 15, 2017 @04:04PM (#13879296)
This has been discussed quite a bit on HN in the past with the general sentiment that their calculator is very off from the market in the US.
Re:GitLab acquires Gitter, will open-source the code by taude on Wednesday March 15, 2017 @05:59PM (#13880240)
In reading all these responses about the low GitLab pay calculator, does anyone have any good tips on how to underpay and still hire talent. It's pretty incredible to me.
Re:GitLab acquires Gitter, will open-source the code by mikekchar on Wednesday March 15, 2017 @10:13PM (#13881825)
I've worked in several jobs where I've thought, "If I'm going to have to put up with this BS, they're going to have to pay me a lot more". And the funny thing is, often times they are willing to pay you more if you ask. So there have been times in my career where I've been miserable pretty much exactly because I decided to work in a really stressful environment while accepting a large salary.

As I get older, I'm not really that interested in putting up with the BS. So if I work in an environment without the BS, or if I have a boss who is willing to shield me from the BS, I'm very happy to pay for it.

Actually, there are tons of things I'll pay for. Remote working on a team that knows how to do it and respects remote workers? That's a big discount. A work process that allows me to work effectively in a different timezone or with flexible hours? Another discount. Guarantee that the work I'm doing will be released with a free software license? HUGE discount (really, huge). Working with interesting and talented people? Yep, discount. No inventions agreement? DISCOUNT.

You get the picture. Hell, I'll do a fair amount of work for free if you tick all the boxes. I'm nowhere near alone in this.

Edit: grammar... :-P

Re:GitLab acquires Gitter, will open-source the code by taude on Thursday March 16, 2017 @11:42AM (#13885932)
At what point do you discount your skills so much that you can't afford to save for kid's education, retirements savings, etc, though.

In looking at those GitLab pay scales, it's a pretty SEVERE pay cut for all but the most junior people. I'm not sure I'd be comfortable with a 50% pay cut to do "something cool".

Re:GitLab acquires Gitter, will open-source the code by mikekchar on Friday March 17, 2017 @12:23AM (#13891475)
From Wikipedia: The U.S. Census Bureau reported in September 2016 that real median household income was $55,775 in 2015.

If you scroll down to education and look at the chart for education, you will see that the median household income for someone with a bachelor's degree is $68,728. With a professional degree (like a P.Eng) it's up to $100K.

Can you afford to save for your kid's education, retirement savings, etc on the median household income in the US? That depends a lot on your lifestyle. It certainly is possible.

I'm not going to tell you what's good for you. I'm just saying that there are people (myself included) who can live comfortably on less and who value things other than money when accepting a job. I was simply answering the question that was asked: How is it possible to hire quality people while paying below market rate? By making it worth the reduction in pay. Whether or not Gitlab succeeds in doing this, I have no idea.

Re:GitLab acquires Gitter, will open-source the code by marktangotango on Wednesday March 15, 2017 @07:43PM (#13881010)
Hire entry level and train them. Have a kick ass culture so they want to stay. Preposterous I know. I've seen it once. In reality, job hoppers are the minority I've found.
Re:GitLab acquires Gitter, will open-source the code by taude on Wednesday March 15, 2017 @08:00PM (#13881099)
Is a lot of their workforce remote? Because I imagine that would influence the lack of job-hopping.
Re:GitLab acquires Gitter, will open-source the code by leesalminen on Wednesday March 15, 2017 @06:27PM (#13880465)
It's really hard. I haven't found a way to do it successfully yet. I think a lot of it depends on the "coolness" factor. Also interested to hear from anyone who has done it successfully.
Re:GitLab acquires Gitter, will open-source the code by barrkel on Wednesday March 15, 2017 @07:55PM (#13881069)
The trouble with this kind of calculator is that it fails to take into account the global opportunities that the higher end of the talent distribution has. Salaries to retain highly skilled people in cheap locations don't have as large a discount; not only does the salary need to compete against other employers in the area, it also needs to compete against moving to a better market.

Top end salaries will still be discounted, naturally, because the costs in high cost areas are real. But not every scales like housing.

Re:GitLab acquires Gitter, will open-source the code by redbeard0x0a on Wednesday March 15, 2017 @08:47PM (#13881373)
Yeah, the calculator seems to cause some weird things.

Living in Seattle, WA, the salary range I used topped out at ~$120k. However, 30 miles south in Tacoma it tops out at at ~$80k. Moving to Dallas would move the top of the range to ~$105k (Hot Market Adjustment?! but not Seattle?!).

Values I used (I rounded the salary up too): * Lead * Above Average Experience * United States * Dallas, Seattle and Tacoma.

I'm looking to move to the Dallas area (from Tacoma) and my rent will likely end up being less in Dallas (at least 20%).

Re:GitLab acquires Gitter, will open-source the code by anderber on Thursday March 16, 2017 @10:01AM (#13885041)
I also had an interview at Gitlab, and I was dinged for being from a smaller market. I thought the interview itself was very nice, straight forward, and friendly.

One thing that I thought was strange was the quiz/test at the end of each interview. I get that you want to make sure that the candidate has an adequate skill level, but I have a lot of open-source projects (hosted in GL), and I am (one of many people) horrible at live quizzes. Mostly because of nerves, being in an interview is stressful enough. The fact that I had to take a 30-45min quiz instead of going over my own code is not ideal. I just don't believe in standardized testing being a good measure to someone's ability. But, I really thought they were nice about it, and I wish them luck.

Re:GitLab acquires Gitter, will open-source the code by netcraft on Wednesday March 15, 2017 @06:42PM (#13880570)
It also comes back with half of my current salary, for a senior with a lot of experience. I know what you mean about future prospects.
Re:GitLab acquires Gitter, will open-source the code by anonymous_green on Friday March 17, 2017 @06:28AM (#13892885)
This is quite common they like to brand themselves as startup and remote company with all their slimy tactics to pay their employees below market rate. I've had their team deny the proof that the salary expectation I asked for is with-in the normal range even if they are a remote company and a startup.

Nobody should be paid as low as 50-60k per annum when they expect people to perform same as someone paid 90-120k. Here are some of the links where I raised this point as well:

https://news.ycombinator.com/item?id=13549948 https://news.ycombinator.com/item?id=10924957

This link suggests their average salaries to be 115k but their calculator is just for people who they'd like to scam into paying below par.

https://www.indeed.com/salaries/Gitlab-Salaries

Re:GitLab acquires Gitter, will open-source the code by sytse on Wednesday March 15, 2017 @03:26PM (#13879002)
Mmm, that is pretty far off. If I understand correctly you're a developer intern in Orlando. In most countries interns are paid less than juniors. Maybe that is not the case in the US currently?

BTW Our compensation principles can be found at https://about.gitlab.com/handbook/people-operations/global-c...

Re:GitLab acquires Gitter, will open-source the code by hamandcheese on Wednesday March 15, 2017 @03:36PM (#13879080)
Definitely not an intern anymore ;)

Edit: and yeah, I've read a lot about your company including that link. I understand your approach, it just excludes me.

Re:GitLab acquires Gitter, will open-source the code by sytse on Wednesday March 15, 2017 @03:42PM (#13879125)
I must have found a different person, sorry. Can you please email [email protected] with your case? If the calculator is so far off we would love to add that data point. The most heard criticism seems to be that for low rent parts of the US the calculator is too low. Before our last change the biggest problem was that for hot cities (Phoenix and Austin) it was too low, we now fixed that.
Re:GitLab acquires Gitter, will open-source the code by tracker1 on Wednesday March 15, 2017 @05:17PM (#13879865)
I'm in Phoenix, and it still seems a bit low.. about 16-20k off at lead with high experience... seeing roles around $130k locally. One of the sites like glassdoor is seeing an average around your top.

For U.S. it may be best to establish a floor, and for most cities don't go below that... Remote work in the U.S. tends to be closer to 65-75% of Northern California pay, from what I've seen. Often more than local rates, but harder to come by the jobs.

Re:GitLab acquires Gitter, will open-source the code by hamandcheese on Wednesday March 15, 2017 @03:51PM (#13879193)
No, you found the right person, it's just dated information :) I was an intern ~2 years ago.
Re:GitLab acquires Gitter, will open-source the code by anonymous_green on Friday March 17, 2017 @07:51AM (#13893240)
Seriously? BTW! I just checked the calculator again and the time I was offered a job, there was no calculator then. The calculator pretty much offers the same amount that I asked for but still Gitlab decided to waste by time by saying we expect to pay 70-80k max. The range is clearly 115-120k and I don't think you understand the concept of remote teams when this range can be quite different than US which I explained to your HR as well.
Re:GitLab acquires Gitter, will open-source the code by homakov on Wednesday March 15, 2017 @05:16PM (#13879860)
How can anyone verify where I live? What if I say I live in SF just don't wanna meet up personally?
Re:GitLab acquires Gitter, will open-source the code by cderwin on Wednesday March 15, 2017 @05:28PM (#13879955)
Assuming you are a law-abiding citizen such information would be critical for tax withholding.
Re:GitLab acquires Gitter, will open-source the code by sytse on Wednesday March 15, 2017 @06:47PM (#13880621)
Hi Egor, we rely on team members telling the truth about where they live and when they move. In SF we sometimes meet up so that would be slightly harder to pull off. But all of our physical get togethers are optional so you can probably keep this going for a while.
Re:GitLab acquires Gitter, will open-source the code by homakov on Wednesday March 15, 2017 @06:56PM (#13880685)
It was a general question to all companies, because geosalary seems to be popular. Always wondered how it works, and how it can be abused.

Also: we, digital nomads, don't have any base. I honestly have no answer to "where do you live"

Re:GitLab acquires Gitter, will open-source the code by sytse on Wednesday March 15, 2017 @07:34PM (#13880948)
We had one person before that didn't have a base. He was registered in Estonia as a digital citizen and company. We opted to use that. But we'll look at this on a case by case basis.
Re:GitLab acquires Gitter, will open-source the code by akerro on Wednesday March 15, 2017 @05:05PM (#13879775)
They have developers from poorer countries like Eastern Europe where your twice less is twice more than local market.
Re:GitLab acquires Gitter, will open-source the code by kilotaras on Wednesday March 15, 2017 @05:59PM (#13880232)
You vastly underestimate situation in Eastern Europe. It's fairly easily for software engineer to move to Europe, so local companies still have to compete with that.

Anyway I've looked at my homecity in Ukraine and salaries proposed are around 80-90th percentile (~$50k for senior developer).

The thing is there's no reason for a person to hold onto Gitlab. Once you get some remote experience there're a lot of companies who provide EU/US salaries even if you happen to live in Eastern Europe.

Re:GitLab acquires Gitter, will open-source the code by sdesol on Wednesday March 15, 2017 @06:20PM (#13880404)
> The thing is there's no reason for a person to hold onto Gitlab

This is the one area, I'm quite interested in seeing how things play out, from a human resources point of view. Since GitLab is so transparent, it'll be interesting to see, if they publish any information on employee turnover in the future. Or any mitigation strategies they may develop, to help retain high value employees.

Re:GitLab acquires Gitter, will open-source the code by sebastianavina on Wednesday March 15, 2017 @03:24PM (#13878979)
how can i get a remote work?
Re:GitLab acquires Gitter, will open-source the code by ed_balls on Wednesday March 15, 2017 @06:15PM (#13880368)
Yeah I'm really surprised that they don't do something similar to https://buffer.com/salary or stackoverflow.

I applied to Gitlab, but then I noticed the calculator. London is below market rate. In Warsaw is half what Google pays.