Your GTM belongs in gitRegister
Blog

Find Companies Using a Technology or Hiring for a Role

16 Oct
6min read

To find companies that use a technology or are hiring for a role, run Cargo’s theirStack.searchCompanies action with the technology slug in fields.company_technology_slug_or and the role in jobFields.job_title_or. Both filters go in one call, it costs 0.5 credits per company returned, and each company comes back with the technologies and job posts that qualified it.

Use theirStack.searchJobs when you want the postings themselves, and theirStack.searchTechnologies to read the stack of one known company. These are the steps behind the find-companies-using-tech skill for go-to-market lists.

How much this gets used #

Cargo platform data, 90 days to Oct 16 2026: theirStack.searchJobs ran about 117,000 times and theirStack.searchTechnologies about 98,000 times.

What each action costs, from its credit definition:

ActionCreditsCharged on
theirStack.searchCompanies0.5each company returned
theirStack.searchJobs0.5each job returned
theirStack.searchTechnologies0.5each call that returns a stack

A search that returns nothing costs 0 credits. No TheirStack account is needed: unless you connect your own key, Cargo runs the search on its key and bills credits.

Know where the technology data comes from #

TheirStack detects a company’s technologies from the technologies its job postings mention. That makes it strong for tools engineers and operators are hired to run (a warehouse, a CRM, a cloud) and blind to tools a company uses but never writes into a job ad. Each detection carries a confidence of high, medium or low, plus first_date_found and last_date_found.

Run it #

1. Install and sign in

shellscript
npm install -g @cargo-ai/cli
cargo-ai login --email you@company.com                 # sends a code
cargo-ai login --email you@company.com --code 123456   # creates the account on first use

2. Companies using a technology and hiring for a role

US companies of 50 to 1,000 people that use Snowflake and posted a data engineer role in the last 60 days:

shellscript
cargo-ai orchestration action execute \
  --action '{"kind":"connector","integrationSlug":"theirStack","actionSlug":"searchCompanies"}' \
  --data '{
    "fields": {
      "company_technology_slug_or": ["snowflake"],
      "company_country_code_or": ["US"],
      "min_employee_count": 50,
      "max_employee_count": 1000
    },
    "jobFields": {
      "job_title_or": ["data engineer"],
      "posted_at_max_age_days": 60
    },
    "limit": 10
  }' \
  --wait-until-finished

Drop jobFields for “uses Snowflake” alone, or drop the technology filter for “is hiring data engineers” alone. limit defaults to 10 and goes up to 500; start at 10 (5 credits at most) and read the results before raising it.

The filters that matter most:

FilterGroupTakes
company_technology_slug_or / _and / _notfieldsTheirStack technology slugs, lowercase (snowflake, hubspot)
company_country_code_orfieldsISO2 country codes, case sensitive (US, GB, FR)
min_employee_count, max_employee_countfieldsnumbers
funding_stage_or, min_funding_usdfieldsfunding filters
job_title_or / job_title_notjobFieldsnatural-language title patterns, case-insensitive (full-text search)
job_title_pattern_orjobFieldsregex title patterns, case-insensitive
posted_at_max_age_daysjobFields0 is today only, 1 is today and yesterday, and so on
job_country_code_or, remotejobFieldswhere the job is
confidence_or, first_date_found_gtetechFieldsdetection confidence and dates for the technology match

Unknown keys are not errors: a filter under the wrong name or group is dropped, and the search runs without it. If the results look unfiltered, check the spelling and the group against this table.

3. The job posts themselves

searchJobs returns postings rather than companies. Job filters go in fields, company filters in companyFields:

shellscript
cargo-ai orchestration action execute \
  --action '{"kind":"connector","integrationSlug":"theirStack","actionSlug":"searchJobs"}' \
  --data '{
    "fields": {"job_title_or": ["revenue operations"], "posted_at_max_age_days": 30, "job_country_code_or": ["US"]},
    "companyFields": {"company_technology_slug_or": ["hubspot"]},
    "limit": 10
  }' \
  --wait-until-finished

4. One company’s stack

searchTechnologies reads the stack of a company you already have:

shellscript
cargo-ai orchestration action execute \
  --action '{"kind":"connector","integrationSlug":"theirStack","actionSlug":"searchTechnologies"}' \
  --data '{"fields": {"company_domain": "acme.com"}, "limit": 50}' \
  --wait-until-finished

It costs 0.5 credits per call, however many technologies come back.

What comes back #

ActionFields to read
searchCompaniesname, domain, linkedin_url, country_code, employee_count, industry, num_jobs, technology_slugs, and the evidence: technologies_found[] (confidence, first_date_found, last_date_found) and jobs_found[]
searchJobsjob_title, url, date_posted, company, company_domain, location, remote, seniority, technology_slugs, hiring_team[] (full_name, role, linkedin_url)
searchTechnologiesper technology: technology.name, technology.category, confidence, jobs, jobs_last_30_days, first_date_found, last_date_found

hiring_team lists the people named on a posting, with their role, when the source names any. It is the shortest path from a job post to the team that will run the tool.

Caveats #

  • Hiring is a short signal. A posting is evidence for weeks, not quarters. Keep posted_at_max_age_days tight and rerun on a schedule rather than working from an old pull.
  • A mention is not a contract. “Experience with Snowflake” in one job ad can be a nice-to-have. Prefer high confidence and several jobs when the technology is the reason for the outreach.

To turn the companies into people, find the buying committee at each domain, or search leads by job title across them.

Frequently asked questions #

AurelienOct 16, 2026

Give your agents a runtime

Bring the agents you have.Start free, deploy in one command.