Google Employment Agreement: What to Look for Before You Sign

Getting an offer from Google is a big deal. Before you celebrate and click "sign," take a few hours to actually read what you're agreeing to. Agreements at Google typically involve multiple documents, each with real legal consequences. Here's what those documents generally look like and what to pay attention to.

The Two-Document Structure

Most tech companies combine everything into one employment agreement. Google typically separates the arrangement into at least two main documents: an offer letter and a separate employment agreement, often accompanied by a Proprietary Information and Inventions Agreement (PIIA) that functions as a third distinct document.

The offer letter covers the basics — your title, start date, compensation, and equity grant summary. The employment agreement handles the legal obligations. The PIIA handles IP and confidentiality obligations specifically. When you're reviewing your package, you need to read all of them. Missing the PIIA because you were focused on the offer letter is one of the most common mistakes candidates make.

IP Assignment and the PIIA

The PIIA is arguably the most consequential document in the stack for engineers. Agreements at Google generally include broad invention assignment language — anything you conceive or reduce to practice that relates to Google's actual or anticipated business, or that uses Google equipment, time, or information, is typically assigned to Google.

The prior inventions schedule is your friend here. Before you sign, list any personal projects, side work, or inventions you want to preserve ownership of and attach that list. What you don't list, you may be assigning away. California Labor Code Section 2870 provides some statutory protection — employers generally cannot require assignment of inventions developed entirely on your own time without using company resources, provided they don't relate to the company's business. But relying solely on the statute without completing the prior inventions schedule is a mistake.

Non-Compete in California

Google is headquartered in California. Under California Business and Professions Code Section 16600, non-compete agreements are generally void as against public policy, with narrow exceptions. This is one of the most employee-friendly non-compete environments in the country.

Agreements at Google generally do not include traditional post-employment non-compete clauses for employees working in California — and even if language existed in an older agreement, California courts would typically refuse to enforce it. That said, confidentiality obligations and trade secret protections remain fully enforceable and can have a similar practical effect. You can go work for a competitor; you just can't take Google's information with you.

Equity: Front-Loaded RSU Vesting

Equity at Google typically takes the form of RSUs (Restricted Stock Units). The standard vesting period is four years, but Google's schedule is generally front-loaded in a specific way — with more shares vesting in years three and four as a retention mechanism.

This is counterintuitive compared to what most people expect. Many companies use a back-loaded approach; Google's approach often delivers larger vesting amounts in the later years of the four-year cycle to incentivize employees to stay. The exact schedule can vary by level, offer date, and negotiation history. What matters is that you understand your specific grant: how many shares, what the vesting dates are, and what happens to unvested shares if you leave before the four years are up (answer: generally, you forfeit them).

Confidentiality Obligations

Even without an enforceable non-compete, confidentiality obligations in agreements at Google are typically broad and survive termination. They generally cover business strategies, product plans, user data, technical information, personnel data, and internal financial information.

The practical implication: after leaving, you should assume you cannot publicly discuss anything you worked on until it has been publicly announced by Google. This is especially important for engineers who worked on products that were never launched — those remain confidential even if the product is dead.

What to Look For

Here's a quick checklist for your review:

• PIIA prior inventions schedule: Complete it with every personal project you want to keep.
• Equity grant details: Confirm your specific vesting schedule in the grant notice, not just the offer letter summary.
• Termination and equity: Understand exactly what happens to unvested RSUs if you resign or are terminated — the answer is typically forfeiture, with no automatic severance of unvested equity.
• Confidentiality duration: How long after your last day do these obligations run? Look for the specific language.
• Governing law: Should be California for California employees, which matters significantly for non-compete provisions.
• Dispute resolution: Is there a mandatory arbitration clause? Many large tech companies include one.

The Bottom Line

Agreements at Google typically favor the employer on IP assignment and confidentiality — this is standard in tech, but the details matter enormously if you have side projects or plan to work on adjacent technology after leaving. Paste your employment agreement and PIIA into dott.legal for a free AI risk analysis that flags the clauses most likely to affect you. For high-stakes situations — especially if you have substantial equity or existing IP — attorney-validated review is $349 with 24-hour turnaround.