OXYGENOXYGEN

Find engineering leads

Find engineering managers by team stack and open roles

A company has one CTO and a dozen engineering managers. Picking the right one is the whole job, because only the manager who owns the service you plug into will answer.

try
Start freeRead the docs

Unlike a CTO, engineering managers come in quantity, and most of them are the wrong person. The one who owns the platform team reads your note about infrastructure; the one who owns mobile deletes it. Team is the filter that matters, and a title never contains it.

Open roles are the cheapest way to see team shape from outside. A posting names the stack, the team, and often the manager the role reports into. TheirStack carries the postings, People Data Labs resolves the managers behind them, and ContactOut covers the ones whose work address never appears anywhere public.

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.

  • Pick the team, not the title

    find engineering managers who run platform or infrastructure teams at series b saas companies

    The team column comes back beside the name, so you can drop every manager whose scope has nothing to do with what you sell.

  • Postings name the stack

    which companies posted a senior backend role naming go or rust in the last two months

    Each posting lands as a row with its date and its technologies, which is a far better opening line than a guess about their architecture.

  • Map one account fully

    give me every engineering manager at these twelve accounts with the team they run

    Account-scoped searches cost far less than market-wide ones, because the company filter is already satisfied before anything resolves.

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.

  • Map the managers on one account

    A named org chart for a target account instead of one contact and a guess.

    1. Tables
    2. Records
    1. 1Run an account-scoped people search and store every manager with their team.
    2. 2Promote the two who match your surface onto the company record as stakeholders.
    oxygen people search run

  • Let the posting write the opening

    A first line about the role they are trying to fill, dated and specific.

    1. Signals
    2. Tables
    3. Sequences
    1. 1Plan a hiring search over your account list and check the routed providers before spending.
    2. 2Enroll the managers attached to accounts whose postings named your category.
    oxygen signals search plan

  • Personal address for the quiet ones

    Managers with no discoverable work email still get a route that is not a guess.

    1. Tables
    2. Sequences
    1. 1Filter to rows where the work-email chain returned nothing on this manager.
    2. 2Run the fallback lane on that slice only, then enroll what resolved.
    oxygen enrich-column run

Who you can reach

Roles you can find at engineering managers

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

RoleSeniorityReachable by
Engineering ManagerManagerWork emailLinkedIn
Senior Engineering ManagerManagerWork emailLinkedIn
Director of EngineeringDirectorWork emailLinkedIn
Head of PlatformDirectorWork emailLinkedIn
Team lead or tech leadICLinkedInWork email
VP of EngineeringVPWork emailLinkedInMobile

Filters you can search on

  • Technologies named in recent job postings
  • Team or discipline the manager runs
  • Open engineering roles by seniority
  • Engineering headcount at the company
  • Headcount band and funding stage
  • Country, region, or metro area
  • Seniority: VP, Director, or Manager

Managers are easier to find than to place. Public profiles rarely name the exact team, so the team column is inferred from postings and profile text and is right more often than not rather than always. Confirm on the profile before writing anything that assumes a specific service or repository.

Data sources

What the data actually comes from

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

  • TheirStack

    Job postings with the technologies inside them, which is how a team's stack becomes visible.

  • People Data Labs

    Person records for resolving how many managers an engineering org actually has.

  • LinkedIn Scraper

    Reads the public profile and posts, which is where a manager states the team they run rather than just their level.

  • Blitz API

    First attempt at a manager's work address, which usually follows the company pattern, plus the public LinkedIn company read.

  • ContactOut

    A later lane for people whose work address is not discoverable through the usual pattern.

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

  • A job posting can stay live for months after the role was filled. Use the posting date rather than its presence when you are timing an outreach around it.
  • At large companies the address pattern is guessable but the gateway is not, so expect part of this list to be reachable only through a public profile.

FAQ

Questions people ask first

Why not just write to the CTO?
Because at any company past fifty engineers the CTO does not own the decision you need. The manager running the affected team does, and they are the one who will forward it upward if it lands.
How do you work out which team someone runs?
From what their team advertises for and what their own profile text says. It is inference, and it is labeled as such on the row, so you can confirm the handful you plan to write to personally.
Can I search inside a fixed list of accounts?
Yes, and it is much cheaper than searching the market. The company filter is already satisfied, so you pay only for resolving people and contacts on accounts you picked deliberately.
What if the work email never resolves?
Then the row stays and moves to a profile-only lane. That is a routing decision rather than a failure, and keeping the row means you never pay to discover the same person twice.
Do engineering managers reply to cold email?
Some do, when the message is about a problem their team posted about publicly. Generic outreach to this group is wasted, which is exactly why the team and posting columns are worth the extra step.
Can I turn this into a repeatable run?
Yes. Keep the account list as a table, bind the hiring search to it, and let new postings arrive as rows. Nothing sends until you enroll, so the sourcing side can run unattended.

Build your engineering managers 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