Software Engineer Employment Contract Guide
Your code is valuable, and so are your rights. Learn what every software engineer should review, negotiate, and understand before signing an employment contract.
Why Software Engineer Employment Contracts Are Different
A software engineer employment contract is not like a standard employment agreement. In the tech industry, your primary output is intellectual property -- code, architectures, algorithms, and systems. This makes the IP assignment clause the single most consequential provision in your contract, far more impactful than salary or title. Unlike most professions, the work product of a software engineer can be directly copied, reused, and monetized indefinitely.
Tech employment contracts also carry unique complexities around equity compensation, open source participation, side projects, remote work across jurisdictions, and the rapidly evolving legal landscape around non-competes. A clause that seems boilerplate could strip you of rights to personal projects you build on your own time, or lock you out of an entire industry segment when you leave.
Whether you are joining a FAANG company, a mid-stage startup, or a consulting firm, understanding these tech-specific provisions is essential. This guide covers every critical clause a software engineer should scrutinize before signing, with real contract language examples and negotiation strategies.
IP Assignment: The Most Important Clause for Engineers
In tech, IP is king. The intellectual property assignment clause determines who owns the code, inventions, and creative works you produce. A poorly written IP clause can claim ownership of everything you create -- including personal GitHub projects, open source contributions, and side projects built entirely on your own time with your own equipment.
Example Contract Language
“Employee agrees to assign to the Company all rights, title, and interest in any and all inventions, developments, improvements, works of authorship, and discoveries, whether or not patentable, made, conceived, or reduced to practice during the period of employment, whether or not made during working hours or using Company resources.”
This is a dangerously broad IP assignment. It claims ownership of everything you create while employed -- including weekend side projects, personal apps, and open source contributions that have nothing to do with your job. This type of clause is common in tech contracts, especially at startups.
Better alternative:
“Employee assigns to the Company all inventions, developments, and works of authorship that (a) are made using Company time, equipment, or proprietary information, (b) relate to the Company's current or demonstrably anticipated business, or (c) result from any work performed for the Company.”
Example Contract Language
“Employee shall disclose promptly to the Company all inventions and creative works conceived during the term of employment. The Company shall have the right of first refusal on any such inventions.”
While the mandatory disclosure requirement may seem mild, combined with a broad IP assignment it creates a chilling effect. You must tell your employer about every personal project, and they get to decide if they want to claim it. This discourages personal innovation and open source contribution.
Better alternative:
“Employee shall disclose inventions that relate to the Company's business or that were developed using Company resources. Employee's personal projects that do not use Company resources or proprietary information and are unrelated to the Company's business are excluded from disclosure and assignment requirements.”
Open Source Contributions
If you contribute to open source projects, ensure your contract explicitly permits this. Many engineers assume they can continue contributing, only to discover their employer claims ownership of those contributions. Negotiate a carve-out that allows contributions to projects unrelated to the company's core business, and ask whether the company has a formal open source contribution policy.
Tip: Ask for explicit written permission for specific open source projects you actively maintain.
Personal GitHub & Side Projects
Your personal GitHub repositories, hobby apps, and side projects may be at risk under a broad IP clause. Even if you build something entirely outside work hours using your own laptop, a sweeping assignment clause could give your employer a claim to it. Protect yourself by listing all existing projects on the prior inventions schedule and negotiating explicit carve-outs for personal work.
Tip: Keep records showing personal projects were developed on personal time and equipment.
Prior Inventions Schedule
The prior inventions schedule (Exhibit A or Exhibit B) is your opportunity to carve out existing work before signing. List every side project, open source contribution, app, patent, and creative work you have produced before your start date. If it is not on this list, your employer may argue it was created during employment and belongs to them.
Tip: Be thorough. Include every GitHub repo, every side project, and any IP you might want to commercialize later.
State Protections
Several states provide statutory protection for employee inventions. California Labor Code Section 2870, for example, prohibits employers from claiming inventions developed entirely on the employee's own time without company resources, unless they relate to the employer's business. Similar laws exist in Delaware, Illinois, Minnesota, Washington, and North Carolina.
Tip: Even with state protections, having explicit contract language is far better than relying on statutory fallbacks.
Non-Compete Clauses in the Tech Industry
Non-compete agreements in tech are a rapidly shifting landscape. California has banned non-competes for decades, which has been a major factor in Silicon Valley's success -- engineers can freely move between companies, accelerating innovation. Other tech hubs are following suit.
Colorado, Minnesota, North Dakota, and Oklahoma have all enacted significant bans or restrictions on non-competes. Washington and Oregon limit enforcement to employees earning above high salary thresholds. The FTC's 2024 rule aimed to ban most non-competes nationwide, though it continues to face legal challenges. The trend is clearly moving toward restricting these agreements, especially for technical workers.
Even in states where non-competes remain enforceable, courts are increasingly skeptical of broad restrictions on software engineers. The specialized, transferable nature of programming skills means that preventing an engineer from working at any competitor is often seen as an unreasonable restraint of trade. For a detailed analysis of non-compete enforceability, see our non-compete clause review guide.
If You Are Based in California
Non-competes are void and unenforceable in California under Business and Professions Code Section 16600. Your employer cannot enforce one even if you signed it, and as of 2024, employers cannot even require you to sign one. If your contract contains a California non-compete, it is a red flag about the company's legal sophistication or intentions.
Non-Solicitation vs. Non-Compete
Many tech companies use non-solicitation agreements as an alternative to non-competes. These prevent you from recruiting former colleagues or soliciting the company's clients after departure. Non-solicitation clauses are generally more enforceable and more reasonable, but review them carefully -- an overly broad non-solicitation can function as a de facto non-compete.
Equity Compensation: Stock Options, RSUs, and Vesting
Equity is a central component of tech compensation and can represent a significant portion of your total pay. Understanding how vesting, exercise windows, and acceleration clauses work is critical before signing.
Vesting Schedule
The industry standard is a four-year vesting schedule with a one-year cliff. During the first year, you earn nothing. At the one-year mark, 25% vests at once (the "cliff"). After that, the remaining 75% typically vests monthly or quarterly. Some companies deviate -- Amazon's back-loaded schedule (5/15/40/40) means most equity arrives in years three and four.
Key question: Does the vesting schedule reset if you transfer teams internally?
Exercise Window
For stock options, the exercise window determines how long after leaving the company you can buy your vested shares. The traditional window is 90 days, but this can be devastating if you have a large tax bill (especially with ISOs and AMT). Many modern startups now offer extended windows of 7-10 years. This is a critical negotiation point, especially at startups.
Key question: What happens to unvested shares if you are terminated without cause?
Acceleration on Termination
Acceleration clauses determine whether your unvested equity speeds up under certain conditions. "Single trigger" acceleration means equity vests immediately upon an acquisition. "Double trigger" requires both an acquisition and your termination or role change. Most companies offer double trigger if anything, but it is worth negotiating, especially for senior roles at acquisition targets.
Key question: Is there any acceleration if you are laid off before the cliff?
Clawback & Repurchase Rights
Some startup contracts include clawback provisions that allow the company to repurchase your vested shares at the original exercise price (not fair market value) when you leave. This effectively erases the value of your equity. Similarly, watch for right-of-first-refusal clauses that prevent you from selling shares on secondary markets.
Red flag: Any clause allowing repurchase of vested shares below fair market value.
Remote Work Terms and Cross-State Implications
Remote work has become standard in tech, but employment contracts often lag behind this reality. If you are working remotely -- especially across state lines -- your contract should explicitly address several key issues. The state where you physically work determines which employment laws apply, which can differ dramatically from your employer's home state on issues like non-compete enforceability, overtime rules, and employee protections.
Cross-state remote work also creates tax complications. You may owe income tax in your state of residence, your employer's state (under "convenience of the employer" rules in states like New York and New Jersey), and potentially any state where you travel for work. Your contract should specify the governing jurisdiction and whether the company offers tax equalization or assistance for multi-state tax filings.
Remote Work Contract Checklist
On-Call Expectations and Overtime: Exempt vs. Non-Exempt
Most software engineers are classified as "exempt" under the Fair Labor Standards Act (FLSA), meaning they do not receive overtime pay. However, this classification is not automatic -- it requires meeting specific salary and duties tests. The computer employee exemption applies to workers earning at least $27.63 per hour (or $684 per week salary) whose primary duties involve systems analysis, programming, software engineering, or similar computer-related work.
Even if you are correctly classified as exempt, your contract should clearly define on-call expectations. Many tech companies maintain on-call rotations where engineers must respond to production incidents within minutes, sometimes in the middle of the night. If on-call is frequent or demanding, negotiate for on-call compensation, reduced on-call frequency, or compensatory time off.
Junior engineers, QA engineers, IT support staff, and some DevOps roles may actually be non-exempt and entitled to overtime. If you are classified as exempt but spend most of your time on tasks that do not involve independent judgment or discretion (such as strictly following specifications), the classification may be incorrect. Misclassification is a significant issue in the tech industry.
Moonlighting and Side Project Policies
Many software engineers maintain side projects, freelance, teach courses, or run small businesses outside their day job. Your employment contract's moonlighting policy determines whether this is permitted. Some contracts outright prohibit any outside employment or business activity. Others require prior written approval. The most engineer-friendly contracts permit outside work as long as it does not conflict with your primary role, use company resources, or compete with the company's business.
The moonlighting policy interacts closely with the IP assignment clause. Even if moonlighting is permitted, a broad IP clause might still claim ownership of what you create. You need both a permissive moonlighting policy and a narrow IP assignment clause to truly protect your side work. When negotiating, ask for explicit written approval for specific side projects you want to maintain, and ensure this approval is documented in the contract or an addendum.
Example Contract Language
“Employee shall devote their full professional time, attention, and energy to the business of the Company and shall not, without the prior written consent of the Company, engage in any other business activity, whether or not such activity is pursued for profit.”
This blanket prohibition on all outside activity goes too far. It could be interpreted to prevent you from freelance writing, teaching a weekend workshop, advising a friend's startup, or even selling crafts online. Most engineers would be in technical violation of this clause.
Better alternative:
“Employee shall devote their professional efforts to the Company during working hours. Outside activities are permitted provided they (a) do not interfere with Employee's responsibilities, (b) do not involve Company resources or confidential information, and (c) are not in direct competition with the Company's business.”
FAANG vs. Startup Contract Differences
The type of company you join dramatically affects what your employment contract looks like. Here is how contracts typically differ between large tech companies and startups:
Large Tech (FAANG)
- RSUs with predictable public market value
- Standard 4-year vesting (varies by company)
- Well-defined IP policies, often with open source programs
- Comprehensive benefits and clear severance terms
- Usually based in non-compete ban states (CA, WA)
- Established HR/legal teams -- less room to negotiate
- Standardized offer letters with less variability
Startups
- Stock options (ISOs/NSOs) with uncertain future value
- Exercise window often only 90 days post-departure
- Broader IP clauses -- sometimes claiming all inventions
- May include non-competes, even in tech-unfriendly terms
- Less structured benefits, may lack severance provisions
- More negotiation flexibility on individual terms
- Offer letters may be less polished -- review carefully
Mid-Stage Companies
Companies between Series B and pre-IPO often present the most complex contracts. They may offer a mix of options and RSUs, have evolving IP policies, and are large enough to have legal teams but small enough that terms are still somewhat negotiable. Pay particular attention to what happens to your equity in the event of an acquisition, as these companies are frequent acquisition targets.
Contract Negotiation Strategies for Software Engineers
Tech talent is in demand, and most employers expect some negotiation. Here are strategies specific to software engineer employment contracts:
Narrow the IP assignment clause
Request language limiting assignment to work created using company time, equipment, or proprietary information. Cite your state's invention protection statute if applicable.
Fill out the prior inventions schedule completely
List every side project, open source contribution, and personal IP. This is your best protection against future disputes. Do not leave it blank -- write "See attached" and provide a comprehensive list.
Negotiate the stock option exercise window
At startups, push for a 7-10 year exercise window instead of the standard 90 days. This protects you from a forced exercise decision (and potential tax hit) if you leave before a liquidity event.
Request an explicit side project carve-out
Get written permission for specific personal projects. Name them in the contract or an addendum. General permission is good, but named exceptions are better.
Push back on overly broad non-competes
If you cannot eliminate the non-compete entirely, narrow the scope to direct competitors (ideally a named list), reduce the duration to 6 months maximum, and add a carve-out for termination without cause.
Clarify remote work permanence
If remote work is important to you, ensure the contract states it explicitly rather than relying on a verbal promise. Specify whether the arrangement is permanent or subject to change, and what happens if you relocate.
Understand your equity in every scenario
Ask what happens to your equity if you are terminated, laid off, or the company is acquired. Get clarity on acceleration triggers, exercise windows, and repurchase rights in each scenario.
How OfferScope Analyzes Tech Employment Contracts
Our AI-powered contract analysis is built with software engineers in mind. Upload your contract and get instant, detailed feedback on every clause that matters to your career:
- Flags overly broad IP assignment clauses and suggests narrower alternatives
- Analyzes non-compete enforceability based on your state and role
- Breaks down equity terms including vesting, exercise windows, and acceleration
- Identifies missing side project and moonlighting protections
- Evaluates remote work provisions and cross-state implications
- Compares your contract terms against industry standards for your level
- Highlights clauses that disproportionately favor the employer
- Provides specific, actionable negotiation talking points
Related Resources
IP Assignment Clause in Employment Contracts
Deep dive into intellectual property assignment clauses, including what employers can and cannot claim.
Non-Compete Clause Review
Comprehensive guide to understanding non-compete enforceability, state laws, and negotiation strategies.
Employment Contract Review
General guide to reviewing your entire employment contract, clause by clause.
Remote Work Contract Clauses
What to look for in remote work provisions, including location flexibility, expenses, and governing law.
Frequently Asked Questions
What should a software engineer look for in an employment contract?
Software engineers should pay special attention to intellectual property (IP) assignment clauses, non-compete and non-solicitation agreements, equity compensation details (vesting schedule, exercise window, acceleration), side project and moonlighting policies, remote work terms, on-call expectations, and confidentiality agreements. IP assignment is often the most impactful clause for engineers, as it can affect your ability to contribute to open source or work on personal projects.
Can my employer own the code I write on my personal time?
It depends on the IP assignment clause in your contract. Many tech companies use broad language claiming ownership of all inventions "related to the company's business," even those created on personal time with personal equipment. Some states, including California, Delaware, Illinois, Minnesota, Washington, and North Carolina, have laws that limit employer claims to inventions created outside of work. Always review the IP clause carefully and negotiate carve-outs for personal projects.
Are non-competes enforceable for software engineers?
Enforceability varies by state. California completely bans non-competes, and many other tech hubs like Colorado, Minnesota, and Oklahoma have banned or heavily restricted them. Even in states that allow non-competes, courts increasingly view broad restrictions on software engineers unfavorably due to the specialized nature of tech skills. The FTC has also moved toward a nationwide ban, though legal challenges continue.
What is a typical vesting schedule for stock options or RSUs?
The standard vesting schedule in tech is four years with a one-year cliff. This means you receive no equity during the first year, then 25% vests at the one-year mark. After that, the remaining 75% vests monthly or quarterly over the next three years. Some companies offer different schedules - Amazon, for example, uses a back-loaded schedule (5%, 15%, 40%, 40%).
What is a prior inventions schedule and should I fill one out?
A prior inventions schedule (also called Exhibit A or Exhibit B to the IP agreement) is a list of inventions, side projects, and open source contributions you created before joining the company. You should absolutely fill this out, listing all personal projects, open source contributions, and any side businesses. This protects your existing work from being claimed by your new employer under the IP assignment clause.
How do FAANG contracts differ from startup contracts?
FAANG (large tech) contracts typically offer RSUs (restricted stock units) with predictable value, standard benefits, and relatively clear IP policies. Startup contracts often include stock options (not RSUs), which carry more risk and complexity, along with broader IP assignment clauses, less generous benefits, and sometimes more aggressive non-compete terms. Startups may also expect more flexibility on hours and on-call responsibilities without explicit compensation.
Can I still contribute to open source after signing a tech employment contract?
This depends entirely on your contract. Some companies encourage open source contributions, while others restrict them. Key factors include your IP assignment clause, whether the company has an open source contribution policy, and whether your contributions relate to the company's business. Negotiate explicit open source carve-outs in your contract, and check if your company has a formal open source program or approval process.
What are the tax implications of working remotely in a different state than my employer?
Remote work across state lines can create tax obligations in multiple states. You may owe income tax in both the state where you live and the state where your employer is based, though most states offer credits to avoid full double taxation. Some states have "convenience of the employer" rules that can tax remote workers as if they were in-office. Your contract should address which state's laws govern your employment and any tax equalization provisions.
Get Your Tech Contract Reviewed
Upload your software engineer employment contract and get instant AI-powered analysis of IP assignment, equity terms, non-competes, and every clause that matters to your career.
No account required for your first analysis. $20 one-time for full report.