.png&w=3840&q=75){kind=logo}
Issues with 'Find Jobs' Feature Reporting Incorrect Job Posts
Anyone having trouble with the 'Find Jobs' feature? It says there were only 2 job posts for 'software developer' yesterday in the US, which is 100% not true
Anyone having trouble with the 'Find Jobs' feature? It says there were only 2 job posts for 'software developer' yesterday in the US, which is 100% not true
You can check my source here
Yes, there are some known limitations with job search results that could affect accuracy:1. The search system doesn't have semantic search capabilities yet, so you'll need to include various permutations of job titles (e.g., "Software Engineer", "SWE", "Software Developer") to capture all relevant openings. 2. The data might show inaccuracies due to limitations from data providers and how they access the information.To get more accurate results, try these tips:** Use multiple variations of the job title ** Start with broader search terms ** Adjust your filters gradually ** Consider expanding your keywords and search parameters if results seem incompleteThe search uses Google's Cloud Talent Solution API for job listings, so results may vary based on their data availability. Sources: Find Jobs Source + Enrichment [Clay 101] - Clay University Find Open Jobs with Google
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
LinkedIn says there should be over 11k results
Can someone please help?
Hey Nicolas, taking a look at your find jobs source now. It looks like the companies filter in your source actually links to the incorrect column in your companies table. It links to a formula text column instead of a column with domains/company linkedIn urls. https://downloads.intercomcdn.com/i/o/w28k1kwz/1296423130/44a435d3662aaff5f76801f9a786/CleanShot+2024-12-13+at+19_55_48%402x.png?expires=1734102000&signature=4fb4bad597a7af46eb3f3611a03abf5a0af38c0e773d6c6fbd4f7df9c9674ff5&req=dSIuEM18noBcWfMW1HO4zauxxm6JffSK5v%2Bh99Vg6ww2SGN65ToSxUeRfKlk%0Ag7F6%0A
I just changed this column to company website
I actually removed this company filter altogether and saw significantly more results
I removed it altogether (I want EVERY job), but it still brings only 250 jobs approx. Should be way more. What else am I doing wrong?
So we did the same 😆
These are updating in your table now - feel free to take a look
Yes, but that's 200. There should be over 1k
Or close to that number
I think something's happening at least since yesterday with the search. My lists were consistently 2-3k, and yesterday it was only 800 jobs. Same everything, so doesn't make a lot of sense, and much less sense that today it's only 200
Or maybe I messed up yesterday's table and am just duplicating the error now?
Hey Nicolas, did you always apply only 1 day filters for the post date?
Yes. This is something I do every single day: I check for the jobs posted the previous day
FYI: if I just re-run the source, it adds more records. I'm at over 350 now Still looks like something's wrong
One of the job titles on my search is 'software engineer'. If I go to LinkedIn, filter by last 24 hours and the same job types on my list, and put 'software engineer' as job title, I get 11k results. If I do the exact same thing on Clay (without any negative keywords), I get 149. Something's broken
Hey Nicolas, our jobs data comes indirectly from LinkedIn so there might be something going on with one of our data providers here. Let me check with our engineers to understand this discrepancy.
Please. Here's a brand new table in which all I did was adding 'software engineer' as a job title, 1 day-old posts, and United States as location. Only 150 results, while the same filters on LinkedIn return 11,882 results
That should eliminate all doubts; there is an issue when pulling the data from LI to Clay
Hey Nicolas, we've also noticed how important pulling recurring jobs have been to your workflow and wanted to share something that would make this easier for you (cue drumroll)... SCHEDULED SOURCES! 🤩 With this feature, you can run your find jobs search on recurring and customizable frequencies. Here's a quick Loom on how this works: https://www.loom.com/share/823e883436f2466c8ba88282abc9ae0b?sid=81e8da93-9d24-4b51-89cc-066072e3b525 Please note this feature is in beta, so you're getting early access because we think it could really benefit you. Would love any feedback here as well. Give it a try and let us know what you think!
This message was deleted
Hey nicolas, got an answer for you! The reason you're seeing a discrepancy in jobs results is due to ingestion lag. These jobs have to be pulled by our data provider, delivered to us, then ingested so they're not updated as immediately as you would see on LinkedIn which is the direct source. We recommended increasing the post filter date here to work around this!
I don't get it. You say that there's a delay on your input so yesterday's posts are not yet there?
Will this get solved eventually or is it by design?
Hey Nicolas, what's occurring is a delay in Clay receiving and processing this jobs data compared to LinkedIn. This is why not all of yesterday's job postings are not visible in the results. This should get better as we increase our data providers here.
So if I waited 10 days (just to put a number), and tried to import everything from the last 10 days, the data from 10 days ago would be complete, but the data from one day ago would be incomplete. Is that so?
hey Nicolas, I don't have an exact number for you on how long the ingestion delay takes to fully update and don't want to misinform you. Checking with my team and will get back to you!
Just making up numbers. I'm tryin to understand if after enough days the'll all be there
?
Hey there - just wanted to check in here to see if you needed anything else! Feel free to reply back here if you do.
All done, thanks
Hi Nicolas P.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Thank you so much for sharing your feedback Nicolas P.!
