The Pre-Series-A AI Startup Hiring Plan: Who to Hire, in What Order, and Why Most Get It Wrong

Most pre-Series-A AI founders hire in panic order, not strategic order. The result is a team that can't ship the product the company actually needs to build.

The pattern I see, repeatedly: a founder closes a seed round, gets pressure from the board to "scale the team," and posts five senior backend engineering openings on a Monday morning. Six months later they've hired four backend engineers, the product still doesn't have a designer, the AI features they're shipping look like internal tools, and the BD pipeline that was supposed to fund the next round is empty because no one has been working it.

The right framing is not "scale the team." It's each hire should either unblock the product or unblock the customer. If the hire doesn't do one of those, it's an expensive bet you didn't need to make at this stage.

Here's the plan I'd run if I were starting an AI-native company today and going from two co-founders through to a Series A.

The six hires before Series A

For an AI-native company with two technical co-founders raising a $3–5M seed round, this is the order I'd hire in. The total span is roughly 14 to 18 months from first close to Series A.

Hire 1: Founding engineer

The first hire is not a "great engineer." The first hire is a third co-founder who didn't get the title.

What you're looking for: full-stack capability, willingness to own a feature end to end, the temperamental capacity to be the only one in the codebase besides you for the first six months. Someone who's been a senior IC at one or two real companies and has decided they want startup risk now.

Comp: heavy equity (1.0–2.5%), market-rate-or-below cash. If they're asking for FAANG cash plus founding-engineer equity, they're not the right hire. The math doesn't work and they're going to bail at month 9.

What this hire should NOT be: a specialist. The first hire is the second pair of hands across the entire stack. The specialists come later.

Hire 2: Product designer

The single most counter-intuitive hire on this list is also the most important. AI products that look like engineering tools die. Almost without exception.

Your customers cannot tell whether your model is good. They can tell whether your product feels considered. A great designer in seat from month four will reshape every feature you ship — for the better — and meaningfully change what an enterprise prospect sees in your demo.

