How we work

Methodology

How every number on this site is made: where it comes from, the rules it is counted by, what it cannot tell you, and a dated record of each time we changed a method.

What we cover, and where it comes from

Our coverage is the companies on the NYC AI 100 and the companies whose people have appeared on the AI in NYC Show, wherever those companies publish their open roles through Greenhouse, Ashby, or Lever. Those three systems provide public interfaces so that third parties can display a company’s postings, and that is what we read. We do not scrape job aggregators, and we do not estimate. As of September 20, 2026 that is 47 companies and 1,567 open roles.

A company that posts jobs only on its own careers page, or through a system without a public interface, is in the NYC AI 100 and absent from the hiring data. That is a real gap, and it is why we say “the companies we track” and never “the New York AI market.”

The daily snapshot

Once a day, early in the New York morning, a script reads every board and records what is open. A posting disappears when a role is filled or withdrawn, so anything not captured that day is gone for good. For that reason roles are classified and their text is read at capture time, and only the derived figures are kept. We do not store job descriptions.

Two safeguards protect the series. If fewer than four in five of the expected boards respond, the run records nothing, because a partial outage looks exactly like a hiring collapse. And a date is never recorded twice.

Measuring change: like-for-like only

Totals cannot simply be subtracted. When a company enters our coverage, its whole board arrives in one day and reads as a hiring surge that never happened. In our first week the raw count rose by 43 roles, of which 37 were two companies joining the coverage. The real change was six.

Every change figure we publish compares only the companies present at both dates. We show the raw difference beside it so the gap between the two is visible.

Function, seniority, and place

Each role is classified from its title into one of nine functions (engineering, research, product, design, go-to-market, operations, people, finance and legal, other) and one of seven levels, from entry to leadership. The rules were audited against real titles before first use: an early version filed “Senior Product Manager” under management and “Member of Technical Staff” under other. Titles are inconsistent across companies, and a share of roles will always land in the wrong bucket. We have not measured that error rate, which is a limitation.

A role counts as New York when its listed location names New York, NYC, or Brooklyn. Remote roles and roles at New York companies’ other offices are counted separately, because a company can have the largest board on the list and almost none of it local.

Posted pay

New York City’s pay transparency law requires a good-faith salary range on roles performed in the city, and most of the New York postings we read carry one. Our pay figures are those employer-posted ranges. They are not survey answers or self-reports, and they are not offers: a posted range says what a company is prepared to pay, not what it paid.

  • New York roles only. Elsewhere, whether a range is posted depends on the state, and a national figure would be biased toward the states that require it.
  • Base salary only. On-target earnings bundle commission and run well above base for sales roles. They are counted for coverage and kept out of every percentile. Equity is excluded.
  • Midpoints, deduplicated. Each range contributes its midpoint. An identical range repeated across one company’s postings counts once, so boilerplate cannot set a median.
  • Eight or nothing. No percentile is published from fewer than eight ranges. The cell is left blank.
  • Medians move with the mix. A function’s median is taken over whichever roles are open that day. If a company posts six senior roles, the median rises and nobody was paid more. Read changes in small cells with that in mind.

Tools, skills, and concepts

The AI skills glossary and the tools figures in the Hiring Index come from reading each job description for named tools (75 of them, from model providers to data platforms) and concepts (33, such as RAG, evals, and fine-tuning). On September 20, 2026, 90 terms appeared at least once across 1,567 postings.

  • Companies first. The headline for any term is how many companies name it. Posting counts are secondary.
  • The role’s own words. Most companies open every posting with the same paragraph about themselves. We remove any sentence a company repeats across a large share of its postings before reading. Without this, a voice-AI company’s finance roles count as voice-AI jobs. Tested on 1,131 postings, it left company counts almost unchanged and cut some posting counts by more than four-fifths.
  • Ordinary words, strictly. Sales postings “fine-tune” messaging, finance postings set “guardrails,” and people get asked things “without prompting.” Such terms count only beside the technical language that gives them their meaning, acronyms are matched case-sensitively, and a term that cannot be separated from its everyday sense is left out.
  • No self-counting. A vendor’s own job postings never count toward its own name.
  • Named is not used. A posting names what an employer asks for. A nice-to-have counts the same as a requirement, and none of it is evidence of what runs in production.
  • Pairings by lift. “Named alongside” lists rank terms by how much more often they appear together than apart, so that Python, which appears beside everything, does not crowd out the informative pairings. A pairing must be made by at least a fifth of the term’s companies.

How fast roles come down

We follow each role from the day it first appears to the day it disappears. The obvious statistic, the median time open among roles that have closed, is wrong: it leaves out every role still open, so it always reads too short. We report a cohort instead. Take every role first seen in a given week, at companies we were already tracking, and ask what share had come down within 28 days.

