While I was hunting for a remote developer job last December, it was hard to find the company that really suited me.
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 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.
You're not worried about accidentally corrupting data? I do that all the time with spreadsheets. Seems like it would could be pretty bad if you accidentally labelled something gluten free and it wasn't.
It's actually quite useful if your application never updates your data and you want a data entry system for free. Downside is validation is a PITA, but for certain things using something like Google spreadsheets will get you a very long way very quickly. You can then build a better data entry system after that.
In my experience the gains made from a quick setup are quickly offset by the amount of time wasted by not having any data validation, and the resulting bad data that gets into the system.
Sorry, not sure I follow. Is mongo public? I dont think so. So the issue isn't the spreadsheet, it's your data with public write access, which is of course a very bad idea.
One of the issues I've found is that testers seem to be underrepresented by remote work listing sites. Or is it just the start-up scene, where testing is pushed onto the developers?
If anybody ever needed an answer to the question "will my startup/product be useful for the world?", take a look at this example/product.
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.
It seems outside the scope of something YC would care about. Also the amount of sunsetted good tech job boards grows every year.
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.
It also forms the basis of a platform and trusted brand that can provide third party services bridging the gaps between remote hires and startups. Nicely done!
I am quite heartened as well to see a wall of companies functioning at "100% Distributed" ;)
This is great and thank you for making it. One suggestion: hiring region does not work as I would expect it to. If company is hiring worldwide, then surely it is also hiring in every region. Right now I can get a bunch of results for a worldwide query and 0 for otherwise same one, but limited to Europe.
Pretty confusing as someone who's familiar with NomadList and RemoteOK (both by the same developer and which this borrows heavily, visual-design wise...)
That said, I like the filtering functionality built in to this more than what's available with RemoteOK.
This is great. One question/comment: I'm a bit confused as to what "100% remote" means in this context. Github is listed as 100% remote, but I'm pretty sure it has an office.
Yes, Trello is also incorrect. It lists 51 people (Non-remote: 0), but they have a significant number of people working from their office in NYC. And 51 seems low...
Really... How is integration with something like Jira a negative thing, how could it be? If HipChat locked out all non-Atlassian products, that would be bad, but they don't.
It makes arguing against the use of JIRA -- and all the project-management-oriented complexity it seems to bring if you don't keep a tight grip on it -- that little bit harder. Sure, not a negative for everyone, but has the potential to be the thin end of the wedge.
Nothing really, it's fine. Based on the comments I read on HackerNews however, I think stability is a major issue in the US (US time zone). HipChat has be extremely stable for us, but we're using it when San Francisco is a sleep.
So my guess is that Atlassian might have issue scaling.
Probably worth stealing from/working with the guys at http://www.golangprojects.com as they often have remote jobs and I note there's no golang on your tech filters.
Great Job Sung, I think with more users/visibility the list can be more easily curate and updated. I was using remoteok but got buggy lately and some jobs are really old. What is interesting about remotebase is that gives you a little look inside the company and tools they are actually using to collaborate and their stack as well. For sure more tech tags options are missing.
I cannot find a filter for Mobile Development (Swift, Objective-C, iOS in general). I would use the site, but I cannot find the positions for me.
Also - clear text search would be useful, too.
Aside from the mobile technologies you mention, I also wish a filter for .NET was present. Granted, maybe no companies in the original dataset do .NET, but if I could filter for .NET and see no results, I would know for sure, currently I just can't tell.
This is great! Would it be possible to display the pitch of each company as an @title when mousing over the company name, as to give an idea of what each company does?
116 comments
[ 4.0 ms ] story [ 78.8 ms ] threadDue 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!
https://mike706.typeform.com/to/o6eSiQ
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" ;)
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.
That said, I like the filtering functionality built in to this more than what's available with RemoteOK.
https://remoteok.io https://nomadlist.com
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.
That's not necessarily a positive.
So my guess is that Atlassian might have issue scaling.