When a team needs people, the most natural response is to post the opening as quickly as possible, schedule more interviews, and push the process faster. But “filling a seat” is only an outcome; it does not prove the hiring was done well. The more important questions are: What capability is the team actually missing? What real problem will this person take on after joining? What gives us reason to believe we can work together on the same stretch of road?
Technical hiring is not a script, nor is it solely the recruiter’s job. It is part of a technical leader’s ongoing team-building: making clear the problems to be solved in the coming period, finding the people who match them, and updating one’s own judgment through each choice.
Define the gap first, not the “ideal person”
“We need someone really strong” hardly helps anyone make a decision. Where they are strong, what problem they solve, and under what constraints they can be effective are all still unstated.
Rather than assembling a perfect profile from scratch, I recommend working backward from the work the team is about to face. The discussion can center on four questions:
- Over the coming period, which problems will directly hurt delivery, quality, or collaboration if left unsolved?
- Do these problems call for deeper expertise, a larger scope of responsibility, or more reliable collaboration and mentoring ability?
- What does the current team already have, and what is it really missing?
- If we don’t hire for now, how will this gap show up: delays, quality risk, knowledge concentration, or people being stretched thin over the long term?
What emerges from this discussion is not a list of attractive labels but a verifiable boundary of responsibility. For example, what is needed may not be an “all-rounder senior engineer” but someone who can untangle a repeatedly out-of-control cross-platform process, align boundaries across multiple roles, and make later iterations no longer depend on one particular person. It may also mean not adding one more doer, but someone who can bring new people into the working methods so the team’s delivery ability no longer rests on a few individuals straining to hold it up.
When the gap is described in terms of problems and responsibilities, candidates can judge whether this is work they are willing to take on; interviewers, too, find it easier to avoid mistaking “like me” for “a good fit.”
The purpose of hiring materials is to reduce guessing on both sides
Many job descriptions read like a wish list of capabilities: a long tech stack, many adjectives, yet little clarity about what actually needs to be done. When information is scarce, candidates can only guess at the team’s situation, the role’s boundaries, and the room for growth; the team likewise judges candidates by vague impressions of whether they “feel right.” This guessing only postpones the mismatch until later, when it surfaces.
A useful description does not need to present the team as capable of everything, but it should honestly answer a few questions:
| What candidates care about | What the team should explain |
|---|---|
| Why is this role needed now? | The user, engineering, or collaboration problem being solved. |
| What comes first after joining? | Near-term responsibilities, who they will work with, and foreseeable difficulties. |
| What counts as doing the job well? | Observable outcomes, not a vague “excellent performance.” |
| What will I gain, and what must I take on? | Learning opportunities, scope of impact, constraints, and boundaries of responsibility. |
The same applies to every conversation. Rather than rushing to prove the team is “good enough,” let the other side see the real work: which problems are already clear, which are still being explored, and which trade-offs are unavoidable in the short term. A mature candidate will not walk away just because they hear about hard problems; what truly matters is whether they are willing to work on those problems and whether the team can offer the corresponding room and support.
Treat the interview as mutual verification, not one-way screening
An interview certainly needs to assess ability, experience, and ways of collaborating, but it should not be understood as an exam for finding the “perfect answer.” What the team wants to reduce is uncertainty in future collaboration, and the candidate is doing the same thing.
More valuable conversations usually revolve around real experience:
- What unclear problem have you faced? How did you understand it at first?
- Which paths did you compare, and why did you ultimately make this choice?
- What resistance did you meet as things moved forward, and how did you collaborate with others?
- How were the results confirmed? If you could do it over, what would you change first?
These questions do not require candidates to have completed grand projects on their own. On the contrary, being able to distinguish one’s own responsibility from others’ contributions and the constraints at the time is often more reliable than turning the story into a personal hero narrative. The team should also allow for “I don’t know”: not having experienced a particular scenario does not equal a lack of potential; the key is how the person fills in the information, builds judgment, and takes on the consequences.
Likewise, candidates have the right to ask questions in return. A healthy hiring conversation should let them understand how the team makes decisions, how conflict is handled, whether feedback is specific, and whether commitments are honored. If we demand candor from candidates one-sidedly while evading the team’s own difficulties, the relationship is unequal from the very start.
Don’t let short-term pressure replace long-term standards
When short-handed, the most dangerous temptation is to lower the bar to an indefensible degree just to relieve pressure immediately. This may seem to speed up the present, but it can turn the problem from “temporarily short-handed” into “long-term repair of collaboration, quality, and trust.”
Standards are not the same as being harsh, and certainly not a quick substitution of background labels for judgment. They should include two layers:
- Non-negotiable parts: integrity, the basic boundary of capability, willingness toward the responsibilities, and the baseline for how one collaborates with the team;
- Trainable parts: domain experience, specific tools, communication style, and scenarios not yet encountered.
By distinguishing these two layers, the team neither misses growth potential in pursuit of a perfect resume nor accepts, out of anxiety, choices that clearly do not match the real work. Every “exception” deserves a written reason: What evidence did we see at the time? What risk did we accept? How do we verify it later? These records are not for assigning blame, but for helping the team calibrate its judgment in the future.
Hiring is a long-term external relationship
Much hiring work appears to happen after a role opens up, but in reality it begins much earlier. The professionalism, sincerity, and sense of boundaries a person experiences in collaboration, public exchanges, community contributions, or everyday interactions will influence whether they are willing to learn about your opportunities in the future.
Therefore, hiring should not start only when you “need people.” In the long run, what is more worth accumulating is:
- honoring commitments on time in collaboration, while also being honest about what cannot be delivered;
- helping others understand the problems you are solving, rather than only spreading job titles;
- being glad to offer help with no immediate return, and not turning every exchange into recruiting;
- respecting others’ current choices, and not treating a refusal as the end of the relationship.
This is not about instrumentalizing every relationship. On the contrary, only when we stop treating people as resources to be converted can trust turn into collaboration at the right moment. Someone who is not a fit to join now may still become a future partner, a referrer, or someone who offers an important outside perspective.
Finally: review judgment through outcomes, not just tally results
The end of hiring is not the end of judgment. Some time after a new hire joins, the team should look back: Was the gap we defined accurate? Did the actual responsibilities match what was communicated? Which signals were overvalued or overlooked in the conversations? Which support should have been provided earlier?
A truly valuable review does not sort people into “hired right” or “hired wrong,” but distinguishes where the problem came from: an unclear role definition, unaligned expectations, an insufficient support system, or a mistaken inference about the match between ability and environment.
Only by consolidating these lessons does hiring turn from repeated firefighting into part of the team’s long-term capability. What remains in the end is not just more people, but clearer judgment, more credible commitments, and an environment where good people can join with confidence and keep performing.