Chemistry First vs. Skills First: Why Traditional Recruiters Get Startup Hiring Wrong (And What to Do Instead)

Three years ago, I watched a brilliant founder make a £150,000 mistake.

She hired a CTO with an incredible CV:

• 15 years of experience
• Previously at Google and Facebook
• Computer Science degree from Stanford
• Impeccable references

On paper, he was perfect.

Eighteen months later, they had a “business divorce.”

He was technically brilliant. But they couldn’t work together.

Their communication styles clashed. Their decision-making approaches were incompatible. Their working rhythms didn’t sync.

She told me: “I hired for what he could do. I should have hired for who he was.”

That conversation changed everything for me.

I realized: Traditional recruitment is fundamentally broken for startups.

It optimizes for credentials and skills.

It completely ignores chemistry.

And chemistry is what determines whether a founding team or early team actually succeeds.

Let me show you why.

THE TRADITIONAL WAY: SKILLS FIRST HIRING

Here’s how most recruiters (and founders) hire:

STEP 1: Write a job description focused on skills

• “5+ years of Python experience”
• “Proven track record at top-tier companies”
• “Bachelor’s degree in Computer Science”
• “Experience with cloud infrastructure”

STEP 2: Filter CVs for credentials

• Top universities (Cambridge, Oxford, Stanford, MIT)
• Big-name companies (Google, Facebook, Amazon, Microsoft)
• Years of experience (more is better)
• Technical skills match (Python, React, AWS, etc.)

STEP 3: Interview for competence

• “Tell me about a time you solved a complex technical problem”
• “Walk me through your experience with microservices”
• “How would you architect this system?”

STEP 4: Check references for performance

• “Were they good at the job?”
• “Did they meet deadlines?”
• “Would you hire them again?”

STEP 5: Make offer to most impressive candidate

Whoever has the best CV + best interview performance wins

This process optimizes for one thing: Can they do the work?

It completely ignores: Will we work well together?

And that’s the problem.

WHY SKILLS FIRST HIRING FAILS FOR STARTUPS

Skills First hiring works fine for large companies with:

• Clear processes and structure
• Defined roles and responsibilities
• Multiple team members to balance personalities
• HR departments to manage people issues

But for startups?

It fails spectacularly.

Here’s why:

REASON 1: Startups need people who can handle chaos, not follow processes

The person with 10 years at Google is excellent at working within established systems.

But can they thrive in a 5-person startup with:

• No clear processes
• Constantly changing priorities
• Limited resources
• High ambiguity

Often, no.

They’re waiting for someone to tell them what to do.

But in a startup, there’s no one to tell them. They need to figure it out.

Skills don’t predict how someone handles chaos.

Chemistry does.

REASON 2: Startups need complementary strengths, not just impressive credentials

Imagine you’re a founder who’s:

• Visionary and big-picture focused
• Comfortable with ambiguity
• Fast decision-maker
• Not detail-oriented

You hire someone with an impressive CV who’s:

• Also big-picture focused
• Also fast-moving
• Also not detail-oriented

What happens?

You move fast in the wrong direction.

No one is catching mistakes. No one is thinking about implementation details. No one is asking “but have we thought through X?”

You needed someone who complements your strengths.

Instead, you hired someone who mirrors them.

CVs tell you what someone has done.

They don’t tell you whether their strengths complement yours.

REASON 3: Startups require high-trust relationships that survive stress

In a corporate job, you can avoid people you don’t click with.

Different departments. Different meetings. Different projects.

In a startup?

You’re in Slack together 12 hours a day.

You’re making critical decisions together weekly.

You’re dealing with near-death experiences (cash running out, key customer leaving, product breaking) monthly.

If you don’t have chemistry, those stress moments destroy the relationship.

I’ve watched it happen over and over:

Impressive hire joins startup → Works fine for 6 months → First major crisis hits → Communication breaks down → Trust erodes → “Business divorce” within 18 months.

Skills get you through normal times.

Chemistry gets you through hard times.

REASON 4: Bad chemistry costs more than lack of skills

Here’s the math:

Scenario A: You hire someone who’s 80% on skills but 100% on chemistry

• They ramp up in 3 months
• You enjoy working with them
• Communication is easy
• They stick around for 3-5 years
• Total value: £200K-£500K over their tenure

Scenario B: You hire someone who’s 100% on skills but 60% on chemistry

