I could call myself CEO of CTRL+ALT+SURVIVE. Technically it’s true. I run six sites, make every decision, and answer to no one but the traffic numbers. But CEO implies a board, reports, and people executing a strategy I set from the top down. I don’t have any of that. I have a keyboard, a publishing schedule, and whatever gets done before the next deadline.
Compare that to Smallware Co., a small AI tools shop I started, building BYOK tools with local LLMs and vibe-coded workflows. I could call myself founder there too, and the title would carry more weight, not because founder sounds bigger than CEO, but because there’s something to check it against. RelayCard, a WordPress plugin I built under that umbrella, went through WordPress.org’s actual review process and came out the other side approved and live. That’s not a claim sitting on a resume. That’s a listing anyone can go verify right now. If you’ve ever looked at a job offer and wondered how do you know what job is right for you when the title alone doesn’t tell you enough, that difference, a title you can check against something real versus one you can’t, is the whole problem this post is about.
Job titles are the easiest thing to inflate and the hardest thing to verify from the outside. There’s no office to walk into, no team to watch in a meeting, nothing to check the claim against except the listing and whatever the interviewer tells you during a video call. That’s true for remote roles by default, and it’s just as true at small in-person companies where the org chart exists mostly on paper. Figuring out how do you know what job is right for you starts with figuring out whether the title in front of you describes something real or something written to look impressive on a website.
Why a Hollow Title Actually Costs You
There’s an immediate cost that hits before any resume damage does. Companies that hand out inflated titles often use the title itself as justification for more responsibility without more pay, since a manager title implies you should be taking on manager-level work regardless of what the title actually came with. You end up doing the job of someone above your actual level, for the pay of someone at it, because the title convinced you the extra work was just what the role required. Meanwhile the hiring bar for that same role was often set low precisely because the company wanted the title to look good on a listing more than it needed someone who could actually run a team. So you’re functionally rank and file, doing rank and file work, but carrying a manager title that raises expectations without raising what’s in your paycheck or what you were actually equipped to handle going in.
The longer-term cost shows up later. You end up doing work with no real scope to match the title, no mentorship structure because there’s no one senior enough to mentor you, and no team to actually lead even though the offer letter implied otherwise. The work itself might be fine. The mismatch between what you were told and what you’re actually doing is what wears people down first.
Then that title shows up on your resume, and the next interviewer who actually knows what a director or head of department does at a functioning company starts asking questions you can’t answer. What did your team look like. What was your budget. Who did you manage, and through what process. The title that got you hired the first time becomes the thing that gets you caught out the second time, in a room where the stakes are higher and the interviewer has less patience for a vague answer.
There’s a version of this I’ve seen more than once. Someone gets made director or head of a department at a company with three, four, five people total. The title exists because it makes the company look more established on a website or a pitch deck, not because there’s a team, a budget, or actual decisions attached to it. Anyone can claim a title. Anyone can say they’re a director. I could say I’m the head of QA at a company I’ve never worked at and the words would be exactly as true as if I’d built the actual experience. The difference is whether you can run a team through a hard call under pressure, and that’s something you only find out by doing it, usually the slow and expensive way.
Why the Usual Advice Doesn’t Catch This
Most career advice tells you to check culture fit, ask about growth potential, watch for red flags in the interviewer’s body language. None of that flags a hollow title, because a hollow title isn’t a culture problem, it’s a structural one that sits underneath the culture conversation entirely. Job boards don’t require a company to disclose headcount next to the role. Nobody’s writing “by the way, this director title has a department of exactly one person” anywhere in the listing.
So the standard checklist for how do you know what job is right for you skips the one question that would actually catch this pattern. You have to go looking for it yourself, and most people don’t know what to look for until they’re already three months into a job that isn’t what it said it was on paper. If you’ve had a rough experience with a company that talked a bigger game than it delivered on, this is usually the mechanism underneath it.
Titles Lie in Both Directions
This isn’t just about companies handing out inflated titles to make a small operation look bigger. It’s part of why I don’t usually apply for head or director level roles myself, even when I could probably talk my way into one. A title like that raises the bar on what’s actually expected of you, and there are a few reasons I’d rather go for lead or senior instead.
My experience doesn’t always match what a company means when it says director. Different companies attach wildly different expectations to the same word, and without knowing their specific bar, applying for the title alone is a guess. There’s also the more honest version of it: I might not have the specific skills a given director role actually needs, even if I’ve led teams before. Leading a QA department is not the same skill set as leading a marketing department, and pretending otherwise is exactly the kind of title-chasing this whole post is about.
Recruitment boards make this worse, not better. You’ll see junior listings asking for four or five years of experience, which isn’t junior by any real definition, it’s a senior role with a junior paycheck attached. You’ll see entry level postings with a cap on education or experience that quietly filters out anyone actually new to the field, while still using the word entry to keep the posted salary low. The title on the listing and the actual bar to get hired are two different things, and companies use that gap on purpose.
Degree requirements follow the same inflation pattern, and it’s easier to see once you compare job markets side by side. US listings mostly leave degree requirements off unless the role is genuinely specialized, a licensed field, engineering, law, something where the credential maps to an actual legal or technical requirement. Other job markets aren’t as selective about it, and the reason isn’t that the work demands more. It’s supply and demand working against the applicant. Where there are far more graduates than there are jobs to absorb them, a degree becomes a cheap filter for narrowing a stack of applicants, not a reflection of what the role actually needs. It’s common to see a college degree listed as a requirement for rank and file work that has nothing to do with a classroom, and even messenger or courier roles sometimes list a high school diploma as a minimum, not because the job demands it, but because the market can afford to ask for it and still fill the position. None of that credential maps to the actual skill the job needs. It’s a filtering mechanism dressed up as a qualification, the same way an inflated title is a status mechanism dressed up as a role. Both do the same job: make the listing look more selective than the position actually is, for reasons that have nothing to do with what the work requires.
Then there’s the appeal side of it. People get pulled toward inflated titles for reasons that have nothing to do with the actual job, the pay bump that sometimes comes with a bigger-sounding title, the sense of power it implies, how it sounds when you’re telling someone what you do. None of that is really about the role. It’s about what the title does for you outside of work, which is a different thing entirely from whether you can actually do the job.
Titles also get diluted on the way in, not just inflated on the way out. Account manager sounds like management. Most of the time it means managing an account, not managing people. Project manager is closer, since you are managing a team, but only for the scope and duration of that project. Once it wraps, that authority doesn’t carry over to the next one automatically, and it never extends past the project’s boundaries in the first place. The word management is doing more work in the title than the actual scope backs up in both cases, just in different ways. Even LinkedIn plays into this, since anyone can add a title to their profile with nothing behind it, and it reads exactly the same to a recruiter scanning fast as a title someone actually earned.
None of this means every senior-sounding title is fake, or that you should distrust every listing. It means the title alone was never reliable information, in either direction, and the same test applies whether you’re the one being offered the title or the one deciding whether to apply for it in the first place.
The Actual Test
Here’s the test that actually works: does the title imply people, budget, or decisions you’re accountable for. If it does, and none of those three things exist, the title is decoration. That’s the whole mechanism, and it holds regardless of industry, company size, or whether the role is remote or in person.
There’s a simpler version of this test too: can the title be checked against anything outside the person’s own claim. RelayCard being live on WordPress.org is checkable. Anyone can search it and see it’s real, approved, and shipped. A director title at a company with no public trace of a team, a product, or a decision that title would’ve made isn’t checkable at all, which is exactly why it’s worth asking for specifics before you accept it instead of after.
Before you accept anything with an impressive title attached, ask direct questions and pay close attention to how they’re answered, not just what the words say. How many people are on the team you’d be joining or leading, specifically, not roughly. Who do you report to, and who reports to you, not “eventually” or “as we grow” but right now, on day one. What decisions do you actually get to make without someone else signing off first. A legitimate offer answers these clearly and quickly, usually without hesitation, because the answer is just a fact about how the company is structured.
A title that’s mostly for show gets you a different kind of answer. A vague response, a pivot into talking about “the vision” instead of the structure, or a promise that the team is coming soon, which usually means it isn’t coming at all. How the interview itself is conducted tends to mirror this pattern closely. A company that’s vague about the role during the interview tends to stay vague about it after you’ve started, and that’s worth watching for before you ever get to the offer stage.
That instinct works both ways too. If the title sounds too good for what the company actually is, a director role at a five-person shop, a VP title at a startup with no funding round to speak of, that gut reaction is usually right. Titles that outpace the size and stage of the company aren’t a sign you got lucky. They’re a sign the company needed the title to do work the actual role and pay can’t.
None of this means small companies are automatically suspect, or that you should only trust roles with big headcounts attached to them. Plenty of small operations are exactly what they say they are, run by people who are upfront about scope and honest about what the role actually involves. A three-person startup can have a completely legitimate marketing lead role with real scope and real accountability behind it. The problem is specifically when the title is written to sound bigger than the job actually is, and that pattern shows up at companies of every size, not just the small ones.
If you’re evaluating a remote offer specifically, this gets harder to check, not easier, since you can’t walk the floor and see who’s actually sitting at the desks. That’s exactly why the direct questions matter more for remote roles than for in-person ones, since a video call gives you far less to observe than a physical office does.
Run the title through the test before you accept anything, not after you’ve already given notice at your last job. It’s a five-minute conversation up front that saves you a resume line you’ll spend an hour explaining away later, in an interview where the stakes are a lot higher than they are right now.
