Stop Hiring for Experience, Start Hiring for Operating System

I used to think experience was everything.

"Five years in hospitality." "Worked at a major theme park." "Managed teams of 20+."

I'd see that resume and think: This person knows what they're doing.

Then I'd hire them, and within a month, I'd realize: they know how to do things one specific way, in one specific context, and they're completely lost here.

Meanwhile, the 19-year-old with zero "experience" who I almost didn't interview? They're three months in and already running circles around people with years on their resume.

That's when I figured it out: I was hiring for the wrong thing.

Experience tells you what someone has done. Operating system tells you how they think.

And how someone thinks matters infinitely more than what they've memorized.

Experience vs. Operating System

Here's the difference:

Experience is learned. It's the scripts, processes, and procedures from previous jobs. It's valuable, but it's also specific to context. Take someone out of their environment, and experience often doesn't transfer.

Operating system is inherent. It's how someone approaches problems, how they treat people under pressure, how they learn, how they adapt. It's the engine that drives everything else.

You can teach someone your systems. You can't teach someone to care, to think critically, or to give a damn about people.

What an Operating System Actually Looks like

When I interview now, I'm looking for these core traits:

Curiosity: Do they ask questions? Do they want to understand why, not just what? Curious people learn fast and adapt faster.

Ownership: When something goes wrong, do they make excuses or look for solutions? Do they see problems as "not my job" or "let me help fix this"?

Resilience: How do they handle frustration, failure, or chaos? Do they shut down or figure it out?

Emotional intelligence: Can they read a room? Do they notice when someone's struggling? Do they adjust their approach based on who they're talking to?

Coachability: When you give feedback, do they get defensive or curious? Do they implement it or ignore it?

These things don't show up on a resume. You have to look for them differently.

The 5 Interview Questions That Reveal Operating System

Forget "Where do you see yourself in five years?" Here's what I actually ask:

1. "Tell me about a time you had to figure something out without anyone telling you what to do." This reveals problem-solving, resourcefulness, and ownership. Listen for whether they took initiative or waited for permission. Listen for how they describe the process, not just the outcome.

2. "Describe a time you disagreed with a rule or policy. What did you do?" You'll learn if they're a compliant order-follower or a critical thinker. You'll see if they know how to navigate disagreement constructively or if they just rebel or comply silently.

3. "Tell me about a time you made a mistake that affected other people. What happened next?" This is pure gold. Do they own it? Deflect? Minimize? How they handle failure tells you everything about their character and their capacity for growth.

4. "What's something you've taught yourself recently, and how did you learn it?" Curiosity and learning agility in action. Are they actively growing? Do they seek out knowledge? How do they approach something unfamiliar?

5. "Describe the best leader you've ever worked for. What made them great?" People describe what they value. If they talk about someone who trusted them, you know they value autonomy. If they talk about someone who taught them, you know they value growth. This question is a window into what kind of environment they'll thrive in.

How to Spot It Beyond the Interview

Interviews are artificial. Here's how to see someone's real operating system:

• Give them a real scenario during the interview. Not hypothetical—actual. "A guest just spilled ice cream on their kid's shirt and is upset. Walk me through what you'd do." Watch how they think out loud.

• Pay attention to how they treat everyone, not just you. How do they interact with the receptionist? How do they talk about previous employers? Kindness and respect aren't situational in people with good operating systems.

• Do a working interview if possible. Let them shadow for a few hours. See how they show up. Do they ask questions? Jump in? Observe? Disengage? You'll learn more in two hours of real work than in ten rounds of interviews.

When Experience Actually Matters

I'm not saying experience never matters. Sometimes it does:

• Technical skills that take years to develop (engineering, culinary arts, specialized safety roles)

• Regulatory knowledge that's non-negotiable (safety compliance, legal requirements)

• Leadership roles where industry context helps (but even then, operating system matters more)

But for most frontline and supervisory roles? Operating system beats experience every single time.

I'd rather hire someone with the right mindset and train them on our systems than hire someone with ten years of bad habits from somewhere else.

Stop asking "Have they done this before?"

Start asking "Can they think, adapt, and care?"

The rest you can teach.