The Interview Question That Predicts How a Tech Will Fight With Your Team

A good chunk of what owners call a "bad hire" isn't about skill. It's about a communication style you never screened for.

Here's one interview question that surfaces self-awareness in seven seconds, what to actually listen for, and why the right level of awareness matters more than any particular style.

Lots of shops have had the same hire go sideways the same way.

Great on paper. Decent on the working interview. Then month two hits and something's off.

The front counter is frustrated. The other techs go quiet around him. Comebacks tick up. Nobody can name the problem.

You didn't hire the wrong tech.

You hired a communication style you never screened for.

Here's what miscommunication actually costs you.

A tech misreads a DVI note and replaces the wrong part. One comeback. One pissed customer. Half a day of bay time you'll never bill.

A service advisor assumes the tech heard the customer's "weird sound only on cold starts" note. The tech didn't. Now it's a diag redo, a warranty conversation, and a bay you can't flip.

A shop owner in our community said this perfectly:

"Sometimes you say things, you're very clear what you thought. The person heard every word you said. But there were six words in your head you never said — and you didn't realize it."

That's what you're paying for. Not the hire. The gap between what got said and what didn't.

Miscommunication doesn't always look loud.

Sometimes it looks like silence. Hesitation. Assumptions nobody said out loud.

Every one of those moments costs you bay time.

And bay time is the most perishable inventory you've got. Monday's empty bay doesn't show up on Tuesday's schedule.

There's no right communication style. There's a right level of awareness.

A tech who thinks out loud isn't better than a tech who processes quietly. A quiet tech isn't better than a loud one.

But a tech who knows how he processes, and knows how it lands on the rest of your team, will save you thousands in avoided friction over his first year.

You're not hiring a style. You're hiring the self-awareness around the style.

So here's the question I'd add to your interview loop this week. One question. Seven seconds to ask. Tells you more than ten minutes of resume review.

"Are you someone who thinks out loud, or do you prefer to think it through quietly and then speak?"

What you're listening for isn't the answer.

It's the structure of the answer.

Do they know themselves? Or do they stall?

Can they describe how their style lands on other people? Or do they talk about themselves like nobody else is in the room?

The real signal is adaptation. A tech who says "I'm a quiet processor, but when I'm working with an advisor who needs me to narrate, I make myself do it" — that tech already knows how to fit into your shop.

You didn't teach him that. You screened for it.

One question won't fix a broken hiring process. But it will catch the hires who looked great on paper and would have gone quiet in month three.

And it costs you nothing to add.

0 comments