Overemployment - one person quietly holding two or three full-time remote jobs at once - is real, and you diagnose it by reading output and ownership, not by watching people work. The tell lives in the deep work. Someone ships the small, safe tasks on time and then goes missing on the architecture call, the roadmap fight, the ugly problem that needs an owner. Build a team where contribution is defined in observable terms and the pattern surfaces on its own, no detective work required.
I have started at nine or ten companies, and as a fractional product leader I walk into a new org every few months and have to read the team's output fast. That is the whole job. I do not get six months to form a gut feeling. Inside a couple of weeks I need to know who is actually carrying weight and who is coasting, because the engagement is short and the client is paying for judgment. So I have gotten used to reading throughput, ownership, and presence in the work the way other people read a room.
Here is the uncomfortable part. I am, by definition, working across several companies at the same time. Surround Insurance knows I am also inside Arkadium. Everyone knows. The disclosure is the entire deal, and there is a real line between fractional work and overemployment, and it is drawn in daylight. The overemployed person is running the same split without telling anyone, which is why the honest version of this problem is not about hours. It is about whether the work is getting owned.
What actually signals an overemployed remote worker?
The clearest signal is a person who consistently does the shallow work and vanishes from the deep work. They close tickets and post status updates, and then they are conveniently unavailable the moment a problem requires real ownership.
When I dropped into a home services marketplace on a fractional basis, one engineer had a spotless activity log. Commits every day, standup notes filed, Slack green. On paper, a model contributor. But every time we opened a hard design question - how do we restructure the booking flow, who owns the migration - he had a reason to punt. He would take the note and never come back with a point of view. The output was fine. The ownership was missing. That gap is the thing to watch, because someone genuinely present in the work cannot help but have opinions about where it is going. Someone whose attention is split across two employers protects their bandwidth by playing defense. They ship what is asked and nothing more, because the second job needs the other half of their brain.
The overemployed person is rarely the one who misses standup. It is the one who never owns the hard problem.
At Arkadium, where the product is browser gaming and the work moves quickly, this shows up as latency on the decisions that matter. A person who is all-in will push back on a bad call in the moment. A person who is stretched across two roles lets it slide, because engaging costs energy they have already spent somewhere else. You feel it as a strange quietness from someone who should have skin in the game.
Why is watching someone's calendar a bad way to catch it?
Because availability is noise, and treating it as signal turns you into a surveillance manager who erodes the trust of everyone who is doing honest work. Missed meetings and slow replies come from childcare, chronic illness, a bad week, or a genuinely async work style. None of that is overemployment.
The mistake I see leaders make is reaching for the wrong instrument. They start tracking login times and Slack response speed, and they end up punishing the single parent while the actually overemployed engineer - who is disciplined about looking busy - sails right through. People holding two jobs are usually good at the optics. That is how they hold two jobs. The observable that survives is not presence, it is contribution: what got owned, what got moved, what got decided.
This is the same reason I am allergic to running a team on response time. Fast Slack replies are the easiest thing in the world to fake, and they tell you nothing about whether the roadmap is moving. I would rather have someone go dark for a day and come back with a real answer than get instant acknowledgments and no progress.
How do you confirm it without turning into Big Brother?
You confirm it by making expectations explicit and then reading the gap between what full contribution looks like and what you are getting. When the definition of good is clear, underperformance is legible on its own, and you never have to spy to see it.
Start with a plain statement of what the role is supposed to produce. Deliverables, responsiveness within reason, meeting quality, decisions owned. Most teams skip this, which is exactly the vagueness an overemployed worker exploits. Then use your one-on-ones for signal instead of small talk. I do not ask anyone whether they are working a second job, because that question is trivially easy to deny and it poisons the relationship. I ask what they are driving this week, where they are stuck, and what they would take off their plate if they could. Someone who is genuinely overloaded from juggling two roles will often tell you they want to shed work, and that is a more honest thread to pull than any accusation.
Peers see it before metrics do. Not through interrogation - just by paying attention to who goes silent mid-week, who skips the moments that need a seat at the table. This is why I treat accountability as a team sport: the team already knows who is carrying and who is not, and a healthy culture makes that visible without anyone playing informant. If you do already run GitHub or ticket data as a normal part of the work, look for shape, not gotchas - solo commits at odd hours, going dark through a sprint. But data without context falsely accuses good people, so hold it loosely.
What do you do once you actually know?
You have two clean options, and which one you pick depends on whether the person is recoverable and how early you caught it. Both require you to treat it as a trust problem and handle it without theater.
If someone is truly holding two full-time jobs without disclosure, that usually breaks their employment agreement, and the move is to have the conversation, document it, and exit calmly. No public shaming, no calling anyone a fraud. Leaders talk, and the story of how you handled the exit travels further than the exit itself. The other option is a reset, and it is rarer than people want it to be. If the person is genuinely high-output and you caught it early, sometimes the second job started because you dropped the ball on structure or purpose. In that case you lay out unambiguous expectations, reconnect them to the mission, and make clear that transparency matters more to you than punishment. Then you wait. If they re-commit, keep them. If not, separate.
Either way, name a directly responsible individual for the work in question, because half of what lets overemployment hide is diffuse ownership where no single person is on the hook. When one name is attached to an outcome, coasting has nowhere to go. And go in expecting friction, because the performance conversation gets tricky the moment the person feels cornered. Stay on the observable facts. What was owned, what was not.
How do you build a team where this cannot hide for long?
You make the work legible by default, so that contribution and ownership are visible to the whole team without anyone being watched. When good is measurable and the mission is real, the incentive to quietly run a second job mostly evaporates.
Three things do most of the work. First, be brutally specific in hiring and onboarding about what success in the role looks like, because overemployment feeds on the "we're chill, just be awesome" culture that never defines anything. Second, normalize visibility without surveillance: shared roadmaps, async progress snapshots, honest standups where it is easy to see who is stuck. Visibility is a property of the work, not a camera on the person. Third, protect intrinsic motivation, because people reach for a second job when they stop feeling connected to the thing they are building. Remind them what the mission is and celebrate the wins that matter.
The table below is how I separate the overemployment pattern from the burnout and life stuff that looks similar on the surface. The difference is almost always ownership over time, not any single behavior.
| Observed behavior | Points to overemployment | Could just be burnout or life | What separates them |
|---|---|---|---|
| Recurring missed meetings | When paired with silence on deep work | Often | Burnout usually comes with an apology and context |
| Ships tasks, dodges architecture and roadmap calls | Strong signal | Rare | Deep disengagement from ownership is the tell |
| Commits only at odd hours, always solo | Frequent | Sometimes | Burnout work still tends to show real quality |
| Reuses the same async status updates | Frequent | Rare | Burned-out people explain the missing pieces |
| Slow to respond | Weak signal on its own | Very often | Only matters as a pattern beside the others |
The best remote teams I have worked with mix real trust with real standards and refuse to let either one slip. They do not police hours, and they do not pretend everyone is fine. They make the work visible, name who owns what, and reward the people who show up with full focus. Do that, and the person quietly running two jobs finds your team is not worth the risk, while everyone else finds it is the best place they have worked.
