The Best Technical Candidate Isn't Always the Right Hire

One candidate masters a tool technically but shuts down when questioned about it. Another has less technical polish but communicates clearly and admits openly when something didn’t work. In a small team, the second one tends to deliver more over the long run, and that’s a harder thing to see in an interview than raw skill.

Technical ability is easier to teach than openness and clear communication. Hiring someone technically strong but closed off means inheriting a problem that’s difficult to fix later, once they’re already on the team and the pattern is set. Signs of the more useful trait show up in how someone talks about a past mistake, whether they over-justify it or explain it plainly, whether they ask questions back, whether they show real interest in understanding the business rather than just the task in front of them.

In a lean team, each person deals directly with the founder and with each other, with no layer of management in between to smooth things over. Someone who doesn’t communicate well creates friction in every interaction that layer would otherwise absorb. This isn’t an argument for hiring someone with no technical grounding at all, it’s weighing both axes deliberately, and when the choice comes down to someone technically stronger but closed off versus someone technically sufficient and open, the second tends to win out over time. Delegating real responsibility, budget calls, strategy decisions, gets safer once someone has already shown they’ll report when something isn’t going well instead of hiding it.

Openness works best as a tiebreaker between candidates with comparable technical skill, not as a substitute for the minimum competence a role actually requires.

Flow Border pairs founders with a dedicated account built on exactly this kind of clear, direct communication.