Outputs on this page come from a live run on September 12, 2026. Company names are masked to initials. No contacts were previewed or revealed.
New job post is one of 26 company signals in the Lusha plugin for Claude, filterable by department. Firmographic fit says a company could be a customer. A job posting in the exact department a product serves says the need is current, specific, and visible before it shows up anywhere else a marketer would normally look.
Find companies with a new job post in a specific department and return a list ready to sync into an ad audience.
Before anything else, run account_usage and tell me my remaining credits. Do not run any signal call if fewer than 50 credits remain; stop and tell me.
Here is my list (domain, one per line):
[PASTE UP TO 25 DOMAINS]
Target department:
[PASTE]
Steps:
1. Run signals_companies_search on the list with signalTypes ["newJobPost"], with filters.include.hiringByDepartments set to the target department, startDate 30 days ago.
2. Group results by account, listing every matching posting with title (where returned), location and posted date.
3. Flag any posting whose job title looks unrelated to the target department (for example a finance or marketing title returned under a Sales department filter); note it rather than dropping it, since department taxonomy can group revenue-adjacent roles together.
4. Sort accounts by number of matching postings, most first.
Output: one table with columns Account | Department | Locations | Posted dates | Posting count. Then two lines: total accounts matched, and credits used.The situation. The same three roster accounts, filtered to new job posts in the Sales department only. Names masked to initials with an industry descriptor: S.K. (data cloud platform), D.D. (cloud monitoring platform), M.G. (database platform). Target department: Sales.
The run. account_usage first, at zero credits. One batch call on 3 domains for newJobPost filtered to Sales, 30 day window. 3 of 3 fired, 14 signal events, 16 credits.
What came back.
| Account | Department | Locations | Posted dates | Posting count |
|---|---|---|---|---|
| S.K. (data cloud platform) | Sales | Canada, Australia, US-TX, UK, US-CA | Sep 2-4 | 5 |
| D.D. (cloud monitoring platform) | Sales (incl. Strategic Account Executive, VP Enterprise Sales) | Singapore, US, Australia, Brazil | Sep 3-7 | 5 |
| M.G. (database platform) | Sales (job titles returned: Regional Marketing Manager, Financial Analyst x3) | US, Ireland, Mexico | Sep 4 | 4 |
Total accounts matched: 3 of 3. Credits used: 16. Confirmed live via Lusha connector, September 12, 2026. Company names masked.
What happens next. All three accounts qualify for the audience, ready to sync into an ad platform or ABM tool. M.G.’s result is the one worth flagging before it ships: three of its four Sales-tagged postings carry titles like Financial Analyst, not a quota-carrying role. That is Lusha’s department taxonomy grouping revenue-adjacent functions under Sales, not a data error, and it is worth a line in the audience brief so whoever runs the campaign does not assume the filter is broken. Layer in the stacked signal scoring play if the audience needs narrowing further before spend.
A department level hiring filter is a sharper targeting criterion than industry or company size alone, and it is rarely used that way because most teams do not have hiring data and firmographic filters available in the same place. This prompt builds the audience directly from live postings, filtered to the exact function a product serves, ready to sync into an ad platform or ABM list without a manual cross reference step. Every signal is sourced under Lusha’s data methodology and compliance framework.
Same underlying signal, different use. That play ranks individual accounts for one to one outreach. This one builds a list level audience filtered by department, meant for an ad platform or ABM tool, not a per account opening line.
Department taxonomy on job postings groups revenue-adjacent roles together; a Sales department filter can return titles like Financial Analyst or Regional Marketing Manager alongside quota carrying roles. This is a taxonomy grouping, not a data error, and the prompt flags it rather than silently dropping those rows.
Refresh at least monthly. Postings close faster than most firmographic filters change, so a stale list will include roles that are no longer open.
Yes. Layering funding or headcount growth on top narrows the list further, the same signals used in the stacked signal scoring play, applied here to audience building instead of individual ranking.
One credit per event returned. In the live run, three roster accounts returned 14 events for 16 credits. No contact preview or reveal runs in this play.
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
