Show HN: I made a database of remote companies
remotebase.io
remotebase.io
For anyone else who's in the same boat, here are a few similarly helpful resources:
https://github.com/jessicard/remote-jobs
http://workingremote.ly/leaders/distributed-companies/
https://triplebyte.com/ycombinator-startups#q=&page=0&refine...
https://stayintech.com/info/explore (The companies on this list aren't all remote, but I'm including it anyway since diversity + inclusivity were also among my criteria.)
It's nice that RemoteBase is adding more structured data with filters to the mix, and while I'm not totally sure what "open database" means, I hope they're be an API.
It'd be really nice to have one authoritative source for referring to remote jobs, which as OP pointed out, for most interests really means remote companies.
This product doesn't seem like a startup-driven idea, but it addresses a serious pain-point for people (more specifically: developers) looking for (remote) jobs in a way that is required to find the right job:
> Using filters to narrow down to a subset of companies to apply to
Great job on this product, it is a great alternative to having to wait 30 days for each "Who is Hiring" without a guarantee that many remote companies who are hiring will post on that HN thread.
- pay to play for big biz - free to small biz - highlights YC gigs - etc.
I think it's a dying business model, and perhaps one reason why we see a tech jobs startup in every YC batch (perhaps after a pivot or two), but approaching the problem from a new angle.
The most recent that come to mind are Gradberry and Triplebyte.
I am quite heartened as well to see a wall of companies functioning at "100% Distributed" ;)
Due to the isolating nature of remote working, it's important to know how the remote team communicates (Slack, email, Skype, Phone call...), and how they collaborate (Dropbox, Google Doc, Git, ...). The purpose of this project is to answer those questions and beyond.
I also wrote an article on this project: https://sungwoncho.io/i-am-making-remotebase/
I wonder, what did you use as a db? Since you started with a spreadsheet, you could just use that. Google Spreadsheet has a json api that you can query directly from your web app.
I did it for http://hasgluten.com, if you want to see it in practice (hosted for free on github). Easier to keep the "backend" updated, since you just have to edit the spreadsheet.
So I just exported the sheet as JSON array and put it in Mongo.
Given that, what kind of background do you have? Please reach out to me on Twitter or elsewhere!
That said, I like the filtering functionality built in to this more than what's available with RemoteOK.
Edit: Just seen there is a "Worldwide" search filter, but it doesn't seem very accurate.
> Is the company fully distributed?*
> This means all of its employees work remotely and the company does not have an office.
So it seems the companies listing as 100% distributed may not be entirely accurate.
This one is awesome. Best Wishes.
A timezone-range would be the preferred method.
Countries are too limited and continents to broad as their timezone can range more than 4 hours.
Somewhat related, but reading that book "Quiet" about introversion really made me feel validated on my feelings of hatred towards the modern open office, and how important it is as a dev (or most people really) to have a quiet, private place to work.
As an engineer, timezone differences are one of my top annoyances. If I want to rapid fire discuss something with an engineer I want to do it now, not this weird game of delayed/janky ping pong.
Minor nitpick: your wait-for-dynamic-content spinner (https://remotebase.io/images/logo.png) exhibits eccentric rotation, which might make some people a bit seasick :-)
It puzzles me that companies insist on remote workers working to specific timezones. Having everyone work the same hours seems to negate a key advantage of remote workers - ideally while you are sleeping, progress is still being made on your projects by the various remote teams. They should be able to work independently, asynchronously.
I can understand if they are remote support roles, where you want to ensure you always have staff to deal with enquiries. But for most roles, it seems more important that the work gets done, rather than that the entire team are tied to Slack / Skype at exactly the same hours.
It all depends on what is being worked on but when I have to work with someone or even just review their code I would like to not have to wait hours/days for my comments on code to be addressed.
As an addition, here is another extensive database of remote companies worth looking at: https://docs.google.com/spreadsheets/d/1TLJSlNxCbwRNxy14Toe1... It was put together by Remotive.io [http://remotive.io/] and found on nodesk.co [http://nodesk.co/], lots of good remote work info there as well.
Example: UTC-01:00 - UTC+02:00
One suggestion: one field in the "add new company" form asks to list the tools in our stack. How about in addition to that, you optionally link to a company's StackShare? We keep track of all of our tools there to give a comprehensive overview of what we use, so that will stay more up to date over time I think.
Here's an example, from my company: http://stackshare.io/third-iron/third-iron
The top one coming to my mind at the time being (which I'm surprised to not see in this thread already, considering the usual popularity of remote/rework/basecamp stuff on HN): https://weworkremotely.com/
Still, nice personal achievement in terms of developing and delivering a product.
Firstly I have to look at every job page individually. So I'd rather look at remoteok.io for that. I guess this is good for speculative applications, but is it a good use of my time trolling through 100's of companies sending out speculative applications?
Secondly I am not in the US or on US time zone so there would be little relevant to me anyway.
Note: the "company name" field in more filters doesn't appear to work in mobile Safari.
That's not necessarily a positive.
So my guess is that Atlassian might have issue scaling.