When Your Title Gets Bigger but Your Job Doesn’t

After nearly forever, you get a promotion, update your LinkedIn, and let yourself feel good about it. You worked hard for that title, and you’re ready to show it off. You’ve been here for a while and even though there were no additional responsibilities that came with it, you finally feel acknowledged for the hard work you’ve put in.

A year or so later when you start interviewing somewhere else, the title suddenly requires a footnote.

“Yes, I was a manager, but I didn’t have direct reports.”

“My title was director, although most of my work involved managing existing accounts.”

[insert third example]

Complicated answers make for complicated comprehension of your experience. And now, you’re trying to describe your experience while also correcting whatever the person across from you assumed when they read your resume.

A title that felt like progress at your company can become surprisingly difficult to translate outside of it.

The same title can describe very different jobs

A manager might supervise six employees. They might manage a client portfolio. They might be the only person responsible for a particular process, with absolutely no authority over anyone else’s work.

All three can involve real responsibility, but they aren’t evaluated in the same capacity by each employer. If a company is hiring someone to supervise a team, those candidates bring different experience to the conversation.

The confusion gets worse when people treat titles as a consistent ladder across employers. Coordinator, specialist, manager, director, etc. It looks organized enough on paper, but in practice, companies have very different ideas about what belongs on each rung.

A director at a small company may handle the day-to-day work themselves. Someone with a specialist title at a larger company may own a complicated program and influence decisions across multiple teams. You need more information before you can meaningfully compare them.

That context can get lost during a job search, especially when someone is reviewing applications quickly or working from a narrow idea of what a qualified candidate’s background should look like.

That’s how you end up explaining why you’re qualified for a role that sounds like a step down, or why a role with the same title would actually be a substantial increase in responsibility.

It’s frustrating to feel like your experience needs an interpreter.

How does this happen?

Sometimes a title reflects the company’s structure more than anything else. There may be one person in a department, so that person becomes the department manager. Elsewhere, the same work might sit within a larger team under a completely different title.

Titles can also become part of a promotion or a retention conversation. That recognition can matter to the employee, even when the change in responsibilities is smaller than the title suggests. Sometimes, a role evolves unevenly. You take on more work without getting more authority, or receive a title that describes where the company hopes the role will go.

You can appreciate the opportunity, and still discover later that other employers interpret it differently. Accepting the promotion wasn’t necessarily a mistake and you were making a decision within the company where you actually worked.

The problem is that title now requiring you to explain the whole job once you leave.

Give the reader something concrete

The advice here can sound like “focus on your impact,” which is easy enough to say. But what does someone reviewing your resume actually need to understand?

Start with the questions your title leaves unanswered.

If you managed accounts, how many? Were you responsible for renewals, new business, or both? Could you negotiate terms, or did those decisions go through someone else?

If you managed content, were you setting the direction or working from an existing plan? Did you choose the channels and control the budget? Were you writing and publishing everything yourself?

If you managed operations, what happened when something went wrong? Could you change the process, approve spending, or reassign work? Or were you coordinating the response and escalating decisions?

Those distinctions help explain what you’ve done and what experience you’d bring to another company.

They also give you a better way to talk about your work than opening every answer with “Well, my title was a little misleading.”

What that looks like on a resume

[change this bc i DO suggest changing the title when it makes sense in the market]

Ask more about the next title, too

When you’re considering another role, it’s reasonable to care about what it’s called. Titles can affect how your experience is understood, as this entire situation demonstrates.

Just spend some time asking what comes with it.

If the role is supposed to move you into people management, will you actually have direct reports? If you want more say in strategy, which decisions will you own? When the job description says you’ll “lead” something, does that mean setting the direction, coordinating everyone’s work, or being responsible when the deadline gets missed?

That last distinction is worth a conversation before you accept.

A better explanation of your experience won’t fix every hiring team’s assumptions. Some employers will still put too much weight on a title, and some opportunities will require experience you haven’t had the chance to build yet.

But you can make the work behind your title easier to understand. The next time an interviewer asks whether you managed people, you can answer directly and explain what you did own, without spending half the conversation apologizing for what your company called you.

I write about hiring, content creation, internet culture, and whatever else I can’t stop thinking about that week.

Subscribe to Said & Dunn to get new articles sent straight to your inbox. No algorithm required.