slug: find-accounts-hiring-for-a-role
type: recipe
format: usecase
audience: sales
status: published
title:
  en: Find which of your accounts are hiring for a role
  zh: 看你的目标客户里谁在招某个岗位
dek:
  en: Count one role's open postings at every company on your list, next to all of its open postings, and call the ones that are hiring for what you sell first.
  zh: 对名单上的每家公司，数它在招的某个岗位，并和它全部在招岗位放在一起看，先联系正在招你所卖产品对应岗位的公司。
datasets: [jobs]
integration: [rest, mcp]
topics: [sales, ai-hiring]
regions: [global]
snapshot: 2026-09-30
published: 2026-09-30
exploration_credits: 10
agent_run: { low: 20, high: 20, cap: 30 }
highlights:
  - value: "14"
    label:
      en: open data engineer postings at Databricks
      zh: 个 Databricks 在招的数据工程师岗位
  - value: "4"
    label:
      en: of 10 accounts have 5 or more
      zh: 家公司（共 10 家）在招 5 个以上
usecase:
  who:
    en: A seller of data infrastructure, or anyone whose buyer is a specific team. A company hiring several data engineers right now is building the thing your product helps with.
    zh: 卖数据基础设施的销售，或者任何客户是某个具体团队的人。一家公司现在同时在招好几个数据工程师，说明它正在做你的产品能帮上忙的事。
  figures:
    - file: accounts.json
      key: company
      value: role_count
      context: open_count
      title:
        en: Open data engineer postings at ten accounts
        zh: 十家公司在招的数据工程师岗位
      note:
        en: Each bar is the open postings whose title matches "data engineer". The number on the right is all of the company's open postings, so a big hirer does not look like a strong signal only because it posts a lot.
        zh: 每条是标题匹配 "data engineer" 的在招岗位数。右边的数字是这家公司全部在招岗位，免得招人多的公司只因为岗位多就显得信号强。
      legend:
        value: { en: "Data engineer postings", zh: "数据工程师岗位" }
        context: { en: "All open postings", zh: "全部在招岗位" }
  reads: [company.name, title, posted_date, location.city]
  next:
    - title: { en: "Start with the strongest signal", zh: "从信号最强的开始" }
      body:
        en: Sort by the role count, then check the share of all postings. Five data roles out of 200 says more than ten out of 2,000.
        zh: 先按岗位数排序，再看占全部岗位的比例。200 个里有 5 个，比 2,000 个里有 10 个更说明问题。
    - title: { en: "Quote the posting", zh: "引用岗位原文" }
      body:
        en: Ask the agent to read the matching postings and pull the tools and problems they name. An email that cites the posting reads as research, not spam.
        zh: 让 agent 读这些岗位，把里面提到的工具和问题找出来。引用岗位原文的邮件读起来像做过功课，而不是群发。
    - title: { en: "Watch it weekly", zh: "每周看一次" }
      body:
        en: Schedule the same prompt weekly and alert when an account's role count rises. 20 API Credits a run for ten accounts.
        zh: 每周定时跑同一段提示词，某家公司的岗位数上升就提醒你。十家公司每次 20 API Credits。
  faq:
    - q: { en: "Where does my account list come from?", zh: "客户名单从哪来？" }
      a:
        en: From your CRM, or from the target account list use case. Company names must match the name on the posting; the agent checks each one with a count before the run.
        zh: 来自你的 CRM，或者用上一个"做目标客户名单"的场景生成。公司名要和岗位上写的一致；agent 会在正式跑之前先逐个计数核对。
    - q: { en: "What does it cost for 100 accounts?", zh: "100 家公司要多少？" }
      a:
        en: Two counts per account, so about 200 API Credits. Drop the total count to halve it.
        zh: 每家公司两次计数，大约 200 API Credits。不算全部在招岗位可以减半。
  method:
    - title: { en: "Population", zh: "统计范围" }
      body:
        en: Open postings visible through the Metix AI Platform on September 30, 2026, for the ten companies in account-list.json. The role is a title match on "data engineer".
        zh: 2026 年 9 月 30 日通过 Metix AI Platform 可见、account-list.json 里十家公司的在招岗位。岗位按标题匹配 "data engineer"。
    - title: { en: "Limits", zh: "局限" }
      body:
        en: Postings in every country count. A title match includes senior and lead roles and can include analytics engineers who use the phrase. Reposts are not collapsed.
        zh: 所有国家的岗位都算在内。标题匹配会包括高级和负责人岗位，也可能包括标题里带这个词的分析工程师。重复发布不合并。