Why Juggling Five Government Jobs Exposes a Broken System Rather Than a Villain

Why Juggling Five Government Jobs Exposes a Broken System Rather Than a Villain

Someone holds five government jobs at once. The headline drops. Cue the outrage.

We love a tidy morality play. A rogue bureaucrat double-dipping, triple-dipping, quintuple-dipping on the taxpayer dime. A confession of "mistakes." A neat little villain to blame for bloated payrolls and slipping deadlines. If you found value in this article, you should check out: this related article.

That story is lazy. Worse, it is backward.

If one civil servant can quietly stack five government jobs without setting off alarms for months or years, the scandal is not merely personal greed. The scandal is institutional design. When a system can be gamed by a single person working from a laptop, the real question is not why he tried it. The real question is why five separate hiring managers, HR departments, and supervisors failed to notice. For another angle on this development, refer to the recent coverage from Financial Times.

The Lazy Consensus Around Overemployment

Conventional commentary treats overemployment in the public sector like a simple math problem with a villain at the center. One paycheck equals forty hours of work. Five paychecks must equal two hundred hours. Since nobody has two hundred hours in a week, the math proves fraud, neglect, or both.

That logic sounds airtight until you look at how modern knowledge work actually operates—especially inside sprawling bureaucracies.

In public administration, output is rarely measured in real-time, hour-by-hour production. It is measured in deliverables, committee sign-offs, procurement packets, policy drafts, compliance checks, and scheduled meetings. Many of those tasks move at glacial speed. Waiting three weeks for legal review, budget sign-off, or inter-agency feedback is standard operating procedure.

I have watched organizations burn millions of dollars on enterprise software, management consultants, and compliance audits while ignoring the most obvious diagnostic tool in front of them: workflow friction. When a process takes ten days because six people have to touch a document that requires forty minutes of actual thought, idle capacity builds up inside the gaps.

Ambitious, opportunistic workers spot those gaps immediately. In the private sector, tech workers call it "overemployment" and turn it into a badge of anti-corporate rebellion. In the public sector, when someone gets caught stacking civil service roles, the reaction shifts from smug fascination to righteous fury.

Defining the Real Terms of the Debate

Before we throw stones, let us get the vocabulary straight.

Moonlighting is holding a second job outside primary working hours, often disclosed and sometimes regulated by conflict-of-interest rules. Time theft occurs when an employee bills for hours not spent working on assigned duties. Overemployment is holding multiple salaried roles simultaneously during overlapping business hours, stretching finite cognitive bandwidth across competing obligations.

Conflating all three into a single moral failing obscures what actually happened. A person can commit time theft at a single job while sitting in a cubicle staring at the wall. Conversely, someone holding multiple roles might finish actual deliverables faster than a peer who spends six hours a day in status meetings.

Neither excuses violating public trust or ignoring ethics disclosures. Conflict-of-interest rules exist for a reason, and public funds carry a higher standard of accountability than private venture capital. Still, calling a structural failure a purely moral anomaly lets leadership off the hook.

How Five Jobs Slip Through the Cracks

Imagine a scenario where a mid-level analyst lands a remote or hybrid public-sector role. Onboarding takes three weeks because IT takes ten days to provision equipment and HR takes another week to verify credentials. Once logged in, expectations for the first month are vague. Weekly check-ins last thirty minutes.

Now multiply that friction across four other agencies, municipalities, or departments.

Why does that happen? Three mechanics do the heavy lifting:

  1. Siloed HR and payroll systems. Government is not one monolithic employer. Federal, state, county, and municipal agencies often operate on separate payroll ledgers, fragmented identity systems, and decentralized hiring pipelines. A background check or W-4 in one jurisdiction does not automatically wave a red flag in another.
  2. Input-theater over output clarity. Many bureaucracies reward presence, responsiveness in chat, and attendance over clearly defined milestones. If a worker answers emails promptly and shows up to recurring calls, managers assume productivity is humming along.
  3. Fear of confrontation. Addressing suspected underperformance in civil service requires documentation, HR alignment, and patience. Many supervisors find it easier to route work around a slow employee than to confront the bottleneck directly.

Economists and organizational theorists have studied variations of this dynamic for decades. Herbert Simon wrote about bounded rationality and how organizations design routines around incomplete information. Max Weber analyzed how rules and hierarchy create predictability, yet can also produce rigid channels where nobody owns the whole picture. When oversight is fragmented across layers of approval, accountability diffuses. Everyone assumes someone else is watching the store.

What People Actually Want to Know

When a story like this breaks, search bars fill up with predictable questions. Most of them ask the wrong thing.

Is it illegal to hold multiple government jobs?

That is the wrong first question. The sharper question is: which rules were broken, and how were they enforced?

