3 ms·

That's a great way of hiring people who aren't good enough to get a remote job at SF wages. The problem is that it cuts off the ability to hire the top of the m

That's a great way of hiring people who aren't good enough to get a remote job at SF wages. The problem is that it cuts off the ability to hire the top of the market. I currently live in Boulder, Co, but I never even considered working for a business that wasn't in (and paying like) NY or SF. For top talent you're not competing with the local crappy .NET consulting shop paying $60k a year, you're competing with every SV startup that's open to going remote for the right hires. All that said, lots of reasons other than comp to take a position, and it seems to be working just fine for GitLab!

emilycook 7y ago
> The problem is that it cuts off the ability to hire the top of the market. To be frank, I don't think the gap in skill between the top-top-top tier employees and those who are competitive candidates for non-SF salary remote positions is all that wide, nor do I think it's necessary for a company's success to only hire the absolute pinnacle of talent. We're also not competing in the same consumer market as many SV startups, so if a different remote company has a higher saturation of top-tier developers, I'm not sure why that affects us unless they're a competitor. I do see this point though, and I'm sure Sid does as well, but the level of skill that the people I work with have vs the employees at my previous (local) company is incomparable. Everyone is very good at what they do, and are motivated to continue working here because of all of the other perks of working for a company like GitLab.