Employment & Labor

Disclaimer: This skill provides general educational information about legal topics relevant to software development. It is not legal advice. Laws vary by jurisdiction and change frequently. Always consult a qualified attorney licensed in the relevant jurisdiction before making legal decisions for your organization.

Overview

Software companies with distributed teams face complex employment law across multiple jurisdictions. Misclassifying workers, failing to secure IP assignment, or violating local labor laws can result in significant liability — including back taxes, penalties, loss of intellectual property rights, and lawsuits. As remote work becomes the norm and companies hire across borders, understanding the employment law landscape is essential to building a legally compliant and sustainable workforce.

Contractor vs Employee Classification

Why It Matters

The distinction between an independent contractor and an employee has profound consequences:

• •Tax obligations — Employers must withhold income taxes, pay Social Security/Medicare (US) or equivalent contributions, and file employment tax returns for employees. Contractors handle their own taxes.
• •Benefits — Employees may be entitled to health insurance, retirement plans, paid leave, unemployment insurance, and workers' compensation. Contractors receive none of these.
• •IP ownership — In many jurisdictions, work created by employees belongs to the employer by default. Work created by contractors generally belongs to the contractor unless assigned by written agreement.
• •Liability — Companies are generally liable for the acts of employees (respondeat superior) but have more limited liability for independent contractors.

Classification Tests

Consequences of Misclassification

• •Back taxes and penalties — The IRS can assess back employment taxes plus penalties and interest. Similar consequences apply in other jurisdictions.
• •Back benefits — Misclassified workers may be entitled to retroactive benefits including health insurance, retirement contributions, overtime pay, and paid leave.
• •IP ownership disputes — If a contractor was actually an employee, the work-for-hire doctrine may not apply as expected, creating uncertainty about who owns the IP.
• •Class action risk — Misclassification cases are frequently brought as class actions, multiplying the potential liability across all similarly situated workers.

IP Assignment

Work-for-Hire Doctrine (US)

Under US copyright law, work created by an employee within the scope of employment is automatically owned by the employer as a "work made for hire." However, this doctrine has important limitations:

• •It applies only to employees, not independent contractors (with narrow exceptions for specific commissioned categories like contributions to collective works, parts of motion pictures, translations, supplementary works, compilations, instructional texts, tests, test answers, and atlases).
• •Software created by a contractor is owned by the contractor unless there is a written assignment agreement.

Invention Assignment Agreements

For contractors and in jurisdictions where the work-for-hire doctrine is limited, companies should require written invention assignment agreements that:

