when doing a find people search, and I upload a list of companies to search... and i also include past experiences... but then i filter out people who are currently employed there.... when i add a job title search, it is showing me their current job titles... not previous job titles at the company, correct ?
Correct. When you enable "Include Past Experiences" and filter out current employees, the job title search will still show their current job titles, not their previous titles at those companies.
The "Include Past Experiences" toggle allows matching against previous roles for company, title, and experience filters, but the results display current job information. [1] To see historical job titles, you'd need to enrich the profiles after importing to get their complete work history.
Is that what you were looking for?
If you need any more help with your people search or understanding how job titles are displayed, I'm here to assist. Would you like to provide more details about what you're trying to achieve or any other questions you have?
this is what i was told: "Ted addressed this - the result list in Clay has to be less than 50,000 for the people search to work, and you're limited to 50k per table anyway. His solution was to not do it all at once. Start with your best customers only (purchased, not just signups), then work through it in batches. He mentioned doing it company by company or segment by segment - like if Nike has 150 former employees, you pull everyone at that company, then filter by title and job function after. The other thing he said was to use the company-level filters to narrow it down before you even get to people. So if your TAM analysis shows consumer software + B2C + growth stage companies convert best, apply those filters first to shrink the company list, then pull people from that smaller set. He also mentioned you can run this as a recurring workflow - once a month, pull people who changed jobs in the last 30 days from customer companies. That way you're not trying to do the entire historical backlog at once, you're just catching new movers on a rolling basis. So the practical approach: tier your customer list by value, start with purchased only, work through in chunks that stay under 50k, and set up a monthly job change trigger for ongoing"
That's solid advice from Ted. The 50k limit is real - both for search results and table capacity. [1]
His batching approach makes sense: start with high-value customers, use company-level filters first to narrow down before pulling people, then segment by company or criteria to stay under limits.
The recurring monthly workflow for job changers is smart too - catches new movers without hitting the historical backlog all at once. [2]
Are you planning to implement this batched approach for your search?
If you need any further assistance with implementing the batched approach or have more questions about your people search, I'm here to help. Would you like to share more about what you're trying to achieve or any specific challenges you're facing?
but really, its just a good signal so as long as they: actually worked there are currently in a marketing role is currently at a company that fits our ICP mold then we should run it
Exactly. With "Include Past Experiences" enabled, you can filter for people who previously worked at your target companies AND currently hold marketing roles at ICP-fit companies. [1]
The search will match their past company experience while showing their current job details, so you get that valuable signal of prior experience plus current relevance. [2]
Did that answer your question?
If you still need help refining your people search or have any other questions, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any challenges you’re facing?
so now that i have all these people, i should filter by job title? why coudlnt i just do that earlier ? what do u htink
You could have filtered by job title earlier - it's available as a search parameter alongside company and experience filters.
The advantage of filtering after is flexibility. You can see all matches first, then narrow down without re-running the search. Plus you stay under the 50k limit Ted mentioned by applying the most restrictive filters last. [1]
Both approaches work - it's about workflow preference and result management. [2]
Is that what you were looking for?
so i will get the same exact output ?
Yes, you'll get the same exact output whether you filter by job title during the initial search or after importing the results. [1] The search parameters work the same way - filtering early just saves you from importing unnecessary records.
