A plug-and-play framework for early-stage teams — and the judgment to know when to break it.
Ask most founders how their interview process works and you’ll get some version of the same answer: “We have a few calls, the team meets them, and then we decide.”
That’s not a process. That’s a series of conversations that happen to end in a hire.
The difference between those two things — a real process and a loose set of conversations — is the difference between building a team that compounds over time and spending every quarter re-hiring for the same roles.
If your interviews feel inconsistent, your debriefs feel like arguments, and your hiring decisions feel more like gut calls than informed choices — this is the post for you.
The Problem With “We Just Know”
Most early-stage companies believe they’re good at hiring because they’ve made a few good hires. But survivorship bias is doing a lot of work there.
The real test isn’t whether you’ve hired great people. It’s whether you can do it consistently, at speed, without the process falling apart every time a key person is unavailable or a candidate has a competing offer on the table.
What most companies are actually running is an improvised loop — different interviewers asking different things, no handoffs, no rubric, and a debrief that bottoms out at “I liked them” or “something felt off.” Then everyone looks to the most senior person in the room and does whatever they say.
That’s not a hiring process. That’s just hierarchy with extra steps.
The issue isn’t that your instincts are wrong. It’s that instincts alone don’t scale — and they definitely don’t protect you when things get complicated. If you’re hiring more than three or four people a year, you need something more deliberate. It doesn’t have to be complicated — it just has to be intentional.
The Framework: Four Stages, Each With One Job
The goal of a good interview process isn’t to be thorough — it’s to be efficient. Every stage should answer one specific question. If it can’t answer that question, either redesign it or cut it.
Here’s the backbone:
Stage 1 — Rough Screen: Is this person worth our time?
Stage 2 — IC/Skills Interview: Can they actually do the job?
Stage 3 — Hiring Manager Round: Are they the right person for this role at this company?
Stage 4 — Close/Sell: Do they want to join — and do we want them to?
Four stages, four questions. Everything else is detail.
The number of rounds inside each stage can flex depending on the role, the seniority, and the speed of your pipeline. A seed-stage startup hiring their first engineer might compress this to three touchpoints. A Series B company hiring a VP of Product might add a presentation round or a reference call before the close. The structure holds either way.
What matters is that everyone on your team knows which stage does what — and nobody is trying to answer all four questions in one conversation.
Stage 1: The Rough Screen — Fast, Ruthless, Not the HM’s Job
The rough screen is a 20 to 25 minute call with one job: filter out candidates who clearly aren’t right before anyone else spends time on them.
You’re checking for compensation alignment, timeline, logistics, basic communication, and genuine interest in the role. That’s it.
This call should be run by a recruiter, a recruiting coordinator, or an experienced office manager for smaller teams. It should not be run by the hiring manager.
Here’s why: the hiring manager’s opinion is too valuable — and too biased — to deploy this early. If they get on a screen call and find someone charming, they’ll carry that warmth into every subsequent evaluation. If they find someone awkward on a 20-minute intro call, they’ll discount them even if the person is technically exceptional.
Save the HM for when their judgment actually matters. The screen is a logistics call, not an evaluation. Treat it accordingly.
Stage 2: The IC Interview — Where the Real Signal Lives
This is the most important stage in your process, and the one most companies underinvest in.
The IC interview is where a peer, a senior team member, or a domain expert actually tests whether the candidate can do the job. Depending on the role, that might mean a technical problem, a case study, a portfolio review, a structured scenario, or a deep-dive on past projects.
The key distinction: this stage is about capability, not likability. The interviewer’s job is to find out whether this person can execute — not whether they’d be fun to grab lunch with.
One note on format: where possible, lean toward live or observed exercises — pair programming, a case walkthrough, a real-time problem-solving session — over pure take-homes. AI tools have made async submissions harder to evaluate reliably; real-time judgment is much harder to outsource. The signal is cleaner, and it has the added benefit of showing candidates how your team actually thinks and works.
This stage should produce a structured output. Not an essay — a simple scorecard. Did they demonstrate the core competencies required for this role? Yes, no, or partially, with a sentence of evidence for each. That document becomes the basis for your debrief and stops the conversation from defaulting to whoever has the strongest opinion in the room.
This is also where most red flags actually surface, if the interviewer knows what to look for. The full list is worth reviewing before you run this stage: Red Flags You Might Be Ignoring in Candidate Interviews.
The Problem Nobody Talks About: Everyone Is Asking the Same Questions
Here’s something that happens in almost every multi-round interview loop, and almost nobody fixes it.
Candidate comes in for a four-person loop. First interviewer asks: “Tell me about a time you had to handle a conflict on your team.” Second interviewer asks: “Can you walk me through a difficult interpersonal situation you’ve navigated?” Third interviewer: “How do you handle disagreement with a manager?”
The candidate is answering the same question for the third time with slight rewordings. They’ve clocked it. They’re less engaged, less sharp, and quietly wondering if this company has its act together.
Meanwhile, your team walks into the debrief having all probed the same surface area — and knowing nothing about half the things that actually matter.
The fix is simple and almost nobody does it: assign each interviewer a lane, and build a handoff.
Each person in the loop owns a specific dimension — technical depth, cross-functional execution, leadership behaviors, culture and values, whatever is relevant to the role. They go deep on that one thing, not wide across everything.
And before each interview starts, the previous interviewer passes a one or two line note: “She was strong on ownership but got vague when I asked about stakeholder pushback — probe there.” Or: “He had a strong answer on the technical side but I didn’t get to long-term thinking — worth exploring.”
The interview becomes a relay, not four people running the same lap. Each stage builds on the last. By the time the candidate reaches the hiring manager, you’ve covered real ground — and the HM walks in with actual intelligence, not just their own first impression.
The Hiring Manager Question: First or Last?
Most teams get this wrong.
The instinct is to put the hiring manager early — they’re the most important person in the decision, so shouldn’t they be in the room from the start?
In most cases, no. Some teams do use an early HM touchpoint as a quick veto on obvious mismatches — that can work if the hiring manager is genuinely disciplined about staying neutral. In practice, most aren’t. The moment they form an impression, it colors everything that follows: other interviewers calibrate toward the HM’s view, and the debrief becomes a referendum on their gut call rather than a synthesis of independent assessments.
More importantly, you lose the most powerful closing tool you have. The hiring manager’s seniority and genuine excitement about the opportunity is most effective as a sell — but only if you’ve saved it for the right moment.
Put the HM at stage three, after the candidate has already cleared the skills bar. At that point, the HM’s job is twofold: make the final assessment on fit, and begin the close. They’re asking the deeper questions — how this person thinks, how they’ll grow, whether they’re the right profile for where the company is headed — while simultaneously giving the candidate a window into the leadership and the opportunity.
That’s a very different conversation than a first-round screen. And it only works if you’ve saved it.
For a related angle on how hiring managers derail their own processes, Stop Falling in Love With One Candidate is worth reading before you redesign your loop.
Senior Leaders Doing Too Many Interviews Is a Math Problem
If you’re running a healthy pipeline for an engineering role, you might be screening 30 candidates, advancing 12 to the IC stage, and bringing 5 or 6 through to the full loop. If the CTO or VP is in every single one of those conversations, they’re doing more interviews than the IC whose actual job includes interviewing.
That’s backwards. And it’s not just an inefficiency — it’s a distortion. When the most senior person in the room is present at every stage, junior interviewers defer to them. Independent assessments get contaminated. The whole point of a structured process — building a picture from multiple independent perspectives — breaks down.
Senior leaders should be involved at the decision point and the close. Their time is the most expensive in the building. Treat it accordingly.
Stage 4: The Close — The HM’s Moment to Sell
By the time a candidate reaches stage four, they’ve cleared every bar you’ve set. They can do the job, they fit the team, and the team wants them.
Now the hiring manager’s job changes completely. They’re no longer evaluating. They’re selling.
This is the conversation where the HM talks about where the company is going, what this person’s role will be in getting there, and why this is the right opportunity at the right time. It’s also where the candidate gets to ask the questions they’ve been holding — the real ones, not the interview-appropriate ones.
If you’ve used the HM at stage one or two, you’ve already spent this moment. You can’t walk back into a room and shift from evaluator to enthusiastic advocate — the candidate’s read of the relationship is already fixed.
Save the HM for the close, and let their seniority and genuine excitement do the work it’s supposed to do.
Knowing When to Break the Process
Here’s the thing nobody puts in the framework post, because it’s uncomfortable to admit: sometimes the process has to break.
Not because the process is wrong. Because the situation has outgrown the rules, and the only thing that saves the hire is trust and judgment.
Scenario: your hiring manager is traveling. A candidate you’ve been courting for six weeks just got a competing offer with a 48-hour deadline. The CTO was supposed to be the final sign-off — but they’re unreachable. The VP of Engineering has met the candidate twice, knows the team’s needs cold, and is confident.
Does the process stop? Does the offer wait? Does the candidate go elsewhere?
In a rigid organization, yes. In a mature one, no. The VP makes the call.
This is what it actually means to build a strong hiring org. It’s not just about having stages and scorecards. It’s about building enough shared context and clarity on decision rights that when an exceptional situation appears, someone on your team knows what they’re empowered to act — without waiting for the right title to be in the room.
Before authorizing an exception, it’s worth running a quick gut-check: Is this candidate genuinely exceptional, or are we just under pressure? Is the person making the call deeply familiar with the role and what we’re looking for? And can we document the rationale clearly afterward? If the answer to all three is yes, move. If not, the process should hold.
There’s a meaningful difference between “we skipped a step” — which is a problem — and “we skipped a step for a genuinely exceptional reason, with the right person making the call” — which is judgment. That distinction lives in culture, not process documentation. You build it by being explicit about what exceptions are on the table, who can authorize them, and what the bar for “exceptional” actually looks like.
The flip side is equally true: a team that breaks the process casually, without accountability, will regress to the improvised loop you started with. The process only earns the right to be broken if it’s being followed the rest of the time.
This connects directly to what we covered in the 48-hour rule — companies that lose great candidates in crunch moments aren’t slower because they lack urgency. They’re slower because nobody is empowered to move. That’s a culture problem, not a calendar problem.
Making This Work for Your Stage
No two companies need the same process. But every company needs a process. Here’s how to calibrate:
Seed stage, small team, early hires: Compress to three touchpoints. Screen → IC or founder interview → close. Keep it tight, keep it fast. Document your scorecard criteria even if it’s just a Google Doc with five bullet points.
Series A, scaling a function: Four stages as outlined above. Assign interviewers to lanes. Build the handoff note habit now, before you’re hiring ten people at once and coordination becomes chaos.
Series B and beyond, senior or executive hires: Consider adding a structured presentation or working session before the close. Reference calls should be built into the process, not an afterthought — we covered how to actually run those in The Reference Check Is Broken. Both the HM and potentially a board member should be in stage four.
The through-line at every stage: clarity on who owns what decision, and what happens when the expected person isn’t available. If those two things are defined before the search starts, the rest is detail. If they’re not, you’ll negotiate them under pressure — which is the worst possible time.
Consistency Beats Perfection
The best interview process isn’t the most sophisticated one. It’s the one your team actually runs — every time, for every candidate, regardless of who’s available that week.
A mediocre process applied consistently will outperform a brilliant process applied occasionally. Consistency means candidates are evaluated against the same criteria. It means your debrief is a synthesis of evidence, not a debate. It means decisions get made faster because the framework for making them is already agreed.
Start simple. Get alignment on the four stages. Assign interview lanes. Build one handoff template. Define two or three exceptions your team is empowered to make.
That’s the whole thing. It doesn’t need to be more complicated than that.
If you want help building this for your org — or just want a second opinion on where your current process is breaking down — let’s talk. We’ve seen enough hiring loops to know exactly where the gaps tend to be.
