This would be more useful to me (as a hiring manager) with something that encouraged better links to somebody's accounts / portfolio / etc. instead of just their usually-empty HN profile.

e.g., I'm currently looking to contract somebody for some devops work here at Mozilla Research, and going through the set of listings that have 'devops' in them and actually finding a link to a resume / github account / anything more substantial than a twitter feed is pretty maddening.

Given that:

https://news.ycombinator.com/item?id=7685170

is coming up on the 1st of June.

I modified the template:

https://gist.github.com/cjbarber/189c84750cd42309201d

Thoughts?

That's fantastic - thanks much!

Lars, any plans for engineering openings at Mozilla Research (servo)?

Zura, I doubt we will open a new batch of full-time positions for Servo before the start of Q4. That said, I'm always willing to see what I can find for candidates with an exceptional background!

Shot an email

Hi! I also build job scrapers (http://nolatechjobs.leesome.com) and have a question about the dependency on redis... why not just generate a time-stamp within the ruby scraper (which you already do) and store it within the resultant json itself? Then you can use string comparison to see if the next scrape has returned a more accurate time-stamp and just overwrite that part of the string.

Basically my question is why couldn't you build the whole scraper with just flat files and no database/key-value store at all?

That would definitely be an improvement. When I originally wrote this in 2011, I had just a few hours, so I went with the quickest solution. For little personal side projects like this I find that Redis makes a great persistent hash map for storing bits of data between runs of a script.

Well someone already being doing this : http://www.ryan-williams.net/hacker-news-hiring-trends/

Thanks for mentioning this one, I hadn't seen it yet, but it's more or less what I had been imagining for my own mini-project...I guess I don't have to build it anymore :-).

It's on Github too if you're interested in improving or suggesting new ideas. https://github.com/ryanwi/hiringtrends

Thanks for posting this, I am the creator. Now, time to go publish June's update.

Seems like you aren't actively developing, but if anyone ends up forking this, it would be nice to see a version that degrades cleanly without JS.

I'll also happily accept pull requests :).

Really useful, I've been Control-F'ing the thread each day which hurts my efficiency vein. Glad I found this before I wrote my own :)

Thanks for the project and data! Just last week I was wondering if I could get it from somewhere :)