Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More Sites to Scrape #52

Closed
rpmullig opened this issue Jan 14, 2020 · 6 comments
Closed

More Sites to Scrape #52

rpmullig opened this issue Jan 14, 2020 · 6 comments

Comments

@rpmullig
Copy link

I attempted to adjust the 'providers' in the settings.yaml, but I found a few that raised errors. The following would be great additions to impact the tool:

  • 'hire.google'
  • 'Angel.co'
  • 'greenhouse.io'
  • 'jobs.jobvite'
  • 'workable'
@PaulMcInnis
Copy link
Owner

Just adding to this list here, so it is captured in the right place: https://news.ycombinator.com/jobs

@PaulMcInnis
Copy link
Owner

This seems like a decent source as well: https://remote.co/remote-jobs/

@rpmullig
Copy link
Author

Before moving into development, I worked in Finance and found many venture capital firms that had websites with listings of jobs for their investments. I could find a few of the main ones and post here.

@apontejosea
Copy link

apontejosea commented Oct 2, 2020

Is there any thoughts on inverting the dependency and make the scrapers pluggable? I'm thinking there is opportunity to define a clear interface/abstract class for people to implement their own scrapers. Later on, we could use the entrypoint mechanism to enable people to implement plugins in a separate package. In that way, the main JobFunnel framework can become more stable and anyone could create and maintain their own plugins as necessary as Python packages. Once in pypi, a requirements file could eventually look something like:

jobfunnel
jobfunnel-linkedin
jobfunnel-monster
...

@PaulMcInnis
Copy link
Owner

@Josian I'd be interested to see this idea with a more fleshed-out example architecture, It might be a good idea for maintainability and as the bloat grows around special cases.

I could see that fitting into the current ABC design where we are essentially building Base objects and then specializing per-locale, per-provider.

If you're interested in taking this further, a design for the class stubs would be a good place to start the discussion.

@PaulMcInnis
Copy link
Owner

#135 indeed India

Repository owner locked and limited conversation to collaborators Nov 25, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

3 participants