Six to Two: How To Slash Your Interview Process Without Missing Red Flags

Your six-round interview process is killing your hiring success. Candidates are dropping out. The best ones are accepting offers elsewhere before you've even scheduled your third round. And your hiring managers are spending more time interviewing than actually managing their teams.

I've spent the last decade in London's tech scene, watching companies sabotage themselves with bloated hiring processes that don't even deliver better results. But it doesn't have to be this way.

The interview inflation problem

Something strange happened during the 2023-2024 hiring crunch. While companies were desperate to fill roles, they paradoxically added more interview steps. I've watched tech interview processes balloon from a sensible two or three rounds to six, seven, sometimes even eight separate interactions.

Why? The fear of making a bad hire became overwhelming. But all that fear accomplished was ensuring the most in-demand candidates never reached the finish line.

In my role as a Tech Lead at three different London startups, I've conducted over 400 technical interviews. And I can tell you with absolute certainty: your fourth and fifth rounds aren't catching anything your first two didn't already reveal.

UK technology and digital roles average 5.2 weeks to hire, with specialist cybersecurity, AI/ML and senior engineering roles taking significantly longer. Companies are conducting 42% more interviews per hire than they did in 2021, with each additional round adding 3-7 days to the timeline, and increasing the odds the candidate accepts a competing offer before you finish.

The cost of interview bloat

There's a hidden cost to all these rounds that rarely gets discussed. Sure, we all know about the obvious candidate drop-off. But what about:

• The engineering hours spent interviewing that could've been spent building
• The decision fatigue that sets in by round four, making assessments less reliable
• The signal dilution when too many people with different priorities weigh in
• The creeping sameness of candidates who survive marathon processes (hint: it's not about skill)

One fintech I worked with last year calculated that their six-round process was costing them approximately £18,000 per hire in lost engineering time alone. Not counting the opportunity cost of positions sitting empty for months.

The two-round framework that actually works

Right, so how do you cut from six rounds to two without missing crucial signals? The answer isn't in adding more interviewers to fewer rounds. It's about completely rethinking what you're testing for.

Here's the framework I've used to help three London tech companies slash their hiring timeline while maintaining - sometimes even improving - quality of hire:

Round One: The Technical + Cultural Snapshot (90 minutes)

This isn't your standard technical screening. It's a carefully structured session that covers:

• 20 minutes: Career trajectory discussion (looking for growth patterns)
• 40 minutes: Technical deep dive on a REAL problem your team has solved
• 20 minutes: Collaborative whiteboarding (focusing on communication as much as solution)
• 10 minutes: Candidate questions (pay attention to WHAT they ask)

The key insight? Stop treating technical and cultural assessment as separate rounds. They're inseparable. How someone solves problems IS their culture contribution.

The biggest mistake companies make is running sterile algorithm tests that reveal nothing about how the person will actually work with your team.

Round Two: The Context Round (2 hours)

This is where you bring in multiple stakeholders, but not as a firing squad. Structure it like:

• 45 minutes: Team working session (with 2-3 potential teammates)
• 30 minutes: Manager deep dive (focused on past projects and growth)
• 30 minutes: Cross-functional stakeholder (product/design/etc.)
• 15 minutes: Wrap-up and next steps

The magic happens when these sessions overlap slightly, with one interviewer handing off to another. This creates a more natural flow and lets the candidate see how the team actually interacts.

Why does this work? Because you're not artificially separating skills assessment from team fit. You're seeing both simultaneously.

What to cut (mercilessly)

To make this two-round approach work, you need to eliminate:

1. The pointless initial HR screening (sorry, recruiters - but a well-crafted application form can do this job)

2. Multiple technical assessments that test the same skills in different ways

3. The redundant "culture fit" round that usually just measures small talk ability

4. The final "meet the CEO" vanity round that adds zero signal and tons of scheduling headaches

Let me be brutally honest about something: most companies are testing for the same things across multiple rounds without realising it. You don't need three different people to verify if someone can code. You need one good assessment that looks at their technical skills in context.

The red flags you won't miss

The pushback I always get is: "But we'll miss red flags if we cut rounds!"

No, you won't. Because red flags are remarkably consistent across interview formats. They show up early and often. The problem isn't that you need more rounds to spot them - it's that you need better questions and better observers in the rounds you have.

In my experience, these signals emerge clearly within two well-structured rounds:

Technical Red Flags

• Fundamental knowledge gaps they claim to have mastered
• Inability to explain past work in detail
• Resistance to feedback during collaborative exercises

Behavioural Red Flags

• Taking credit for team accomplishments while using "I" exclusively
• Speaking negatively about all previous employers
• Inability to discuss failures or weaknesses

The key is having your interviewers specifically trained on what to look for. A checklist of red and green flags distributed before interviews works wonders.

Implementation: How to make the switch

Transitioning from six rounds to two isn't something you do overnight. Here's how to approach it:

1. Run a pilot with non-critical roles first Test your new format on positions where a bad hire won't sink the team.

2. Train your interviewers properly Spend the time you're saving on actually preparing your team to conduct effective interviews.

3. Create detailed scorecards More structure in fewer rounds means better documentation of decision criteria.

4. Measure everything Time-to-hire, offer acceptance rate, quality of hire at 3/6/12 months.

When I implemented this at my current company last year, we saw offer acceptance rates jump from 67% to 91%. Time-to-hire dropped from 41 days to 12. Most importantly, our new hires were ramping up faster because the interview process itself gave them a clearer picture of the actual work.

What your process is really for

What if your lengthy process isn't actually about finding the best candidate?

In many organisations I've consulted with, the bloated interview process serves other purposes: distributing hiring responsibility so no one person takes the blame for a bad hire. Creating the illusion of rigour. Massaging egos by giving everyone a say.

These are organisational dysfunctions masquerading as thoroughness.

If your hiring process is designed to avoid blame rather than make good decisions quickly, no framework I suggest will help until you address that underlying issue.

Signal is what matters, not time

The companies winning the talent war in 2026 aren't the ones with the most thorough processes. They're the ones with the most efficient signal-gathering mechanisms.

Can you accurately assess a candidate's abilities and fit in two rounds instead of six? Absolutely. But only if those rounds are thoughtfully designed to reveal what actually matters for success in the role.

The most competitive tech companies in London have already made this shift. The rest are still scheduling their fourth round while wondering why they can't hire senior engineers.

The most competitive tech companies in London have already made this shift. The rest are still scheduling their fourth round while wondering why they can't hire senior engineers.

---

Raj Patel is a Tech Lead who has hired and managed engineering teams at three London startups. He writes about software engineering careers and technical hiring for UK tech publications. Connect with him on The OHub for more hiring insights.