How Vague Job Descriptions Lead to Clear Burnout

When I first read my job description, I remember thinking it sounded reasonable. The language was broad, but not alarming. Phrases like “supporting cross-functional efforts,” “contributing where needed,” and “wearing multiple hats” felt modern, even generous. It suggested trust. Autonomy. Room to grow.

I didn’t interpret the vagueness as a warning. I interpreted it as freedom.

In the early days, that openness felt energizing. I could step into different areas. I could help shape how the work actually looked in practice. There wasn’t a rigid box, and that made me feel useful — like my judgment mattered.

But over time, something shifted. The absence of clear boundaries stopped feeling like freedom and started feeling like exposure. The job description didn’t evolve, but the expectations did. Slowly, quietly, without a clear moment where anyone said, “This is now part of your role.”

I began to notice how often I was filling gaps — not because they were assigned to me explicitly, but because someone had to do them and my role was flexible enough to absorb them. That pattern mirrors what I described in what happens when you’re always filling gaps no one acknowledges. The work expands, but the recognition doesn’t.

The problem with a vague job description isn’t confusion at the start. It’s accumulation over time. Each new responsibility feels small in isolation. Each one makes sense when it arrives. But because there’s no clear definition of what *isn’t* part of the job, nothing ever feels out of scope.

I found myself constantly asking internal questions that never had clear answers. Is this mine to handle? Should I be doing this, or just helping? Am I overstepping, or is this expected? And because clarity wasn’t built into the role, the safest option always felt like doing the thing anyway.

That internal hesitation became a constant background process. I wasn’t just doing the work — I was continuously evaluating whether the work belonged to me. And that cognitive load added up in ways I didn’t recognize right away.

There’s something uniquely draining about never knowing when you’ve done enough. Without clear role boundaries, completion becomes subjective. You can finish a task, but the job itself never feels finished. There’s always another loose end that technically falls within the wide perimeter of “other duties as assigned.”

At first, I told myself this was just part of being adaptable. That flexibility was a strength. That ambiguity meant opportunity. But over time, the lack of definition stopped feeling like trust and started feeling like quiet avoidance — avoidance of making decisions about ownership, responsibility, and limits.

What made this especially exhausting was how invisible the strain was. From the outside, I looked capable. Engaged. Useful. I was getting things done, responding quickly, stepping in where needed. But internally, I was constantly recalibrating — trying to figure out where the job ended and where I began.

Because the expectations weren’t explicit, it was hard to push back without sounding uncooperative. There was no document to point to, no defined scope to reference. Saying no felt less like enforcing a boundary and more like refusing to help.

This blurred the line between responsibility and overextension. I wasn’t being overworked in an obvious way. I was being *under-defined*. And that lack of definition required me to supply the structure myself — emotionally, cognitively, and logistically.

I noticed how often my energy went not into the work itself, but into managing uncertainty around it. Anticipating needs. Preempting gaps. Making judgment calls that no one had officially assigned me the authority to make, but that someone would have to live with anyway.

Over time, this turned into a kind of low-level burnout that didn’t announce itself loudly. It showed up as constant vigilance. As difficulty relaxing. As the feeling that I was always slightly behind, even when I was working hard.

The clarity never came because the system didn’t require it to. As long as the work got done, the ambiguity remained intact. And because I was capable of navigating that ambiguity, it quietly became part of what I was relied on for — even though it was the very thing wearing me down.

What I eventually realized is that vague job descriptions don’t just create flexibility. They shift the burden of structure onto the person doing the work. And carrying that structure internally, day after day, is more draining than any clearly defined workload.

Burnout didn’t come from doing too much of one thing. It came from doing too many undefined things, all loosely connected by the idea that they were somehow mine to manage.

And that’s how vagueness turns into exhaustion — not suddenly, not dramatically, but steadily, as the role expands without ever being named.