Holding two or more public jobs is not automatically a crime in every jurisdiction, especially part-time, seasonal, or non-overlapping roles. Problems start when an employee falsifies timecards, conceals conflicts of interest, violates agency dual-employment policies, or collects pay for work not performed. Criminal fraud statutes, ethics codes, and civil service rules draw distinct lines. Treating every multi-job case as an identical felony muddies legal analysis; treating it as a harmless loophole ignores real fiduciary breaches.

How does someone pull off juggling five jobs without getting caught?

Brutally honest answer: by exploiting low-visibility work, slow feedback loops, and managers who do not measure real output.

If a role requires daily physical presence, real-time customer service, or immediate operational triage, holding four other jobs alongside it collapses fast. If a role involves asynchronous drafting, data cleanup, or waiting on external approvals, a fast worker can batch tasks into narrow windows. The less visible the work product, the easier it is to hide split attention.

Why doesn't HR catch this immediately?

Because HR departments are typically built for compliance and processing, not continuous behavioral surveillance. Once an employee passes onboarding, routine cross-checking across unrelated agencies is rarely automated. Add remote flexibility, backlogged audits, and thin management spans of control, and a clever operator can stay under radar longer than critics want to admit.

The Uncomfortable Truth About Public Productivity

Here is the part that makes both sides squirm.

If one person can juggle five government jobs for a stretch, two possibilities exist at the same time. Either some or all of those roles were under-delivered, or the baseline workload expectations in those roles were shockingly low.

Often, both are true.

Critics on the right see proof of government bloat—proof that taxpayers are funding phantom hours and featherbedded positions. Defenders on the left often rush to frame the story as an isolated bad actor who abused remote work or public trust.

Both narratives miss the deeper operational rot.

Public servants are not lazy by nature. Many teachers, transit workers, inspectors, engineers, and caseworkers carry crushing caseloads with outdated tools and stagnant pay. Yet inside the same broader public sector, certain desk and coordination roles suffer from severe ambiguity. Nobody defines what "good" looks like in measurable terms. Meetings multiply to compensate for unclear authority. Weeks pass while approvals inch forward.

When work lacks clear definitions and real accountability, two things happen:

  • High-integrity employees burn out trying to push boulders uphill through red tape.
  • Low-integrity or hyper-opportunistic employees realize they can collect multiple paychecks while doing the bare minimum required to stay off the radar.

That is a terrible bargain for the public. Worse, it poisons morale for honest civil servants who actually care about the mission.

Where My Contrarian Argument Has Limits

I am arguing that institutional design explains more of this mess than individual villainy alone. Fair enough. Now let us test the weak spots in that view.

First, structural flaws do not erase personal responsibility. An adult who signs employment agreements, checks boxes on conflict disclosures, and collects public money knows when they are gaming the system. Saying "the system allowed it" does not make deception ethical.

Second, over-correcting toward surveillance creates its own misery. If leadership responds to a five-job scandal by installing invasive keystroke trackers, demanding constant check-ins, and micromanaging every minute, you will drive away capable professionals and turn knowledge work into performative theater.

Third, some government roles genuinely have cyclical spikes. A policy specialist or grant coordinator might have quieter stretches between legislative sessions or funding cycles, followed by intense crunch periods. Mistaking cyclical work for permanent slack leads to clumsy cuts that backfire later.

What Leaders Should Do Instead of Lecturing

Apologizing for "mistakes" after getting caught is standard crisis PR. It changes nothing. If executives, mayors, agency heads, and lawmakers actually want fewer scandals like this, they need to fix incentives and visibility—not just issue stern memos.

1. Audit Roles by Deliverables, Not Hours

Stop pretending that sitting in front of a screen for eight hours equals eight hours of value. Define clear quarterly outcomes, service-level targets, and handoff timelines for every role. When expectations are concrete, coasting becomes obvious without needing a hall monitor.

2. Fix Identity, Payroll, and Disclosure Hygiene

Require plain-language, periodic conflict and outside-employment disclosures across agencies. Cross-check payroll and tax identifiers where legally permitted, and close obvious onboarding blind spots so dual-role conflicts surface early rather than after a media investigation.

3. Give Managers Backbone and Span Limits

A manager supervising twenty people across fragmented workflows cannot realistically evaluate individual output. Tighten spans of control where needed, train supervisors to give direct feedback early, and back them up when documented performance falls short.

4. Cut Process Drag Before Cutting Headcount

Slashing positions blindly often leaves the same broken approval chains intact while overloading the people who stay. Strip out redundant sign-offs, modernize clunky software, and let capable staff move faster. When work flows cleanly, slack has nowhere to hide.

The civil servant who juggled five jobs gave us an embarrassing mirror. Smash the mirror if you want, blame one guy if it makes you feel better, and move on to the next outrage.

Or fix the machinery so nobody can pull it off again.

AY

Aaliyah Young

With a passion for uncovering the truth, Aaliyah Young has spent years reporting on complex issues across business, technology, and global affairs.