3 ms·
If you’re not already, consider scraping and building a list of company workday public instances and pulling job postings from there as well. Should be straight
by toomuchtodo 2y ago
If you’re not already, consider scraping and building a list of company workday public instances and pulling job postings from there as well. Should be straightforward to find breadcrumbs in search engines with those URLs, or render permutations for testing based on known domain patterns.
- Jabbs 2y agoI'm not yet but thank you that is an interesting idea. Currently it is quite dumb and just looks for listings on each company website but in the future it would be nice to connect to workday or other such services
- day_visit 2y agoI'm not familiar with workday and new to coding. Is this beneficial compared to scraping company pages because workday will have consistent structure across companies?
- toomuchtodo 2y agoWorkday (if used, there are many other HRIS systems out there) is traditionally the source of truth as an HRIS (HR information system), is built into the org’s recruiting workflow, and the data has consistent structure. You don’t know where the data is coming from when directly on the company website, who is updating it and on what cadence (if any), etc.
- thih9 2y agoThis seems a small part of the problem - how would you know these jobs aren’t also listed on a popular job aggregator?
- toomuchtodo 2y agoYou wouldn’t, so you would have to scrape both and reconcile potentially. But where is the most accurate, current information likely to be sourced from? (think in systems)
- deleted 2y ago[deleted]