Feature Request: Extend "Easy apply" to non-"Easy apply" jobs

[helderjbe]

I know the repo's name is linkedin-"easy-apply"-bot, but extending the bot to search for non-easy-apply jobs could add a lot of value to the project.

For example, since my applications are very targeted, I use the bot mostly for the scraping functionality. I use extended regexes for finding terms in the descriptions and that for me is the best part of this tool.

A first version takes very little effort as well. Just add an option for scraping also non-easy-apply jobs.

Also, thank you for this project. It helped me tremendously.

[joaosilvalopes]

Hi again @helderjbe sorry for the delayed response things have been a bit busy at work

I need to do some research on how easy it would be to add this functionality but it is definitely in the roadmap and has been on my mind for quite a while :)

I am happy that this tool has been of some use to you, and i am particularly happy that the regex functionalities has been of some use to you :smile:, i wasn't sure whether to do it with regexes since non technical folk might get a bit confused

This issue can stay here for when this functionality is added :+1:

[IggsGrey]

I'm sure this has crossed the minds of many people, but first of all considering the wide differences between websites and their design schema, this could be a very challenging feat.

For instance:

• Some websites will have landing page for the job post with the job description and an "apply" button. This could either open a new page (in a new tab, same tab or heck even a new window) or a modal.
• Some websites will most likely have other fields that will require human intervention in order to fill - since there are just too many questions a recruiter might ask. (believe it or not, I've been asked what my favorite food is before)
• Not to forget about the famous captchas and are you a robot checkboxes.
• Some websites might even have popups covering the screen on load.

With all these factors to consider, I wonder if we'll be able to pull this off.

[helderjbe]

Ah, what I meant as a first version is to simply add an option to disable the "easy apply jobs only". What I am doing currently is going to fetchJobLinksUser and change f_AL to false, like so:

const searchParams: { [key: string]: string } = {
    keywords,
    location,
    start: numSeenJobs.toString(),
    f_WT: fWt,
    f_AL: "false", // Setting false removes the Easy apply option on search
  };

With this, the script presses apply and it goes on to a new page. Just this functionality by itself is awesome because I don't have to read the descriptions of the jobs and whatnot. Essentially I'm using this as a pure job scraper.

[SlideeScherz]

Crawling a single website is easy, but every site has different selectors and this is a difficult task without AI. I suggest this issue be marked stale