skip to content

safety4 min read

How to moonlight without a conflict of interest

Most moonlighting problems come from one of three places: the client, the clock, or the company's property. Get those right and a second job rarely causes trouble. This guide takes each rule in turn, with examples of what is fine, what is risky, and what to avoid.

What a conflict of interest actually is

A conflict of interest is a situation where your personal interest could pull against your duty to your employer. It does not require bad intent. A perfectly honest person can be in a conflict simply because of who they are working for or what they have access to. That is why the rules below focus on situations, not motives.

Rule one: no competitors

Do not work for a business that competes with your employer, and do not serve your employer's clients on the side. This is the clearest line in almost every contract and policy, and the one employers care about most.

Competition is broader than the same product. A payments engineer advising a rival payments startup is an obvious conflict. A recruiter placing candidates for a company that hires from the same talent pool may be one. Building a website for a bakery is not. When in doubt, ask whether your employer would reasonably be upset to learn who you are helping.

  • Usually fine: a client in an unrelated industry, a non-profit, a personal project with no commercial overlap.
  • Grey area: a client in an adjacent market, a supplier to your employer, a company that might become a competitor.
  • Avoid: a direct competitor, your employer's own clients, anyone your employer is negotiating with.

Rule two: no clashing hours

Side work happens in your own time. That means no calls with side clients during work meetings, no deadlines that force you to take a sick day, and no late nights that leave you useless the next morning. Remote work makes this easier to get wrong, because nobody sees which window is open on your screen.

  • Block fixed hours for side work in your calendar, outside your working hours.
  • Agree on response times with side clients that fit around your job, and put them in writing.
  • Turn down projects with deadlines you cannot meet without borrowing from your day job.
  • Never use paid leave to catch up on side work you over-committed to; treat that as a signal to take on less.

Rule three: no company IP or data

Never use your employer's laptop, software licences, accounts, code, documents or contacts for side work. Anything created with company resources may belong to the company, and leaking information is one of the fastest routes to dismissal.

  • Use a separate personal device and personal accounts.
  • Do not copy code, templates or documents from work, even ones you wrote yourself.
  • Keep work email, chat and cloud storage out of your side work entirely.
  • Do not use knowledge that is confidential, such as unreleased plans, pricing or client lists, even indirectly.

General skills and experience are yours. Knowing how to build a good data pipeline is yours; your employer's pipeline code is not. Knowing how to run a pricing study is yours; your employer's pricing data is not.

Three examples

A product designer at a bank designs a booking app for a local clinic, in the evenings, on her own laptop. Different industry, own time, own tools: no conflict. She mentions it to her manager because the bank's policy asks for disclosure, and it is approved quickly.

A data analyst at a retailer is approached by another retailer to build a sales dashboard. Same industry, likely the same kind of data and insight. Even if he never touches his employer's data, this is a conflict he should decline.

A software engineer wants to publish a small open-source library at weekends. Own time and tools, but her contract has a broad IP clause. She asks HR in writing, gets confirmation that the library is outside the clause, and keeps the email.

When to disclose

If your contract or policy asks for disclosure or approval, follow it. Disclosure turns a secret into an agreement, and an agreement protects you. Keep it short: what the work is, roughly how much time it takes, and confirmation that it follows the three rules above.

Clear rules beat secret side jobs. They protect the employee and the employer at the same time.

Mondeed is built around the same rules: every gig is checked against your day job, so a competitor or a clashing schedule never reaches you in the first place.

common questions

Can I work for my employer's client on the side?

Almost always no, unless you have explicit written approval. Serving your employer's clients directly is one of the clearest conflicts there is.

Can I use skills I learned at work?

Yes. Your general skills and experience are yours to use. What you cannot use is your employer's confidential information, code, documents, data or tools.

Is it a conflict if my side work is in the same field but not a competitor?

Not necessarily. Same field is fine when the client is not a competitor, client or partner of your employer and no confidential knowledge is involved. If it is close, disclose it and ask.

What if a conflict appears later?

Tell your employer early and offer a fix, such as changing the scope or ending the side project. Conflicts that are raised promptly are far easier to resolve than ones that are discovered.

this article is general information, not legal, tax or financial advice. always check your own contract and local rules.

← all posts