Yours has a much nicer/full featured implementation and would definitely not want to have two scripts running simultaneously.
Since LinkedIn's boolean logic is very limited and there are so many variations of job titles, it seems like setting a "loose" search on LinkedIn and then filtering out a longer list of specific job titles on the client side is the most versatile route. Without a UI (like yours has) the other script forces me to keep open devtools and the userscript while job hunting :)
Awesome!
Suggestion... Any chance of adding a wildcard or regex job title filter (and possibly a company/location one if it wouldn't make the script too heavy) like how this script is:
https://greasyfork.org/en/scripts/380954-linkedin-job-search-result-filter/code
Yours has a much nicer/full featured implementation and would definitely not want to have two scripts running simultaneously.
Since LinkedIn's boolean logic is very limited and there are so many variations of job titles, it seems like setting a "loose" search on LinkedIn and then filtering out a longer list of specific job titles on the client side is the most versatile route. Without a UI (like yours has) the other script forces me to keep open devtools and the userscript while job hunting :)