How This Happens
Budget decisions at most companies happen in cycles — quarterly planning, annual headcount reviews. The business need, though, doesn't wait. A team loses a key person. A new initiative launches. A product scales faster than anticipated and suddenly there are three jobs to do and money for one hire.
What does a manager in that position do? They write the most comprehensive job description they can. They list every function they need covered. They tell themselves — and whoever approved the headcount — that they're looking for a "strategic generalist" or a "senior leader who can build and do." And they go to market hoping to find someone who will, through ambition or naivety or a genuine love of the work, cover the gap.
This isn't malice. It's institutional pressure creating a problem that gets transferred, invisibly, to a job candidate. The problem with invisible transfers is that you don't know you've accepted the debt until you're carrying it.
You're hired as a "Head of Marketing." Three months in, you're managing the CRM because there's no ops person. Six months in, you're owning the event budget because there's no events coordinator. A year in, you're burned out doing work that would require a five-person team, getting performance feedback from a manager who expected all five people's output from you alone.
The role wasn't dishonest. The job description covered all of this — if you read it carefully enough. The problem was what it omitted: that there was no one else.
The Signals to Look For
Budget-constrained job descriptions have patterns. None of these alone is decisive — but in combination, they're telling.
The seniority-to-scope mismatch
The title says "Director" or "Head of" but the responsibilities include tasks that are clearly individual contributor work — writing copy, managing ad platforms directly, pulling weekly reports. Senior roles that include tactical execution alongside strategic direction aren't automatically bad, but when the tactical list is long and there's no mention of team members, ask who else is doing this work. The answer is: you.
"Build and scale" language on small teams
"You'll have the opportunity to build the function from the ground up" sounds like empowerment. Sometimes it is. More often it means the function doesn't exist yet, there's no infrastructure, no tooling, no process, and no team — and you're expected to create all of that while also delivering the work the function is supposed to produce. Building takes time. Delivering takes time. Doing both simultaneously, alone, is where people get broken.
The responsibilities list has no coherent narrative
A role with a clear reason to exist has a coherent set of responsibilities. They connect. "Own the content calendar, manage the editorial team, and report on content performance" is a content marketing role. "Own the content calendar, manage the Salesforce instance, run the weekly analytics report, oversee the vendor relationships, and coordinate PR" is a compilation from four separate jobs. That's not a role description — it's a coverage plan.
No mention of team structure
Good job postings tell you who you'll work with, who reports to you, and what the team looks like. When there's complete silence on team structure — no "manage a team of," no "collaborate closely with the design team" — that silence is data. It often means the answer to "who else is on this team" is nobody.
Compensation that doesn't match the scope
When a salary range appears and it's materially below what the listed experience level commands in the market, the company has revealed something. They know this role is overscoped. They're hoping someone will undervalue themselves, be excited about the title, or accept the work in exchange for future promises. Pay attention when the scope of a posting and its compensation tell different stories.
"This role covers a lot of ground — can you walk me through the current team structure and where each of these responsibilities sits today?" If the answer is vague, deflecting, or involves the phrase "that's part of what you'd be building," you now know what you're walking into. Whether that's okay is your call — but make it with full information.
What This Means for Your Application
Overscoped roles aren't automatically wrong for everyone. If you're early in your career and want to accumulate experience fast, a scrappy role where you do everything can be genuinely valuable. If you're an operator who builds functions from scratch and has done it before, some of these postings are real. The question isn't whether to apply — it's whether you're going in with your eyes open.
If you do decide to apply, go in eyes open: negotiate clearly, document the scope in writing if you can, and set explicit expectations early about what success looks like and what isn't sustainable long-term. Knowing the budget problem exists puts you in a position to name it — and naming it is the difference between thriving in a difficult role and burning out in one.
If the signals are strong enough that you'd be walking into a structural problem the company hasn't solved and has no plan to solve — that's worth knowing before you spend three weeks in a hiring process that leads to a job that leads to a quiet exit nine months later.
The Bigger Point
Nobody writes a budget-problem job description out of malice. The hiring manager is usually under real pressure — headcount approved for one, need for four, deadline yesterday. The gap between what the company needs and what it can afford is genuine. It just gets closed, quietly, by whoever accepts the job.
Reading a posting critically isn't cynicism. It's the skill that separates people who end up in the right jobs from people who end up in the wrong ones. The language is there. The signals are there. You just have to know what you're looking at.