A Hiring Manager's Guide to Avoiding Fit Mistakes

By Ejieme Eromosele

September 2026

You're heading into Q4 and your team is already stretched. You've got open job reqs that have been open for a few weeks, and suddenly you're in a position where you need to hire fast.

I get it. I've been there.

But this is exactly when fit mistakes in hiring happen.

You become so focused on getting someone in the door that you skip the necessary work of defining what ‘a good fit’ actually looks like for your team. You instead default to the person who feels familiar, maybe the person who reminds you of your best performer. Or you assume chemistry in an interview means they'll actually work. You tell yourself you'll know it when you see it.

And then you hire someone technically solid who struggles with the pace of your environment, or who leaves in nine months because the role isn't what they thought it was.

I've seen this play out too often and what I’ve learned is that most fit mistakes are less about being wrong about a candidate, and instead more about being unclear about what you're actually looking for.

The mistake: Not naming what "team fit" actually means

You've probably said this: "I want someone who fits with the team."

Now ask yourself: what does that mean?

Does it mean they have to be friends with everyone on your team? Because that's a high bar, and it's also not really your job to hire for. Does it mean they share the team's work style? That's clearer, but you still need to name what that work style is. Are we talking about synchronous collaboration, or can someone who prefers async work thrive here? Do we need someone who thrives on process, or do we need someone who can operate in ambiguity and help us build the process?

I worked on a team once where the unspoken rule was that you were always responsive. Slack messages got answered immediately. You checked in constantly. And then we hired someone brilliant who batched communication and protected deep work time. The team saw that as not being responsive enough. But she saw the team as chaotic and interrupt-driven.

Nobody was wrong. We just didn't name what we needed.

Here's what I recommend: pick the two or three dimensions of team dynamic - how your team works - that actually matter for success in this role. Are they about communication style, pace, how you handle conflict, how decisions get made? Next, name them clearly. Then evaluate candidates against those specific dimensions, not against the vague feeling of whether they'd be fun to grab coffee with.

The mistake: Assuming interview chemistry means role success

You have a great conversation with someone. They're warm, sharp and they ask good questions. You can picture them in the role so you recommend them to the hiring committee.

And then, six months in, you realize that it’s a misalignment.

Here's probably what happened: you evaluated chemistry with you but not fit for the role.

Those are different things. I know a VP of Customer Success who hired someone partly because they had such a smooth, consultative communication style in the interview. She assumed that style would translate beautifully to customer-facing work. And while it did, the role more heavily required jumping into reactive support tickets, managing CS ops systems, and running spreadsheets. The candidate thrived in the polished parts and struggled with the messy, operational parts. No one had spelled that out upfront.

When you create a Fit Profile before you interview, you're building clarity around what the role actually demands. Not your preferred communication style. Not the personality type you get along with best, but the actual day-to-day.

What percentage of the week is this person in meetings versus doing independent work? Are they managing people, systems, customers, or ideas? What's the highest-stress scenario they'll face in their first month? Do they need to inherit relationships, or are they building from scratch?

Interview chemistry tells you whether someone is likable. A Fit Profile tells you whether they can succeed in the role.

The mistake: Hiring for culture fit, not culture add

This one still happens everywhere, and it's usually not intentional.

Culture fit sounds good in theory. You want someone who shares your values, fits the team dynamic, meshes with the way you work. The problem is that "fit" often becomes code for "similar to us." And that's when your team starts looking the same, thinking the same, and solving problems the same way.

I interviewed at a company once where the hiring manager was very upfront about culture fit. "We're a fun team," she said. "We grab beers together after work, we're pretty informal, we joke around a lot." She wasn't being unkind. She genuinely thought she was painting an appealing picture.

But what she was actually saying was: if you're someone who recharges alone, or if casual-first relationships don't come naturally to you, this might not be the place for you. And if your communication style is more formal, or if you have a family you want to get home to, we're going to see that as not fitting in.

I didn't take that job.

Here's the shift that matters more: move from culture fit to culture add. Culture add means you're looking for someone who shares your core values, understands how you operate, and can be successful in your environment. But you're also asking: what does this person bring that we don't already have? What perspectives, complimentary work styles, or problem-solving approaches are we missing?

That's the hiring manager's job in Q4. Define what you actually need, not who you already are.

The mistake: Letting unconscious bias fill in the blanks

When you're unclear about what you're looking for, bias rushes in to fill the gap.

You're more likely to see potential in candidates who remind you of yourself. You're more likely to overlook red flags in people who have your communication style or background. You're more likely to assume that the candidate who seems the most "polished" (which often means the most comfortable in professional spaces that weren't built for everyone) is the best fit for leadership.

A study I reference in the Playbook showed that when hiring managers use vague, subjective criteria for fit, they end up hiring less diverse teams. Not because they're discriminating on purpose. Because they're evaluating fit intuitively, and intuition is riddled with patterns.

The Fit Profile isn't just about clarity. It's also a bias check.

When you write down what you're looking for, you make it harder to unconsciously rule people out. You create a standard that you can apply consistently. You make it possible to say: "This person doesn't have experience with X, but they've shown they can learn complex systems quickly, and that matters more for this role."

You also make it easier to push back on the gut feeling that someone doesn't fit, because you've named what fit means.

What to do right now

If you already have open reqs, you already have resumes coming in. Take a few hours this week to create a Fit Profile for each role. Not a job description. A Fit Profile. In it, document:

Role fit: What does this role demand on a day-to-day basis? What's the actual work, not the job title?

Team fit: What two or three dimensions of team dynamic matter most for someone to be successful here? Name them specifically.

Company fit: What values or ways of operating do they need to understand and embrace to thrive in your company?

Culture add: What would this person bring that your team doesn't already have?

Write it down and share it with your recruiting partner or hiring committee. That way, you can consistently evaluate candidates against it.

Will this solve every hiring challenge? No. But it will keep you from making the most common fit mistake: outsourcing clarity to a feeling.

And in Q4, when you're hiring fast, clarity is everything.