There is a particular irony embedded in the modern hyperscaler hiring machine. AWS, Google, and Microsoft did more than any other institutions to create the infrastructure of compensation transparency: internal L-band ladders with documented pay ranges at each level, public H-1B wage filings that leaked base salary data into the market, and an implicit endorsement of the crowdsourced benchmarking culture that made Levels.fyi the de facto comp bible for every senior engineer in North America. Then California passed SB 1162 in September 2022, effective January 2023, and required every employer with fifteen or more workers to post salary ranges on job listings. AWS, Google, and Microsoft — companies that had spent years telling engineers their pay was built on transparent, equitable L-band frameworks — responded by posting ranges so strategically constructed that they reveal almost nothing useful about what a candidate will actually earn.
This is not incidental. It is architectural. State salary disclosure laws require employers to post what they expect to pay in base salary for a given position. They do not require employers to disclose annual RSU grants, equity refresh schedules, or performance bonuses — which at senior levels in AWS Bedrock, GCP Vertex AI, and Azure ML constitute anywhere from 40 to 65 percent of total compensation. A Google L6 SWE can be handed a legally compliant job posting in California disclosing a salary range of $222,000 to $336,000, accept an offer in that range, and ultimately receive $629,000 in annual total compensation once equity vests. The posted range is factually accurate. It is also analytically useless.
Three and a half years after SB 1162 took effect, the gap between what state salary disclosure laws capture and what senior IT engineers at hyperscalers actually receive averages $131,000 for L6 equivalent roles — the difference between a posting's ceiling and the Levels.fyi total compensation median for the same level at the same company. That figure is not a negotiation outcome variable. It is structural: baked into every hiring cycle by the combination of legal compliance minimums and compensation architectures that front-load equity in ways the disclosure laws were never designed to see.
California tried to close the gap. Senate Bill 642, signed in 2025 and effective January 1, 2026, amended the definition of "pay scale" to mean a "good faith estimate" of what an employer "reasonably expects to pay for the position upon hire" — language specifically designed to prevent the $90,000-to-$900,000 Netflix-style absurdities that made headlines when SB 1162 first took effect. The fix works for its narrow purpose: posted base salary ranges at hyperscalers are now narrower and more internally consistent than they were in 2023. What SB 642 cannot do is require employers to disclose equity, because equity is categorically outside the statute's reach. For an L6 Staff SWE at Google or a Principal SDE at AWS Bedrock, that omission is the entire story.
What AWS, Google, and Microsoft Post vs. What They Pay
The table below presents base salary ranges as disclosed in current job postings on LinkedIn and company career sites for L5-to-L6 equivalent engineering roles at the three hyperscalers, the three dominant enterprise SaaS employers, and Cloudflare as a mid-tier infrastructure benchmark. The Levels.fyi Median column represents total compensation — base salary, annual cash bonus, and annualized RSU grant — as reported by Levels.fyi crowdsourced submissions in August 2026. Range Width is the arithmetic difference between posted maximum and posted minimum. The disclosure gap — the distance between what is posted and what is paid — is discussed in the following sections.
| Company | Role | State | Posted Low | Posted High | Levels.fyi Median | Range Width | |---------|------|-------|-----------|------------|-------------------|------------| | AWS | Senior SDE (L5) | WA | $129,300 | $219,700 | $271,000 | $90,400 | | AWS | SDE III (L6) | CA | $161,900 | $259,900 | $390,000 | $98,000 | | Google | L5 SWE | CA | $185,000 | $248,000 | $404,000 | $63,000 | | Google | L6 SWE | CA | $222,000 | $336,000 | $629,000 | $114,000 | | Microsoft | Senior SDE (L63) | WA | $113,900 | $171,500 | $233,000 | $57,600 | | Microsoft | Senior SDE (L64) | WA | $125,000 | $187,700 | $281,000 | $62,700 | | Salesforce | Senior SWE | CA | $168,800 | $266,400 | $300,000 | $97,600 | | ServiceNow | Senior SWE | CA | $161,100 | $254,400 | $260,000 | $93,300 | | Workday | Senior SWE | CA | $162,400 | $256,700 | $268,000 | $94,300 | | Cloudflare | Senior SWE | CA | $168,000 | $248,000 | $263,000 | $80,000 |
Posted Low / Posted High: base salary ranges as disclosed on LinkedIn job postings and company career sites, collected August 2026, under CA SB 1162, CO EPEWA, and WA EPOA disclosure requirements. Microsoft L63/L64 figures reflect Washington state postings cross-referenced against publicly reported internal pay band documents. Levels.fyi Median: total compensation (base + bonus + annualized RSU), Levels.fyi crowdsourced data, August 2026. Salesforce, ServiceNow, Workday, and Cloudflare TC medians derived from Glassdoor 25th–75th percentile base data, Levels.fyi reported ranges, and ENTRA senior band estimates. All figures in USD.
The table makes the structural inequality legible in a way that individual data points cannot. At Google, the L6 SWE disclosed ceiling is $336,000. The Levels.fyi total comp median for that role is $629,000. A candidate who negotiates to the very top of the posted range — a best-case scenario that most offers will not achieve — is still $293,000 below median total compensation. No amount of reading the job posting tells them that. At AWS, an L6 SDE III posted ceiling of $259,900 conceals $130,100 in total compensation. Microsoft L64 posts a ceiling of $187,700 against a $281,000 total comp median: a $93,300 gap that is the smallest of the three hyperscalers but still represents equity and bonus compensation invisible to any candidate relying on the disclosure alone.
The enterprise SaaS companies tell a different story. Salesforce, ServiceNow, and Workday post ranges that are slightly wider than Google's L5 row — but their total compensation medians are far closer to their posted ceilings. Salesforce's $266,400 ceiling against a $300,000 total comp median leaves a $33,600 gap. ServiceNow's $254,400 ceiling against a $260,000 total comp median produces a rounding-error gap of $5,600. Workday's $256,700 ceiling against $268,000 total comp means its posted range captures 95.8 percent of actual compensation. These companies are not more virtuous in their disclosure design — they are structurally less equity-heavy than hyperscalers, which means the base salary range a law requires them to post actually describes most of what they pay.
Range Width Analysis
Range width — the arithmetic distance between a posting's minimum and maximum — is the metric most often cited in compliance debates, because it is the one regulators can measure without knowing what employees actually earn. By this measure, the ranking of most to least transparent runs in a direction that may surprise: Microsoft is narrowest, followed by Google at L5, followed by Cloudflare, then enterprise SaaS, then AWS.
Microsoft L63 posts a base range of $113,900 to $171,500 — a $57,600 window. Microsoft L64 runs $125,000 to $187,700 — a $62,700 window. Google L5 posts $63,000 of width in California. These are the tightest ranges in the sample and, by the only metric state law can evaluate, the most compliant. AWS L6 in California runs $98,000 wide. Google L6 — where a single role spans roughly two seniority tiers in practice — runs $114,000 wide, the widest in the dataset.
The average posted range width across hyperscalers (all six rows) is $80,950. The average across enterprise SaaS is $95,067. This is the counterintuitive finding: enterprise SaaS companies post wider base salary ranges than hyperscalers, but they have smaller disclosure gaps because the total compensation is closer to the posted base. California's SB 642 tightened the "good faith" language to prevent absurdly wide ranges, and the post-SB 642 data confirms the law worked for its stated purpose — the $90,000-to-$900,000 outliers are gone. What SB 642 cannot fix is the fact that a narrow, precise, and legally impeccable salary range can still be fundamentally misleading when it describes 38 percent of what an employee receives.
Geography compounds the problem by reducing comparability across postings. Comparing AWS's California L6 SDE III ($161,900–$259,900) against Washington L5 Senior SDE ($129,300–$219,700) reveals a combined geography-and-level effect — the ~19% range reduction reflects both geographic adjustment and a level step, not purely location pricing. For Austin, Texas, where no state salary disclosure law applies and Amazon posts only because its own policy requires it, the estimated L5 band typically runs $115,000 to $196,000 — another 10 percent below the Seattle L5 band. The estimated L5 band in Raleigh, North Carolina comes in around $107,000 to $183,000. The posted ceiling gap between California's L6 SDE III and an estimated L5 Raleigh posting runs approximately $76,900 — a figure that means the combined geography-and-level premium in itself exceeds most salary negotiation outcomes.
Enterprise SaaS vs. Hyperscaler Benchmarks
The comp gap between hyperscalers and enterprise SaaS for equivalent-seniority engineering roles is real, persistent, and wider at senior levels than the posted salary ranges suggest. For a Senior SWE at L5 seniority — the level where engineers typically have five to eight years of professional experience and ownership of production systems — the Levels.fyi total comp median runs $404,000 at Google, $271,000 at Amazon L5, and $233,000 at Microsoft L63. Salesforce's equivalent senior SWE median of $300,000 sits above Amazon but well below Google, while ServiceNow ($260,000) and Workday ($268,000) run 32 to 36 percent below Google and roughly at parity with Amazon L5.
The comp gap at L5 between hyperscalers and enterprise SaaS has not narrowed in 2025-2026. The AI infrastructure buildout — concentrated at AWS Bedrock, Azure ML, and GCP Vertex AI — has driven a secondary repricing of platform engineers and senior SWEs on AI-adjacent teams that has no equivalent at Salesforce, ServiceNow, or Workday. A senior SWE at Salesforce's Einstein platform team is not building inference infrastructure for a multi-model serving architecture managing dozens of foundation model variants; the technical scope is different, and the market comp reflects that. The premium for running production AI workloads at hyperscaler scale runs $80,000 to $180,000 at the L5-L6 band in 2026 (ENTRA analysis of Levels.fyi 2026 crowdsourced data), and that premium is almost entirely invisible in the posted salary ranges because it lives in equity grants that the posting does not have to disclose.
Cloudflare sits in an instructive middle position. Its Workers AI product — running inference at the network edge across more than 310 data center locations globally — has repriced senior SWE compensation upward from the company's historical $175,000-$220,000 base band to a current median of $263,000 in total compensation, with specialized Workers AI platform engineers at $400,000 to $460,000 (ENTRA estimate). Cloudflare's posted California range for a Senior SWE ($168,000 to $248,000) is the tightest outside Microsoft, and its $15,000 disclosure gap (the distance between $248,000 ceiling and $263,000 TC median) is the smallest among all non-Microsoft entries. For a senior engineer evaluating Cloudflare, the posted range is actually informative — a rare exception to the hyperscaler pattern.
Will SB 1162 and EU Pay Transparency Law Close the Disclosure Gap?
California's SB 642 is the most consequential US salary transparency update since SB 1162 itself, but its practical effect on hyperscaler disclosures is limited. The "good faith estimate of what the employer reasonably expects to pay for the position upon hire" language does successfully eliminate ranges that span junior-to-principal career tracks within a single posting. What it does not change is the categorical exclusion of equity from the disclosure requirement. Hyperscalers could respond to SB 642 by posting narrower, more accurate base salary ranges — and the evidence suggests they broadly have — while the equity component that represents the majority of senior engineer compensation remains legally invisible. California's enforcement mechanism (civil penalties of $100 to $10,000 per violation, with escalating fines for repeat violations) creates compliance pressure to narrow the base range. It creates zero pressure to disclose equity.
Washington state's Equal Pay and Opportunities Act received an important enforcement expansion in September 2025 when the Washington Supreme Court ruled in Branson v. Washington Fine Wine & Spirits that any individual who submits an application to a noncompliant job posting qualifies for statutory relief — regardless of whether they applied in good faith or had genuine interest in the position. This ruling transformed WA EPOA enforcement from an abstract employer obligation into a live litigation risk from serial plaintiffs. For AWS and Microsoft, both headquartered in the Seattle metro and required to post under WA EPOA for Washington state roles, the Branson decision materially raised the cost of noncompliance. It has no effect on the equity exclusion either, but it has forced tighter drafting discipline on the ranges that are posted.
The European Union Pay Transparency Directive — which required member state transposition by June 7, 2026 — theoretically creates the most aggressive disclosure framework in the world, requiring pre-hire salary range disclosure, pay gap reporting for employers with 100 or more workers, and joint pay assessments where gender gaps exceed five percent. In practice, it is not yet law in the jurisdictions where hyperscalers employ the most engineers. Only four of the twenty-seven EU member states — Slovakia, Italy, Lithuania, and Malta — met the June 2026 transposition deadline. France and Germany — each of which had published no completed transposition legislation as of the June 7 deadline — are tracking toward 2027 implementation timelines, per EU transposition monitoring by DCI Consult and Trusaic (June 2026). For AWS's Dublin and Luxembourg entity engineering teams, for Google's Munich engineering center, and for Microsoft's Stockholm Copilot team, the Directive's salary disclosure requirements will not apply until 2027 at the earliest. When they do, they will be the first regulatory framework to require disclosure of the full compensation package — including equity — for roles above defined seniority thresholds. That is the regulation that will actually matter, and it is two to three years from full effect in the markets where it would move real numbers.
At the US federal level, the NLRB — which had been operating without a quorum through most of 2025 — confirmed its three-member minimum in December 2025. But the current General Counsel's enforcement priorities have explicitly de-prioritized broad wage transparency rulemaking. NLRA-based pay transparency challenges, which had been emerging from the prior Board's general counsel guidance, have been shelved under the current administration. Federal action on pay transparency enforcement is not a 2026-2027 variable.
What IT Engineers Should Do With This Data
The practical extraction from this analysis is specific. A wide posted range — $90,000 wide or more — tells you that the employer is either posting across multiple career levels in a single requisition, or is operating under minimal disclosure discipline and treating the legal requirement as an inconvenience to comply with narrowly. At AWS, an $98,000-wide range for an L6 SDE III in California is not incompetence; it is the consequence of Amazon's well-documented back-loaded RSU vesting structure (5/15/40/40 across four years) combined with a desire not to reveal level-specific equity grants. When you see an AWS posting with that range width, the useful signal is not in the width — it is in the midpoint ($210,900 for the L6 CA row above), which functions as a floor estimate for realistic base negotiations. Everything above that midpoint is your negotiation target; everything above the posted ceiling is equity that exists but was never disclosed.
Narrow ranges telegraph more, not less. Microsoft's $57,600-wide L63 range in Washington state is the most useful posted range in the entire dataset, because it actually reflects the base salary band that Microsoft legitimately plans to pay. A Microsoft L63 offer below $130,000 or above $160,000 on base would be genuinely anomalous. The Levels.fyi $233,000 total comp median at L63 then tells you the equity and bonus target to negotiate against: roughly $60,000 in annualized RSU and bonus over the four-year vesting cycle. For IT engineers reading job postings on their commute, the hierarchy of transparency runs: narrow range (use it as a real negotiation anchor) → wide range (extract the midpoint only, treat it as a floor) → no range (you are negotiating blind and need a Levels.fyi data point before the first conversation).
The engineers most exposed to the disclosure gap are those moving from enterprise SaaS employers — where the posted range genuinely describes most of what they earn — into hyperscaler roles, where the same posted range may describe less than half. A ServiceNow senior SWE reading a Google L5 California posting at $185,000-$248,000 should not benchmark the offer against their current Salesforce base. They should benchmark it against the $404,000 Levels.fyi total comp median and negotiate accordingly — specifically by asking for the RSU grant amount, the vesting schedule, and the refresh grant policy at the first compensation conversation. That information is not in the posting. It never will be, under any law currently in force in the United States. It is the only number that matters.
Methodology: Salary data sourced from job postings on LinkedIn and company career sites (collected August 2026), Levels.fyi crowdsourced compensation data (August 2026), and publicly available state-mandated salary disclosures under CA SB 1162 (as amended by SB 642, effective January 1, 2026), CO EPEWA, NY Labor Law § 194-b, and WA EPOA. Microsoft L63/L64 base ranges sourced from widely reported internal pay band documents and cross-referenced against current LinkedIn postings for Washington state roles. Range Width calculated as (posted maximum − posted minimum). Levels.fyi Median represents total compensation (base + annual cash bonus + annualized RSU) at stated experience levels from Levels.fyi crowdsourced submissions, August 2026. Salesforce, ServiceNow, Workday, and Cloudflare total compensation medians derived from Glassdoor 25th–75th percentile base data, Levels.fyi reported ranges for those companies, and ENTRA senior band estimates; these figures carry higher estimation uncertainty than the hyperscaler Levels.fyi medians, which draw on larger submission samples. All figures in USD. Geography-adjusted ranges for AWS L5 (WA vs. CA vs. TX vs. NC) are ENTRA estimates based on known Amazon geography multipliers and publicly available salary data; they are illustrative, not exact. Comparisons are illustrative; individual compensation varies by negotiation, performance tier, and location.
Global Career PlatformFind AI talent. Find your next role.
Booking is hotels. · Airbnb is apartments. · ENTRA is global careers.