A software developer has two laptops open somewhere, whether it’s in a spare bedroom in suburban New Jersey or a home office in Austin or Columbus. A San Francisco-based financial company’s Slack workplace is displayed on the left screen. A Teams channel for a Minneapolis insurance company is displayed on the right screen. Each team believes they have a full-time worker. Both are partially right. With appropriate task prioritization, automation tools, and a well-practiced set of deflection habits, the engineer’s real working hours, divided across the two roles, total about forty hours per week. In total. Together, they make well over six figures. Neither employer is aware of the other.
Since the early years of the remote work era, the Overemployed movement (abbreviated OE by its expanding online community) has been growing and has been accelerating as AI tools make it easier to complete knowledge-work deliverables in significantly less time than the nominal job description implies.
The fundamental idea behind it is not new: the change to fully distributed teams eliminated the final natural check on whether an employee was sitting at their desk for eight hours, and remote white-collar labor has traditionally been assessed more by production than by presence. The OE community has formalized the strategic framework for operating in this gap, including the regulations, risk management, and particular methods for handling overlapping responsibilities without any employers realizing the seam.
One of the more intriguing tactical problems is the meeting problem. A significant number of planned calls are part of full-time remote jobs, and having two jobs implies having two calendars that periodically clash. The documented methods include running one meeting on a laptop while the other plays on a monitor with just enough peripheral awareness to catch action items, claiming microphone or connection issues to buy time to switch attention, and muting one call and passively monitoring it while actively participating in the other.
This may sound more complicated than it actually is because most corporate meetings follow a set format where participation is required for the beginning and last five minutes but not for the middle thirty. Due of their greater motivation to map it, OE practitioners typically know this better than anybody else.
The setup is especially vulnerable in the siloing discipline. LinkedIn never shows secondary jobs. Routine chores that might otherwise result in a clear capacity issue are handled by AI technologies and delegation to outside assistance. The primary position is regarded as non-negotiable since it serves as the foundation for the employment history and serves as the reference for background checks.
The remainder is handled using a calculus that practitioners characterize as being ready to swiftly leave any position the moment a boss gets overly focused or a project calls for longer hours than the arrangement permits. Instead of being removed, risk is managed.
A large portion of the public discourse on OE ignores the actual legal exposure. Practitioners who work for direct competitors are in non-compete and NDA territory, where the repercussions might go beyond termination to include wage clawback or legal action.
The majority of OE policies take this into consideration by keeping work in non-overlapping industries, although employment contracts were not drafted with this particular arrangement in mind, and the distinction between “adjacent” and “competing” is not often clear. As the community grows, there’s a sense that the legal framework for dealing with this hasn’t kept up with how widespread the practice has grown. When the first significant public case arises, it will shed light on a lot of issues that are currently in a purposeful gray area.