• They’re technically brilliant
• But working with them is awkward
• Communication takes 2X longer than it should
• They leave (or you let them go) after 18 months
• Total cost: £60K salary + £20K recruiting + £30K lost productivity = £110K lost

Which would you rather have?

Most founders choose Scenario B without realizing it.

Because Skills First hiring optimizes for credentials on paper, not fit in practice.

THE BETTER WAY: CHEMISTRY FIRST HIRING

Here’s a radical idea:

What if you flipped the script?

What if you tested for chemistry FIRST, then filtered for skills?

Not chemistry INSTEAD of skills.

Chemistry ALONGSIDE skills.

Here’s what that looks like:

CHEMISTRY FIRST HIRING PROCESS

STEP 1: Define the chemistry you actually need

Before writing a job description, ask:

“What kind of person will complement this team?”

For example:

If your team is:

• Fast-moving and visionary but weak on details
• Strong on product but weak on process
• High-trust but conflict-avoidant

You need someone who:

• Asks “but have we thought through X?” without slowing you down
• Builds systems without creating bureaucracy
• Gives direct feedback without destroying relationships

This is chemistry profiling.

You’re defining the working style, communication style, and decision-making approach that will complement your existing team.

Most founders skip this step entirely.

They write a job description focused on skills (“5+ years of Python”) without thinking about chemistry (“comfortable challenging assumptions”).

STEP 2: Locate candidates beyond the obvious places

Skills First hiring sources from:

• LinkedIn job posts
• Indeed
• Referrals from friends

Chemistry First hiring expands the search:

• Industry Slack communities (where people share how they think)
• Open-source contributors (see how they collaborate)
• Conference speakers (see how they communicate)
• Blog/newsletter writers (see how they think)
• Thoughtful commenters (see how they engage)

Why?

Because the best chemistry fits aren’t always actively job-searching.

They’re building things, contributing to communities, and sharing their thinking.

Finding them requires looking where others aren’t.

STEP 3: Test for chemistry BEFORE deep-diving on skills

Traditional hiring: Interview for skills first, hope chemistry works out.

Chemistry First hiring: Test chemistry first, then validate skills.

How to test chemistry:

A) PAID TRIAL PROJECT (2-5 days)

• Give them a real problem your startup is facing
• Work together on it (not “go away and come back with a solution”)
• Pay them £500-£1,500 for their time
• Notice: Does working with them feel easy or awkward? Do you enjoy the collaboration?

B) WORKING SESSION (2-3 hours)

• Bring them in for a “working interview”
• Solve a real problem together
• See how they think, communicate, ask questions, and handle feedback

C) CHEMISTRY-FOCUSED INTERVIEW QUESTIONS

Instead of: “Tell me about a time you solved a complex technical problem”

Ask: “Tell me about a time you disagreed with your co-founder or manager about a major decision. How did you handle it?”

Instead of: “What’s your experience with microservices?”

Ask: “How do you prefer to receive feedback? What communication style helps you do your best work?”

Instead of: “Walk me through your CV”

Ask: “What kind of team brings out your best work? What kind of environment makes you struggle?”

These questions reveal how someone works, not just what they’ve done.

D) TEAM COFFEE/LUNCH (INFORMAL)

If you already have a team, introduce the candidate in a casual setting.

See how they interact. Do they fit the vibe?

Your existing team will pick up on chemistry signals you might miss.

STEP 4: Validate skills after chemistry is confirmed

Once you’ve confirmed chemistry fit, THEN do deep skills validation:

• Technical assessment (for engineers)
• Portfolio review (for designers)
• Work samples (for writers/marketers)
• Reference checks focused on competence

But here’s the key: You’re only doing deep skills validation on candidates who’ve already passed the chemistry test.

This is the opposite of traditional hiring (which validates skills first and hopes for chemistry).

STEP 5: Hire for complementary chemistry + adequate skills

You’re not looking for the most impressive CV.

You’re looking for someone who:

• Complements your team’s strengths and weaknesses
• Communicates in a compatible way
• Handles stress and feedback similarly (or in a complementary way)
• Shares core values but challenges your thinking
• Has adequate skills (80% is often enough)

The Chemistry First principle: Hire people you work well with who can do the job, not people with impressive credentials who you hope you’ll work well with.

THE CHEMISTRY FIRST FRAMEWORK: ALIGN

At HFBAC, we’ve codified this approach into a 4-phase framework called ALIGN.

Here’s how it works:

PHASE 1: ASSESS

