I recently came across this article http://zachholman.com/posts/how-github-works/, and I really enjoyed reading it. However, there's one thing I was wondering after reading this article: you said that you don't value hours, but quality. But how is that done with salary? What do you base that on?
Hey- sorry for the delay in getting back to you... been jetsettin' 'round the world.
As a starting point, we mostly have the same base salary (I think contractors and some junior devs get paid differently, but for the rest of us I think we're all still paid the same base rate).
After that point, you don't really have to do much micromanaging on salary. Are they doing their job? Cool. If they're not, talk to them. If they continue not to, then let them go. Those are mostly the metrics.
How much do you earn? Mind sharing?
Yes, I mind.
I'm trying to wrap my head around how this would work in practical terms. So does everyone make the same at GitHub, regardless of where they live? The cost of living does vary greatly across the US, so I find it hard to believe it's not taken into account when paying salaries.
If the goal is to maintain an egalitarian culture within the company, it feels like cost of living differences could really make that difficult. I suppose if you leave it to the individual to choose whether they want to stretch their dollars in SF or live like a king in Detroit, then maybe it works. It may even work as a built-in filter to filter out those for whom monetary needs are too important and for whom the culture may not be a fit anyway.
Sounds like I might have just answered my own question, but I would love to hear your thoughts on this.
We mostly pay the same salary to developers. You could clearly live like a king in Detroit, but then you'd live in Detroit.
Holman you are the best. Dying laughing over here.
120 - 160 according to glassdoor: http://www.glassdoor.com/Salary/GitHub-Salaries-E671945.htm
Is that accurate?