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

Our Handbook is open source: here's why

about.gitlab.com

Post reply on HN
Print view View original

61–70 of 105 posts

Re: Our Handbook is open source: here's why

#61

Post by fweespeech »

sytse wrote: post #54
fweespeech wrote: post #53

Earlier quoted context omitted.

Have you considered open salaries (just the formula really would be all that was needed) like Buffer?

Yes, we're working on a global compensation framework. This is hinted at on https://about.gitlab.com/handbook/hiring/#hiring-processa-na... "The hiring manager can then make the actual offer to the applicant. This may change if/when we have a global compensation framework in place." and in the job description of the Director of People Operations https://about.gitlab.com/jobs/dir-or-vp-of-people-ops/ "Compensation gui…

Cool.

I look forward to seeing a blog post when you have that compensation framework completed. :)

I've seen/heard words like that meaning anything from a 10% paycut to a 55% paycut in practical terms, its too big a range for me to really take away an effective idea of GitLab's pay level which is why I was curious about the more concrete form.

A 10-15% haircut for a place as good as GitLab sounds on paper seems reasonable, a 50% haircut...not so much.

Re: Our Handbook is open source: here's why

#62

Post by sytse »

fweespeech wrote: post #61
sytse wrote: post #54

Earlier quoted context omitted.

Yes, we're working on a global compensation framework. This is hinted at on https://about.gitlab.com/handbook/hiring/#hiring-processa-na... "The hiring manager can then make the actual offer to the applicant. This may change if/when we have a global compensation framework in place." and in the job description of the Director of People Operations https://about.gitlab.com/jobs/dir-or-vp-of-people-ops/ "Compensation gui…

Cool. I look forward to seeing a blog post when you have that compensation framework completed. :) I've seen/heard words like that meaning anything from a 10% paycut to a 55% paycut in practical terms, its too big a range for me to really take away an effective idea of GitLab's pay level which is why I was curious about the more concrete form. A 10-15% haircut for a place as good as GitLab sounds on paper seems reaso…

For sure we'll do a blog post about it. By the way if you want something now the Travis CI talk is really good https://www.youtube.com/watch?v=N8u9H6JDAzo

We don't have any hard data on this but I think we're in the reasonable range.

Re: Our Handbook is open source: here's why

#63

Post by sytse »

repomies691 wrote: post #58
sytse wrote: post #50

Earlier quoted context omitted.

Our pay depends on your location. So if you're currently charging an SF rate without the expenses of living there you're better off.

So people are paid according what they spend, not what they produce? That doesn't sound very sensible to me.

We thought about paying independent of location. If we pay everyone the same we would have either a huge burn rate or we could never hire great people from the Bay Area.

Another consideration is that people's costs are strongly related to where they live.

But I can also see the case for paying everyone the same. But I think other remote friendly companies are doing the same as us, this video shows how Travis CI thinks about it https://www.youtube.com/watch?v=N8u9H6JDAzo

Re: Our Handbook is open source: here's why

#64

Post by sytse »

amyjess wrote: post #60
leetrout wrote: post #8

Just absolutely fantastic values for work-life balance and certainly makes GitLab look _very_ appealing... Some of my favorites: We're a distributed, remote-only company where people work remote without missing out. For this, we use asynchronous communication and are as open as we can be by communicating through public issues, chat channels, and placing an emphasis on ensuring that conclusions of offline conversation…

Between this and the above comment about interviewing practices (especially regarding language proficiency), I would so apply to GitLab if I hadn't just started a new job last month. Still... circumstances might force me to move out of state next year, and if that happens and I can't stay with my current employer, I'm certainly going to check GitLab's openings first.

Glad to hear that GitLab will be on top of your list if you have to start interviewing again :)

Re: Our Handbook is open source: here's why

#65

Post by [deleted] »

Trundle wrote: post #11
sytse wrote: post #2

I'll be around for 30 minutes to answer any questions.

