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

GitLab Handbook

about.gitlab.com

Post reply on HN
Print view View original

41–50 of 82 posts

Re: GitLab Handbook

#41

Post by dsetaos »

Tade0 wrote: post #28
nbulka wrote: post #7

I applied for an Engineering role at Gitlab. I didn't make it past the initial interview screening and politely asked for feedback in order to grow professionally. I never heard back from the recruiter or company after that yet their handbook says: "If the candidate asks for further feedback, only offer frank feedback. This is hard, but it is part of our company values." I always wondered if it was because I question…

I applied twice with a year between the two attempts: First time I was rejected after the first interview because they found somebody better suited for the role(my lack of Ruby experience was likely a factor) - that at least was the response I got. Second time I was rejected outright - the reason given was that for people with more than five years of experience, they expected candidates to spend more than two years i…

Not to be mean but I'm sceptical of CVs like that too. I expect people to stick around for a while. I need to know I can depend on them not to jump ship at the slightest hiccup.

Unless they can give me a reasonable explanation for the job hopping I'm not going to take the risk.

If I want mercenaries I'll just get some freelancers.

Re: GitLab Handbook

#42

Post by stonogo »

orf wrote: post #13

Gitlab Unfiltered[1] is pretty cool. Say what you want about Gitlab, but they go hard on the openness aspect of things. I can't think of another company that is on the same level as them - streaming meetings and other stuff on Youtube almost seems like overkill. 1. https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A/

They're open when it doesn't matter. When it does, they go just as hard in the other direction: https://gitlab.com/gitlab-com/diversity-and-inclusion/issues...

About which more here: https://www.theregister.co.uk/2020/02/06/gitlab_sales_women/

Re: GitLab Handbook

#44

Post by relaunched »

orf wrote: post #13

Gitlab Unfiltered[1] is pretty cool. Say what you want about Gitlab, but they go hard on the openness aspect of things. I can't think of another company that is on the same level as them - streaming meetings and other stuff on Youtube almost seems like overkill. 1. https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A/

Super open, except when it comes to compliance

https://www.google.com/amp/s/www.wsj.com/amp/articles/resign...

Or women

https://www.theregister.co.uk/AMP/2020/02/03/gitlab_proclaim...

Or my wife:

https://news.bloomberglaw.com/corporate-law/former-top-gitla...

Re: GitLab Handbook

#45

Post by bmarnane »

ljm wrote: post #36
leipert wrote: post #21

Earlier quoted context omitted.

Interesting. I have worked a bit on our calculator in the past (technical implementation). Some clarifications, best of my knowledge, currently on mobile: It would be impractical to calculate all the location factors in the world, and in your case it would be calculated. I agree with you that this is less than optimal, as it might stop people from applying if that data is missing. So this is an area where we could im…

I would like to ask why you feel a job should be rewarded differently based on location when the deliverables and other gains from the employee are the same? E.g I don’t see why I should take a pay cut moving from the US to the EU. Looking at Basecamp, they give everyone the US salary and they arrange their culture around remote work that way. Note how it doesn’t even work this way between countries, through the ‘mos…

We talk about our reasoning for paying local rates at https://about.gitlab.com/handbook/people-group/global-compen...

Re: GitLab Handbook

#46

Post by itake »

nbulka wrote: post #7

I applied for an Engineering role at Gitlab. I didn't make it past the initial interview screening and politely asked for feedback in order to grow professionally. I never heard back from the recruiter or company after that yet their handbook says: "If the candidate asks for further feedback, only offer frank feedback. This is hard, but it is part of our company values." I always wondered if it was because I question…

> I always wondered if it was because I questioned the policy of paying people differently based on their location (more specifically, some algorithm's idea of the rent in their area) rather than the work they do.

I had the exact same experience. Even if you lived in SF, they pay way below market rate. I have sympathy for their engineers that don't have any other options but to take their deal.

Re: GitLab Handbook

#47

Post by itake »

bmarnane wrote: post #45
ljm wrote: post #36

Earlier quoted context omitted.

I would like to ask why you feel a job should be rewarded differently based on location when the deliverables and other gains from the employee are the same? E.g I don’t see why I should take a pay cut moving from the US to the EU. Looking at Basecamp, they give everyone the US salary and they arrange their culture around remote work that way. Note how it doesn’t even work this way between countries, through the ‘mos…

We talk about our reasoning for paying local rates at https://about.gitlab.com/handbook/people-group/global-compen...

Your wages aren't even competitive for SF.

Re: GitLab Handbook

#48

Post by bmarnane »

itake wrote: post #47
bmarnane wrote: post #45

Earlier quoted context omitted.

We talk about our reasoning for paying local rates at https://about.gitlab.com/handbook/people-group/global-compen...

Your wages aren't even competitive for SF.

We're always adjusting our calculations based on market research. Are you including the value of stock options as well?

Re: GitLab Handbook

#49

Post by woutr_be »

Dramatize wrote: post #19

I like the section on the CEO: https://about.gitlab.com/handbook/ceo/#flaws

For some reason, that rubs me the wrong way. I had a manager who acted the same way, told us all his flaws and then expected us to cater towards him, without him making much effort. If anything went wrong, and we somehow didn't cater to his flaws, he would blame us for it.

He also came into one of our retrospectives, and said "I'm feeling really emotional today, so I might act a bit strange". Everyone asked him to leave so the rest of the team could have our retrospective, but he insisted on stay and just asked everyone to be aware of it. Of course nothing productive came out of that meeting, in fact, I'm pretty sure that's why a few engineers resigned.

Re: GitLab Handbook

#50

Post by alexhutcheson »

dvtrn wrote: post #23
leipert wrote: post #21

Earlier quoted context omitted.

Interesting. I have worked a bit on our calculator in the past (technical implementation). Some clarifications, best of my knowledge, currently on mobile: It would be impractical to calculate all the location factors in the world, and in your case it would be calculated. I agree with you that this is less than optimal, as it might stop people from applying if that data is missing. So this is an area where we could im…

Hello there, thanks for the response. It would be impractical to calculate all the location factors in the world On the one hand I absolutely agree with you here, however I searched for multiple cities in the state of consideration, two of them are international destinations on the Atlantic coastline with considerable economic impact to the state and region at large, and as mentioned one of them is the state Capitol…

Did you see that "South Carolina" is an option in the drop-down? It has a value of 0.7, which seems pretty generous: it's higher than New Jersey (0.633), and is the same as Atlanta, Charlotte, and Connecticut (0.7), all of which have higher cost-of-living than most parts of South Carolina.

The fact that the urban areas of South Carolina aren't broken out actually seems better for anyone who would plan to live in a rural part of the state. By comparison, "Everywhere else, Georgia", "Everywhere else, North Carolina", and "Everywhere else, Virginia" all have a multiplier of 0.633. This seems to indicate that you'd get paid about ~10.5% more in rural SC than you would in other rural places in the SE.

Post reply on HN