Hire for Character, Train for Skill: Why Soft Skills Trump a Resume?
Imagine you’re assembling a team for a critical project. You have two final candidates for a key role. The first is a “rock star” with a brilliant resume, an impressive portfolio, and answers to all your technical questions. But their conversation is tinged with arrogance, and when asked about past failures, they blame others.
The second candidate is noticeably more modest in their experience. They don’t know the answers to a couple of tricky questions, but their eyes are full of passion. They talk about how they taught themselves a new tool for a personal project, speak honestly about their past mistakes, and enthusiastically ask about the company’s learning and development process.
Who do you choose? The classic approach to hiring screams, “Take the first one!” But experience tells a different story.
An employee’s competence is not as important as their personal qualities. You can become a professional, but changing your character and behavior is nearly impossible.
We often fall into the “expertise trap.” We think that by hiring the most technically skilled specialist, we automatically solve all our problems. But we forget about the hidden costs that a toxic employee brings, even if they are a genius in their field.
The Developer Example: Take that “10x engineer.” They write complex but efficient code. However, they refuse to follow common standards, don’t write documentation (“my code is self-documenting”), and humiliate colleagues in code reviews. The result: the team is afraid to touch their code, new hires can’t understand it, and strong specialists leave, tired of the constant hostility. Morale plummets, and development speed eventually slows down.
The Designer Example: A talented designer creates incredible mockups but is completely resistant to criticism. Any feedback from development (“this is hard to implement”) or from a manager (“this doesn’t solve the user’s problem”) is taken as a personal insult. The result: the team spends weeks implementing a beautiful but useless feature. The product fails to launch, and relationships within the team become strained.
The Analyst Example: A “star” analyst finds brilliant insights in the data but considers it beneath them to share their methodology or help colleagues. They are a “black box.” The result: when they go on vacation or resign, all their expertise leaves with them. The company becomes a hostage to one person.
If an employee lacks discipline, responsibility, or respect for others, there’s nothing you can do about it. You’ll spend your time resolving conflicts instead of working.
Now, let’s return to the second candidate. Yes, they lack knowledge in a specific area. But what do they have?
A person who wants to develop, is disciplined, and knows how to get things done, but may not be up to par with their technical skills, will always be better than a highly skilled specialist who demoralizes the team.
You can teach someone to write code, use Figma, or build SQL queries. You cannot teach them to be responsible.
This doesn’t mean you should ignore technical skills. Of course not. But they shouldn’t be the sole or primary criterion.
Your task is to find someone who:
Stop looking for the “perfect” candidate with the ideal skill set. Start looking for people with the right character. It’s a long-term investment that will pay off handsomely in the form of a strong, healthy, and effective team capable of tackling any challenge.