The term "quiet hiring" was coined by Gartner's HR research team, describing organizations filling skill gaps by expanding existing employees' responsibilities instead of hiring externally — often without a corresponding change in title or pay. The framing companies use is invariably positive: "internal mobility," "stretch assignment," "skill development." What that framing often obscures, in practice, is a simpler transaction: doing meaningfully more work for the same salary, with a vague promise of future recognition standing in for an actual raise.
I don't think quiet hiring is inherently exploitative — genuine stretch assignments, real cross-training, and legitimate internal mobility all exist and can benefit both sides. But the label gets applied to a wide range of situations, and the ethical difference between the good version and the bad version comes down to a small number of concrete things, not to the label itself.
What Actually Separates the Ethical Version From the Exploitative One
The test I'd apply is whether three things are present: transparency, compensation, and consent. Transparent quiet hiring means the company is honest about what's happening and why — "we need you to cover this gap while we figure out headcount" is a very different conversation than responsibilities quietly accumulating with no acknowledgment at all. Compensation means there's an actual conversation about pay or title within a reasonable window, not an indefinitely deferred promise. And consent means the employee had a real option to decline or negotiate, rather than the expansion simply becoming the new expectation with no discussion.
Where all three are present — the company communicates clearly, discusses compensation within a defined timeframe, and gives the employee genuine input — quiet hiring can be a legitimate form of internal development. Where none of them are present, it's a cost-avoidance strategy wearing a growth narrative, and the person absorbing the extra work is providing free value the company would otherwise have had to pay a new hire's salary and recruiting costs to get. If the answer to any of the three is genuinely no, I'd treat that as being used rather than developed, regardless of how the conversation with your manager was framed.
Recognizing the Pattern in Your Own Situation
A few concrete situations are worth naming specifically because they show up so often. Covering a vacant position indefinitely after a colleague leaves or is laid off, with no discussion of additional pay, is quiet hiring in its rawest form — you're doing two jobs for one salary with no end date attached. Absorbing a manager's reporting duties after their role is eliminated, without a title change, is a version of the same thing dressed up as trust. Doing senior-level work under a junior title, for months or years, with vague promises about "when the budget allows" is the clearest sign that the compensation half of the equation isn't being honored. Contrast that with genuinely time-limited emergency coverage during a real crisis, or a structured cross-training rotation with defined boundaries — those can be legitimate, especially if there's a real skill-building component and an actual end date rather than an assignment that quietly becomes permanent.
What I'd Actually Do About It
Document what's changed, concretely — the responsibilities that weren't part of your original role, roughly how many hours a week they take, and what you've delivered because of them. That's not paranoia; it's the material you need for an honest conversation, because "I feel like I'm doing more" is much weaker than "here's specifically what's changed since my role was defined." Then have the direct conversation rather than waiting for the company to initiate it — something like "I'd like to talk about how my role has evolved and make sure we're aligned on compensation for it" opens the door without being confrontational. If the response is genuine engagement — a real conversation about a timeline, a raise, or a title change — that's a reasonable sign the situation is more development than exploitation. If the response is indefinite deferral with no specific commitment, that tells you something too.
It's also worth asking what you'd accept if money genuinely isn't available right now: a defined end date on the expanded scope, a formal title change even without an immediate pay bump, or a clear commitment to revisit the conversation on a specific date rather than "at some point." Vague promises with no timeline are the clearest tell that the company would rather you keep doing the work than actually resolve the ambiguity.
For Anyone Managing People Through This
If you're the one asking someone to take on more, the obligation runs the other way: say clearly what's changing and why, have the compensation conversation proactively rather than waiting to be asked, and set an actual timeline — 90 days is a reasonable outer bound — for revisiting title or pay rather than leaving it open-ended. Removing or redistributing some of the person's existing workload matters as much as the new responsibilities you're adding; quiet hiring done badly is pure addition with nothing taken off the plate, which is a fast route to burnout regardless of how meaningful the new work is. And if the arrangement was framed as temporary, treat it as temporary — either formalize it into the role it's actually become, or return the person to their original scope. Leaving someone in extended limbo, doing expanded work under an unchanged title indefinitely, is the single most common way a reasonable short-term ask curdles into something closer to exploitation.
The underlying dynamic isn't new — asking existing employees to absorb more has always been cheaper than hiring, and companies have always been tempted by that math during periods of cost pressure. What's changed is mostly the vocabulary companies use to describe it. The vocabulary doesn't matter much. What matters is whether the person doing the extra work actually gets acknowledged and compensated for it, on a timeline they can rely on, rather than indefinitely.