Is Microsoft Actually Hiring in 2026?

Yes — but the answer depends entirely on which team you are targeting. Microsoft is not running a company-wide freeze, and it is not running open hiring across the board. The current reality is a deliberate bifurcation: some divisions are paused, others are among the most actively recruited teams in global technology.

In March 2026, Microsoft executives directed managers in Azure cloud operations and North American sales to pause new hiring searches. The instruction was reported by The Information and confirmed by Reuters. It is real. It is also division-specific.

At the same time, Microsoft committed more than $80 billion in AI data centre capital expenditure for fiscal year 2025, with Bloomberg projecting FY2026 capex exceeding $100 billion. The engineering and research teams building against that investment — Copilot, Azure AI Foundry, Azure OpenAI Service, Microsoft Foundry, and Microsoft Research — were explicitly exempt from the March freeze. As of June 25, 2026, Microsoft Research alone carried more than 175 open positions.

Microsoft's workforce timeline, 2023–2026

1. January 2023

   10,000 layoffs — Microsoft's largest reduction since 2014, driven by post-pandemic over-hiring correction.

2. 2024

   Gaming division restructure following the Activision Blizzard acquisition; several hundred roles eliminated.

3. May 2025

   6,000 layoffs across all levels and teams. Company cited AI investment reallocation, not performance, as the driver.

4. July 2025

   9,000 additional layoffs — approximately 4% of total headcount. Microsoft's largest single reduction in 2025.

5. Late 2025

   Nadella signals selective hiring resumes with an "AI-powered leverage" philosophy — fewer roles, higher individual output via AI-augmented workflows.

6. February 2026

   Hybrid policy formalised: 3 days per week in-office for employees based near a Microsoft campus. Remote-designated roles continue unchanged.

7. March 2026

   Selective hiring freeze: Azure cloud operations and North American sales. AI, Copilot, Foundry, security, and research teams remain fully active.

8. June 2026 (ongoing)

   175+ Microsoft Research openings confirmed. AI engineering recruitment active. Fiscal year ends June; post-FY hiring patterns expected to reset from July.

Hiring Status by Division (June 2026)

Use this reference before investing preparation time. Status is based on multi-source reporting as of June 28, 2026, and may shift after Microsoft's fiscal year closes. Verify any specific listing directly on careers.microsoft.com.

How to Apply: Eightfold AI, Not Workday

The most widely repeated mistake in Microsoft application advice is telling candidates to optimize their resume for Workday. Microsoft uses Eightfold AI as its applicant tracking system. The two platforms parse resumes differently and weight skill signals differently. Optimizing for the wrong system means your resume may be mis-scored before any human reviews it.

When you upload your resume to careers.microsoft.com, Eightfold's parser extracts your name, skills, experience, education, and certifications, then auto-populates your candidate profile. Microsoft discloses this on its Transparency FAQ page — one of the few major tech employers to state AI's role in the screening process publicly.

Four actions that improve your Eightfold match score

• Review the auto-filled profile before submitting. Wrong skill tags, misread dates, or a missed certification can misrepresent your qualifications before any human sees your application.
• Use canonical skill names. "Python," "Azure DevOps," "CI/CD" parse correctly. Creative paraphrases like "cloud automation scripting" may not surface under the right skill category.
• Use standard section headers. "Work Experience," "Education," "Certifications" signal clean structure to the parser. Creative headings like "My Journey" break extraction logic.
• Mirror the exact language in the job description. Eightfold scores fit between your profile and the posting. If the JD says "distributed systems at scale," use that phrase — not a synonym.

Referrals: useful, not decisive

An employee referral at Microsoft is visible to the recruiting team through the Action Center. Community sources consistently report that referrals improve the likelihood of a human review, particularly for high-volume postings. The bar for every interview stage remains identical regardless of referral status — a referral gets your resume read; it does not bypass any round.

Microsoft Talent Network

Candidates not ready to apply can create a lightweight Talent Network profile — a job-alert subscription without a full application. This enables Microsoft recruiters to surface your profile for future roles and delivers alerts when new positions open in your target area. It is worth setting up if your target division is currently paused.

The Interview Process, Step by Step

Microsoft's standard technical hiring process runs six stages. The total timeline is typically four to six weeks. In 2026, the average time from a final interview to a hiring decision is 16.8 days — slower than the roughly ten-day pace in 2023. Around 68% of candidates hear back within two weeks of their final round.

