This is awesome. It doesn't seem to deal well with jobs posted in multiple locations - mine from April only shows up in DC when it was for both DC and Boston.
Tesla Motors, Stationary Storage Group, Palo Alto
- shows up on the 'Intern' filter, but it explicitly says they're not looking for interns at this time.
I am 20 years old and I can't have XP with 20 stacks/languages, although I am quite open to learning new stuff. Sadly, there are only so much technologies in demand where I am located.
I think what he means is you don't necessarily need to have experience with the particular stack before hand (and they probably don't expect interns to). You can pick it up on the job
Unfortunately it doesn't seem to handle multiple pins in the same location very well, you can sometimes zoom all the way in and still have a cluster circle - making it impossible to click on individual items.
Very fun to cruise around the world and see what areas are boiling over with opportunities. Perhaps unsurprisingly San Fran, London and NYC were my winners.
Interesting, if honest mistake: railsmachine.com is hiring in "Remote, USA". If you look that up, it actually exists as an aptly named wide spot on the road in Oregon.
I've seen Remote, USA used on several occasions on popular job boards that didn't support the option for telecommute or working remotely. It's a great hack that seemed to gain in popularity with the tech sector specifically. Luckily for all of us, it's far more common that remote jobs are explicitly listed as such nowadays and this workaround is diminishing.
So as a weekend project to learn a certain framework, I thought i'll build a Whoishiring frontend -- to make things easy for someone seeking a job (filtering via location, role, etc, tracking etc).
So some market fit: Would you be interested as a user (is this better than looking at 100s of comments on the monthly posts? Easier than Ctrl-F and looking for terms?)? This will be to whoishiring posts, what ProductHunt is for Show HN.
This is too sparse, and not much more usable than the actual hackernews thread. I'm thinking:
All metadata go through 2 steps -- machine learning (for best guess) + confirmation/correction via crowdsourcing.
* Filtering by location.
* Filtering by role
* Filtering Remote/in location
* Filtering by technology.
* Some UI enhancements to pin roles, and save for later. And UI to share with someone.
* Devs setup criteria and be notified monthly for matching openings.
29 comments
[ 4.2 ms ] story [ 55.4 ms ] threadI am 20 years old and I can't have XP with 20 stacks/languages, although I am quite open to learning new stuff. Sadly, there are only so much technologies in demand where I am located.
http://google-maps-utility-library-v3.googlecode.com/svn/tru...
Makes it easier to play with data analysis on the hiring threads in R. http://pastebin.com/TpLfSKjP
My employer is hiring as well, and we're not listed, but we would like to be!
Just post there.
http://en.wikipedia.org/wiki/Remote,_Oregon
https://www.google.com/maps/place/Remote,+OR+97458/@43.00594...
So some market fit: Would you be interested as a user (is this better than looking at 100s of comments on the monthly posts? Easier than Ctrl-F and looking for terms?)? This will be to whoishiring posts, what ProductHunt is for Show HN.
So there's definitely space for improvement :)