How Google pays: base salary ranges, bonuses and equity

If you have a Google offer in hand, or you're about to apply, this guide shows you how to check the numbers against what Google and Alphabet publish themselves. You'll learn how to read the salary range on a Google job posting, what that range leaves out, what Alphabet's proxy statement says about typical pay, and what to ask your recruiter before you sign.

Everything here comes from Google's own careers pages, Alphabet's SEC filings and US Department of Labor data. No crowdsourced salary figures.

The parts of a Google offer: base, bonus and equity

A Google offer for a US role usually has three money pieces plus benefits. Every US posting reviewed for this guide spells out the same formula: a base salary range, then "+ bonus target + equity + benefits."

Equity is the piece you can't see until the offer arrives. Your offer letter sets out the grant value and the vesting schedule, meaning when the units become yours, usually only if you're still employed on each date. Read that schedule rather than assuming an even split across the years. If you're new to RSUs, the company pay section of this site explains how vesting and taxes work.

The key point for now: the range on the posting covers only the first row of that table.

Where Google publishes US base salary ranges

Google posts a salary range on each US-based job listing on its careers site. Its help page on salary ranges explains what that range means, and it's worth knowing Google's own wording:

• Ranges are set by "role, level, and location."
• The range on a posting is the minimum and maximum target for new hire salaries for that position "across all US locations."
• Where you land within it depends on your work location plus skills, experience, and education or training.
• Recruiters can tell you the specific range for your preferred location during the hiring process.
• The posted figures are base salary only and "do not include bonus, equity, or benefits."

Two things follow from that. First, one range covers every US city where the job could sit, so the full spread isn't on offer to everyone. Second, because it's a new-hire range, it says nothing about what people already in the role earn after raises and promotions.

Ranges from postings opened in October 2026

These are the US ranges shown on Google postings opened on Google's careers site in late October 2026. Postings close and get replaced, so treat these as a snapshot, not a pay table.

Notice how wide these are. On the Mid-level Software Engineer posting, the top of the range is about 38% above the bottom. On the Staff Software Engineer posting, the gap is about 45%. A range that wide tells you the band, not your number.

Reading a Google posting: location and level

Each posting gives you three clues. Here's how to use them.

1. The level badge

Near the top, under the location, Google shows a level label such as Mid or Advanced, with a one-line description. Mid is described as "experience driving progress, solving problems, and mentoring more junior team members." Advanced is described in terms of owning outcomes and decision making, solving ambiguous problems and influencing stakeholders.

These are broad bands. Both the Staff and the Senior Staff postings above carry the "Advanced" badge, yet their ranges differ by tens of thousands of dollars at each end. The job title and the minimum qualifications narrow it down. For example, the Mid Software Engineer posting asks for 2 years of experience, while the Staff and Senior Staff postings ask for 8 years of programming plus 5 years of design and architecture.

The bonus target moves with seniority too. On the postings above it's 15% at Mid, 20% on the Staff role and 25% on the Senior Staff role.

2. The location list

Many postings carry a note that you can share your preferred working location from a list. The GSRS program manager posting, for instance, lists Sunnyvale, Atlanta, Chicago, New York, Los Angeles, Washington DC and Austin, yet it shows one range: $128,000 to $187,000.

Google's help page tells you why: the range spans all US locations, and location is one of the things that sets your pay within it. Google doesn't publish the city-by-city sub-ranges, so this is the single most useful thing to ask a recruiter for.

A single-city posting doesn't change this. The Mid Software Engineer role lists only Mountain View, but by Google's own description the printed range is the US-wide new-hire range for the position.

3. The fine print

Postings repeat that individual pay depends on job-related skills, experience, and relevant education or training. Some also include a benefits list "in accordance with Washington state law," which is handy even if you're not in Washington (more on that below).

Example: turning a range into a plan

Hypothetical example. Say you're offered the Mid-level Software Engineer job in Mountain View with a base of $180,000. That sits a little below the middle of the posted $152,800 to $211,000 range, whose midpoint is $181,900.

If the 15% bonus target is calculated on base (confirm this with your recruiter), your target bonus would be $27,000, for $207,000 in target cash before equity and benefits. The bonus is a target, so the actual payout can differ.

What you'd want to find out next: the range for Mountain View specifically, the level you've been placed at, and why you're at that point in the band.

What Alphabet's proxy statement reveals

Public companies must report the pay of their median employee each year in the proxy statement. "Median" means the person in the middle: if you lined up every employee by pay, half would earn more and half less. It's a better guide than an average, which a small number of very high earners can drag up.

From Alphabet's 2026 proxy statement:

• Median employee pay, fiscal year 2025: $310,826 in annual total compensation.
• CEO pay, 2025: $10,906,079, giving a ratio of 35 to 1.

How Alphabet got there matters when you compare it with your offer:

• It looked at all Alphabet employees (excluding the CEO) as of December 31, 2025. That's a global group, not just the US, and it covers Alphabet as a whole, not only Google.
• It picked the median person using base salary plus target bonus, then calculated that person's total pay the same way it reports executive pay. That total includes the grant-date value of stock awards.