1. Recruiter Screen

   A 20–30 minute phone call to confirm basic qualifications. No trick questions. Ask the recruiter for the specific team and product area — if they don't volunteer it, ask directly. Tailoring your examples to that product is one of the highest-leverage preparation actions available, and most candidates skip it. The recruiter also determines your pathway: online assessment, phone screen, or straight to the Loop.

2. Online Assessment — Codility

   Most engineering roles include a timed coding assessment on Codility lasting 60–90 minutes with two to four problems. Difficulty ranges from LeetCode Medium to Hard. Codility provides a plain text editor: no autocomplete, no syntax highlighting, no compiler feedback. Practice in a plain environment beforehand — the friction surprises candidates who only ever code in an IDE. Non-engineering roles may have a different or no assessment.

3. Phone / Technical Screen (not universal)

   A 30–45 minute virtual interview via Microsoft Teams covering one or two coding problems alongside behavioral questions. Microsoft allocates notably more time to behavioral content in phone screens than most peer companies do — prepare STAR-format stories even at this stage. For experienced-hire roles, this may include a short written coding exercise followed by a verbal explanation session.

4. The Loop — Four to Five Rounds, One Day

   The Loop is Microsoft's main interview block: four to five back-to-back rounds in a single day, conducted virtually in most cases, each lasting 45–60 minutes. A standard engineering Loop includes DSA (data structures and algorithms) rounds, a low-level design (LLD) round focused on object-oriented design, a system design round for L62 and above, and a behavioral round. Every interviewer assesses technical ability and Growth Mindset simultaneously — not just the behavioral round.

5. The AA Round (As Appropriate) — dedicated section follows

   Triggered only when the Loop panel votes "Hire." A Director, Principal PM, or Partner-level leader conducts this final interview. It carries full veto power. One in seven candidates who pass the Loop fails here. The section below covers the AA in full because it deserves its own treatment — not a footnote.

6. Offer and Negotiation

   After a successful AA, a verbal offer follows within three to five business days. A written offer letter typically arrives three to seven days later, depending on executive approvals and background checks. Data centre roles require a Microsoft Cloud Background Check that repeats every two years. The highest-leverage negotiation move for external hires is arguing for a higher level placement (L60 vs. L59) before signing — the financial gap between bands far exceeds anything achievable through within-band negotiation.

Interview timeline at a glance

The AA Round: The Most Misunderstood Stage in Microsoft Hiring

The As Appropriate (AA) interview is conducted by a Director, Principal PM, or Partner-level leader. It is triggered only when the Loop team votes "Hire." It is not a rubber stamp. It carries full veto power over the Loop result — even a unanimous strong Loop can be overturned at the AA.

The statistics matter: approximately 30% of candidates who complete the Loop advance to the AA round. Of those, approximately 85% receive an offer. That means roughly one in seven candidates who pass the Loop are still rejected. The AA is where technically strong candidates who delivered generic behavioral content lose their offer.

What the AA interviewer is actually assessing

The AA focus is behavioral depth, leadership signal, and organizational risk — not technical retesting. A Director running an AA is implicitly asking: Can this person grow into greater scope? Will they be constructive across teams? Does any signal suggest a management problem, a culture problem, or an early departure risk? The technical evidence was gathered in the Loop. The AA uses behavioral depth to pressure-test the Loop's conclusion.

The four mistakes candidates make in the AA

• Reusing Loop examples. AA interviewers sometimes compare notes with Loop panelists. Using the same stories signals shallow experience depth. Prepare a completely separate set of behavioral examples for the AA.
• Treating it as a formality. "I've already passed the Loop" is the most common mindset that produces underperformance here. The AA starts the clock over.
• Giving polished success narratives only. AA interviewers specifically probe failure, conflict, and ambiguity handling. An unbroken sequence of successful outcomes reads as selective editing or limited scope.
• Not researching the AA interviewer. A Director-level interviewer has a public professional history. Knowing what they built or which teams they have run helps you frame examples that resonate with their perspective.

The Growth Mindset Requirement: What Microsoft Actually Scores

Growth Mindset is not a soft HR concept at Microsoft. It is a scored competency with a rubric applied at every interview stage and every level — from L59 interns to Partner-level hires. Satya Nadella restructured Microsoft's culture from "know-it-all" to "learn-it-all" after taking over as CEO in 2014, and the hiring process was explicitly rebuilt around this shift.

Microsoft's "How We Hire" page lists four core values: Respect, Integrity, Accountability, and Growth Mindset. Every interviewer in the Loop and the AA is scoring Growth Mindset signals alongside technical performance. A strong DSA performance paired with flat behavioral content is not a "Hire" vote at L62 and above.