What it means: Define what chemistry you actually need

What we do:

• Map your team’s current strengths and weaknesses
• Identify what working style would complement (not duplicate) your team
• Define communication preferences and decision-making approaches that fit
• Clarify what “culture fit” actually means for your startup stage

Why it matters:

• You can’t test for chemistry if you don’t know what chemistry you need
• Most founders hire “people like me” when they actually need “people who complement me”

Example:

• Founder is visionary, fast-moving, big-picture
• Team needs: Someone detail-oriented who asks “but have we thought through X?”
• NOT: Another visionary who’s also fast-moving (that just creates chaos)

PHASE 2: LOCATE

What it means: Find candidates beyond the obvious places

What we do:

• Search communities, not just job boards (Slack groups, GitHub, conferences)
• Look for chemistry signals (how they think, communicate, collaborate)
• Direct outreach to people who aren’t actively job-searching
• Focus on quality over quantity (5 great-fit candidates > 100 CV matches)

Why it matters:

• The best chemistry fits aren’t on LinkedIn applying to jobs
• They’re building things and contributing to communities
• You find them through their thinking, not their credentials

Example:

• Instead of posting “Senior Developer Wanted”
• Search GitHub for contributors to projects you use
• Reach out to speakers from relevant conferences
• Engage with thoughtful commenters in Slack communities

PHASE 3: INVESTIGATE

What it means: Test for chemistry, not just interview for skills

What we do:

• Paid trial projects (2-5 days of real work together)
• Working sessions (2-3 hours solving actual problems)
• Chemistry-focused interviews (working style, communication, conflict handling)
• Team interactions (see how they fit with existing people)

Why it matters:

• You can’t tell chemistry from a 1-hour interview
• You need to actually WORK together before committing
• Skills can be assessed quickly; chemistry takes time

Example:

• Instead of 3 rounds of interviews asking about experience
• Do 1 interview + 1 paid trial project + 1 team lunch
• See how they think, work, and interact in practice

PHASE 4: GUIDE

What it means: Onboard for chemistry and skills

What we do:

• Set clear expectations about working style and communication
• Establish feedback rhythms (weekly 1-on-1s, not quarterly reviews)
• Create space for relationship-building (not just task assignments)
• Check chemistry fit ongoing (doesn’t stop after hiring)

Why it matters:

• Chemistry isn’t just “hire right and hope”
• It’s actively maintained through clear communication and feedback
• First 90 days set the tone for the entire relationship

Example:

• Week 1: “Here’s how we work, communicate, make decisions, handle conflict”
• Week 4: “How’s the chemistry feeling for you? What’s working? What’s not?”
• Week 12: “Let’s revisit working styles and adjust what’s not clicking”

REAL EXAMPLES: CHEMISTRY FIRST VS SKILLS FIRST

Let me show you what this looks like in practice.

EXAMPLE 1: HIRING A TECHNICAL CO-FOUNDER

Skills First Approach:

• Post on LinkedIn: “Looking for technical co-founder with 10+ years experience”
• Filter for impressive CVs (Google, Facebook, Stanford)
• Interview top 5 candidates about technical skills
• Hire whoever is most impressive
• Hope chemistry works out

Result: 60% of these partnerships fail within 18 months because chemistry wasn’t tested.

Chemistry First Approach:

• Define what chemistry you need: “I’m big-picture and non-technical. I need someone detail-oriented who can translate vision into technical roadmap.”
• Locate candidates in communities: “Who’s active in [your industry] Slack? Who writes thoughtful technical blog posts?”
• Test chemistry first: “Let’s work together on a small paid project for 2 weeks before discussing co-founder partnership”
• Validate skills after: “Chemistry feels great. Now let’s do technical validation.”

Result: 80-90% success rate because chemistry is tested before equity is committed.

EXAMPLE 2: HIRING A FIRST EMPLOYEE

Skills First Approach:

• Job post: “Startup generalist wanted, 5+ years experience”
• Screen 150 CVs for credentials
• Interview 10 candidates with impressive backgrounds
• Hire whoever seems “good enough”
• Hope they figure out the role

Result: 40-50% leave or are let go within 12 months because role clarity + chemistry weren’t tested.

Chemistry First Approach:

• Assess needs first: “Our biggest bottleneck is customer support. We need someone patient, detail-oriented, who can work independently.”
• Locate beyond job boards: “Who in our industry is known for great customer communication?”
• Test via paid project: “Handle 20 customer support tickets this week. Let’s see how you communicate with customers and with us.”
• Validate fit ongoing: “Weekly 1-on-1s to make sure chemistry + role clarity are working”

