The Job You're Doing That Nobody Hired You For
Most people carry a second, undocumented job: the onboarding, the note-taking, the process nobody owns. Here's how it accretes, how to tell which parts are worth keeping, and the exact conversation for handing back the rest.
By JobPost Team · Sep 17, 2026 · 4 min read
Somewhere in your week is a block of work nobody hired you for. You didn't apply for it, it isn't in your job description, and if you stopped doing it Monday, three people would notice by Wednesday.
How It Gets Assigned Without Being Assigned
It never arrives as an assignment. It arrives as a favour.
A new hire asks you a question because you sit nearby. You answer it well. You answer the next four. Eight months later you are the team's onboarding program, and the actual onboarding document is a Confluence page last edited in 2022 by someone who left.
The mechanism is always the same: a one-time ask, competence, then default ownership. Nobody decided you should own it. The org simply discovered it was cheaper to let you keep doing it than to staff it.
What it looks like in practice:
- The developer who unblocks the release every time the pipeline breaks, on a team with no ops role.
- The person who quietly rewrites the account manager's email before it reaches the client.
- The de facto project manager on a team that lost its project manager and never backfilled.
- The one who takes notes, because the alternative is that nobody remembers what was decided.
- The bilingual employee who ends up handling every French-language call, every French-language document, and every French-language complaint — a job that appears in nobody's title and in everybody's expectations.
None of this is sabotage. It is drift. And drift is only a problem when it stops being counted.
Work That Compounds Versus Work That Disappears
Tanya Reilly's talk *Being Glue* named the category well: the work that holds a team together and shows up on no one's roadmap. But not all of it is equally invisible. Two tests separate the parts worth keeping from the parts eating your week.
Test one: can it be stated as an outcome with your name on it? "I redesigned onboarding and cut ramp time for the last four hires" survives a promotion conversation. "I answer a lot of questions" does not. The first is a project. The second is weather.
Test two: is it visible when done, or only when undone? Nobody notices a release that ships cleanly. Everybody notices the one that doesn't. Work that is only legible in its absence generates no credit and unlimited blame, which is the worst trade available in any workplace.
Glue work that fails both tests is not a stepping stone. It is a tax you volunteered for.
Making It Countable
Before you raise it with anyone, write it down. Four weeks, one running list: what you did that falls outside your role, and roughly how long it took. Not a grievance file — an inventory. Most people are surprised by the total, and the number is the entire argument.
Then sort each item into one of three piles.
Formalize it. If the work matters and you want it, get it written into your objectives, your job description, or your title. The ask is narrow: "I've been running the release process for seven months. I'd like it listed as one of my goals this cycle, since it's about a day a week." You are not asking permission to do the work. You are asking for it to be counted.
Hand it back. This is the part people skip, because they think handing something back means dropping it. It doesn't. It means documenting it, naming a successor, picking a date, and telling your manager before you tell the team. A clean handoff reads as ownership. An abrupt stop reads as sulking.
Keep it, deliberately. Some unassigned work is the best leverage you have — it puts you in rooms your title doesn't. Keep it on purpose, keep the receipts, and know what you're trading for it.
The conversation that works best gives your manager a choice instead of a complaint: *"Here are six things I do that aren't in my role. I'd like to keep two. Which two matter most to you?"* Almost every manager will answer that question honestly, because you've made it a prioritization problem, which is a thing they know how to do.
If You're The One Doing The Assigning
Managers rarely know the size of this. Ask directly, in one-on-ones, in these words: *what do you spend time on that isn't in your job description?* Then look at the pattern of who answers with the longest list. It is usually the most agreeable person on the team, or the most junior, or the only one who can do the thing in French, or the only one who has been there long enough to remember why the system works that way.
Three fixes, none of them expensive:
- Give the work an owner on paper, with time budgeted for it.
- Put it in the review, with the same specificity you'd use for shipped work.
- Rotate the parts that don't need expertise — notes, standup facilitation, the on-call inbox.
The cost of leaving it undocumented isn't unfairness. It's that the person carrying it eventually leaves, and takes an unwritten process with them. Then you discover, in the third week of the gap, exactly what they were doing and exactly how much of it there was.