My suggestion would be, if you're not already doing/working on it, to start doing some basic NLP around the specific verbiage used for each param, and then you can organize by match instead of by position in the list. I'm betting you'll see some nice results without much optimization even since each expected param argument is pretty different from one another.
Just an idea, best of luck!
As for the NLP, I'm doing it (kind of and I've tested many things including Stanford NER lib and external APIs) Having said that, If your format wont comply, no worries. I will do my best to find the location, tag the job if it's remote or intern. Although to get the rest like company name, positions names the mission is hard here.
Anyone searching through the comments for "REMOTE" is going to get all those NO REMOTE jobs as well, which is a pain. Using ONSITE makes it much more clear.
> Please lead with the location of the position and include the keywords REMOTE, INTERNS and/or VISA when the corresponding sort of candidate is welcome. When remote work is not an option, please include ONSITE.
https://whoishiring.io
Also I’ve started a small campaign to update thread format and make it more parser friendly for whoishiring.io and others (I know that at least few websites that do similar thing). Also you can read more about whoishiring.io in a recent “Show HN” (https://news.ycombinator.com/item?id=13500701)
Here is the format.
or I’m using this regex to test the firstline. You can test it in Python or here https://regex101.com/r/relwQD/3 (for the match look right).As a result off this calling in previous editions of “Who is Hiring” many posters actually complied. Which resulted in more accurate map positions, better tagging (REMOTE, VISA, INTERNSHIP, …) and for some I was even able to get LOGOS!. Thanks!