Hire people, not résumés: what to look for beyond the interview

To hire people, not résumés, you look past titles and keyword matches and focus on how someone actually works, what the role really needs, and how they’ll fit into the team you have. A résumé tells you what a person has done. It can’t tell you how they’ll do it with you.

I learned this by getting it wrong. Here’s the story, what changed, and what I’d do differently from the first job post.

What does it look like to hire résumés instead of people?

When I became VP of Operations and Product at a small marketing and software firm, I was asked to rebuild the team. I had no management experience. So I hired the way most first-time managers do: I read résumés, matched experience to the job description, and made offers.

On paper, every hire made sense. In practice, they didn’t last. Clients left. Everyone was stressed.

I was hiring résumés, not people. I knew what each person had done. I had no idea how they liked to work, what the role would really ask of them day to day, or how they’d get along with the rest of the team. I also assumed everyone worked the way I did, which is a mistake I wrote about in you are not your team.

What changed when Billy redesigned hiring?

Short-staffed, not out of brilliance, I put Billy in charge of the people side of digital marketing. Billy, now my co-founder, is a product leader with nearly 20 years of experience and a background in design thinking. She treated the team like a design problem.

She decoded the team’s personality assessments and put everyone on one page. She reframed opposing work styles as balance instead of friction. She defined everyone’s roles. And she redesigned how hiring, onboarding, and work assignments happened.

The same roles that had failed under my hiring succeeded under hers. The team stayed together, and they say they love their jobs.

That’s the part that stuck with me. The roles were the same. The market was the same. What changed was how the team was being managed. Almost every people problem is a management problem, and hiring is where a lot of those problems start. The full story, and the method behind it, is in our guide your team is a design problem.

Why isn’t a résumé enough?

A résumé is a highlight reel written for a keyword filter. It’s useful for some things and silent on others.

None of this makes résumés useless. It just means the right column is where most hires succeed or fail, and a standard interview doesn’t do much to fill it in.

What should you look for beyond the interview?

Look for signs of how someone actually works, in conditions that resemble the real job.

• How they approach a real problem. Not a brainteaser. A small, honest slice of the work.
• How they communicate. Do they explain their thinking? Do they write clearly? Do they listen?
• What questions they ask. Good questions about the role, the team, and how decisions get made tell you a lot.
• How they talk about past teams. Listen for what helped them do their best work, and what got in the way.
• Whether the role, as it really is, suits them. A role that’s mostly quiet, focused work and a role that’s mostly fast-moving collaboration are very different jobs, even with the same title.

Notice what isn’t on this list: whether they remind you of yourself. That instinct feels like good judgment. Often it’s just familiarity.

How do you design interviews around how your team actually works?

Treat the interview like a small prototype of the job. Here’s how to set that up.

Define the role before you write the job post

In small companies, people wear several hats that nobody has defined. If you don’t know what the role really is, you can’t hire for it. Write down what this person will own, who they’ll work with most, how decisions get made, and what a normal week looks like. That’s role clarity, and it’s the foundation of everything else. Clear roles are to a team what clear navigation is to a product.

Describe the job honestly

Put the real version of the role in the job post and the interview. If it’s lots of client calls, say so. If priorities change every week, say so. The right people will lean in. The wrong fit can opt out before anyone gets hurt.

Use a work sample that looks like the real job

Ask candidates to do a short, paid or reasonably sized task that mirrors actual work. Keep it the same for everyone so you can compare fairly. Then talk through it together. How they explain their choices often tells you more than the result.

Give people more than one way to show what they can do

Some people think out loud. Others do their best thinking alone. Share the interview topics in advance, and allow a follow-up in writing. You’re not lowering the bar. You’re making sure the interview measures the job, not who’s best at interviews.

Let them meet the team they’d work with

The people they’d work with every day can answer questions you can’t. It also lets the candidate see how the team really works, which is fair to both sides.

Use the same questions for every candidate

Consistent, job-related questions keep you focused on the role and make comparisons fairer. Write them down before the first interview.

Where do work-style tools fit in hiring?

Carefully. Understanding how people work is incredibly useful, but its best use comes after the offer, not before it.

Don’t screen candidates by personality type. Hiring decisions should rest on job-related skills and the real demands of the role.

Where work-style understanding shines is in fit-to-role and onboarding: helping a new hire and their manager talk openly about how they take in information, make decisions, collaborate, and handle stress, so the first months go well. A work-style assessment gives everyone a shared, judgment-free language for that conversation.

How do you onboard someone into the team you actually have?

Hiring doesn’t end when they sign. Onboarding is where it succeeds or fails. People decide early whether a job is working for them.

Here’s what good onboarding looks like when you design it around real people:

• Show them the whole team. Who does what, who to ask about what, and how each person likes to work. A one-page view beats a dozen intro meetings.
• Confirm the role in writing. Restate what they own, what they don’t, and what success looks like in the first month and the first quarter.
• Ask how they work best. How do they like to get information? How do they like feedback? What helps on a stressful week? Then adjust.
• Pair them thoughtfully. Some pairings click naturally. Think about who complements their style, not just who has free time.
• Assign work that fits. Early wins matter. Give them work that plays to their strengths while they learn the rest.
• Check in often, and listen. Short, regular one-on-ones catch small problems while they’re still small.

This is how the people you hire become people who stay. If you want to go deeper on keeping good people, see our glossary entry on employee retention.

What’s the real lesson?

The roles I struggled to fill were never the problem. The problem was how I hired for them and how the team was being managed. When hiring, onboarding, and assignments were redesigned around real people, the same roles worked.

So before you post your next job, step back. Define the role. Describe it honestly. Interview with real work. Then onboard the person into the team you actually have, not the one you imagine.

We’re building Woosah Teams to help with that last part: a short work-style assessment for each person, and a manager view that shows the whole team on one page, so a new hire and their manager can understand each other from week one. You can see how it works, or read more about our story.

Hire people, not résumés. Then build a team they want to stay on.