The hiring packet was open beside a half-finished cup of coffee, and the team had reached the familiar pause. One candidate had years of direct experience with the stack. Another had less experience, but the interview notes kept circling the same signals: they learned quickly, asked careful questions, and improved after feedback inside the same conversation.
This is one of the quieter decisions in engineering hiring. Experience feels safer because it is visible. A person has shipped similar systems, used familiar tools, survived familiar incidents, and collected stories that sound close to the work in front of us. Potential is harder to hold. It asks us to imagine what someone may become with context, support, pressure, and time.
The mistake is treating the two as opposites. Experience is not only a number of years, and potential is not a warm feeling about someone. Both need evidence. Experience should show up as judgment: clearer trade-offs, better risk awareness, calmer debugging, stronger communication, and the ability to recognize patterns without pretending every problem is the same. Potential should show up as learning behavior: how someone receives feedback, repairs a wrong assumption, asks for missing context, and turns a new constraint into a better answer.
A senior candidate can have long exposure without much growth. A junior candidate can have limited exposure but a strong learning loop. Neither label is enough. The useful question is not who has the most impressive history. It is what evidence suggests this person can meet the actual need of the team in the next season of work.
That team need matters more than hiring slogans usually admit. If the team is entering a fragile migration with little room for supervision, direct experience may be the responsible choice. Someone who has seen similar failure modes can reduce risk quickly. If the team has enough senior support but lacks fresh energy, careful execution, or future internal leaders, hiring for potential may be a better long-term investment. The same candidate can be a wise hire in one context and a difficult fit in another.
Potential also has a cost, and naming that cost makes the decision more honest. A person with less experience may need more onboarding, clearer feedback, smaller first problems, and a manager who will actually make time for coaching. If the team says it wants to hire for potential but has no patience for questions, no review discipline, and no space for mistakes that are caught early, then it is not hiring for potential. It is asking someone to grow in poor soil and calling the risk theirs.
Experience has a cost too. A person who has done something many times may bring useful shortcuts, but they may also bring assumptions from a different company, scale, or culture. Past success can become a quiet script. Good hiring does not punish experience for that; it simply checks whether the person can still listen, adapt, and learn the local system before prescribing solutions.
The interview process should make these signals observable. Instead of asking whether someone is high potential, ask what they changed after a hint. Instead of asking whether someone is experienced, ask them to explain a trade-off they once got wrong and what they watch for now. Let candidates show how they think when the problem moves slightly under their feet. The best evidence often appears in the correction, not the first answer.
I have become cautious about decisions that sound too clean. Hire only seniors. Hire only hungry juniors. Hire only people from this kind of company. These rules reduce uncertainty, but they also reduce attention. Real teams need a portfolio: people who have seen the road before, people who are ready to stretch, people who stabilize quality, and people who bring new questions into habits that have become too automatic.
A good hiring decision is not a bet on a resume or a bet on hope. It is a bet on evidence matched to context. What does this person already know? How do they learn what they do not know? What support will the team honestly provide? What risk are we accepting, and what future capability might we build if the bet works?
The next time a hiring conversation gets stuck between potential and experience, it may help to slow the room down. Name the work ahead. Name the support available. Name the evidence observed. Then choose the person whose current strengths and learning path fit the team you are actually building, not only the team you wish you already had.