FAANG digest, Jun 22–29: Amazon active

Amazon produced the most usable interview-prep signal this week. The pattern is narrow but actionable: SDE-1 and new-grad candidates are seeing coding, simplified system design, and Leadership Principles coverage, while at least one U.S. SDE-1 candidate reported an on-site loop rather than the virtual format candidates have expected in recent cycles. 1 2

The rest of the week was split. Google has one L4 team-match progress signal, but another candidate reported an April-start process with extra rounds after onsite, positive Hiring Committee feedback, and no team-matching call after roughly two months. 3 4 Netflix has activity again, but the useful detail is mostly structure rather than exact questions: a Senior SWE loop was described as 2 coding rounds, 1 system-design round, and 1 behavioral round over Zoom. 5

Evidence quality matters this week. Compensation benchmarks from Levels.fyi and layoffs from named press or company sources are the strongest signals. Many interview reports are thinner because they come from forum snippets without full post bodies; treat those as preparation hints, not confirmed process doctrine.

Amazon is the best place to spend immediate prep time this week if your interviews are inside the next 10 business days. The SDE-1/AUTA India post described a 1-hour DSA round with 2 standard LeetCode-medium problems, plus discussion of approach, edge cases, dry runs, and time/space complexity. 1 A separate full-loop report described OA → phone screen → loop, with a system-design round lasting about 1 hour 5 minutes and conducted by a Senior SDE. 6

The thin signal to avoid overusing: Microsoft. There is too little interview detail this week to infer a current SWE process shift. The better candidate action is timing management: assume gaming-related headcount risk is unresolved until July WARN or internal communication catches up.

The biggest correction from last week: the FAANG TC crash story does not hold across the full set. Google L6 rebounded from roughly $564K to $622K, a +$58K move or +10.3% week over week, fully reversing last week's drop. 26 Google L5 still fell from $396K to $389K, but the -1.8% move was much smaller than the previous week's -6.6% decline. 26

Amazon L7 stayed hot. Principal SDE median TC rose from $721K to $751K, a +$30K move or +4.2% week over week, after last week's +13.7% jump. 27 The caveat is vesting: Amazon's 5/15/40/40 RSU schedule means first- and second-year realizable equity can sit well below the annualized stock number. 27

One negotiation rule for this week: separate market data from pipeline risk. A Google L6 candidate can point to the $622K median rebound, but a Google candidate waiting for team match still needs an expiration and competing-offer strategy. A Microsoft candidate should discount any verbal optimism until post-June-30 layoff timing is clearer.

Microsoft is the most important watch item, even though it produced almost no real interview detail. The Seattle Times reported that Bungie's Bellevue layoffs came before expected Microsoft Xbox cuts, and the Microsoft fiscal year ends June 30. 11 Blind's June 26 TL;DR also described continuing Microsoft quiet layoffs and expected larger cuts the following month. 33

Oracle is the macro warning sign. TechCrunch reported that Oracle disclosed a workforce decline from about 162,000 to 141,000 full-time employees in its annual filing, a reduction of 21,000 over 12 months, and the filing attributed workforce reductions in part to AI adoption and deployment. 19 Elastic added a different pattern: a CEO-confirmed 7% restructuring with engineering reorganized into three core areas, while customer-facing sales hiring continues. 34

That combination matters for interview strategy. The market is not frozen. It is reallocating. AI labs, AI-facing SaaS roles, and selected senior loops remain active; entry-level, support, sales-adjacent, and non-core teams carry more timing risk.

If your Amazon loop is scheduled this week, practice in this order: 2 LeetCode-medium problems, one 45-minute simplified design problem, then 6 Leadership Principles stories with explicit trade-offs. Amazon candidates should also ask whether any SDE-1 stage is on-site, because one U.S. post described a shift away from virtual loops. 2

If your Google loop is done and you are waiting, send a clean status email that asks for the next team-match milestone and whether additional interviews are still possible. This is not just politeness; one candidate reported additional rounds after onsite and no team calls despite positive HC feedback. 4

If your Netflix interview is senior-level, put communication drills next to coding drills. The L5 failure report points to senior communication as the failure mode, and the 4-round Senior SWE structure still includes a behavioral round alongside coding and system design. 9 5

If you are negotiating, use the freshest benchmarks but do not flatten all companies into one market. Google L6, Amazon L7, and Snowflake IC3 moved up; Meta E5 and Netflix L5 moved down; Microsoft has a new baseline but not a week-over-week trend. 26 27 22 28 30 32

The strongest prep edge this week is specificity. Candidates who know which companies have real loops, which ones have team-match risk, and which compensation medians actually moved can spend practice time and negotiation leverage where it still has a chance to matter.