← Blog

How to Find Candidates Who Have Already Scaled a Company From Seed to Series A

    A Seed-stage company that wants to reach Series A has a very specific hiring problem, and most sourcing tools are the wrong shape for it. The ideal hire is often someone who has already made the Seed-to-Series-A journey and can see the walls before the company runs into them. But that person almost never describes themselves that way on their profile. Their title says "Head of Growth" or "Founding AE," not "person who took a company from Seed to Series A." A keyword search will miss them, and a title filter will bury them under people who held the same title at companies that never had to make the jump.

    The short answer

    To find candidates who have already scaled a company from Seed to Series A, stop searching by title and start searching for career triggers: people who joined a company at roughly the Seed stage, stayed through the funding and headcount step-up, and owned the function that had to be built for the round to happen. The signal is in the dates and the company stage at the time, not in the job title.

    This guide walks through how to do that, using the exact example a recruiter raised with us: a Seed-stage client that needs someone who has already been through the next step. It builds on the broader argument that trajectory fit beats skills fit, and it gets practical fast.

    Step 1: Write the brief as a problem, not a title

    Before you open any sourcing tool, write down the single hardest thing this hire has to accomplish. For a Seed company chasing Series A, it is usually some version of "build the repeatable engine that convinces a Series A investor the growth will continue without the founders holding it up." That might be a first real sales motion, a first marketing function that generates pipeline predictably, or the product maturity that unlocks it.

    Phrase it as a problem, because the problem is what you match against. "Take us from founder-led sales to a repeatable motion by Series A" tells you what to look for in a career. "VP of Sales" does not. The title is an output of the search, not the input.

    Step 2: Turn the problem into triggers

    Now ask what a career history would look like if the person had already solved that problem. These are your triggers, the specific and checkable markers you will actually screen for. For the Seed-to-Series-A journey, the strongest ones are:

    • Joined at the right stage. They came in when the company was pre-Series-A, roughly ten to thirty people or a small seed round on record, not after the machine already worked.
    • Stayed through the transition. Their tenure spans the moment the company raised its Series A. Joining just after the round is a much weaker signal than being there to make it happen.
    • Owned the function that had to be built. The round depended on the thing they were responsible for. If the Series A story was about revenue repeatability and they ran sales, that is a direct match.
    • Built rather than inherited. The signal is strongest when there was no established function before them. "First sales hire" beats "joined a sales team of twelve."

    Each of these is a trigger you can look for in a profile. For the wider set that predicts startup survival beyond this one journey, see the seven career triggers that predict a candidate can survive hypergrowth.

    Step 3: Find the triggers on LinkedIn and in your database

    Here is where Boolean search runs out of road. You cannot search for "was at a company when it raised its Series A," because that fact is not a field. You have to reconstruct it from the dates and the company's history. The workflow that actually works looks like this:

    1. Start from companies, not people. Build a list of companies that made the Seed-to-Series-A jump in your target market and time window. Funding databases and announcements give you this directly, and it is far more reliable than any people-search filter.
    2. Find who was there during the jump. For each company, look at who held the relevant function in the window around the raise. The people whose tenure brackets the Series A announcement are your shortlist.
    3. Read the profile for stage, not title. Check what the company looked like when they joined. A "Head of Sales" who arrived at employee eight is a completely different candidate from one who arrived at employee two hundred, even though the title is identical. The dates tell you which one you are looking at.
    4. Confirm ownership, not proximity. Being at the company during the raise is necessary but not sufficient. You want the person who owned the thing that made the round possible, not someone who happened to be in the building.

    This is slower than pasting a Boolean string, and it is also why it works. The candidates it surfaces are the ones your competitors' keyword searches never reach, because the signal was never a keyword.

    Step 4: Confirm the trigger in the interview

    A profile can only show that the trigger is plausible. The interview is where you confirm it. The core question is always the same: what did you personally do, versus what did the team around you do? Someone can be present for a Series A without having driven any of the work that earned it.

    Ask them to walk through the state of their function when they joined and when they left. Ask what broke during the scale-up and what they changed. Ask what they would do differently. The people who genuinely drove the transition answer these with specifics and scars. The people who were merely present answer in generalities.

    This is exactly the kind of evidence worth capturing as a structured record rather than trusting to memory. An interview intelligence tool records and structures what the candidate actually said, so the person weighing the trajectory claim later is reading evidence rather than a hazy recollection. Numi does this on EU infrastructure and does not score or rank the candidate for you, which keeps the trajectory judgment where it belongs, with your hiring team.

    A worked example

    Say the client is a Seed-stage fintech that needs a first real revenue leader to reach Series A. You would not search "VP Sales fintech." You would build a list of fintechs that raised a Series A in the last two to three years in your region, find the person who owned revenue at each one in the eighteen months before the raise, and filter to those who joined while the company was still pre-Series-A and built the motion from close to nothing. That list might be forty people. After you read each profile for stage and ownership, it might be five real matches. Those five have already solved the exact problem your client is hiring for. That is the whole point of matching on trajectory instead of on titles.

    Frequently asked questions

    How do you find candidates who have scaled a company from Seed to Series A?

    Do not search by job title. Instead, build a list of companies that made the Seed-to-Series-A jump in your target market, then find the people who owned the relevant function during the raise. Filter to those whose tenure shows they joined while the company was still pre-Series-A and stayed through the round. The signal lives in the dates and the company stage at the time, not in the title on the profile.

    Why does Boolean search miss these candidates?

    Because the fact you care about, that someone was at a company when it raised its Series A and owned the work that earned the round, is not a searchable field. Boolean search matches keywords and titles, but the trajectory signal is reconstructed from tenure dates and the company's funding history. Two people with the identical title can be completely different candidates depending on the stage of the company when they joined, and keyword search cannot tell them apart.

    What career triggers predict Seed-to-Series-A experience?

    The strongest triggers are: joining the company while it was still pre-Series-A, staying through the moment it raised the round, owning the function the round depended on, and building that function rather than inheriting an established one. A first sales or growth hire whose tenure brackets the Series A announcement is a far stronger match than someone who joined an existing team after the round closed.

    How do you confirm the experience in an interview?

    Ask the candidate to describe the state of their function when they joined and when they left, what broke during the scale-up, and what they changed. The goal is to separate what they personally drove from what the team around them did, since being present for a Series A is not the same as having earned it. Capturing that conversation as a structured record makes the trajectory claim reviewable rather than a matter of memory.

    Does industry match matter for Seed-to-Series-A hires?

    Less than most people assume. The relevant match is the problem and the stage transition, not the vertical. Someone who built a repeatable revenue motion from scratch in an adjacent market before Series A is usually a stronger trajectory match than someone who ran an already-working motion in your exact industry. Match on the journey first, then treat domain knowledge as a secondary filter.

    Numi is an EU-hosted AI meeting assistant built for interviews. It records, transcribes, and structures every conversation on European infrastructure, and never trains on your data.

    Start for free