I spent years assuming that a job title was a straightforward indicator of where someone sat in an organization’s hierarchy. A senior manager was senior. A director had broader scope than a coordinator. The title told you something real about the person’s experience, authority, and what they could actually do. That assumption has become increasingly unreliable, and I’ve watched this erosion happen across dozens of organizations and industries.
The shift didn’t happen overnight, but it’s now pervasive enough that I treat job titles with genuine skepticism when I’m trying to understand someone’s actual role or experience level. I’ve met people with “senior” in their title who were newer to their field than someone with “associate” in theirs. I’ve seen “director” positions that carried less decision-making power than individual contributor roles in other companies. The title has become decoupled from the substance it once represented.
This matters because titles still carry weight in how we perceive people’s competence and seniority, even when they shouldn’t. Hiring managers, peers, and even the people holding the titles themselves often treat them as if they still mean something consistent across organizations. They don’t. And that gap between perception and reality creates friction in how people learn from one another, how they’re evaluated, and how they understand their own career progression.
Why titles became inflated and fragmented
The primary driver has been compensation and retention strategy. As organizations faced pressure to keep salaries competitive without fundamentally restructuring pay bands, they began handing out fancier titles. A person doing the same work as they did five years ago might get “senior” added to their title as a substitute for a raise. This happened across tech, finance, consulting, and professional services first, but it spread everywhere.
At the same time, organizations started creating entirely new titles to describe roles that didn’t fit traditional hierarchies. “Growth lead,” “impact manager,” “technical strategist,” “operations partner” – these titles attempt to describe hybrid responsibilities that don’t map cleanly onto old structures. A company might have three people doing similar work but with three different titles because they came from different departments or were hired at different times.
Remote work and distributed teams accelerated this fragmentation. When you can’t see someone’s desk location or their physical proximity to leadership, titles become even more important as signals. But they also become less standardized, because each company’s remote structure is slightly different. A “senior engineer” at one company might be managing people; at another, they’re an individual contributor. Neither is wrong, but the title doesn’t tell you which.
The gap between title and actual responsibility
I’ve watched people get promoted into a new title without any change in their actual day-to-day work. The title change was meant to reflect market rates or to keep them engaged, but their responsibilities, authority, and scope stayed the same. Conversely, I’ve seen people take on vastly expanded roles without a title change, because the organization was waiting for budget approval or restructuring.
This creates real confusion when someone new joins a team. You can’t look at titles and understand the actual reporting structure or decision-making authority. You have to ask questions. You have to observe. You have to learn through experience what the title actually means in that specific context. That’s inefficient, and it means people often misread the room early on.
It also affects how people learn from each other. If you’re trying to understand how someone at a more senior level approaches a problem, you need to know whether their “senior” title reflects deeper expertise, broader scope, people management, or just longer tenure. Without that clarity, you might be learning from someone whose experience is narrower than their title suggests, or missing insights from someone whose title undersells their actual depth.
What has actually replaced titles as a signal
In organizations where I’ve seen this most clearly, people have started using other markers to understand seniority and scope. They look at who reports to whom. They pay attention to who gets invited to certain meetings. They notice who makes final decisions on key questions. These are more reliable than titles, but they’re also harder to see quickly, especially in large or distributed organizations.
Budget ownership has become a clearer signal than title in many places. If someone controls budget for a function or project, that tells you something real about their scope and authority. Similarly, project scope and complexity matter more than the title on the business card. Someone managing a multi-year, cross-functional initiative has different seniority than someone managing a single project, regardless of what their title says.
In some organizations, I’ve noticed people defaulting to educational background or years of experience as proxies for seniority when titles fail them. That’s not ideal either – experience doesn’t always correlate with good judgment or current capability – but it’s at least a different kind of signal. Some companies have started being more explicit about career levels in internal systems, using numerical levels or bands that exist behind the scenes, separate from the public-facing title.
How this affects learning and collaboration
When titles lose their meaning, it becomes harder for people to calibrate what they should be learning from whom. A junior person might spend time trying to learn strategic thinking from someone with a senior title who actually specializes in execution. Or they might overlook someone with a modest title who has exactly the expertise they need. The friction increases because the shorthand stops working.
It also affects how people position themselves when they’re trying to learn. If you can’t trust titles to tell you who has deep expertise in something, you have to ask more questions, observe more carefully, or take more time to figure out who to learn from. That’s not necessarily bad – it can lead to deeper relationships and more honest conversations about capability – but it requires more intentionality.
For people teaching or mentoring others, the loss of clear titles can actually be useful. It forces you to explain what you actually do and what you actually know, rather than relying on your title to do that work for you. But it also means you can’t assume people understand your scope or expertise based on your title alone. You have to be more explicit about it.
The practical reality I’ve observed is that organizations with the clearest internal communication about roles and scope – where people actually understand what different titles mean in that specific context – tend to have less confusion and faster onboarding. But that clarity has to be intentional. It doesn’t come from the titles themselves anymore. It comes from how the organization documents and discusses what people actually do.
