Blog
The Job Nobody Was Hired For
Every repository has a second job: answering issues, landing updates, fixing the red build, finishing the pull request. Nobody is hired to do it, so it lands on your best engineer, late. Here's why that job needs an owner, and why the owner should be an agent.
Every software team has a job that isn’t on the org chart.
Nobody was hired to do it. It has no title and never comes up in planning. But it’s there every week: the issue nobody has answered, the dependency update that needs one small fix, the nightly build that’s been red since Tuesday, the pull request one review comment away from done.
Call it maintenance. It’s the job nobody was hired for, and it’s why repositories slowly get worse even when the team is shipping.
How a small thing becomes a big one
Follow one dependency update through a normal team.
On Monday, a bot opens a pull request to bump a library from 3.2 to 4.0. It’s a major version, so the build fails: two function names changed. The fix is twenty minutes of work.
Nobody picks it up. Not because the team is lazy. Everyone has a feature due, and this isn’t anyone’s feature. It sits.
Two weeks later, the library announces a security hole in 3.x. Now the update is a priority. Someone senior drops what they’re doing, reads three changelogs, fixes the call sites, untangles the conflicts that piled up and pushes it through. It takes an afternoon, plus the cost of switching away from their real work.
Nothing about that afternoon was hard. It was just late. Every piece of upkeep works this way: cheap on the day it shows up, more expensive every week after.
Why tools haven’t fixed it
We’ve had bots for this for years. Dependabot and Renovate open updates. Scanners file alerts. Templates sort issues.
They all do the same thing: they create work. They open the pull request, raise the alert, label the issue. Then they stop, and a person has to finish it.
That’s the gap. The hard part of maintenance was never noticing the work. It’s owning it until it’s done: making the build pass, answering the reviewer, resolving the conflict, merging. A tool that opens a pull request and walks away has handed you one more thing to babysit.
Give the job an owner
So we gave the job to an agent. The Repo Maintainer is an AI agent hired for exactly this, and its whole job is to finish things.
Play the same Monday again.
The bot opens the 4.0 update. The maintainer sees the build fail, reads the changelog, updates both call sites and the tests, and pushes. Our AI code reviewer checks the change and approves it. The maintainer merges before lunch. When the security fix ships two weeks later, it’s a one-line update that lands the same day. Nobody on the team ever hears about it.
That’s the whole idea. The work didn’t get easier. It got an owner, so it gets done while it’s still small.
The same goes for everything else on the list. A new issue gets checked against the code and answered in minutes, and if it’s a bug, it comes with a fix and a test. When main goes red at 2 AM, it’s green again by morning. A security alert gets checked against the advisory and patched. A contributor’s pull request that stalled for three weeks gets rebased, finished and merged, with the author credited.
An owner knows where its job ends
Owning a job also means knowing what isn’t yours.
The maintainer brings you the decisions only you can make: a feature that changes how your product works, a fix it couldn’t prove, a security report that shouldn’t be public. You choose how much it merges on its own, from “ask me every time” to “everything in scope.” And it never grades its own work. Every change goes through the code reviewer first, with checks passing and no open threads.
That’s what makes it safe to hand over the job, not just the tasks.
What you get back
The obvious win is time. Upkeep often costs a senior engineer a day a week, and that day comes back to building.
The bigger win is the repository itself. When upkeep happens the day it shows up, nothing piles up. No backlog to dread, no update too scary to merge, no red build everyone has learned to ignore. The codebase stays the way it was on its best day.
We run our own company this way. human0 is built, reviewed and maintained by AI agents. In the 30 days to October 6 we merged 177 pull requests, every one written by AI, and shipped on 29 days in a row.
Every team has the job nobody was hired for. Now you can hire for it.