The most expensive hiring mistakes I have made were not unqualified people. They were qualified people without judgment. They had the right background, the right skills, the impressive resume, and they could do exactly what they were told. The problem appeared the moment the situation drifted off the script, which in a growing company is most of the time. They would optimize the wrong thing flawlessly, escalate what they should have decided, decide what they should have escalated, and pour real effort into work that did not matter while the thing that mattered sat untouched. None of that is a skills gap. It is a judgment gap, and judgment is the one thing I have found you cannot reliably install after the fact.
Skills are teachable. A smart, motivated person can learn a framework, a codebase, a market, a tool, a domain, given time and a reason to. I have watched it happen hundreds of times and I now take it almost for granted. Judgment, the instinct for what matters and what to do when the playbook runs out, is a different category. It develops slowly, through experience and reflection and a certain temperament, and it is largely formed by the time someone reaches you. So we rebuilt our hiring around a simple priority: hire for judgment, and train for everything else. Here is what that actually looks like, because the slogan is easy and the practice is not.
What judgment actually is
It helps to define the thing precisely, because judgment gets used as a vague compliment when it is really a specific capability. Judgment is the ability to make good decisions with incomplete information, under real constraints, when the right answer is not written down anywhere. It has a few observable components. The first is knowing what matters, the ability to look at a noisy situation and identify the one or two things that actually move the outcome. The second is proportion, spending effort and worry in line with the stakes rather than treating every problem as equally urgent. The third is knowing the limits of your own knowledge, being calibrated about what you are confident in and what you are guessing at.
People with judgment are not the ones who are right most often. They are the ones who are wrong in cheap ways and right in expensive ones. They make small reversible mistakes freely and reserve their caution for the decisions that are hard to undo. That single trait, calibrating reversibility against stakes, is most of what separates someone you can trust with ambiguity from someone you have to supervise through it. And it is almost invisible on a resume, which is why so much hiring misses it entirely.
Why interviews usually miss it
Most interview processes are built to measure skills and credentials because those are easy to measure. You can test whether someone can code, whether they know the domain, whether they have done the job before. So that is what gets tested, and judgment, being harder to see, gets a vague gut-feel rating at the end that is really just whether the interviewers liked the person. That is how you end up with a team full of capable people who collectively make poor decisions, which is one of the most demoralizing situations a company can be in.
The other failure mode is mistaking confidence for judgment. The candidate who answers every question quickly and decisively reads as strong, and interviewers reward it. But fast and confident is not the same as well-judged, and in fact the people with the best judgment often answer more slowly, because they are actually weighing the trade-offs the question contains instead of pattern-matching to a memorized answer. The fix is to retrain interviewers to stop scoring polish and start scoring reasoning, which means changing the questions you ask.
How we screen for it
You cannot ask someone whether they have good judgment. You have to create situations where judgment is the thing being exercised and then watch how they move. A few approaches do most of the work for us.
We ask about real decisions from their past, in detail, and we push on the reasoning rather than the outcome. Not what did you accomplish, but what were the options you considered, what did you not know at the time, why did you choose what you chose, and what would you do differently now. Someone with judgment can reconstruct the decision honestly, including the parts that were uncertain and the parts they got wrong. Someone without it tells a clean story where everything was obvious, which is itself a tell, because real decisions are never that clean.
We give ambiguous, underspecified problems and watch what they do with the ambiguity. The point is not the answer. It is whether they identify the missing information, state their assumptions, and reason toward something defensible, or whether they freeze waiting for a complete spec that is never coming. We tell them explicitly that there is no single right answer, which surfaces the difference between people who are comfortable in ambiguity and people who are quietly terrified of it.
And we look hard for evidence of good prioritization in how they have actually spent their time. People reveal their judgment in what they chose not to do. A candidate who can explain something they deliberately let fail or left undone because the cost was not worth it usually has the proportion instinct I most want. A candidate who never made a trade-off, who tried to do everything to the same high standard, is telling me they cannot tell the difference between what matters and what does not.
Example: Imagine interviewing two engineers for the same role. One has built a beautiful, elaborate system that solved a problem the company turned out not to have. The other shipped something rougher but had killed two of their own planned features after realizing nobody needed them. On paper the first looks stronger. The one worth hiring is the second, because the willingness to cut your own work when the stakes do not justify it is judgment in its purest form, and it does not come from training.
Training for everything else, in practice
The second half of the slogan gets less attention than it deserves, and it is the part that makes the first half honest. If you are going to hire for judgment and accept people who are missing specific skills, you have to actually be good at teaching those skills, or you have just hired a team of thoughtful people who cannot do the job yet. Skill development has to be treated as a real obligation, not a hope. New hires need a defined path to competence, a clear owner responsible for getting them there, and the explicit expectation that they will be slower for a while and that this is fine. The judgment you hired for is exactly what lets them learn fast, because they know what to prioritize and when to ask, but the learning still has to be supported.
This has a practical hiring consequence that surprises people. It means we will pass on the candidate who has every skill but shows shaky judgment, and take the one with obvious judgment and visible skill gaps, because the gaps close and the judgment does not appear. It feels risky in the moment, especially to hiring managers under pressure to fill a role with someone who can contribute on day one. But day one is a tiny fraction of a tenure. The person who can contribute immediately and then makes consistently poor calls for two years is the far more expensive hire, and the cost is mostly invisible until it is enormous.
What judgment makes possible in company building
The reason this matters so much is that judgment is the trait that lets you scale without drowning in process. The default way companies cope with growth is to add rules, approvals, and checklists, because they no longer trust people to decide well on their own. Every one of those additions is a tax on speed and a quiet admission that you hired people you have to constrain. A team of people with genuine judgment needs far less of that scaffolding, because you can give them context and goals and trust them to make sound calls inside it. That trust is the actual engine of a fast company, and it is only possible if you got the hiring right.
It also changes what your best people do with their time. When you trust judgment, leaders can stop adjudicating decisions that should never have reached them and spend their attention on the genuinely hard, genuinely high-stakes calls. The whole organization makes better decisions faster, not because anyone is smarter, but because the right decisions are being made by the right people at the right level. That is recruiting paying off as leadership capacity, and it compounds in a way that almost nothing else in company building does.
So I will keep saying it to anyone building a team: hire for judgment, train for everything else. The skills you are tempted to over-weight are the cheap part, the part you can teach. The instinct for what matters is rare, slow to form, and nearly impossible to add later, which is exactly why it belongs at the center of how you hire rather than as a footnote at the end of the interview. Get that right and most of the other problems of growth get easier. Get it wrong and no amount of process will save you. We have written more about the discipline of building a company over on the wrxstack blog.