How Microsoft pays: salary ranges, bonuses and stock awards

If you are interviewing at Microsoft or already work there, you can check your offer or your pay against numbers Microsoft publishes itself. This guide shows you where those numbers live, how to read a Microsoft pay range for your level and location, and what to ask a recruiter so you know where an offer actually sits.

Everything here comes from Microsoft's own careers pages, its 2026 proxy statement filed with the SEC, and the Department of Labor's visa data. No crowdsourced salary sites.

The parts of a Microsoft offer: base, bonus and stock awards

Microsoft's US corporate pay page describes the pieces in plain terms. Every job has base pay. On top of that, Microsoft says certain roles are eligible for merit increases, an annual bonus and stock, and that these awards are allocated based on individual performance. Some roles can also earn sales incentives tied to revenue or utilization, under the terms of the plan for that role.

Here is how those pieces fit together:

Notice the word "certain." Microsoft does not promise a bonus or stock to every hire, and the posting itself only says that some roles may be eligible for other compensation. So the base range in a posting is the one number you can treat as firm. Bonus and stock are things you confirm in writing at offer stage.

If stock awards are new to you, our company pay section covers how restricted stock units work, how vesting and taxes play out, and how to value a grant.

Where Microsoft publishes base pay ranges

Microsoft prints a base pay range in its US job postings. You will find them in two places:

• The job posting itself, near the bottom, just after the qualifications.
• Microsoft's location and program pages on careers.microsoft.com, such as the Seattle, New York, Atlanta, DC metro and datacenter pages, which show recent postings in full, including the pay paragraph and the date shown on the listing.

Each posting links to the US corporate pay page, which explains the rules behind the numbers. Three points on that page matter most for you:

1. The range covers potential base pay across the US for that role, and your range depends on what Microsoft decides is your primary work location.
2. Where you land inside the range depends on things like the complexity of the role, its duties and requirements, and your relevant experience and skills.
3. Ranges are reviewed and typically updated each year, and "Offers are made within the base pay range applicable at the time."

That last line is useful. If a recruiter quotes a base above the top of the posted range for your location, something is off: a different level, a different location, or a range that has since been updated. Ask which.

How to read the range in a Microsoft job posting

Every US range paragraph follows the same pattern. Here is how to decode it.

Step 1: Find the discipline and career stage

The paragraph opens with a label such as "Software Engineering IC4" or "Business Planning IC4." Microsoft's corporate pay page explains that a role is defined by two things: the discipline (the type of work) and the career stage (scope and complexity).

The career stage starts with a letter code:

• IC means individual contributor.
• M means manager.
• ATR means admin, technician or retail jobs.
• Interns have their own stage.

The number or letter after it shows seniority. A higher number, or a later letter for ATR roles, means more scope. So IC5 is more senior than IC4, and ATR-C is more senior than ATR-B.

This label is the key to the whole range. The job title ("Senior," "Principal") is a hint, but the career stage code is what the pay range is attached to.

Step 2: Read both ranges

Most US postings give two ranges. The first is the "typical base pay range for this role across the U.S." The second applies to what Microsoft calls "a different range applicable to specific work locations": the San Francisco Bay Area and the New York City metropolitan area.

That is Microsoft's own wording in the posting. It does not list other cities with their own ranges, so if you will be based in Redmond, Atlanta, Austin or working remotely elsewhere in the US, the first range is the one shown for you.

Step 3: Compare with real postings

Here are ranges from US postings shown on Microsoft's careers pages, with the date on each listing and the location as Microsoft lists it. "+2 more" means the posting names additional possible locations.

Sources: Microsoft careers Seattle area, New York, Atlanta and DC metro pages, read October 28, 2026. The date is the one shown on the listing, which Microsoft marks with an update icon, so it may reflect an update rather than the first day the job went live.

Hourly roles work the same way, just per hour. A Logistics Technician posting in San Antonio, Texas, dated 2026-10-28 on Microsoft's datacenter careers page, gave two levels:

What the table tells you

A few patterns stand out once you line the postings up.

• The range follows the level, not the team. The IC4 software engineering role and the IC4 data science role show identical ranges. If you know your level, you can often find the range from any posting at that level in a similar discipline.
• Disciplines differ. At IC4, the business planning range and the business program management range are not the same as the engineering range. Compare like with like.
• Some postings cover two levels. The logistics posting lists both ATR-B and ATR-C. When a posting shows two stages, ask which one your offer is at, because the range changes.
• The ranges are wide. For the US IC4 engineering range, the top is nearly double the bottom. That width is normal for broad salary bands, but it means "the posted range" alone tells you little about your own number.
• The Bay Area and NYC range is higher and narrower. The bottom rises a lot more than the top does.

Find where an offer sits in the range

A range is just the lowest and highest base Microsoft expects to pay at that level. The midpoint is the number exactly halfway between them. People new to a level often start below the midpoint, and people with deep relevant experience may start above it, but Microsoft does not publish where offers usually land, so treat that as a rule of thumb, not a promise.

To place your offer:

1. Take the range for your career stage and your location.
2. Subtract the bottom of the range from your offered base.
3. Divide that by the full width of the range (top minus bottom).
4. The result is how far up the range you are: near 0 means the floor, near 1 means the ceiling, around half means the middle.

Example (hypothetical): You are offered a Software Engineering IC4 role based in Redmond. You use the US range of $119,800 to $234,700, not the higher Bay Area and NYC range. If your offered base works out to about a third of the way up, you are below the middle, and it is reasonable to ask what would move you higher.

What Microsoft's proxy statement shows about pay

