The Series A Hiring Triage: Know What Not to Compromise On

At 22 employees and $4 million in the bank, every open role feels like a crisis. The sales hire is three months late. Engineering is behind because you are missing a backend lead. Your head of product does customer support 40 percent of the time. The board wants to see headcount against plan.

This is where Series A hiring processes break. Not because founders do not care about culture. Because the pressure to fill seats overwhelms the discipline to fill them well. You start rationalizing: "They can learn." "The team can absorb one difficult personality." "We will fix issues later."

Later arrives around week six, when the expensive new hire has alienated two of your best people.

The solution is not to slow down. At Series A, speed is a genuine advantage. The solution is to build a triage system that tells you, before a live candidate clouds your judgment, what you will compromise on and what you will not.

Why speed breaks your hiring brain

When people feel time pressure, they overweight immediately available options and underweight long-term consequences. In hiring, this means you lower standards on the hardest-to-measure things (collaboration style, ownership instinct, handling disagreement) while staying rigid on the easiest-to-measure things (years of experience, tool proficiency, educational background).

The problem: the hard-to-measure things are almost always what determine startup success. The ex-FAANG engineer who cannot ship without a fully specified PRD sinks your velocity. The sales hire with the perfect Rolodex who treats SDRs like furniture costs you your pipeline team. You know this. But after six weeks of recruiting and two declined offers, the temptation to rationalize "good enough" is enormous.

The three tiers

Before you open any role, define three categories. Every qualification goes into exactly one bucket.

Tier 1: Non-negotiable. Dealbreakers. If the candidate does not clear this bar, you walk. No founder override, no "but they are really strong technically."

Tier 2: Negotiable. These matter and you will evaluate them, but you can flex for the right person. A single Tier 2 gap is not disqualifying; a pattern of gaps might be.

Tier 3: Trainable. Things the person can learn on the job. Specific tooling, internal processes, a particular programming language if fundamentals are strong. You are not ignoring these, but you are not making a hiring decision on them.

Making these decisions before a candidate is in the pipeline is the entire point. When you are staring at someone who is strong everywhere except the one thing you actually cannot compromise on, the pre-made decision is your shield.

What belongs in Tier 1

Most Series A teams get this backwards: they put technical requirements in Tier 1 and behavioral traits in Tier 2. This is exactly wrong. Technical skills are almost always Tier 2 or 3. What cannot be acquired is how someone operates under pressure.

Here is a realistic Tier 1 list for most Series A roles:

Ownership instinct. Does the candidate describe work in terms of outcomes or tasks? When things went wrong, do they say "we missed the deadline" or "I underestimated the scope and did not communicate early enough"? The difference predicts everything.

Response to ambiguity. Priorities shift weekly. Strategy docs become obsolete before the ink dries. Ask for a specific example of shipping without clear requirements. If the answer reveals discomfort rather than resourcefulness, that is a Tier 1 flag.

Low-ego collaboration. Look for candidates who name others when describing successes and name themselves when describing failures. The pattern is consistent and predictive.

Disagreement without undermining. Ask about a time they disagreed with a decision and lost. What did they do next? The answer reveals whether they support decisions they disagree with or quietly undermine them. At 25 people, quiet undermining is visible to everyone.

Notice what is not here: years of experience, specific tools, industry background, educational pedigree. Those belong in Tier 2 or 3.

What goes in Tier 2 and Tier 3

Tier 2 is where real judgment lives. Domain-adjacent experience is genuinely helpful, but a three-month ramp is worth it for exceptional Tier 1 signals. Management experience matters for your first people-leader hires, but be specific: you need someone who has managed through a scaling phase like the one you are entering, not "ten years of management experience."

Tier 3 is liberating. Your technology stack, your internal processes, your company-specific context, all of it. Nobody has used your bespoke project management workflow before. If these are in your Tier 1, you have confused process with competence.

Running the triage in practice

Before you post the job, the hiring manager fills out a single-page triage document. Each Tier 1 requirement gets two behavioral questions. Each Tier 2 requirement gets one. Tier 3 stays out of the interview entirely.

Each interviewer owns one or two requirements. They ask the questions, score 1-to-5, and write a two-sentence justification for every score.

After interviews, check Tier 1 first. If any Tier 1 item scores below 3, the candidate is out. No discussion. The decision was made when you wrote the triage document.

This sounds harsh. It is meant to be. The most expensive hiring mistake at Series A is not someone who lacked a specific skill. It is someone weak on ownership or collaboration where everyone on the loop felt the concern but nobody had the structure to articulate it as a pass.

If Tier 1 is clear, examine the Tier 2 pattern. Multiple below-3 scores trigger discussion. A single gap is usually fine. Two or three and you need to ask whether the ramp time is realistic given your current bandwidth.

This adds maybe 30 minutes of upfront work per role. The payback is eliminating three-week founder debates where nobody shares a decision framework.

When this breaks

The most common failure: founders putting real Tier 1 requirements in Tier 2 because admitting they are dealbreakers feels too restrictive. "We cannot require ownership instinct for an IC engineer. What if we cannot find enough candidates?"

You will find enough candidates. You will not find a way to fix an engineer who ships bugs and blames the PM for unclear requirements. That person costs more than an extra two weeks of recruiting.

The second failure: hiring managers treating Tier 2 gaps as Tier 1 blockers because they are nervous. The triage enables speed by giving you permission to flex. If you reject every candidate with a minor gap, you are back to not filling roles.

Fix both by reviewing your triage with someone outside the hire. A co-founder, an advisor, a peer at another startup. Ask: "Is this Tier 1 honest?" and "Can real candidates clear Tier 2?"

Series A companies live and die by their first 30 hires. They set the cultural DNA. If those 30 include people who deflect blame, cannot operate without a spec, or treat junior teammates poorly, that is your culture now. You will spend two years trying to undo it, and it will cost you your best people along the way.

A triage does not guarantee perfect hires. Nothing does. What it guarantees is that you will not compromise on the things that actually determine success at your company, at your stage, under your specific conditions. And it gives you the speed you need everywhere else.

Make the Tier 1 list before the req opens. Do not touch it during the search. Trust it when the answer is no.