I think remote roles are becoming a lot more accepted in tech. No time wasted on the commute, and companies can save costs of office spaces, etc.
I'm so optimistic about remote working for developers, it's even been a key feature in a job matching platform I've been working on: https://www.rocketship.dev/
OP here! I’m Eric, and I’m a PM at Rocketship Jobs.
As a startup, our aim is to help developers build stellar careers by matching them to jobs with extreme precision and accuracy. To achieve this, we built a matching hierarchy that identifies the software elements shared by developers and employers.
-What’s the product?-
It’s a skill-centric job matching platform, presently run out of Google Forms. Developers and employers are matched based on an inventory of software skills inventory, values, and preferences. We're hoping to promote remote jobs as more mainstream through our platform as well.
-How to use Rocketship?-
Developers who would like to participate in our matching platform beta can submit a response though the link. It takes about 10 minutes. There’s no resume required, but try to give a specific representation of your skills. We’ll then use responses to identify the strongest matching clusters, and connect those developers and employers.
-The Key Features-
* A skills section on steroids: categorized banks of platforms, languages, frameworks, etc...
* Hyper-specific matching: we’d rather send zero matches than non-matches
* Spam-free by design: employers simply cannot access non-matching profiles
* Top Secret mode: developers can now search anonymously and passively
Rocketship was built with the developer community in mind, so if there’s anything we can improve, please let us know. Thanks HN!
I'm actually assisting with a startup in building a solution for things like this, so your comment really struck home!
And as somebody with a past in technical recruiting, I really like your thinking. Indeed you're right: many recruiters are poorly equipped to actually understand the roles. We have non-coders as the first or second tier gatekeepers for development roles, which does not seem ideal.
Sometimes I'd get different signals from the job descriptions than the senior recruiters or hiring managers, which was frustrating. Other times, the requirements in descriptions were way too broad: like the team had an idea of what they wanted, but couldn't get it down on paper in a concise way.
Resumes can be a challenge, too: many engineers don't always give full details of their work. Perhaps because they're tired of getting recruiters reaching out for irrelevant roles (that happen to have a keyword match somewhere). Perhaps they don't have the time to always be updating and polishing.
A two-front solution could be really great. We need developers to write their best resumes, and we need employers to write their best job descriptions. Having them 'speak the same language' on concise accomplishments, metrics, technologies will make more automated matching a lot (a lot) easier.
And then, of course - build the interview process around the shared skills / technologies / etc.
Hopefully I'll have something to share here soon, or perhaps do an ask HN to chat more about making hiring developers easier for everyone
I'm so optimistic about remote working for developers, it's even been a key feature in a job matching platform I've been working on: https://www.rocketship.dev/