24 karma · joined December 26, 2019
If you’re interested in the journey, I’ve outlined the build process to date in the following blog post (also hosted at the edge):
https://www.remote.io/blog/19/globally-distributed-website-f...
There's an entire industry around that called Cash Parking. There's at least four different remote job sites with similar domains that I receive traffic (and email) for if you'd like to look those up to make some more pointless comments.
I believe it may be a cache issue from our original build and you having visited previously. If you could, please hard-refresh (Ctrl+F5) or visit the job portal directly: https://portal.remote.io/
I'll work on a quick temporary fix as well.
If your issue persists, please contact us with the address of the page that you were on previously when you clicked to post so we can investigate further.
The listings come from feeds of numerous job sites and applicant tracking systems. I run them through custom filters to pull out the ones that are specifically remote-friendly.
I initially launched it in September but that was more of a soft launch to see if it would be worth my time and the traffic has been increasing. The past 2 days have been a bit higher with this HN post and averaged between 4-5k unique visitors / day.
The problem is that a separate index must first be built to assign all related tags to job listings as some don't have any and others don't have all related ones.
Once that is completed, the search functionality will be reverted to what it was initially with the ability to search by strings and/or tech tags individually.
I've been contemplating how I'm going to achieve this for a couple weeks and have a pretty good model in mind but no ETA on when it will be implemented.
"coder" isn't a great choice of search term. If that's what you searched for, that's what you'll get as the search results are based on the job description, as well as the technology tags.
I'll also look into adding a filter to exclude those without salary listing but can't promise any timeline on that.
Another interesting coincidence is that he has levels.io and I have level.io (I registered it about 4 years prior to him).
To make things even stranger, he posted my exact birthday on a mock ID he created for his blog (Feb 20, 86): https://levels.io/remote-worker-visa/
I originally registered it with the intent of building a remote monitoring and management tool or an infrastructure provider company but never got around to doing either venture.
The remote job site came about because I realized I was getting a lot of unintentional traffic from people searching for remote jobs. As it wasn't a terribly difficult venture, I decided to build it out and see how it went and so far, it's done well.
When searching, you can see the number of results returned at the top left.
EDIT: I did find an error that was sometimes causing auto-complete and search to not work. This has been resolved.
Since the bad example has already been brought up, you're going to be fighting an uphill battle to redeem yourself. You may want to start negotiating a different shift that still puts in the hours but allows you to come in later and leave later. Another idea is to push remote work and stress that you aren't customer facing and that you'd be more productive working from home anyway.
Companies that are reluctant to take this approach will sometimes allow work from home X days / week so that they can see you're still producing so that's another option you can try if they flat-out turn down fully-remote.