I'm glad to see Remote as a location, but due to the free-form writing in the original posts, there are errors. For example, "Haskell dev at Standard Chartered Bank" is listed under Remote, but the post itself says "Remote work isn’t an option". The post for Button similarly doesn't allow remote, but uses "Remote - no" to convey that.
I've been planning on building some filtering for the Who is Hiring threads, and I've pretty much determined that some degree of manual review will be needed. In the most recent thread, I found a huge number of posts containing "remote" which don't actually allow remote working. "No remote" is fairly common and easy to filter out, but there are any number of variations that you can't anticipate a priori.
You're spot on with everything. I did a lot of manual review and the site already filters out "NO REMOTE", "REMOTE no", "Remote not" and "No Remote" entries. I did spot the "Remote work isn’t an option" post, but I decided I'm not going to write that kind of completely ad-hoc filtering rules, it's just ugly.
Let users can log in and change the remote/non-remote status (and other attributes).
Have some kind of trust system (could be linked to HN points or whatever).
(Even better if the YC guys made a custom job board where you fill in a form with all the details so there is no inconsistency.)
I think a combination of dependency parsing and regex is the way to go.
regex examples: "Remote: No", "No remote please"
Dependency parsing examples: ""Remote work isn’t an option", "Remote work will not be considered"
 look for negation in the parse tree using something like http://demo.ark.cs.cmu.edu/parse?sentence=Remote%20work%20is...
N-grams + Naive Bayes is potentially Good Enough.
Given these number I believe pretty much everything more complicated than that would be a total overkill... Good food for thoughts though!
"REMOTE no problem!" :) Just kidding. Great job.
A sample entry could be:
company: 'Some Company',
visa: 'Required/Not required/Transfer only/Sponsored',
Anyhow, I'm surprised. I'm a Hardware Engineer myself, so how could I miss that!
Once thing I changed to was just including top level comments and no replies/discussion of the posting. Do you handle similarly?
Here's how I pull them all down: https://github.com/ryanwi/hiringtrends/blob/master/lib/hirin...
// string contains string against lower case / no whitespace
As a sugestion for next feature, I'd recommend a selection for visa sponsorship or not.
On the other hand, once you're already browsing New York City, good ol' ctrl-f for VISA will probably serve you well enough.
keyworks: python, startup, collstuff
Visas Sponsered: YES
I am from Melbourne which made me looked at the Australian entries.
Perhaps add a simple tagging system where users can add tags to hiring posts. That way you don't need to comb through every post and hopefully you crowdsource some helpful taxonomic data.
what u have is too simplistic.
these things are just a starting point - further investigation on the company's site and actual location are always necessary.
One comment I got was that I had just mapped where HN users are in the world.
Less sure about lumping San Francisco and Palo Alto. Thoughts?
You can easily build your local Sqlite database like that. I wrote some more instructions about it on the README.md on Github.
It was pretty useful ~6 months ago. But, the amount of spam generated from recruiting and sourcing firms, various startups trying to push their revolutionary new online coding tools, etc. is pretty ridiculous and many of them, especially the SV-area startups, have been quite aggressive (e.g., phone calls and switching to my personal e-mail address after I told them I was not interested).
Posting jobs on twitter has been a far more effective sourcing tool than HN "Who is hiring" has become recently, at least in the free space.
One company, allowing remote work, sent me to do a personality inventory without even talking to me first -- which really bothered me. (They're still posting looking for DevOps and Developers in Indianapolis.)
One company scheduled an introduction phone call on the 25th of the month, and then didn't show up on time and attempted to reschedule on the 15th of the following month. (Apparently, they didn't understand "Hire fast, fire faster.")
Finally, one company wasn't up-front or honest about their salary expectations until after I had spent almost a month in their system -- even taking a week off of work to do one of their "trial weeks" only to discover that they were going to offer me approximately 50% less than what I was making now and that they had a standard 'formula' for salaries...things that if I would have known, I wouldn't have wasted their time (nor mine) going forward.
Don't get me wrong -- HN has brought me a lot of great things: context, opportunities, viewpoints, and friends. Unfortunately, the "Who is Hiring" has morphed into traditional HR -- where you send a resume and don't hear back anything from anyone, versus the near-immediate feedback that you would once get in 2012.
How do you go about posting jobs on Twitter? Rather, is there a special tag you use or something?
I think something like this would help you focus your recruitment efforts on those who have at least contributed to the community in some way, which should filter out people spamming every single email in the thread.
Another idea is to mask emails with a craigslist-like mailing address, which would give the end-user the ability to report an email as spam, and therefore tie that email to the offending party's hacker news account.
Edit: What I mean is that each hacker news account would see the email address as a different one, so when they emailed that account it uniquely identifies the account that originally viewed that email address. So, Spammer A sees Poster B's email address as email@example.com, and Legitimate Candidate C sees Poster B's address as firstname.lastname@example.org. When either one emails that address, if Poster B reports the email as spam, and if enough reports accumulate, the HN account sending the spam can be docked karma and lower them below the threshold allowed to view further posts.
The Who Is Hiring threads belong to this community. If something needs to be done to protect them for the community, we'll do it. But we'd ideally like to see a consensus emerge.
We should probably discuss this in a separate thread (and probably not today, as I'm about to be traveling). And I feel bad for taking a Show HN further off-topic, so will mark this subthread as such (which lowers it), even though it's obviously an important question.