Fit is not the same as contribution

At a point in my career I interviewed for a senior role where every question in the loop was about how I’d think through a problem. What tradeoffs I’d weigh. Where I’d push back on a plan I thought was wrong. I got the job partly because of an answer where I disagreed with the interviewer’s framing and explained why.

Six months in, my input on anything that mattered had quietly stopped being asked for. Decisions still got made. They just routed around me, to whoever the team had already decided to trust. My days filled up with execution work and cleanup on calls I hadn’t been in the room for. Nobody told me to stop contributing. The invitations just stopped coming.

Two different things called seniority

Studios use “senior” to mean two different things and rarely say which one they mean. One is tenure: how long you’ve been at the company, how well you know its systems, how little supervision you need to get through a normal week. The other is judgment: whether your calls, over time, have been good ones, and whether the org has learned to route decisions through you because of that track record.

Tenure is easy to measure and easy to manage. It shows up in an org chart and a start date. Judgment is harder. It requires someone to actually track whether a person’s calls held up, across enough decisions, to be trusted with bigger ones. Most studios default to tenure because it takes no effort to observe. The two kinds of seniority correlate sometimes and not at all other times, and when a team defaults to the easy one, its most capable people get treated the same as its longest-serving ones. Those are not always the same group of people.

What fitting in actually asks for

There’s a version of “fit” that means you communicate well and don’t create unnecessary friction. That version is fine. There’s another version that means: go along with however the team already works, and don’t make anyone rethink a decision they’ve already made. That version is what erodes a senior hire’s reason for being there.

Nobody takes a senior role to execute someone else’s plan without comment. They take it because they think their judgment is good enough to change what gets built, not just how it gets built. When that stops being true, the job becomes indistinguishable from a junior one with a higher salary attached. The person doesn’t get less capable. The role just stops asking anything of their capability.

What actually has to change

On the individual side, waiting to be noticed doesn’t work. If your input on a specific kind of decision has gone quiet, name the decision and ask for a seat at it directly, rather than hoping someone remembers you’re qualified. Treat the answer as information about the org, not a verdict on you. If a lead says no, that tells you something true about how the team is run. It doesn’t tell you anything true about your judgment. Set a real timeline, not an open-ended one, for whether that answer changes. A quarter, not “eventually.”

On the company side, the fix starts with defining seniority by track record instead of years in the seat, and writing that definition down somewhere people can point to it. It continues with checking who actually gets consulted on important calls. If it’s the same two or three names every time, regardless of who has the most relevant judgment for that specific decision, that’s worth noticing before it hardens into policy. And it means asking a harder question honestly: has “keep the team running smoothly” become a justification for routing decisions around the people who’d complicate them with a better answer. Smooth is not the same as right, and a team that optimizes for the first at the expense of the second will keep its most experienced people quiet right up until they leave.