3 ms·
From looking at postings so far, my guess is it's not natural for the submitters to remember or accurately list the job params as you've laid out. My suggestio
by asidiali 10y ago
From looking at postings so far, my guess is it's not natural for the submitters to remember or accurately list the job params as you've laid out.
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!
- xando 10y agoI agree. I'm talking to HN people, they are in loop as well here. There is a chance that they will suggest something or we will adopt the format that I'm posting. Always would be good to have some feedback before too not miss to many things later. 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.