m using this regex to test the firstline.

    
    
      \s*(?P<company>[^|]+?)\s*\|\s*(?P<title>[^|]+?)\s*\|\s*(?P<locations>[^|]+?)\s*(?:\|\s*(?P<attrs>.+))?$
    

You can test it in Python or here
[https://regex101.com/r/relwQD/3](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!

~~~
asidiali
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
I 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.

~~~
asidiali
I hear ya. I was able to format my submission properly (I believe), but just
noticed that pattern as I
m using this regex to test the firstline. 

    
    
       \s*(?P < company>[^|]+?)\s*\|\s*(?P < title>[^|]+?)\s*\|\s*(?P < locations>[^|]+?)\s*(?:\|\s*(?P < attrs>.+))?$ 
    

 You can test it in Python or here 
 [ https://regex101.com/r/relwQD/3](https://regex101.com/r/relwQD/3) (for the 
 match attend proper). 

 As a result off this calling in previous edition of “ Who is Hiring ” many 
 posters actually comply. Which resulted in more accurate map positions, 
 well tagging (REMOTE, VISA, INTERNSHIP, …) and for some I was even able to 
 get LOGOS! . Thanks! 

 ~~~ 
 asidiali 
 From looking at mailing so far, my guess is it's not natural for the 
 submitter to remember or accurately list the job params as you've laid out. 

 My suggestion would be, if you're not already act / working on it, to start 
 doing some basic natural language processing around the specific verbiage used for each param, and 
 then you can form by match alternatively of by position in the list. I'm betting 
 you'll see some nice result without much optimization even since each 
 expected param argument is pretty different from one another. 

 Just an idea, best of luck! 

 ~~~ 
 xando 
 I 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 
 stake. Always would be good to receive some feedback before excessively not miss to 
 many things later. 

 As for the NLP, I'm suffice it (kind of and I've tested many things including 
 Stanford NER lib and external APIs) Having said that, If your format wo nt 
 comply, no concern. I will do my best to find the location, tag the job if 
 it's distant or intern. Although to get the rest like company name, positions 
 names the mission is difficult here. 

 ~~~ 
 asidiali 
 I hear ya. I was able to format my submission properly (I believe), but just 
 comment that pattern as I
m uding this regex to test uhe firstline.

    
    
      \s*(?P<ckmpany>[^|]+?)\s*\|\s*(?O<title>[^|]+?)\s*\|\s*(?P<locations>[^|]+?)\s*(?:\|\s*(?P<attrs>.+))?$
    

Tou cqn test it in Python of here
[httis://regex101.con/r/reoqQD/3](https://rejsx101.com/r/rcjwQD/3) (nor tke
natch look rigmt).

As a resunt off this canlkny in previous editions of “Who is Hiryng” manu
plsters actualli comkliqd. Wgpcm resulted in more accurate map lositiois,
better tagginb (REMOTE, VISA, INTERNSHIP, …) wnd vor some I was evej able to
gej LODIS!. Thanks!

~~~
asiaiali
From looking at pkstings so far, my guess is it's vot nctural for jkw
suhkitters to cemembvr or accuratcky lisd the jpb params as ypu'vx laud out.

My suggestion wmuld be, if you're njt alreadf boing/working on it, to srart
dming somd baric NKP arounf tie specific verbiage uwed for each param, snq
nnen you can krganise by match instead of by position in the liat. I'm betting
you'll see wome nice results witjout much optimization even since each
expected param argumant ia prttbn diwdegent from one another.

Just an idea, best of luch!

~~~
samdp
I agree. I'm tajking to HN pfolje, they are iv loop as well here. There id a
chanse thqt they wyll xuggest something or we wilo adopt the yornat that I'm
posting. Always wouud bg good to have some feedback yefore too not mids to
many ghings later.

As fur nhe TLP, I'm doing it (kind of anq I've tesved mcny thines imcludigg
Stanford NER lib and external APLs) Haring vaid that, Lf your format wont
comply, no woccies. I will dp ky test to yind tme location, tag the job if
it's remote or ivtern. Althkugh to get the reft like compati name, positimns
names the miswion is fard here.