• •Assign all IP created during the engagement to the company.
• •Include a present tense assignment ("hereby assigns") rather than an agreement to assign in the future.
• •Cover patents, copyrights, trade secrets, and all other IP rights.
• •Comply with local restrictions (e.g., California Labor Code Section 2870 protects inventions developed entirely on the employee's own time without company resources).

IP Ownership by Jurisdiction

Critical point: Contractor IP is NOT automatically assigned to the company in any jurisdiction. Always execute a written IP assignment agreement before a contractor begins work.

Non-Compete Agreements

The enforceability of non-compete agreements has undergone dramatic changes in recent years:

Recent Developments (2024-2025)

• •FTC Non-Compete Ban (US) — The FTC issued a rule in 2024 banning most non-compete agreements nationwide. The rule was stayed by federal courts (Ryan LLC v. FTC), but the FTC's action signals the regulatory direction and has emboldened state-level restrictions.
• •California — Non-competes are banned entirely under Business and Professions Code Section 16600. California also prohibits employers from requiring employees to sign non-competes governed by another state's law.
• •Growing state restrictions — Colorado, Minnesota, Oklahoma, North Dakota, and other states have enacted or strengthened restrictions on non-competes.

Enforceability by Jurisdiction

Alternatives to Non-Competes

• •Non-solicitation agreements — Restrict soliciting the company's employees or customers, generally more enforceable.
• •Confidentiality/NDA agreements — Protect trade secrets and confidential information without restricting employment.
• •Garden leave — Employee remains employed (and paid) during the notice period but does not work, preventing immediate competition.

Remote Work Across Borders

Hiring remote workers in other countries or allowing employees to work remotely from abroad creates significant legal complexities:

Key Risks

• •Permanent establishment — A remote employee may create a taxable presence (permanent establishment or tax nexus) for the company in the employee's country, triggering corporate tax obligations.
• •Local employment law applies — The employee is generally subject to the labor laws of the country where they physically work, regardless of where the company is headquartered. This includes minimum wage, working hours, overtime, leave entitlements, termination protections, and benefits.
• •Social security and benefits — Companies may be required to register for and contribute to local social security, pension, and health insurance schemes.
• •Immigration and work authorization — Even remote workers may need work permits or visas depending on the jurisdiction.

Employer of Record (EOR)

An Employer of Record is a third-party organization that legally employs workers on behalf of the client company in jurisdictions where the client does not have a legal entity. The EOR handles:

• •Employment contracts compliant with local law
• •Payroll, tax withholding, and statutory contributions
• •Benefits administration
• •Termination procedures

Common EOR providers include Deel, Remote, Oyster, and Papaya Global. Using an EOR allows companies to hire in foreign jurisdictions without establishing a local subsidiary, but comes with costs and some loss of direct control.

Equity Compensation

Stock options, RSUs, and other equity compensation are common in software companies but create complex cross-border issues:

Key Considerations

• •409A valuation (US) — Under Section 409A of the Internal Revenue Code, stock options must be granted at or above fair market value, determined by an independent 409A valuation. Non-compliant grants can result in severe tax penalties for recipients.
• •Securities registration — Issuing equity may trigger securities registration requirements in each jurisdiction where recipients reside. Many jurisdictions have exemptions for employee equity plans, but these must be actively claimed.
• •Tax treatment varies dramatically — The timing and rate of taxation on stock options and RSUs differs by jurisdiction. In some countries, options are taxed at grant; in others, at exercise; in others, at sale. Rates range from favorable capital gains treatment to ordinary income plus social security contributions.
• •Vesting schedules — Standard 4-year vesting with a 1-year cliff is common in the US but may conflict with local labor laws in some jurisdictions (e.g., some countries treat unvested equity as earned compensation upon termination).
• •Exercise windows for departing employees — The standard 90-day post-termination exercise window in the US may be insufficient or may conflict with local requirements. Many companies now offer extended exercise windows (e.g., 1-10 years).

Whistleblower Protections

Software companies must be aware of growing whistleblower protection laws:

Key Legislation

• •EU Whistleblower Directive (2019/1937) — Requires companies with 50+ employees in the EU to establish internal reporting channels. Protects whistleblowers from retaliation. Applies to reports about EU law violations including fraud, corruption, public procurement, data protection, and more.
• •US Sarbanes-Oxley Act (SOX) — Protects employees of publicly traded companies who report securities fraud or violations. Provides for reinstatement, back pay, and compensatory damages.
• •US Dodd-Frank Act — Provides financial incentives (10-30% of sanctions over $1 million) and anti-retaliation protections for individuals who report securities violations to the SEC.

Required Actions

• •Establish internal reporting channels (confidential hotline, web portal, or designated officer).
• •Protect reporters from retaliation (termination, demotion, harassment).
• •Investigate reports promptly and document findings.
• •Comply with jurisdiction-specific timelines for acknowledgment and follow-up.

Employee Monitoring

The ability to monitor employees — especially remote workers — is subject to increasing legal restrictions:

Regulatory Framework

• •EU/GDPR — Employee monitoring is considered processing of personal data and must comply with GDPR principles: lawfulness, purpose limitation, data minimization, and transparency. Covert monitoring is generally prohibited except in limited circumstances.
• •Transparency requirements — Most jurisdictions require employers to inform employees about the nature, extent, and purpose of monitoring before it begins.
• •Proportionality — Monitoring must be proportionate to the legitimate business interest. Keystroke logging, continuous screen capture, and webcam monitoring face particular scrutiny.
• •Works councils and employee representatives — In countries like Germany, France, and the Netherlands, employee monitoring policies may need to be negotiated with or approved by works councils or employee representatives.
• •US — Federal law (Electronic Communications Privacy Act) generally permits employer monitoring of company-owned devices with notice, but state laws vary. Connecticut and Delaware require written notice before monitoring.

Best Practices

• •Consult employment counsel in each jurisdiction where you have workers. Employment law varies dramatically across borders, and even within countries (e.g., California vs Texas in the US). Local counsel is essential for compliance.
• •Classify workers correctly from the start. Perform a classification analysis using the applicable test before engaging any worker. Document the analysis. When in doubt, err toward employee classification — the consequences of misclassifying an employee as a contractor are far more severe than the reverse.
• •Execute written IP assignment agreements before work begins. Never assume that contractor work product belongs to the company. Get a signed, jurisdiction-appropriate IP assignment agreement in place before the contractor writes a single line of code.
• •Audit your non-compete agreements. Given the rapid changes in non-compete law, review all existing non-compete agreements with counsel. Consider whether non-solicitation or confidentiality agreements would better serve your interests with lower legal risk.
• •Use an Employer of Record for international hires until you establish local entities. EORs provide a compliant way to hire in foreign jurisdictions without the cost and complexity of setting up a local subsidiary.
• •Get local tax and securities advice before granting equity to international employees. Equity compensation triggers different tax and regulatory consequences in every jurisdiction. A plan that is tax-efficient in the US may create severe tax liabilities for a recipient in another country.
• •Implement transparent and proportionate employee monitoring policies. If you monitor employees, disclose the monitoring clearly, limit it to what is necessary for legitimate business purposes, and comply with local laws regarding consent and employee representation.
• •Establish whistleblower reporting channels. Even if not legally required in every jurisdiction where you operate, internal reporting channels demonstrate good governance and can help surface problems before they become enforcement actions.