What the rubric looks for, by level

One clarification that distinguishes well-prepared candidates: Microsoft's Leadership Principles — Create Clarity, Generate Energy, Deliver Success — are a separate framework used primarily for managers. Many preparation guides conflate them with the Growth Mindset rubric used in interviews. Knowing the distinction signals genuine familiarity with Microsoft's culture, which itself reads as a positive signal in the behavioral round.

Microsoft Engineering Levels: L59 to L70 Explained

Microsoft does not publish an official level-to-title map. The table below reflects the community consensus from levels.fyi, Blind, and Reddit as of June 2026. All mappings are community-confirmed estimates — not official Microsoft data.

The L63 terminal level: a feature, not a ceiling

L63 is one of the most consequential and least-understood details of a Microsoft engineering career. Microsoft explicitly designed it as a stable landing point — engineers can remain Senior SDE for the duration of their career with no organizational pressure to pursue Principal or management tracks. This is uncommon in tech, where many employers apply informal "up or out" norms at the senior level. For engineers who prefer deep technical specialization, L63 is a deliberate destination.

The L59 vs. L60 placement argument

Microsoft sometimes withholds the level designation from candidates during the process — a documented community pattern. If you hold a master's degree, one to two years of relevant experience, or a Microsoft internship on your record, make the case for L60 placement before signing an offer at L59. The total compensation gap between the two bands is substantially larger than any within-band improvement achievable through negotiation. This is the most financially impactful lever available to early-career Microsoft candidates, and very few guides cover it explicitly.

Salary and Total Compensation

Total compensation by engineering level — Redmond, WA (community-reported)

Total compensation (TC) includes base salary, annual RSU vesting, and target performance bonus. Sign-on bonuses are separate.

How total compensation is structured

• Base salary: Fixed; set within a band for each level. Negotiable up to the band ceiling before signing.
• RSUs (Restricted Stock Units): 4-year vesting, 1-year cliff, then quarterly. RSUs become a proportionally larger share of TC at L63 and above.
• Performance bonus: Target typically 10–25% of base, depending on level. Paid based on Connects review scores.
• Sign-on bonus: Common for external hires. Often $15K–$25K at L59–L60. Separate from base and RSUs, and negotiable.
• RSU refresh grants: Awarded through the bi-annual Connects review cycle. Consecutive strong Connects scores compound over time — this is the most underappreciated financial mechanic of a Microsoft career.
• ESPP: Buy Microsoft stock at a 10% discount; contribute up to 15% of pay per period.
• 401(k) match: Approximately 50% of employee contributions up to plan limits.
• Mega Backdoor Roth: Available via Fidelity NetBenefits for employees who maximize the standard 401(k) limit.
• Deferred Compensation Plan (DCP): Available at L67 and above; allows tax-advantaged deferral beyond 401(k) limits.
• "55 and 15" RSU rule: If you leave Microsoft at age 55 or older with at least 15 years of service, unvested RSUs may continue vesting on their original schedule post-departure.

Skills and Certifications Microsoft Wants in 2026

Most demanded programming languages

• Python
• C#
• TypeScript / JavaScript
• C++
• Java
• SQL
• PowerShell / Bash
• Rust (emerging)

Most demanded cloud and AI capabilities

• Azure AI Foundry
• Azure OpenAI Service
• Copilot platform development
• MLOps & Responsible AI
• Microsoft Fabric
• Azure Databricks
• LangChain / Semantic Kernel
• PyTorch / TensorFlow
• GitHub Copilot / GitHub Actions
• Enterprise system design

Microsoft certification roadmap — 2026 current state

Graduate and Early Career Programmes

Microsoft runs six structured early career pipelines that are significantly under-covered in mainstream hiring content. If you are a student or recent graduate, these routes are more strategic than a cold application to a standard open role — they come with cohort support, structured onboarding, and learning frameworks that standard external hires do not receive.

Benefits Package 2026

Microsoft's benefits are widely considered among the strongest in the technology industry. Three specific changes took effect in 2026 that anyone evaluating an offer should account for explicitly before signing.

Visa Sponsorship: H-1B and Green Card

Microsoft sponsors H-1B visas and is one of the largest sponsors in the United States. In fiscal year 2025, Microsoft recorded 5,189 H-1B approvals with a 98.4% approval rate, according to US Department of Labor and USCIS filings. The median salary for sponsored positions at Microsoft is $152,620. Sponsorship is concentrated in software engineering, AI, cloud computing, data science, and product development roles.