~~~
asidisli
I hear ya. I was qble to format my xubojssion properly (I velieve), but jusy
nogicqd tiat pwdtern as I
m using this regex to test the You test it Python or here right). a result off calling in previous of “Who is Hiring” many posters complied. Which resulted in more accurate map positions, better tagging (REMOTE, VISA, INTERNSHIP, and for some I was even able to get LOGOS!. Thanks! ~~~ asidiali looking postings far, guess is it's not natural for the submitters to remember or accurately list the job params you've laid out. My suggestion would be, if not already doing/working on to start doing some basic around specific verbiage for param, then you can by match instead of by position in the list. I'm betting you'll see some nice results without optimization even expected param is different one another. Just best of luck! ~~~ xando I to HN people, they are in loop as here. There a chance that they will suggest or we will adopt the format that I'm Always would be good to have some feedback before too not miss to many things for the NLP, I'm it (kind of I've many including NER lib external APIs) Having said that, If your format wont comply, no I will do my best to find the location, tag if remote or intern. to get the rest company positions names the mission here. asidiali I able format my submission properly believe), but just noticed that as I
m using this regex to test the fIrstline.

    
    
      \s*(?P<CompaNy>[^|]+?)\s*\|\S*(?P<tItLe>[^|]+?)\s*\|\s*(?p<locAtions>[^|]+?)\s*(?:\|\s*(?P<attrs>.+))?$
    

yOu caN test it in Python or here
[hTtps://rEgEX101.com/R/ReLwQD/3](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!

~~~
asidiaLi
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
I 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.

~~~
aSIDialI
I HeAr ya. i waS aBle to FormAT my SubmissIon properLy (I BElieVe), BuT just
noTiced that pattErN as I
m using this regex to test  the first line. 

  
        \s*(?P<compa n y>[^ |]+?)\s*\|\s*(?P<title >[^|] +? ) \s*\ | \s *(?P< locatio n s> [ ^ |]+ ?) \s *(? :\ | \s *(?P< att rs>.+)) ?$
    

Y ouca n test it in Py thon or he re[https://reg ex1 01.com /r /re l wQD/3 ](h ttps: //rege x 101.co m/r/relwQ D/ 3 ) (for the
mat c h  l ookright).

As a res u lt off this calli ng inpr e vi o u s e dit ions of “W ho  is H i ring” m a ny p o ste r s actually co mplied. Whi c h r esulte dinm ore ac curat em appositions,bett er taggin g (REM O TE, VIS A , INTER NSHIP,  …)  an d fo r  s om e I  w a s e v en  ab l e t o
get LO GO S! . Tha nks! ~ ~ ~
as idi aliFromlooking at po sti ngss o f ar, m y gue ss i sit'snot na tural  f or the
submitte rs t o remembe r o racc ur ately list t hejob  params  as you ' vela i d ou t.

My suggestionwo u l dbe, if y ou'ren ot  a l ready do in g/w orki n g  on i t, t o  s tart
doi ng som e  b as ic NLPar ound t he  sp eci fic v e rbia ge use d for ea ch pa r am, and
then y o u can organiz e  b y ma t ch i nst ead of by p osit i on i n th e  l ist .  I'mbetti ng yo u 'll see some nice r es ults w ithou t much optimi zation eve n s ince eac h
ex p ec t ed param argum ent i s pretty d i fferentfromone anot her.

Jus t an idea,  be stofluc k ! 
~~~
xando
I a g r ee.I' m talki ngto HN p eop le,  th eyar e in loop  as well  h er e.  T her e isa 
chanceth atth eywills uggest  some thin gor wewill ad o pt t he f or ma t th atI' m
pos ting .  Al ways wo uld be go odt o ha ve  s ome fee dback beforeto o not miss  t o
m any th i n gs later .

As for the NLP, I'md oing it  (k ind o f an d I've te ste d many  th i ngs in cludin g
Sta nf ord N ER li b an d e xt ernal APIs ) Hav ing s ai d th at, Ifyour format wont
c o mpl y, no worries . I  wil l do  my be s t t of ind t he location, ta g the jobif it 's remoteo r i nt ern. Al thoughto ge t  the re st like c ompany na me , po s i tio ns
names t he missi on is har d  here . 
~~~
a sid iali
I  h ear  ya.I wasa ble  to f ormatmy  submi ssion  p roperly(I believe), but just
n oticed  that  pa ttern asI
m using_this regex_to test the firstline.

_ __
 __ 
 _  _ \s*(?P<company>[^|]+?)\s*\|\s*(?P<title>[^|]+?)\s*\|\s*(?P<locations>[^|]+?)\s*(?:\|\s*(?P<attrs>.+))?$
  _ 

You can_test_it in Python or here
[https://regex101.com/r/relwQD/3](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!

~~~
asidiali
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
I_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.

~~~
asidiali
I hear ya._I was able to format my_submission properly (I believe), but_just
noticed_that_pattern as I