What you're looking for: someone who's shipped product design at a venture-backed startup, ideally one with a complex underlying technology. Senior level. Comfortable with no full-time PM in seat (you're the PM, the founder, until much later).

Comp: market-rate cash, 0.5–1.0% equity. Fewer designers than engineers in the candidate pool, so you'll pay closer to senior-PM rates.

Hire 3: ML or Applied AI specialist

By month six or seven, your AI features have moved past "wrap an LLM in a UI" and into territory where someone needs to think hard about prompt engineering, retrieval, fine-tuning, evals, and the rest of the AI engineering stack. This is not the founding engineer's job. This is a specialist.

What you're looking for: someone who's shipped AI features in production at another company. Not a research scientist. Not a PhD straight out of grad school. The hire is "applied" — they know how to ship, they know how to handle the messiness of LLMs in production, and they have opinions about evals.

Comp: market-rate cash, 0.4–0.8% equity. Hot market — be ready to move quickly when you find the right one.

Hire 4: The GTM hire

This is where most founders get the order wrong. They hire engineer 3, then engineer 4, then engineer 5, then somewhere around month twelve realize they have no one running the customer side and they're still doing all the BD calls themselves.

By the time you're at four engineers, you should have one person whose job is owning customer development end to end. What flavor of GTM hire depends on your product:

• Founder-led sales motion still working? Hire a founding BDR / sales associate to handle the top of funnel and let the founder close.
• Self-serve / PLG product? Hire a growth engineer who's also done marketing.
• Enterprise contracts already pulling? Hire a founding AE — yes, even at $200k base + variable + equity. The math works if they close one deal.

This hire pays back the seed round in pipeline within their first year if you've hired the right person. Skipping it for "one more engineer" is the most common pre-A mistake.

Hire 5: Senior product engineer

Now, finally, you hire engineer #3 (after the founding engineer and the AI specialist). This is the engineer who builds product features against the backlog the designer has shaped.

What you're looking for: someone who's shipped product features at scale at a previous startup. Less senior than the founding engineer, but with enough taste to make the right tradeoffs without supervision. Strong frontend or strong full-stack — depends on where the gap is at this point.

Comp: market-rate cash, 0.3–0.5% equity.

Hire 6: Security / ops person

By month 14, your customer pipeline is asking for SOC 2, vendor questionnaires, and a security trust page. Your vCISO has been doing the strategy work, but you need someone in seat for the day-to-day execution. This hire is part security engineer, part DevOps, part compliance ops.

What you're looking for: someone with cloud security and compliance ops experience at a startup of similar stage. Not a full CISO yet — you're not ready for that role. Senior IC with leadership trajectory.

Comp: market-rate cash, 0.3–0.5% equity. The vCISO transitions to advisor; the in-house person owns execution.

The hires NOT to make pre-A

For every hire on the list above, there's a tempting wrong-stage hire that founders make instead. The list of don'ts:

• Don't hire a full-time PM yet. Founder is PM. The day you hire a PM is the day product velocity drops 30% as the PM "gets up to speed" and adds a layer between engineering and customers. Wait until post-A.
• Don't hire an EM yet. Same reason. You're managing six engineers; you don't need an engineering manager. The founding engineer is the de-facto tech lead.
• Don't hire a CISO. Hire a vCISO (covered in vCISO Math). Save the full-time hire for $20M ARR or after a regulatory event.
• Don't hire a research scientist. Almost all AI startups don't need one. The applied AI specialist (hire 3) is sufficient until you're shipping novel research as the product.
• Don't hire a full-time recruiter. Founder is recruiter. If you can't recruit your own first six hires, you don't yet know what you're hiring for.
• Don't hire a head of marketing. Wait until you have a repeatable GTM motion the head of marketing can scale. Until then, the founder owns positioning.

The compensation framework

The biggest reason founders blow this plan is bad comp framework. They either underpay and lose candidates to bigger checks, or overpay and burn the runway they need for the next 18 months of progress.

The framework that's worked for me:

• Cash: roughly 80–90% of market median for a senior at a similar-stage startup. Pull market data from Carta, Pave, or Levels.fyi. Pay slightly below median because you're paying in equity.
• Equity: heavy for early hires (founding engineer 1.0–2.5%), tapering down (hire 6 at 0.3–0.5%). Use a tool like Carta to manage option pool dilution carefully.
• Refresh grants: commit in writing to a refresh grant at the 24-month mark. This is how you keep early hires from leaving when their original grant gets eclipsed by new joiners' grants.
• Cash-vs-equity flexibility: some great candidates need more cash because of life circumstances. Have a documented sliding scale (e.g., "+$20k base = -0.2% equity") so you're not negotiating each one from scratch.

The post-Series-A inflection

This plan stops at six hires. After Series A, the discipline changes.

You'll go from six to roughly thirty in the year following the A. The hire-by-hire framing breaks down at that velocity; you start hiring against role profiles and team needs. The right framing at that scale is "how many engineers do we need to ship the product roadmap" — but you only earn the right to ask that question after you've shipped pre-A with a tight team that proves the product works.

The single biggest predictor of which AI startups successfully transition pre-A to post-A is whether the team they assembled before the Series A could actually ship. The roster matters more than the headcount. Get the first six right and the rest of the company is downstream of that decision.

What it actually costs to get this wrong

Founders skip past hiring sequencing because the cost of getting it wrong feels abstract. It isn't. Here's what hiring two extra engineers in months 4–6 instead of a designer + a GTM hire actually costs.

• Two engineers fully loaded: ~$500K cash + 1.0% equity over 18 months.
• Lost product quality from no designer: hard to quantify directly, but typically manifests as enterprise demos that don't convert. Three lost enterprise deals at $80K ACV each = $240K in lost first-year revenue.
• Lost pipeline from no GTM hire: a competent founding BDR generates $300–500K in qualified pipeline in their first six months. Not having one means the founder is doing top-of-funnel work instead of product or fundraising.
• Compounding delay: the Series A pitch eighteen months later is "we have great product, weak distribution" — a much harder pitch than "we have great product and a working GTM motion." Down-round risk goes up materially.

Total expected cost of the wrong sequencing in real dollars and equity: somewhere between $800K and $1.5M over two years, plus the fundraising delta. The right sequencing has a better expected value even if the product takes one more month to ship, because the customer-side work compounds in parallel with the engineering work.