The squeeze is hitting the middle
The labor market is pinching in two directions at once. On one end, entry-level hiring has cooled fast: U.S. postings for junior roles are down by about a third compared with early 2023. On the other, companies have spent the last year taking a saw to their middle layers. In a 2025 survey of 15,000 professionals, roughly two in five said their employers had cut management layers over the previous 12 months.
That leaves a very specific group in the squeeze. Experienced individual contributors. Managers with a few seasons under their belt. Directors who know where the bodies are buried, or at least where the budget lives. They are the people who keep strategy from becoming a slide deck with nice fonts. They fix the process when it breaks, keep launches moving, and answer the awkward question of who is actually doing the work once the org chart gets flatter.
When companies remove layers, the work usually doesn’t disappear. It gets spread across the people still standing.
That redistribution is where the pain starts to feel personal. A team loses a coordinator, so the remaining manager now chases approvals and edits status updates. A director loses a deputy, so she takes on the work that used to get filtered before it hit her desk. A senior IC gets handed a slice of the job that used to belong to a junior hire who never got backfilled. The title stays put. The calendar fills up anyway.
This is where the labor market gets strange. Entry-level workers are finding fewer seats at the table just as mid-career employees are being asked to carry more of it. In tech news, the same pattern shows up in quieter ways too: leaner product teams, fewer layers between staff engineers and executives, and a lot more “can you just handle this” energy. AI policy debates often talk about jobs at the edges, but digital culture inside companies is changing in the middle, where judgment, memory, and coordination still matter and still take time.
The result is a large group of workers who are too experienced to be treated like rookies and too junior to have real power over the shape of the job. They get the extra tasks, the context switching, the late-night cleanup. What they usually don’t get is a cleaner title, more headcount, or money that matches the new scope.
That mismatch is the story here. The pressure is not landing on a single role so much as on the layer that was supposed to absorb friction. Once that layer thins out, the friction doesn’t vanish. It moves downhill, and the people in the middle are the ones left carrying it.
What actually changed in your job?
The easiest way to spot mid-career stagnation is to stop using your title as the reference point. Titles age badly. The work doesn’t.
Start with the role you actually had before the org got flatter, leaner, and more allergic to headcount. What did you own then? Maybe you wrote the first draft of plans, handled routine client questions, coordinated deadlines, prepped materials for your boss, or cleaned up the mess after meetings nobody needed in the first place. Whatever the version, name the core pieces without dressing them up. You’re not writing a performance review. You’re building a before-and-after map.
The weird part isn’t that your job changed. It’s that nobody sent a memo.
Once you have that baseline, sort today’s work into buckets. The simplest split is who used to do it and what now seems to live on your desk.
- Work that came from below: the junior associate who used to draft the deck, the coordinator who booked the calls, the analyst who pulled the numbers, the assistant who chased signatures. - Work that came from above: the decisions your old manager used to make, the approvals you now chase, the status reporting that once stopped at one layer higher. - Work that came from sideways: coordination with adjacent teams, follow-up across departments, and the little diplomatic tasks that never appeared in your job description but somehow became your job anyway. - Work that came from new systems or AI workflows: first-pass summaries, note cleanup, email drafts, basic research, scheduling, and the other chores a machine can now do well enough to make a human wonder why they were doing them at all.
That last bucket matters more than people admit. A lot of companies added AI policy faster than they rewrote responsibilities, which means the tools changed before the rules did. So a person who used to spend an afternoon on a report may now spend an afternoon checking a machine’s report, editing the machine’s notes, and explaining to three different people why the machine’s tone sounds like a cheerful tax form. Progress, apparently.
The goal here is not to build a resentment museum. It’s to find the seams in the role. Some tasks grew because the team got smaller. Others moved because your manager left and never got replaced. Some arrived through power and politics, the quiet sort that happen when no one wants a problem to fall into their lap. And some were simply handed to the nearest competent adult, which is a noble tradition in many companies.
Now mark the work where your judgment changes the outcome. That’s the good stuff. If you catch a bad decision before it spreads, if you spot a mismatch in priorities, if you know which client concern will explode later unless someone handles it now, circle it. If a task only needs your name on it because you know the context, keep it on the list. If it needs your judgment because the wrong call could slow a launch, annoy a customer, or waste a week of engineering time, that’s not busywork. That’s real responsibility.
Then be equally honest about the rest. Some tasks can be automated, especially the repetitive ones tied to lifestyle tech, dashboards, scheduling, and recurring reporting. Some can be delegated if there’s still a person around who can take them on. Some should be redesigned so they happen once instead of four times through a chain of approvals. A few can probably be dropped altogether, which tends to feel revolutionary right up until everyone notices nothing bad happened.
This is where the diagnosis becomes useful. You’re trying to separate visible work from inherited clutter. The point isn’t to prove you’re busy. It’s to show how your job has expanded without being renamed, which is how so many people drift into mid-career stagnation without ever making a dramatic decision about it.
If the reshuffle seems to track age as much as hierarchy, it’s worth knowing the lines companies are not supposed to cross. The EEOC’s age discrimination guidance explains the basics, and the International Labour Organization’s material on older workers and human resource policy gives a broader view of how employers can handle longer careers without quietly piling on the leftovers.
By the end of this pass, you should have a cleaner picture of what your role is now: the work that only you can do, the work that landed on you by accident, and the work that should be handed back, handed off, or deleted. That’s the map you need before you decide what stays.
Draw the line between busywork and leverage
By this point, the list of tasks has probably stopped looking like a job description and started looking like a swap meet. That’s where the real sorting begins. The goal isn’t to protect everything you’ve been handed. It’s to separate the work that needs your judgment from the work that only needs your calendar.
A useful test is simple: would this task get slower, riskier, or less effective if someone else did it? If the answer is yes, keep it. If the answer is no, or only no because nobody else has been trained to do it, that’s a different story. In a flatter company, especially one trimmed by organizational flattening, senior people often end up babysitting processes that could be handed off, automated, or killed off entirely. That’s how middle management gets buried under a pile of admin work and called “flexible.”
Keep the decisions that break things if they’re wrong. Lose the chores that only make you look busy.
Start with the work that prevents bad outcomes. That usually means final calls on trade-offs, approval on messy exceptions, conflict between teams, or the judgment needed when the data is incomplete and the stakes are real. If a missed detail could trigger a bad launch, a compliance problem, a customer mess, or a budget overrun, that task belongs on the keep pile. It doesn’t matter whether the task is glamorous. A lot of useful work isn’t. Somebody still has to notice when two plans conflict, when a deadline is fake, or when a cheerful dashboard is hiding a bad assumption.
There’s also the quieter category: the jobs that keep systems from breaking. Not heroic stuff. Just the boring, necessary judgment calls that stop small problems from turning into expensive ones. A manager who spots that three teams are about to duplicate the same project saves more money than the person who spent an hour polishing the slide deck about it. A director who kills a flawed plan before it reaches senior leadership saves everyone from a month of theater. That’s the sort of work that should stay on your plate.
For a useful outside check, the Brookings discussion of workers’ capacity to adapt to AI-driven job displacement makes a plain point that matters here: routine tasks are easier to shift than work that depends on context, judgment, and timing. That doesn’t mean AI magically clears your calendar. It does mean a lot of repetitive admin, status collection, and first-pass sorting has little reason to stay attached to a senior title.
Now for the other pile, the one that should make you mildly annoyed. Underline the low-value chores that have somehow followed you upward: scheduling meetings that could be booked by someone else, rewriting updates for people who could read the original notes, copying numbers between systems, sitting in review calls only to say “looks fine,” and producing status reports no one uses after Friday. Those tasks are not proof of leadership. They are often just evidence that the org has gotten lazy about who does what.
That matters even more when career advancement slows down. In a lot of companies, the path upward narrows before anyone says so out loud. A senior employee can wind up carrying junior work, manager work, and cleanup work at the same time. The title stays polished. The workload gets weird. And if you’re an older worker, the problem can become harder to separate from age bias. AARP’s workplace guide on age discrimination is a blunt reminder that people can get stuck doing support work long after they should have moved on to higher-value decisions. The same person who once shaped strategy can end up formatting the agenda for it.
The point of this section is to make your real job legible. If you keep everything, your role stays foggy. If you trim the accidental extras, the remaining work gets easier to describe, easier to defend, and harder for anyone to mistake for “just helping out.” That’s the line worth drawing before you try to explain your value in business terms.
Explain your value in business terms
Once you’ve stripped away the chores that crept into your day, the next move is translation. Managers don’t need a diary entry. They need a sentence they can repeat in a review, a budget meeting, or a promotion conversation: I do X so that Y happens. It sounds almost too plain, which is exactly why it works. Plain language survives contact with the person signing off on pay.
That frame forces you to stop describing motion and start describing outcomes. “I managed the launch” is mush. “I do the final launch review so that we ship on the promised date instead of sliding for three more weeks” gives the job shape. “I attended vendor calls” vanishes in a puff of calendar smoke. “I clear vendor issues before they hit the exec team so that decisions don’t stall” tells a manager what changed because you were there.
The same goes for verbs. “Helped” is the workplace equivalent of saying you almost did a thing. Swap it out. Say you reduced, shortened, prevented, recovered, or closed. If you cut launch delays from six a quarter to two, write that down. If you brought approval time from eight days to three, say it. If your work kept a forecast from going off the rails, name the before and after. A clean number beats a warm feeling every time.
A manager can’t reward effort they can’t measure. Give them the number, the before, and the after.
That advice gets even sharper when the org gets flatter and the job scope quietly grows. In a layered company, some of your work used to be buried under a few more people. In a leaner one, you may now be the person catching problems, making calls, and cleaning up the fallout after other people move on. If that’s true, your description shouldn’t read like a list of duties from 2022. It should read like the result of what you actually do now.
This is where business language earns its keep. “I run the weekly review” tells almost no one anything. “I do the weekly review so that product, sales, and support stop chasing three different answers for the same issue” tells a manager why the meeting exists. “I draft the briefing” is thin. “I do the briefing so that senior leaders decide in one meeting instead of sending the question back for another round” is usable. You’re not bragging. You’re making your work legible.
The shift matters more as AI at work starts to trim routine tasks. Brookings’ AI workforce policy framework treats that change as a job-design issue, which is about right. If software can handle the first pass, the human value often sits in the judgment after that: the call you make, the error you catch, the trade-off you explain, the deadline you save. Your wording should reflect that. Don’t say you “worked with AI.” Say what changed because you used it. Did draft time drop by half? Did review cycles shrink? Did the team ship with fewer corrections? That’s the part a manager can price.
There’s another reason to be this blunt: people who are trying to stay in, move up, or get back in after a rough stretch need proof, not vibes. An AARP release in February 2026 noted that many older Americans were heading back to work because costs had gotten heavier, which is a polite way of saying nobody gets to coast on good intentions for long. AARP’s report on older Americans returning to work sits in the same reality. Whether you’re angling for an employee promotion or just trying to justify the job you already have, outcome-first language does the heavy lifting.
So write the version that a manager can use without translation. “I do the monthly revenue review so that leadership spots misses before the quarter is toast.” “I do the release check so that we ship on time and spend less on cleanup.” “I do the escalation triage so that customers get answers in hours, not days.” That’s the material you bring into the next conversation about scope, support, and what should stay on your plate.
Renegotiate before the role swallows you
By the time you’ve mapped the work and put numbers on the outcomes, the next move is pretty plain: get it in front of your manager before the planning cycle or review season turns into a ceremonial shrug. Don’t wait until your calendar is already packed with the same old duties plus three new “quick asks” that somehow now belong to you. Bring the notes. Bring the examples. Bring the receipts, ideally in a form that doesn’t require anyone to squint.
If your job changed in practice, it has to be renegotiated in plain English, or it will keep expanding by accident.
That conversation works best when it’s specific. Say what shifted into your role over the past year. Name the pieces that used to live with a junior hire, a former manager, or another team entirely. If you used to write the first draft, chase the approvals, and then somehow clean up the mess after launch, say that out loud. If you’ve become the person who catches bad decisions before they spread, say that too. A manager can’t fix what they don’t see, and in a flattened company, invisible work tends to get treated like free samples.
Then make the ask. Move me toward the work that depends on judgment. Pull me away from low-value tasks that can be automated, delegated, or dropped. That wording matters. It tells the other side you’re not trying to dodge responsibility. You’re trying to use your time on the part of the job that only a senior person can do without causing a small riot in the spreadsheet.
This is also where workplace politics sneaks in, wearing a fake mustache. If you don’t name the scope shift yourself, someone else will define it for you, usually in the cheapest possible terms. So ask what recognition fits the current job, not the old one. That might mean more decision rights. It might mean a title that matches the scope. It might mean compensation that reflects the extra load. In some cases, it means getting visible with senior leaders so your work is attached to the business, not just to your inbox.
You’re not begging for a favor. You’re correcting the record. And in organizations that keep flattening out, the work that gets seen is the work that survives. Name it clearly, or it can disappear while everyone assumes somebody else is handling it.