Result: 80%+ retention because role and chemistry were both validated before hiring.

THE OBJECTIONS I HEAR

“But chemistry is subjective. How do you actually measure it?”

You’re right, it’s not as simple as “5+ years of Python experience.”

But it’s not unmeasurable either.

Chemistry has observable signals:

GOOD CHEMISTRY SIGNALS:

• Conversations flow easily (not awkward pauses or misunderstandings)
• You finish 2-hour working sessions energized (not drained)
• Feedback is received well (not defensively)
• Disagreements are productive (not relationship-damaging)
• You look forward to working with them (not dreading it)

BAD CHEMISTRY SIGNALS:

• Conversations feel effortful (you’re constantly clarifying)
• Working together is exhausting (even when it goes well)
• Feedback creates tension (they shut down or get defensive)
• Disagreements feel personal (not constructive)
• You feel stressed before meetings with them

These aren’t subjective feelings. They’re observable patterns.

“Doesn’t this mean you’re just hiring people you like?”

No.

“Liking” someone is not the same as having good working chemistry.

I like lots of people I wouldn’t want to work with 50 hours a week.

Good chemistry means:

• Complementary working styles (not identical)
• Compatible communication (not necessarily the same)
• Shared values but different perspectives
• Ability to challenge each other without destroying trust

You don’t need to be best friends.

You need to work well together under stress.

“What if I can’t find someone with great chemistry AND great skills?”

Then you’re looking in the wrong places.

Or your chemistry requirements are too narrow (“someone exactly like me”).

The Chemistry First approach expands your candidate pool because:

• You’re not limiting yourself to people actively job-searching
• You’re looking beyond LinkedIn for people in communities
• You’re willing to train someone on skills if chemistry is excellent

I’d rather hire someone with 80% skills and 100% chemistry than 100% skills and 60% chemistry.

Because I can teach skills.

I can’t teach chemistry.

WHY TRADITIONAL RECRUITERS GET THIS WRONG

Traditional recruiters optimize for speed and CV matches.

Their incentive structure is:

• Fill the role fast
• Charge 20-30% of first-year salary
• Move on to the next placement

They don’t have skin in the game if the hire leaves after 18 months.

They measure success by: “Did we fill the role?”

Not: “Is this person thriving 2 years later?”

That’s why traditional recruitment focuses on credentials:

• Easy to filter (years of experience, company names)
• Fast to assess (1-2 interviews)
• Defendable if it goes wrong (“They had great credentials!”)

Chemistry is harder:

• Takes time to test (paid projects, working sessions)
• Requires judgment (not just CV screening)
• Riskier if you get it wrong (no credentials to point to)

So most recruiters skip it entirely.

At HFBAC, we do the opposite.

We spend more time upfront testing chemistry because we know it’s what determines long-term success.

Our measure of success: “Are they still thriving 2 years later?”

Not: “Did we fill the role fast?”

SO WHAT SHOULD YOU DO?

If you’re about to hire for your startup, here’s my honest recommendation:

Don’t use traditional recruiters who optimize for CVs and speed.

Use a Chemistry First approach:

1. BEFORE HIRING: Define what chemistry you actually need (complement your strengths, don’t duplicate them)
2. WHILE HIRING: Test chemistry alongside skills (paid projects, working sessions, chemistry-focused interviews)
3. AFTER HIRING: Maintain chemistry through clear communication and ongoing feedback

The goal isn’t to hire the most impressive CV.

The goal is to hire someone you work brilliantly with who can do the job.

Because great companies are built by people with awesome chemistry, not just impressive credentials.

READY TO HIRE USING CHEMISTRY FIRST?

If you’re hiring for your startup and want to avoid the “impressive CV, terrible fit” mistake, here’s what I’d recommend:

Inside, you’ll get:

• Chemistry assessment worksheet (define what fit you actually need)
• Paid trial project templates (test chemistry before committing)
• Chemistry-focused interview questions (reveal working style, not just experience)
• Red flag checklist (warning signs of bad chemistry)

Let’s talk about your hiring needs and whether Chemistry First hiring makes sense for your startup.

I’ve helped 400+ founders find people who don’t just have the right skills – they have the right fit.

No sales pitch. Just honest advice about whether we’re the right fit to help you.