The Trait I Trust Most
There is a type of person I trust much more than average in a growing company. They are not always the smoothest in interviews or the most polished communicators. They do not always have the cleanest frameworks. But they have one trait that matters enormously: they are constitutionally incapable of watching something be broken without trying to fix it.
That instinct is hard to replace.
Most People Adapt to Broken Systems
A surprising number of people can work around dysfunction forever. They see the broken onboarding flow, the stale dashboard, the manual spreadsheet, the process nobody understands, or the customer complaint that keeps repeating. Then they adapt. They route around it, complain about it, maybe mention it in a meeting, and keep going.
They can live next to the problem. The people I want to hire usually cannot.
In a fast-moving company, a lot of important work is not assigned cleanly. The roadmap never captures everything. The org chart does not cover every gap. The biggest sources of drag often sit between teams, between tools, between priorities, or between "someone should handle this" and "nobody owns this."
The people who change a company are often the ones who cannot leave those gaps alone.
This Shows Up Before The Big Wins
This trait usually appears in small moments first. An engineer notices that a flaky internal script wastes time every week and cleans it up without being asked. A PM sees that the team keeps relitigating the same decision and creates a better decision process. A designer notices users misunderstanding the same interaction and pushes to simplify it instead of normalizing the confusion.
None of this looks heroic. It is not a big launch or a board-slide achievement. But across months, these people quietly raise the quality bar around them. They do not just complete assigned work. They reduce ambient brokenness.
That matters because most organizations decay through small tolerances. A bad process becomes normal. A broken workflow becomes "just how it works." A confusing product pattern becomes something support learns to explain. The best people interrupt that drift.
Skill Is Easier to Teach Than This
Most companies over-index on credentials because they are easy to evaluate. They look for polish, pedigree, and the ability to give a convincing answer in a structured interview. Those things can matter, but I would much rather take someone with a strong fixing instinct and level them up on the craft than hire someone who is technically solid but emotionally comfortable living in a broken system.
You can teach better prioritization, product sense, and communication. It is much harder to teach someone to care when something is off. That part tends to be built in.
The opposite profile is dangerous because it can look strong in interviews. These are smart, capable people who perform well inside a defined box, but have no real discomfort with persistent dysfunction. If the task is not explicitly theirs, they leave it alone. If the process is bad, they tolerate it. If the product is confusing, they work around it. Then you hire them into a messy company and realize they do not improve the environment around them. They simply survive inside it.
Hiring for This Is Uncomfortable
Companies miss this trait because it does not always look tidy. People who cannot tolerate broken things ask annoying questions. They push on weak assumptions. They notice inefficiencies nobody wanted to discuss. They create friction, but usually the useful kind.
That can be misread as lack of alignment, lack of patience, or lack of seniority. Sometimes it is. Often it is the raw material of ownership.
The Signal
If I am building a team, I want people who feel a real itch when they see something broken. Not people who merely identify issues or explain why the issue exists. People who have a hard time leaving it alone.
A lot of hiring comes down to one question: when this person sees something clearly wrong, what happens next?