So the $310,826 figure is base, bonus and equity combined for one person in the middle of a worldwide workforce. It's not a typical base salary, and it's not a number to expect for any particular job. Use it as context, not a benchmark. For more on how pay ratios are calculated, see the pay trends section.

The proxy also lists the benefits executives share with all employees, which is useful for a candidate (see the benefits section below).

Checking pay with visa filings

When a US employer hires someone on an H-1B, H-1B1 or E-3 visa, it files a Labor Condition Application (LCA) with the Department of Labor stating the wage it will pay. The DOL's Office of Foreign Labor Certification publishes these as quarterly disclosure files on its performance data page.

The record layout for the worksite file shows which fields you get. The useful ones for a pay check:

• WAGE_RATE_OF_PAY_FROM and WAGE_RATE_OF_PAY_TO: the wage paid at the worksite, with a unit (hour, week, bi-weekly, month or year).
• PREVAILING_WAGE: the prevailing wage for the job at that location.
• PW_WAGE_LEVEL: levels I to IV where the employer used the OES wage data.
• WORKSITE_CITY and WORKSITE_STATE: where the job is.

How to use it:

1. Download the latest cumulative file for the most recent fiscal year from the DOL page. The federal fiscal year starts October 1; the FY2026 first-quarter file, for example, covered October 1 to December 31, 2025.
2. Filter on Google's employer name. Check for more than one legal entity name.
3. Filter by a job title close to yours and by your city.
4. Compare the wage rates with the posting range and with your offer.

Know the limits. These are wages employers attest to on an application, not confirmed paychecks, and a filed LCA doesn't mean anyone was hired. The file has wage fields only, so bonus and equity aren't there. Job titles in filings may not match posting titles. Treat this as a cross-check for base pay in a specific city, which is exactly what the posting doesn't show you.

Benefits Google lists that affect total pay

Google's main benefits page on its careers site loads its content dynamically and didn't display details when checked for this guide. Two primary sources fill the gap.

What Washington-compliant postings list

Postings that include the Washington state law notice, such as the GSRS program manager role, say these benefits are available to all eligible US-based employees:

The 401(k) match

Alphabet's 2026 proxy describes the 2025 match: the greater of 100% of your contributions up to $3,000, or 50% of contributions up to $23,500, for a maximum match of $11,750. The match was fully vested when contributed, so you didn't have to stay a set number of years to keep it.

Hypothetical examples using the 2025 formula:

• You put in $5,000: 100% of the first $3,000 gives $3,000; 50% of $5,000 gives $2,500. You'd get the larger amount, $3,000.
• You put in $10,000: 50% gives $5,000, which beats $3,000.
• You put in $23,500: 50% gives the maximum $11,750.

The formula is tied to the IRS contribution limit and can change each year, so ask for the current plan year's match.

The proxy also lists flexible spending accounts, life and travel insurance, a survivor income benefit, an employee assistance program and a matching gift program among the plans all employees can join, and says Alphabet pays life insurance premiums for all employees (with two named exceptions).

Questions to ask a Google recruiter

Recruiters expect questions. Clear ones get you clearer answers.

On the range

• "What's the base salary range for this level in [city]?"
• "Where in that range does this offer sit, and what would move it higher?"

On level

• "What level is this offer at, and how did you decide that?"
• "What would I need to show to be considered at the next level?"

On bonus and equity

• "Is the bonus target a percentage of base, and how has payout compared with target?"
• "What's the RSU grant value, how was it converted into units, and what's the vesting schedule?"
• "Is there a sign-on bonus, and does any of it have to be repaid if I leave early?"

On benefits

• "What's the 401(k) match formula for the current plan year?"
• "Which benefits start on day one?"

A short script for level placement

Level drives your range, your bonus target and usually your equity, so it's worth raising before you talk numbers.

"Thanks, I'm excited about this role. Before we get into the numbers, I'd like to understand the level. My background includes [X years doing Y, plus one concrete result]. The posting's minimum qualifications look closer to [describe], and I want to make sure the level reflects that. Could you share how the level was decided, and whether the hiring team would consider [next level]?"

If the answer is no, follow up with: "Understood. Could you share the range for this level in [city], so I can see where the offer sits?" That keeps the conversation going without boxing anyone in. It won't guarantee a change, but it puts the reasoning on the table. The negotiation section has more scripts.

What to do next

• Open the posting for your role and note the range, level badge, bonus target and listed locations. Save a copy, as postings come down.
• Ask your recruiter for the range in your city and your level placement.
• Put your offer in a simple table: base, target bonus, RSU value and schedule, sign-on, and 401(k) match.
• Cross-check base pay for your title and city in the DOL disclosure file.
• Read the vesting schedule and any repayment terms in your offer letter before you sign. If anything's unclear on equity taxes or repayment clauses, a tax professional or employment lawyer can review it.