Microsoft is not classified as an H-1B-dependent employer — meaning it maintains a qualifying ratio of US workers to foreign nationals and faces fewer additional compliance requirements than dependent employers. This is operationally relevant: H-1B-dependent employers face additional attestation requirements that can slow or complicate individual sponsorships.

Green card (PERM) sponsorship

Microsoft sponsors PERM green card petitions for eligible employees, typically after a period of H-1B employment. In fiscal year 2025, Microsoft filed 60 PERM petitions with the Department of Labor. The green card timeline depends on the employee's priority date, country of birth, and role category — variation is substantial enough that candidates should consult an immigration attorney for their specific situation rather than relying on general guidance.

Where Microsoft Is Hiring Globally

Common Mistakes Microsoft Candidates Make

Application and resume mistakes

• Optimizing for Workday instead of Eightfold AI. The platforms differ in parsing behavior and skill scoring. This is a correctable mistake with a direct impact on whether your resume surfaces to a recruiter at all.
• No quantified outcomes. "Improved system performance" tells an interviewer nothing. "Reduced p99 latency by 43% across three regional clusters serving 2M daily users" communicates scope, method, and impact. Every bullet point needs a number, a scale, or a denominator.
• Writing scope language for a level below your target. An L62 resume describes feature ownership, technical trade-off decisions, and cross-team coordination. An L60 resume describes assigned task completion. If your language reflects L60 scope while you are targeting L62, both the Eightfold system and the recruiter will calibrate to the lower level.
• Not reviewing the auto-filled Eightfold profile. Misread dates or missing certifications in the parsed profile can materially misrepresent your qualifications before any human review.

Interview mistakes

• Preparing only for coding. Microsoft's behavioral bar is demonstrably higher than at most peer companies. Candidates who practice only LeetCode and then give flat behavioral answers consistently fail in the Loop or the AA — even with strong technical scores.
• Reusing Loop examples in the AA. AA interviewers sometimes compare notes with Loop panelists. Using the same stories signals experience depth that is narrower than the level warrants.
• Underestimating the AA because you passed the Loop. The AA has full veto power. One in seven Loop successes is rejected here. Treat the AA as if the clock resets.
• Not researching the specific team. A Copilot team interview values different examples than an Azure infrastructure or Xbox interview. Tailoring your behavioral examples to the product is one of the highest-leverage preparation steps available — and most candidates skip it.
• Performing Growth Mindset language rather than demonstrating it. Saying "I have a growth mindset" scores nothing. Describing a specific failure, the causal analysis you ran, the specific behavior you changed, and the measurable outcome that followed — that is what interviewers record as a positive signal.

Offer and negotiation mistakes

• Accepting L59 without arguing for L60. The financial gap between bands far exceeds the maximum achievable within-band improvement. The level placement argument is the highest-leverage negotiation move available to early-career Microsoft candidates.
• Not modeling the RSU compounding effect. Two engineers at the same level who join on the same day can diverge significantly in total compensation within three years based purely on Connects performance and RSU refresh accumulation. Knowing this changes how you should evaluate an offer and how much attention you should pay to early performance reviews.

Should You Apply to Microsoft Right Now?

Use this framework to assess whether your target team and timing align with the current hiring landscape.

Frequently Asked Questions

Summary: What to Do Before You Apply

Microsoft's 2026 hiring environment rewards preparation more than application volume. The company is smaller, more selective, and more AI-focused than two years ago — but it is actively hiring for the roles that will define its next decade. The gaps that eliminate most candidates are behavioral and informational, not purely technical.

The three decisions that move the needle most before you apply: confirm your target division's current status, optimize your resume for Eightfold AI rather than Workday, and prepare a completely separate behavioral story set for the AA round. These are the gaps that most guides miss, and they directly affect the outcome.

• ✓Confirm your target division's current hiring status using the Division Map above
• ✓Optimize resume for Eightfold AI: canonical skill names, standard section headers
• ✓Review your auto-filled Eightfold candidate profile before submitting
• ✓Prepare 3+ Growth Mindset stories: specific failure → causal reflection → behavior change → measurable outcome
• ✓Practice Codility-style coding in a plain text editor with no autocomplete
• ✓Research the specific team and product area before your recruiter screen
• ✓Prepare a completely separate behavioral story set reserved for the AA round
• ✓Know the L59 vs. L60 level placement argument before the offer stage
• ✓Verify all certifications are current: AI-900 retired June 30, 2026 — use AI-901 instead
• ✓If applying internationally: confirm H-1B sponsorship is included in the specific job description