4 ms·

There's not much remote work available. Those jobs are the most desirable and also the very hardest to get. In the past 10 years, i've received 100s of calls

There's not much remote work available. Those jobs are the most desirable and also the very hardest to get. In the past 10 years, i've received 100s of calls from desperate recruiters looking for Software engineers: and every single time, it's because they're looking to fill positions of companies in Palo Alto or San Francisco. Anytime, I ask them to find a position outside of the penninsula or SF, they turn up empty handed (east bay). Companies can learn from this as well: there's a difference between # of workers working in a field and labor supply vs labor demand.

chrissnell 9y ago
I think we're starting to see a shift. Today, as a hiring manager that hires remote workers, I have the pick-of-the-litter when it comes to talent for my team (infrastructure engineering). I can find the very best folks, people that I would have a much harder time winning when up against the FANGs (Facebook-Amazon-Netflix-Google) of the world if I was hiring in my company's SFBA home base. Having remote-friendliness in my pocket, I can be choosy and can hire strong senior-level folks. I think it's inevitable that the rest of the Valley catches on and figures out how to make remote work for them. When this happens, I think we'll see who things: - A leveling-up of remote salaries. Not such a big deal at my company and on my team, because we don't hold someone's remoteness against them and we pay fair SFBA salaries. Other companies (GitLab, etc.) adjust salaries based on cost-of-living. This is a reduced-fare lunch for them but probably not sustainable. Other companies are going to catch on and snap up top talent at average SFBA comp levels and the salary-savers will be forced to level up. - SFBA talent will start leaving the Bay Area for more affordable and enjoyable areas. We'll see engineers moving to Central American beach towns, Colorado ski towns, back home to flyover states, etc.
- johan_larson 9y ago
  Interesting. Where do you usually advertise remote positions, Chris?
  - chrissnell 9y ago
    The HN Who's Hiring thread, our website, a few other job sites, etc. You can probably find it in my recent comment history.

chrissnell 9y ago

I think we're starting to see a shift. Today, as a hiring manager that hires remote workers, I have the pick-of-the-litter when it comes to talent for my team (infrastructure engineering). I can find the very best folks, people that I would have a much harder time winning when up against the FANGs (Facebook-Amazon-Netflix-Google) of the world if I was hiring in my company's SFBA home base. Having remote-friendliness in my pocket, I can be choosy and can hire strong senior-level folks. I think it's inevitable that the rest of the Valley catches on and figures out how to make remote work for them. When this happens, I think we'll see who things: - A leveling-up of remote salaries. Not such a big deal at my company and on my team, because we don't hold someone's remoteness against them and we pay fair SFBA salaries. Other companies (GitLab, etc.) adjust salaries based on cost-of-living. This is a reduced-fare lunch for them but probably not sustainable. Other companies are going to catch on and snap up top talent at average SFBA comp levels and the salary-savers will be forced to level up. - SFBA talent will start leaving the Bay Area for more affordable and enjoyable areas. We'll see engineers moving to Central American beach towns, Colorado ski towns, back home to flyover states, etc.

johan_larson 9y ago
Interesting. Where do you usually advertise remote positions, Chris?
- chrissnell 9y ago
  The HN Who's Hiring thread, our website, a few other job sites, etc. You can probably find it in my recent comment history.