Find platform owners

Find DevOps leaders by cloud, tooling, and open roles

Platform teams get created the week the on-call rotation stops being funny. Before that, DevOps is a hat worn by whichever backend engineer knows the deploy script.

try
Start freeRead the docs

This function goes by five names and the name tells you which era the company is in. DevOps, Platform Engineering, Infrastructure, SRE, and Cloud Operations cover overlapping ground, and most companies kept whichever label was fashionable when they hired the first person. Match across all of them or you see only part of the market.

What they run is far more stable than what they call themselves. Cloud provider, orchestration, build systems, and monitoring tooling turn up in engineering postings long before anyone writes about them, and a little of it is visible on the domain. Build the account list from that and resolve the person afterwards.

Example searches

Ask for it the way you'd say it

Each example is a request in plain words, with what it returns underneath.

  • Match every name for the job

    find platform, devops, sre and infrastructure leads at series b saas companies

    All five title families run as one search, and the exact string found stays on the row so your opening line uses their word, not yours.

  • Cloud and orchestration

    which companies name kubernetes and a specific cloud provider in their engineering job posts

    Each named technology becomes its own column, which is what lets you require one, exclude another, and still keep the account.

  • On-call is the pain

    companies hiring their first site reliability engineer in the last two months

    A first reliability hire says the current rotation broke, which is a far better reason to write than anything about company size.

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.

  • Match every label for the role

    One list covering platform, SRE, infrastructure, and DevOps without five separate searches.

    1. Tables
    2. Records
    3. Sequences
    1. 1Search the whole title family at once and keep the exact string found on each row.
    2. 2Promote the confirmed owners, then enroll with the wording their own team uses.
    oxygen people search run

  • Timing from the first SRE hire

    A message that lands the month reliability became somebody's actual job.

    1. Signals
    2. Tables
    3. Sequences
    1. 1Bind a hiring search for reliability and platform roles across your segment.
    2. 2Enroll only accounts where such a role appeared for the first time recently.
    oxygen signals search run

  • Work a confirmation queue

    No account sits with a platform owner who left two quarters ago.

    1. Tables
    2. Records
    1. 1Save a view of accounts whose platform owner has not been confirmed this quarter.
    2. 2Work that view down, promoting each confirmed person onto the company record.
    oxygen tables views create

Who you can reach

Roles you can find at DevOps and platform leaders

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

RoleSeniorityReachable by
Head of Platform EngineeringDirectorWork emailLinkedIn
Director of InfrastructureDirectorWork emailLinkedIn
DevOps ManagerManagerWork emailLinkedIn
SRE ManagerManagerWork emailLinkedIn
Cloud Operations LeadManagerWork email
VP of Engineering covering platformVPWork emailLinkedInMobile
First infrastructure hireICLinkedInWork email

Filters you can search on

  • Cloud provider named in postings or on the domain
  • Container and orchestration tooling mentioned
  • Build and monitoring tools named in postings
  • Open platform, SRE, or DevOps roles
  • Engineering headcount at the company
  • Headcount band and funding stage
  • Seniority: VP, Director, or Manager

Stack evidence for this function comes mostly from hiring, because infrastructure choices rarely touch a public page. Coverage is therefore good at companies that advertise engineering roles and thin at ones hiring through networks. Where the postings are silent, engineering headcount is the only honest filter you have left.

Data sources

Data sources and CRM connections

  • TheirStack

    Engineering postings and the infrastructure tools named inside them, the main evidence on this page.

  • People Data Labs

    Person and company records for sizing an engineering org and locating who owns the platform.

  • BuiltWith

    Technology detected on the domain, which covers the small share of infrastructure facing outward.

  • Professional Network Data

    Cookieless public profile reads, used to confirm scope on a role that is named five ways.

  • Blitz API

    Reads the public LinkedIn company record beside the posting evidence, then takes the first swing at the owner's address.

Use managed credits where available, or connect a supported provider key on an eligible paid plan. Your provider bills its calls; OXYGEN adds a per-call platform fee. Signed-in CRM connections such as HubSpot have no per-call fee. Connected sending accounts reserve monthly credits. See pricing and supported integrations.

Limits

Where this stops

  • Infrastructure is invisible from a website. Nearly everything here comes from what a company advertises for, so an account that never posts roles looks empty no matter what it actually runs.
  • The same person is a DevOps manager at one company and a director of platform at the next. Rank on engineering headcount rather than assuming a title implies team size.

FAQ

Questions people ask first

Why search five title families instead of one?
Because they are the same job with different branding. Searching only DevOps returns the companies that stopped renaming things in 2018 and misses everyone who adopted platform or reliability language later.
Where does the stack information come from?
Mostly from engineering job postings, which have to name the cloud and the tooling to attract candidates. A little comes from the domain, but infrastructure choices usually leave no public trace at all.
Is a first reliability hire a good trigger?
It is one of the better ones. Companies create that role after an incident or a growth wall, which means budget was just approved and tooling decisions are open for a quarter or two.
What about companies that never post jobs?
They come back with no stack evidence, which is a blank and not a negative. Keep them ranked lower on engineering headcount rather than removing them, because silence here is common.
How do I keep the owner on each account current?
Save a view of accounts whose contact was confirmed before a cutoff date and work it down on a rhythm. This function turns over quickly, and a stale name costs you the first reply.
Does any of this spend credits before I say so?
No. Nothing runs until you start it. Viewing rows, saving views, tagging, and defining columns are free. The sourcing run, the resolution and enrichment columns, and an AI-drafted sequence all draw credits, and each takes a credit ceiling. If an Oxygent, OXYGEN's in-app AI agent, runs them for you, its chat starts on Auto-approve; switch to Ask for approval to approve larger steps first.

Build your devops and platform leaders 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