How to Moonlight and Consult Without Violating Your Employment Agreement

Most engineers sign their employment agreements without reading them carefully — and most of the time, nothing bad happens. Until they start a consulting engagement and discover their company has a claim on everything they built. IP assignment clauses and non-compete provisions are not hypothetical risks; they've ended consulting arrangements, and occasionally careers. Before you take on your first client, you need to understand what you actually signed. If your consulting work grows into something bigger, the math in building side revenue as an engineer becomes relevant quickly — but the legal foundation has to come first.

Most employment agreements are longer than engineers expect — and the clauses that matter are rarely in the first few pages.

The Three Clauses That Actually Create Risk

Employment agreements vary by company, state, and when you were hired — but the clauses that generate real exposure for consulting engineers cluster around three provisions.

• IP assignment clauses — These assign ownership of your inventions to your employer. The broad versions cover anything you create that "relates to the company's current or anticipated business or research." That phrase is doing heavy lifting. If you're consulting in an adjacent domain — say, building data pipelines for a client while your employer also works on data infrastructure — the clause may give your employer a plausible claim to your client work.
• Non-compete provisions — These restrict you from working for competitors, or in certain industries, for a period after employment. Their enforceability varies dramatically by state: California and North Dakota effectively don't enforce them; many other states do, with varying restrictions on scope and duration. A non-compete that's unenforceable in your home state may still create headaches if your employer is incorporated elsewhere.
• Non-solicitation clauses — Separate from non-competes, these prohibit you from soliciting your employer's clients or recruiting their employees. Most engineers overlook these, but they apply even in states where non-competes are unenforceable. Consulting for a company that's also a client of your employer is the pattern that triggers these most often.

You need to read all three sections of your actual agreement before taking on a client. Not a summary, not someone else's interpretation — the contract you signed. If you no longer have it, your HR department is required to give you a copy.

1. 1
   Install Ambitology Cortex
2. 2
   Read as usual
3. 3
   Turn skills to jobs in realtime

CHROME EXTENSIONDownload Ambitology Cortex↗

What "Related to Company Business" Actually Means

The IP clause is where most engineers get into trouble, and the key question is always the same: is your consulting work "related to" your employer's business?

Courts have generally interpreted this narrowly when the language is narrow — "work performed during employment hours using company resources" — and more broadly when the language says "relates to business the company is engaged in or may engage in." That "may engage in" phrase is worth taking seriously at growth-stage companies, which often claim broad future product territory.

“The safest consulting arrangement is one you'd be comfortable describing to your manager during your performance review.”

A few practical tests: Does your consulting work solve the same kind of problem your employer solves? Does it serve the same customer segment? Does it use proprietary methods, training data, or architectural patterns you developed on company time? If the honest answer to any of these is yes, you need a conversation with employment counsel before you start — not after.

How to Structure Consulting Work Safely

If your contract language is broad and you still want to consult, the structure of the work matters as much as the substance.

• Work in a genuinely different domain. A backend engineer at a healthcare company consulting for a retail analytics startup is in clearly different territory than one who takes on healthcare data clients. The further the domain distance, the cleaner the separation.
• Use only your personal equipment and accounts. Doing any client work on your work laptop — even for five minutes — is a problem. Work email, Slack, company GitHub accounts, internal tools: none of these should touch client work. Use a personal machine, personal GitHub, and separate accounts for everything.
• Work outside work hours. This doesn't eliminate IP exposure (most clauses don't have a time-of-day carveout), but it removes the argument that you were using company time. Work done on weekends and evenings is clearly separable from your employed duties.
• Consider a separate legal entity. Consulting through an LLC rather than as an individual creates a cleaner separation between the work and your employment. It doesn't defeat an IP claim, but it signals — and creates — a professional separation that makes the distinction clearer in any dispute.

When to Get Written Approval

Some companies have explicit moonlighting policies. If yours does, read it. If it requires approval for outside work, get that approval in writing before you start — not after. A quick email to HR outlining the engagement ("I'm planning to do independent consulting work for a company in the retail sector, using my personal equipment, on my own time") and a written sign-off is protection worth having.

Many employers will approve without issue, especially when the work is clearly in a different domain. The ones that won't approve are often the ones where the risk is real — which is useful information to have before you start rather than mid-engagement. If you're doing more substantial independent work, the financial and structural comparison between contractor versus full-time employment is worth understanding — especially when you're deciding how much of your income to route through consulting versus a staff role.

FAQ

Can my employer claim ownership of a side project I built on my own time?

Potentially yes, depending on your IP assignment clause. If the clause covers work "related to the company's current or anticipated business" and your project falls in that space, your employer may have a colorable claim even if you built it entirely on your own time and equipment. Some states (California, Delaware, Illinois, Minnesota, North Carolina, Washington) have statutes that limit employer IP claims to work done using company resources or on company time — check whether your state is one of them.

Do non-compete clauses actually hold up in court?

It depends heavily on state law. California, North Dakota, Oklahoma, and Minnesota have strong restrictions on non-compete enforcement. Other states — Texas, New York, Florida — enforce them more readily, subject to reasonableness standards around duration and scope. Even if your agreement is technically unenforceable, an employer with legal resources can make the dispute expensive enough to deter you. If your contract has a broad non-compete, consult an employment attorney before accepting consulting work in an overlapping field — the cost of a 30-minute consultation is much lower than the cost of finding out later.

Should I tell my employer about consulting work?

If your contract requires disclosure of outside work, yes — and in writing. If it doesn't require it, the calculation is more nuanced. Transparency creates goodwill and removes the question entirely, but it also invites scrutiny the work might not survive. The practical answer: disclose when the work is clearly separated from your employment, and always when your contract requires it. Don't disclose if you're not required to and the work is in a gray area — the disclosure itself draws attention to the ambiguity.

What happens if I violate my employment agreement?

At minimum, termination. Depending on the damages and the employer, litigation is possible — particularly if the consulting work competed directly or generated substantial revenue in an area the company considers its own. More commonly, the risk surfaces when you leave and the company does a standard exit review. The best-case outcome is a cease and desist; the worst is a lawsuit over IP ownership or non-compete breach. Neither is worth a consulting engagement that could have been structured differently from the start.