Are you guys focusing on ramping up direct sales yet? Emailed Michael earlier in the year and he said that he's focusing on your reseller program at the moment and to get back to him in August to see where you're at. Still very much on my calendar but I figured it can't hurt to check now if you're offering answers!

[deleted]

Re: Our Handbook is open source: here's why

#66

Post by lloeki »

jobvandervoort wrote: post #14
deanclatworthy wrote: post #10

Is your only source of income right now the paid hosted repos? If so, how do you plan to scale that to support a staff of over 100 as well as compete with GitHub and Bitbucket who already have a huge market share?

Our main source of income is organisations running GitLab Enterprise Edition on-premises, paying us a yearly subscription fee [0]. GitLab.com is completely free, public and private repositories, CI and unlimited collaborators. [1] [0]: https://about.gitlab.com/pricing/ [1]: https://about.gitlab.com/gitlab-com/

You didn't mention githost.io, is it a non-significant part of revenue (yet)?

Re: Our Handbook is open source: here's why

#67

Post by itsdrewmiller »

jobvandervoort wrote: post #46
jack-ess wrote: post #44

Earlier quoted context omitted.

No junior jobs, eh?

We have a few junior team members [0]. If you think you would make a great fit in one of the roles, but at a more junior level, I urge you to still apply. The respective hiring manager can let you know whether it's possible to fulfill the same role as a junior. [0]: https://about.gitlab.com/team/

If you are open to people applying that don't quite meet the requirements of the position, you should change the position description. It's well documented that this type of approach tends to reduce the diversity of applicants.

(Not to be a nag - I think it is great that you folks are sharing this, and it sounds like a great place to work.)

Re: Our Handbook is open source: here's why

#68

Post by lukevers »

kriro wrote: post #9

Pretty interesting that you use "1password (PeopleOps vault)". I guess I never thought about using PW-vaults in a corporate setting. Seems like an interesting approach (compared to some alternatives I know that don't work well).

We're using 1Password for teams at MM.LaFleur and it really is nice. A lot of our employees were already 1Password personal users, and the Teams for 1P just started in Beta when we started looking for a new way to share passwords in a corporate setting, and after trying some different options out this was by far the best.

You can add people to specific vaults and it works really well.

Re: Our Handbook is open source: here's why

#69

Post by sytse »

itsdrewmiller wrote: post #67
jobvandervoort wrote: post #46

Earlier quoted context omitted.

We have a few junior team members [0]. If you think you would make a great fit in one of the roles, but at a more junior level, I urge you to still apply. The respective hiring manager can let you know whether it's possible to fulfill the same role as a junior. [0]: https://about.gitlab.com/team/

If you are open to people applying that don't quite meet the requirements of the position, you should change the position description. It's well documented that this type of approach tends to reduce the diversity of applicants. (Not to be a nag - I think it is great that you folks are sharing this, and it sounds like a great place to work.)

The diversity is indeed an important issue. We thought about this and all of our job posts contain the following text: "Avoid the confidence gap; you do not have to match all the listed requirements exactly to apply.". Confidence gap links to http://www.theatlantic.com/magazine/archive/2014/05/the-conf...

For an example see https://about.gitlab.com/jobs/production-engineer/

Please let me know if you have any other suggestions.

Re: Our Handbook is open source: here's why

#70

Post by sytse »

lloeki wrote: post #66
jobvandervoort wrote: post #14

Earlier quoted context omitted.

Our main source of income is organisations running GitLab Enterprise Edition on-premises, paying us a yearly subscription fee [0]. GitLab.com is completely free, public and private repositories, CI and unlimited collaborators. [1] [0]: https://about.gitlab.com/pricing/ [1]: https://about.gitlab.com/gitlab-com/

You didn't mention githost.io, is it a non-significant part of revenue (yet)?

The revenue of Githost.io is indeed not significant yet, but we expect it to grow over time.
Post reply on HN