A job post tells you what a company plans to build and where it lacks capacity. If the role overlaps with your service, that company is worth researching now.
This workflow uses public job posting data from LinkedIn, X, and Google to build a sourced B2B lead list. Hiring is a research signal, not proof that the company wants an outside vendor.
SocialListeningAPI searches public posts on LinkedIn and X and Google results for the phrases you choose. It returns normalized records with source URLs.
Step 1: Match roles to the problem you solve
Create a SocialListeningAPI account and copy your API key. Write a small list of roles and skills that connect directly to your offer.
For a data engineering agency, useful searches may include:
we are hiring data engineerhiring analytics engineerdbt developer jobbuilding our data teamSnowflake migration hiring
The phrase should reveal both the role and the work behind it.
Step 2: Search public job posting data
Run each phrase across LinkedIn, X, and Google:
for endpoint in linkedin/search-posts x/search-posts google/search
do
curl --get "https://api.sociallisteningapi.com/api/v1/$endpoint" \
--data-urlencode 'query=we are hiring data engineer' \
--header 'x-api-key: YOUR_API_KEY'
doneOne phrase across three sources costs 4 credits when all requests succeed. Use the LinkedIn post search endpoint, X post search endpoint, and Google search endpoint for source-specific details.
Social results include the post text, author, URL, and publication time. Google results include the
page title, description, and URL in the same data.items location.
Step 3: Verify the role is still open
Open the source and confirm the company, role, location, posting date, and application page. Remove staffing reposts, closed jobs, and list pages that do not identify the employer.
If several posts point to the same role, keep one company record and attach the strongest source.
Step 4: Build the account note
Store the company, role, required skill, source URL, posting date, and one reason your service may help. Your spreadsheet, CRM, contact enrichment, and scoring happen outside SocialListeningAPI.
A useful note is specific: Hiring two analytics engineers while migrating to Snowflake. Avoid
generic notes such as Company is growing.
Step 5: Review the list weekly
Five phrases across three sources cost up to 15 credits per run. An external weekly schedule keeps the list current without checking the same jobs every day.
Conclusion
Pick one role your service knows well, then research each company before contacting anyone. Refer to the visible project instead of sending a generic hiring pitch.
Before using the list, check that every company still has a live role and a clear link between its hiring plan and the problem you solve.
Continue with Build an Event-Based Account List.
