I guess this is the HN way of turning a simple proposal by dang (for feedback) into an engineering problem where we try to solve:
The optimal method of describing a job post where the utility of most users/readers is, at least, mostly satisfied
Companies have been asking candidates to give their salary up front ("expectations" or "history") without ever justifying it when it's obviously not in our best interest to do so...yet they do already have a budget for these positions, so let us decide if we are in the range or not. (Rather than applying for jobs which will never offer a salary commensurate with our experience because we read the demand for high end skills and "salary commensurate with experience"-- and don't realize it's someone trying to score a deal, and not really offering a market salary.)
Acme Products | Test Engineer | Las Vegas, NV; Austin, TX | Onsite; Remote | Full-Time; Part-Time | Visa (H1B) | Tunnel Theory; Kinematics
Engineer needed to test prototype products. Must be able to lift and carry anvils.
The only real problem I've had with existing listings, is that people tend to list both "remote" and "no-remote" -- making search hard.
I propose moving those "tags" to "hash-tags", and just list them at the bottom of the ad:
Acme Products | Test Engineer | Las Vegas, NV; Austin, TX
#on-site #full-time #part-Time
Note that the two are different; I don't see how you could work remotely testing anvil-lifting... ;-)
At any rate, if we're talking about a new "spec", I'd say:
* Apart from position, and location, as little as possible on the first line.
* Replace the "text"-tags with "hash"-tags - #remote is easy to search for with text-search, and won't match #no-remote, No-remote -- and doesn't require regexp magic to match word-boundaries etc (which few (no?) browsers support anyway).
* Put the tags at the bottom -- they're really for searching (and machine parsing), with the amount of listings we are getting now -- no-one is reading just your ad, they're reading a stream of ads.
* Don't go overboard with "hash"-tags. I'm not all that interested in seeing: mulitple-line lists of #python #ruby #haskell #c++ #dev-ops (...)
Now, if we really want to over-engineer this thing, why not draw some inspiration from the Dewy decimal system? So 001-234 could be 001:devops 2:python and bash 3:unix-like-and-windows-nt 4:remote-or-onsite ... ;-)
Pretty easy to build, not so easy to get community engagement unless the HN folks endorse it officially as an alternative.
The companies posting in Who is Hiring aren't posting on HN because they have no place else to post.
Then the post is still on HN and is formatted to the spec.