Imagine this: HR introduces you to a new colleague with the message, “Here’s your new team member. Their CV is great, and they passed all recruitment stages.” And you look at them and think, “Okay, but will I be able to work with this person for the next two years?” Sounds familiar?
The Problem with Traditional Recruitment
Classic recruitment is a bit like buying shoes online – they look great in the picture, but only when you put them on do you realize they pinch your toes. HR checks the skills, the manager checks the experience, and the team? The team finds out about the new member on Monday morning.
The result? The new person might be a brilliant specialist, but if their communication style resembles a telegram from the 1920s, and the team loves chatting about everything and nothing during Daily – we have a problem. Or vice versa – someone who needs silence like a monk in a monastery joins a team that discusses every piece of code like football experts on TV.
Team-Based Recruitment – How Does It Work?
In several companies, I managed to convince people to try a completely different approach. The process looks like this:
Step 0: Recruiters present candidates (optional)
The classic CV screening. Nothing new here.
Step 1: Short technical interview
One of the team’s specialists talks to the candidate for 30-45 minutes. The goal? To check the level of knowledge and experience. No deep dives into bubble sort implementation or questions like “how much does an elephant weigh in Java.” Just: does this person know what we’re talking about?
Step 2: Interview with the whole team
And here’s where the magic happens. The candidate meets the entire team they’ll be working with. Everyone asks questions, everyone observes, everyone makes the decision. It’s not an interrogation – it’s getting to know each other.
Step 3: Salary talk
The line manager discusses financial terms. That’s it, signature on the contract.
Why Does This Make Sense?
When I introduced this system, I always asked candidates at the end of the interview: “How would you feel if the next stage was a meeting with the team?” And I presented the arguments:
- You’re going to be part of the team – so let the team check if your character fits what you say about yourself
- You’re supposed to bring value to the team – maybe let the team decide if they see that value
- If the team says ‘Yes’ – you’ll have support from day one
- If the team says ‘No’ – well, there’s no point in forcing it
Reactions? Always positive. “I’ve never had such an interview, but I see the point.” Some expressed concerns, but said it was worth trying.
Real-Life Examples
Case one: Senior Developer with communication issues
The candidate had a great CV – 8 years of experience, knew all the frameworks by heart. During the technical interview, he shone. But when he met the team, it turned out his communication style was a series of monologues. The team worked in a mode of constant consultation and collaboration. Verdict? “Great specialist, but not for us.”
Case two: Junior with potential
A young programmer, one year of experience, a modest CV. But during the team meeting, she asked great questions, listened carefully, and her energy was contagious. The team said: “We’ll teach her everything, but we want her with us.” A year later, she was one of the best in the team.
Case three: Expert who didn’t fit culturally
A candidate with 15 years of experience, a guru in his field. But during the team interview, it turned out his approach was “I know better, you all learn from me.” The team valued equality and mutual learning. Despite his skills – he didn’t make it.
What Does the Team Check During Such an Interview?
Team chemistry
Will this person fit our way of talking, joking, solving conflicts? This isn’t about skills – it’s about whether we’ll like each other for the next few years.
Work approach
One team loves long discussions about architecture, another prefers quick decisions and iterations. One values precision, another experimentation. The candidate can be brilliant, but if their work style is the opposite of the team’s – there will be suffering.
Motivation and values
Does this person want to develop in the same direction as the team? Do they have a similar approach to code quality, testing, documentation? Will they push the team forward, or hold it back?
Benefits for Everyone
For the team:
- They have a say in who joins them
- They take responsibility for integrating the new person
- They feel co-responsible for recruitment success
For the candidate:
- They know who they’ll work with
- They can assess if the team suits them
- They start with the support of the whole group
For the company:
- Lower risk of a bad hire
- Faster integration of new people
- Better cultural fit
When Doesn’t It Work?
This system only makes sense in teams that actually collaborate. If people sit in their caves and only contact each other via Slack, team-based recruitment is a waste of time. But if you work together, plan together, solve problems together – the team knows best who they need.
Summary
The team knows best, is self-governing, makes decisions, and takes responsibility. Whoever tried this approach never went back to classic recruitment. Why guess, when you can ask the people who’ll work with the new person every day?
As I always say – you can build teams by force, or you can let them build themselves. The second option is simply smarter.