What People Build for Fun Tells You How They'll Behave at Work

The Signal Nobody Asks About

Most interviews follow a predictable script. Walk me through your experience. Here's a technical problem. Tell me about a time you handled conflict. Everyone involved has rehearsed their part, and the result is a performance — polished, professional, and almost completely uninformative about how this person actually operates.

There's a category of signal that rarely makes it into the evaluation: what does this person choose to do when nobody is asking them to do anything?

Not as a trick question. Not as a lifestyle audit. But as a genuine window into the behaviours that will show up on your team every day — curiosity, persistence, tolerance for complexity, the instinct to build versus the instinct to consume. These aren't things you can test with a whiteboard problem. But they're often the things that determine whether someone thrives on a team or just occupies a seat.

You don't hire someone's hobbies. You hire the habits those hobbies reveal.

What Voluntary Interests Actually Expose

When someone chooses to spend their free time on something difficult — learning a new language, building furniture, training for a competition, writing an open-source tool, restoring an old car — they're demonstrating a set of behaviours without being asked to. That's the part that matters. Not the hobby itself. The pattern underneath it.

Here's what different kinds of voluntary pursuits tend to reveal:

• Building things (woodworking, coding side projects, electronics, home renovation) — Signals curiosity, persistence, and comfort with iterative problem-solving. Someone who builds things for fun has a tolerance for failure that you can't teach in onboarding. They've broken things, fixed them, started over. That's a disposition.
• Competitive pursuits (ranked gaming, martial arts, competitive sports, debate) — Signals resilience, appetite for feedback, and a drive to improve against a benchmark. People who compete voluntarily tend to handle performance pressure and constructive criticism differently than people who've never sought either out.
• Collaborative hobbies (team sports, bands, open-source contribution, D&D campaigns, community organising) — Signals coordination instincts and comfort with shared ownership. These people have practiced negotiating priorities with others in low-stakes environments. That translates.
• Long-form craft (writing, painting, music, photography, gardening) — Signals patience, care, and the ability to sustain effort on something that doesn't pay off immediately. In a world of quick dopamine loops, someone who voluntarily commits to a slow-return activity is telling you something about their attention span and their relationship with quality.
• Systematic learning (self-studying a new field, working through textbooks, earning certifications for fun, learning instruments) — Signals learning velocity and self-direction. Not because the credential matters, but because the behaviour of structuring your own education without external pressure is exactly the behaviour you want when the job demands a skill nobody on the team has yet.

None of these categories are better than the others. They're different. And each one tells you something a résumé can't.

The Signals in Context

What makes this useful isn't knowing that someone plays chess or builds keyboards. It's understanding what pattern of behaviour that interest reinforces — and whether that pattern fits what your team actually needs.

A team that struggles with follow-through might benefit from someone whose off-the-clock life is defined by long-form commitment — the person who spent two years restoring a motorcycle or who's been slowly writing a novel. A team that's technically sharp but insular might benefit from someone who runs a community meetup or plays in a band. A team that avoids risk might benefit from someone who competes in something and has learned to lose without shutting down.

What This Doesn't Mean

This is the section that matters most, because this idea goes wrong fast if you're not careful.

Plenty of outstanding people don't have visible hobbies. They have family obligations. They've dealt with burnout. They have private interests that don't show up on a portfolio or a GitHub profile. They spend their free time recovering from demanding work — which is its own form of self-awareness and discipline.

The absence of a flashy hobby tells you nothing. Someone who goes home and reads to their kids every night is demonstrating patience, consistency, and selflessness — behaviours that absolutely translate to how they'll show up on a team.

The point is not to evaluate the hobby. It's to notice, when the signal is there, what it's actually telling you. And to create space in your process for those signals to surface naturally — not as a filter, but as context.

What people do when nobody is watching often tells you how they'll behave when the job stops being easy.

The Right Question Isn't "What Are Your Hobbies?"

If you ask "what do you do outside work?" in an interview, you'll get one of two things: an awkward non-answer, or a rehearsed response designed to sound impressive. Neither is useful.

The better approach is to create openings where these signals emerge on their own. Some ways I've seen this work:

• "What's something you taught yourself recently?" — This isn't about the topic. It's about whether they have the instinct to learn without being told to, and how they describe the process of getting through the hard parts.
• "What's a problem you solved that nobody asked you to solve?" — At work or outside of it. The answer tells you whether they see problems as someone else's job or as interesting.
• "What do you do when you're stuck on something and there's no deadline?" — Do they walk away? Push through? Ask someone? Sleep on it? Each of those is a real behaviour that will show up on your team.
• "Tell me about something you're proud of that has nothing to do with your career." — This one opens the door without prescribing what a "good" answer looks like. Some of the best answers I've heard have been about cooking, coaching a kid's team, or finishing a long hike.

These aren't trick questions. They're invitations. And the people who light up when answering them are often the people who bring that same energy to work.

How This Shapes Culture

Culture isn't a mission statement. It's the aggregate of what your team members reinforce in each other, every day, without being asked.

A team full of people who naturally tinker, learn, and pursue mastery outside of formal obligation tends to create a specific kind of environment — one where growth is the default, where asking "how does this work?" isn't seen as a distraction, and where quality is something people care about intrinsically rather than because someone is measuring it. That doesn't happen by accident. It happens because someone in the hiring process noticed that this candidate cares about getting better at things — not because they're told to, but because that's how they're wired.

And when you put a team of those people together, the culture gets much easier to build and sustain. They push each other. They share what they've learned. They raise the bar not through pressure but through example. That's not something you can mandate in a handbook. It's something you select for — or you don't.

What to Actually Look For

If you're evaluating candidates and want to use these signals well, here's the framework:

• Look for self-direction — Do they pursue things without external structure or incentives?
• Look for sustained interest — Have they stuck with something long enough to get past the easy part?
• Look for capacity for growth — Do they describe learning as something they do, or something that happens to them?
• Look for how they engage with challenge — When something is hard, do they lean in or back off?
• Look for energy — Do they bring something to the room when they talk about what they care about?
• Treat the absence of visible hobbies as neutral — never as a negative signal

None of this replaces technical evaluation. It supplements it. You're still hiring for competence. But between two equally competent candidates, the one whose off-the-clock life reveals curiosity, resilience, and self-direction is more likely to grow, adapt, and raise the level of the team around them.

The Bottom Line

The things people choose to care about often reveal how they learn, persist, collaborate, and grow — and those traits absolutely affect team culture. Not because hobbies make someone a better person, but because voluntary behaviour is the most honest behaviour. It's what someone does when there's no performance review, no deadline, and no one watching.

If your hiring process captures what people know but misses who they are when they're not performing, you're leaving the most important signal on the table. I help teams design interview processes and evaluation frameworks that surface the behavioural patterns behind the résumé — not just skills, but dispositions. Let's talk about what your process might be missing.