“Came down” means the posting disappeared. That covers filled, cancelled, and reposted under a new link, and we cannot tell those apart. Roles that were already open on the first day of tracking are excluded, because their true start is unknown.

The NYC AI 100 (2026 edition)

An annual list of 100 AI companies headquartered in the New York area, in four tiers by size: $10 billion and up, $1 billion to $10 billion, a growth tier ($200 million valuation or $75 million raised), and an emerging tier. The top tier is ranked; the rest are alphabetical, because the public figures below that level do not support a ranking.

  • Headquarters verified. Each company’s New York headquarters was checked individually. Metro-area headquarters are labeled with their city. Big-technology offices are listed separately as outposts and never in the 100.
  • Figures dated. Every valuation or funding total shows when it was established. Where the latest mark is old, the date says so.
  • Judgment disclosed. Companies where AI powers the product without being the product are footnoted.
  • Verify or omit. Founding years, addresses, and rounds appear only where we found a source. Missing fields are left empty, not guessed.
  • Annual, and never paid. It is an edition, compiled in August 2026 and revised yearly, not a live directory. No company can pay to be on it.

Funding, moves, and executive searches

The funding and moves tracker has two halves made in different ways. Deals and leadership changes are curated: each needs a source we have opened, whether the company’s announcement, a regulatory filing, or first-hand reporting, and amounts and names are given as that source gives them. A leadership move is recorded only when it was publicly announced. It is a record of what we could confirm, not a complete ledger.

Executive searches are automated. The daily snapshot keeps the titles of leadership and director-level roles, and the tracker shows those with a C-level, president, general manager, VP, or “head of” title. A posting coming down means filled, cancelled, or reposted, and we never infer from it who was hired. Many executive searches are never posted publicly, so this understates them.

The show episode guide

The episode guide covers all 37 episodes of the AI in NYC Show. Dates and running times come from the show’s public podcast feed, and video links from its public playlist. Guest names and titles are as given in the show’s own notes at the time of recording. The summaries are written by us from those notes and are not transcripts.

Guides and outside statistics

Our guides cite statistics and legal facts that are not ours. Each one is read in its primary source and linked, with the population it describes kept attached: a survey of people who use AI at work is not a survey of all employees. Search-demand figures we quote come from a commercial keyword database and are estimates. How we choose and check sources is in our editorial standards.

Known limits

  • Startup-weighted. Our coverage is venture-backed AI companies. The city’s banks, insurers, law firms, and hospitals hire heavily for AI and are not in it, so anything that matters most there, governance above all, is understated.
  • Three posting systems. Companies that post elsewhere are missing from the hiring data.
  • A few large boards. A handful of companies account for a large share of all postings. This is why companies are our headline unit, and why any posting-level figure should be read beside the company count.
  • Short history. The series began in August 2026. We do not yet know what is seasonal.
  • Postings are intentions. An open role is not a hire, a posted range is not an offer, and a named tool is not a deployed one.
  • Pattern matching. Titles and descriptions are read by rules we wrote. They were audited on real postings, and they will still misread some.

Method changes

When we change how a number is made, the change is recorded here on the day it happens. Earlier data is never rewritten to match: it keeps its original values and is marked. Changes that corrected an error also appear in the corrections log.

  1. Began keeping the titles of leadership and director-level roles in the daily snapshot, so that senior searches can be followed from opening to coming down. Titles of other roles are still not stored.

  2. Tools are now counted from each role’s own text, after removing sentences a company repeats across its postings. Previously the full description was read, which counted a vendor named in a company’s introduction once per open role. Company counts moved by one for four tools and not at all for the rest; posting counts fell sharply for a few (OpenAI from 138 to 37). Rows before this date keep their original values and are marked as the old method. See the corrections log.

  3. Began extracting concepts (RAG, evals, fine-tuning, and about thirty others) from posting text, alongside tools. These series start on this date and cannot be backfilled, because posting text is not stored.

  4. Time-to-fill is now reported as a cohort: of the roles first seen in a given week, the share that had come down within 28 days. A median over closed roles alone leaves out every role still open and so reads too short.

  5. Began recording posted salary ranges and the tools named in job descriptions in the daily snapshot.

  6. Began tracking each role from the day it first appears to the day it disappears, and classifying roles by function, seniority, and workplace.

  7. First daily snapshot of open roles. The 2026 edition of the NYC AI 100 was compiled.

Questions about a method, or a cut of the data we do not publish? Use the contact page. The standards behind all of this are in our editorial standards, and our interests are set out in our disclosures.