Every year Microsoft files a proxy statement with the SEC before its annual shareholder meeting. The 2026 proxy statement covers fiscal year 2026, which ended June 30, 2026, ahead of a virtual meeting on December 8, 2026.

The median employee figure

The proxy reports that for fiscal year 2026, the annual total compensation of Microsoft's median employee (other than the CEO) was $215,057. The median is the person in the exact middle: half of employees were paid more and half less.

Read that number carefully before you compare yourself with it:

• It is total compensation, not salary. It includes base pay, bonus and the value of stock awards, calculated under SEC rules.
• It is global. Microsoft identified the median from its worldwide workforce, and converted non-dollar pay to US dollars using 12-month average exchange rates.
• It is the same person as last year. Microsoft says it kept the median employee chosen for the 2025 proxy because there were no significant changes in its workforce or that person's pay arrangements. The median was originally picked from employees as of June 30, 2025, using fiscal 2025 base pay, target bonuses and cash incentives, and the value of stock awards granted that year.
• It is one person. It tells you about the middle of a very large and varied workforce, not about any role or level.

The same section puts the CEO's fiscal 2026 total compensation at $90,628,977, a ratio of 421 to 1 against the median employee.

What the executive section tells you about structure

The bulk of the proxy is about the top executives, not regular staff, but it shows how Microsoft thinks about the parts of pay. Executive pay combines base salary, an annual cash incentive and stock awards. For fiscal 2026, the proxy reports a payout of 129.03% of target on the financial-metric portion of executive annual cash incentives, which shows that bonuses at Microsoft can pay out above or below target depending on results.

The executive stock awards granted in September 2025 vest over four years: 25% on August 31, 2026, then 12.5% every six months after that, and vesting depends on staying employed. That schedule is for named executives. Microsoft's public pages do not set out the vesting schedule for employee stock awards, so get yours from your offer letter or award agreement.

The proxy also confirms that the named executives get the same benefits as other full-time employees, and that in the US those include a 401(k) plan, an employee stock purchase plan, health care and life insurance.

Using visa filings as a second check

When Microsoft hires someone on an H-1B visa, it files a labor condition application (LCA) with the Department of Labor. The application states the job, the worksite and the wage Microsoft will pay. The Department of Labor's Office of Foreign Labor Certification publishes this as disclosure data on its performance data page, in quarterly and full fiscal-year releases.

These filings can confirm that base pay for a job title in a specific city matches the posted range. To use them well:

• Download the latest LCA disclosure file and filter the employer name for Microsoft. The files are large spreadsheets, so a spreadsheet program with filters helps.
• Match on worksite city and job title. LCA titles do not always match posting titles, and they usually do not show the career stage code.
• Remember it is base wage only. No bonus, no stock, no benefits.
• Remember a filing is not a hire. An application shows what Microsoft said it would pay, not that someone took the job at that figure.

Treat LCA data as a cross-check. The job posting range is still the most direct, current source for your level. Our salaries by city section has more on comparing pay across metros.

Benefits Microsoft lists that affect total pay

Benefits do not show up in the base range, but they change what a job is worth to you. Microsoft's US corporate pay page lists, for US-based employees:

• Medical, dental and vision insurance
• A 401(k) plan with a company match
• Short-term and long-term disability cover and basic life insurance
• Wellbeing benefits
• Up to 10 scheduled paid holidays per calendar year
• Up to 80 hours of Holistic Health Time Off per calendar year
• Paid vacation of up to 120 hours a year accrued by hourly (non-exempt) employees, while salaried (exempt) employees have Discretionary Time Off, which has no set number of days

The proxy adds an employee stock purchase plan to the list of US benefits. Microsoft's main benefits page also mentions parental leave, education support, product discounts and giving programs.

What the public pages do not give you is the exact 401(k) match formula, the stock purchase discount or your health premiums. Benefits can also vary depending on the type of employment and the country you work in, so ask for the benefits summary for your specific role.

Questions to ask a Microsoft recruiter

Go into the offer call knowing your career stage and the range for your location. Then ask:

• What career stage is this offer at, and which base pay range applies to my work location?
• Where does my base sit in that range, and what would move it higher?
• Is this role eligible for an annual bonus, and what is the target?
• Is there a stock award with this offer? What is its value, and what is the vesting schedule?
• Is there a sign-on or on-hire bonus, and does it have a payback condition if I leave early?
• If the role has a sales incentive, how is it calculated and what share of pay is at risk?
• What is the 401(k) match, and when can I join the stock purchase plan?

A short script for asking where you sit

You can say something like this, by email or on the phone:

"Thanks, I'm excited about this role. I'd like to understand the base a little better. The posting shows a range of [bottom] to [top] for [career stage] in my location. Can you tell me roughly where my offer sits in that range, and what would put me closer to the middle or the upper part?"

If the answer is that you are low in the range, follow up:

"Given my experience with [specific skill the posting asks for], I'd hoped to be closer to the midpoint. Is there flexibility on base, or could a larger stock award or sign-on bonus close the gap?"

If the base truly cannot move, ask whether the stock award or a sign-on bonus can. Our negotiation section has more scripts for offer stage and review time.

What to do next

• Find the job posting for your role and write down the career stage code and both ranges. Do it now, since ranges are updated and postings come down.
• Work out where your offer sits in the range for your primary work location using the four steps above.
• Ask the recruiter for the bonus target, the stock award value and vesting schedule, and the benefits summary in writing.
• If you want a second check, look up Microsoft's recent LCA filings for your city and job title.
• Use the proxy's median figure for context only. It describes Microsoft's whole global workforce, not your role.

For how pay rules and posting laws are changing, follow our pay trends coverage.