The Two-Paycheck Trend: How to Write an AI-Era Moonlighting Policy
Employees are openly using autonomous AI to hold two remote full-time jobs at once. Banning it won't work, ignoring it is reckless. Here's a practical, outcome-based moonlighting policy that protects the business without pretending the trend doesn't exist.
If you've spent any time on r/overemployed or TikTok in the last 12 months, you've seen the new normal: a developer in their late twenties showing how they hold three remote jobs with the help of AI agents handling stand-ups, code drafts, and Slack replies. The comments aren't outrage. They're requests for the setup guide.
HR's old answer — "it's against policy" — is meaningless when the work is async, outcome-based, and partially automated. We need a new contract.
Why the old policy doesn't hold
Old moonlighting clauses were written for a world where work meant hours-in-a-seat. "You shall devote your full business hours to the Company." That sentence has no teeth in 2026. There are no business hours. There is only output, and AI is doing some of it.
- "Devote full business hours to the Company."
- "No outside employment without written consent."
- "Available during core hours."
- Focuses on time, location, and presence.
- Clear deliverables, response SLAs, and quality bars.
- Explicit data-security and IP-isolation clauses.
- Conflict-of-interest list (named competitors, customers, partners).
- AI-use disclosure — what tools, what data, what's been trained on.
A 7-clause AI-era moonlighting policy
- Outcome standard: define what "meeting expectations" looks like in deliverables, not hours.
- Conflict register: maintain a named list of companies the employee cannot work for in parallel.
- Data isolation: forbid uploading company data into personal AI tools or shared accounts.
- Device hygiene: company work happens on company-managed devices; no second-screen mirroring of confidential work.
- Availability SLA: response windows for synchronous moments (incidents, customer escalations), not blanket presence.
- Disclosure trigger: employees must disclose any outside engagement above a defined hours-per-week or revenue threshold.
- Remedy ladder: coaching → written warning → termination, applied to outcomes and integrity breaches, not to the existence of a second job.
What to do this quarter
- Audit your current employment agreement language with employment counsel.
- Draft an outcome-based performance standard for every role above a certain level.
- Stand up a data-security review with IT — focus on AI tool sprawl and shared logins.
- Train managers to coach on output and SLAs, not on "green dot" presence.
HR & Operations leader scaling global remote teams across Nepal, the Philippines, Australia, and the US. Tech-leaning writing lives on Medium.