OXYGENOXYGEN

Find people

Find CTOs by the stack they run and the roles they are hiring

A CTO list built from titles alone is mostly noise. Built from the stack a company runs and the engineers it is hiring, it is a short list worth writing to.

try
Start freeRead the docs

The hard part of finding a CTO is not the title, it is the company. Two accounts at the same headcount differ entirely if one runs the stack your product attaches to. Company first, person second.

All of it happens in one table. TheirStack and BuiltWith supply the stack layer from postings and from the domain. People Data Labs and the LinkedIn Scraper resolve the person, and Blitz API runs the email waterfall on the same rows, billed on a hit.

Example searches

Ask for it the way you'd say it

Every search below runs on the same hosted Tables, with the cost previewed before anything is spent.

  • Stack first, person second

    find series A saas companies running kubernetes, then get the cto or vp of engineering at each

    Stack filters apply before the people lookup, so you only pay for accounts that passed.

  • Hiring as the timing signal

    show me companies that posted a platform engineer role this quarter and find the engineering leader

    The posting lands as a dated row on the account you keep, not a one-off alert you have to act on the day it fires.

  • Small-company reality

    for companies under 30 people find the technical co-founder rather than a cto title

    Seniority is its own filter, so a company with no CTO title still returns a decision owner.

Plays

Three motions you can run this week

Each one is a chain of Oxygen primitives — the same hosted objects your workspace already has, composed.

  • Stack-matched engineering leaders

    A short list where every account runs something you attach to.

    1. Tables
    2. Records
    3. Sequences
    1. 1Source accounts by detected and posting-derived technology.
    2. 2Resolve the engineering leader, run the email column, enroll.
    oxygen people search run

  • Timing from open roles

    Outreach that lands the week a team staffs up around your category.

    1. Tables
    2. Sequences
    1. 1Bind the hiring search to the table so new postings arrive as dated rows you can filter and enroll by hand.
    2. 2Enroll only accounts whose postings name your category.
    oxygen signals search run

  • Fill the engineering side of the CRM

    Existing accounts get a named technical contact, not a blank field.

    1. Records
    2. Tables
    3. Records
    1. 1Open the object-backed table behind your company records.
    2. 2Resolve the leader and promote the verified contact back.
    oxygen tables promote

Who you can reach

Roles you can find at CTOs and heads of engineering

Reachability is per channel: a role marked for mobile is one the phone waterfall usually resolves, not a guarantee for every record.

RoleSeniorityReachable by
Chief Technology OfficerC-levelWork emailLinkedInMobile
VP of EngineeringVPWork emailLinkedIn
Head of PlatformDirectorWork emailLinkedIn
Director of EngineeringDirectorWork emailLinkedIn
Engineering ManagerManagerWork emailLinkedIn
Technical co-founderOwner/FounderWork emailLinkedInMobile

Filters you can search on

  • Company headcount band
  • Funding stage and date of last round
  • Cloud provider and data warehouse in use
  • Frameworks detected on the company domain
  • Technologies named in recent job postings
  • Open engineering roles posted this quarter
  • Country, region, or metro area
  • Seniority: C-level, VP, or Director
  • Title keywords to include or exclude

Title language moves with company size. At a twenty person startup the CTO is the technical co-founder and there is no VP layer. At a two hundred person company your buyer may sit two levels down. Filter on seniority and stack, then read the title column.

Data sources

What the data actually comes from

Every value lands with its provider and cost recorded on the cell.

  • People Data Labs

    People and company records for resolving a title to a person, with headcount and stage around it.

  • TheirStack

    Job postings and the technologies named inside them, which show a stack decision early.

  • BuiltWith

    Technology detected on the company domain: clouds, frameworks, and tools visible outside.

  • LinkedIn Scraper

    Reads the public profile of whoever came back as the technical owner, so a stored title is checked against what the person says.

  • Blitz API

    The LinkedIn company and profile read behind the stack columns, and the first leg of the work-email chain on the leader you resolved.

Run these on Oxygen's managed credits, or connect your own provider keys and pay the vendor directly — the same columns, the same runs, the same provenance either way. See every integration.

Limits

Where this stops

  • Stack detection sees what is public. A team running your category behind a private network will not show it, so treat a negative match as unknown.

FAQ

Questions people ask first

Why filter by stack, not just title?
The title says who to write to; the stack says whether to write at all. Filtering accounts first keeps the waterfall off companies that failed.
What if the company has no CTO title?
Common below thirty people, where the technical co-founder holds the role. Filter on seniority, and the table records the title it actually found.
Can I get mobile numbers too?
Yes, through a separate phone waterfall as its own column. It is a different chain at a different cost, so run it only where you will call.
How do I keep a list like this current?
Bind the search to the table as a feed with a cadence and a per-cycle cap. Job changes then surface on re-enrichment instead of going stale.
Does reading profiles need my own account?
No. Profile and company reads run on a managed cookieless path, so your own session is never used and no seat is consumed. A connected account buys exactly one thing, the ability to send from it, and that is a separate paid step.
What does building this list cost?
Sourcing and enrichment are metered at 1,000 credits per dollar, with top-ups at $1.25 per 1,000. A preview on your filters is the only honest estimate.

Build your ctos and heads of engineering list

Start with a search, preview the cost before anything is spent, and keep the rows, sources, and runs in a workspace you own.

Start freeSee pricing