One suggestion for the posting text: maybe provide a more machine-readable template for submitters to provide metadata? Just a minimal amount of metadata to make it easier for those who write mini-apps to parse the submissions.
Soostone | NYC or Remote Possible | Functional Programmer (Haskell) | Backend, Frontend, DevOps, UI/UX Engineering
San Francisco - Full Time - iOS, Android, Design
GoDaddy | Product Manager - Managed WordPress | Sunnyvale, CA or Phoenix, AZ | Local
How about this, for each job:
[Company name] | [Job title] | [location(s), semi-colon delimited] ["Remote", if applicable] | [Full-time/Part-Time/Intern/Visa/Remote | [Optional list of semi-colon delimited skills]
e.g.
Acme | Senior Database Engineer | San Francisco, CA; Las Vegas, NV (Remote possible) | Full-time | MySQL
Yeah, the balance has to be between ease of reading and ease of typing into the browser's plaintext input box. It just has to be easier to parse than what is now...which, to be honest, isn't terribly hard to parse, but it's enough of a barrier to make it more than an afternoon hack project.
Yes. Please add a way to reliably determine metadata on hiring posts. I wrote https://github.com/perspectivezoom/curated-hn-hiring but abandoned it after a couple months because it took way too much time to tag all posts.
By far the most important information seemed to be location and/or remote filtering. Gaganpreet stepped up and is doing a pretty good job with https://github.com/gaganpreet/hn-hiring-mapped, but it's still not 100%.
I would really love for whoshiring to provide this pipe-delimited template, and then optionally allow posters to conform to it. I also agree with danso's order of importance, but would also like to add that the location string(s) should be something geocodable by Maps APIs (ie, feed the string in and get an unambiguous LatLng).
I don't actually like that proposal[1] very much as it stands -- but perhaps moving discussion/pull-requests there would be useful? (I've not yet added my own comments there, but now with two threads on the subject on hn, I'm seeing the need to consolidate, if we want to get a wide range of contributions, and try to gravitate to the "best" solution...).
[ed: ah, I see I'm replying to the author here... I was a bit quick. Anyway -- the point of discussing a spec with a tool that support pull-requests/diffs etc still stands -- and I think it might be a good idea.]
One suggestion for the posting text: maybe provide a more machine-readable template for submitters to provide metadata? Just a minimal amount of metadata to make it easier for those who write mini-apps to parse the submissions.
To refer back to the most recent hiring post:
https://news.ycombinator.com/item?id=9471287
Seems like submitters try to do their own, e.g.
How about this, for each job:[Company name] | [Job title] | [location(s), semi-colon delimited] ["Remote", if applicable] | [Full-time/Part-Time/Intern/Visa/Remote | [Optional list of semi-colon delimited skills]
e.g.
Acme | Senior Database Engineer | San Francisco, CA; Las Vegas, NV (Remote possible) | Full-time | MySQL