FAANG digest, June 1–8: Amazon's Gen AI question

This week's most actionable signal doesn't come from a system design deep-dive or a compensation leak — it comes from two independent Amazon behavioral rounds confirming a new question that candidates aren't preparing for. Amazon hiring managers are now asking about Generative AI usage directly. What they're probing for and how to answer it is the lead story. Alongside that: Google's recruiting operation produced three separate dysfunction reports this week, PayPal's much-discussed "June 30 layoffs" turn out to be the execution date for a February announcement, and the question banks from two detailed Amazon interview decodes are below.

Hiring status by company

The table below reflects community-reported signals as of June 8, 2026. Companies with no new signals this week carry forward from the June 1 issue.

Company	Status	Signal this week
Google	Active hiring	Three separate recruiting dysfunction reports (details below); technical bar unchanged
Meta	Frozen / restructuring	8K cut May 20; 6K HC slots still frozen; no confirmed reopenings 1
Apple	Selective	No new signals this week; ICT3 downlevel pattern persists
Amazon	Selective	SDE intern and junior SWE loops active; Gen AI behavioral question confirmed
Netflix	Backfill only	No new signals; Blind-confirmed freeze since May 12 2
Microsoft	Partial freeze	No new signals; July cut rumors remain unverified
Stripe	Active (senior)	No new signals this week
LinkedIn	Restructuring	No new signals; ~875 cut in May restructuring
Cloudflare	Post-restructuring	No new signals; 1,100 cut in May AI pivot
Databricks	Active	No new signals; ML pipeline remains active
PayPal	Executing announced cuts	WSJ reports 4,760 cuts (20% of workforce, announced February 2026); Blind tracker shows Jun 30 date and 5,000 figure (21.7%) 3 4
Snowflake	Selective	Chakra AI (AI-powered coding screen) active for backend engineer roles; no new signals this week

Amazon's new behavioral question: Gen AI usage and verification

Two independent Amazon interview reports filed June 7–8 both document the same new behavioral prompt appearing in round-one hiring manager sessions. 5 6

The question, as recorded in the SDE Fall Intern report, was: "How do you use Gen AI, and how do you make sure it's correct?"

The Junior SWE report described round one's behavioral component as focused on the candidate's experience using Generative AI, with similar framing.

This is not a casual warm-up question. The "how do you verify correctness" follow-up signals that Amazon is evaluating AI judgment, not just adoption. A strong answer would walk through a concrete example: which tool you used, what it produced, where you caught an error or limitation, and how you validated the output before relying on it. "I use GitHub Copilot to write boilerplate" without a verification story is unlikely to score well. The Leadership Principle subtext here maps most directly to Dive Deep and Ownership — you own the output even when a model generated the first draft.

Both reports come from entry-to-junior-level loops (intern and junior SWE), but the pattern is almost certainly present at L4–L5 loops as well. Prepare a Gen AI story before any Amazon screen.

正在加载内容卡片…

Google recruiting: three separate dysfunction signals this week

Three posts from different candidates, different roles, and different stages of the process arrived in the same week — all pointing at process failures rather than bar-raise events.

The Randstad contractor reject cycle

A candidate on r/ExperiencedDevs reported applying to Google SDE 3+ roles five times over six months. 7 Each attempt followed the same pattern: a Randstad contractor recruiter reached out, the candidate filled out a questionnaire, and a rejection arrived exactly two days later — from five different recruiters, across five different roles.

"I feel like I'm in the twilight zone with Google right now. I apply for jobs, a recruiter from Randstad reaches out asking to fill out a questionnaire, I do, they say they will keep me posted. Two days later I get a rejection. [...] This has happened 5 times now. From 5 different recruiters for 5 different roles. In the last 6 months." — u/doodooheadpoopoohead 7

The two-day turnaround on a questionnaire rejection suggests an automated gate — not a recruiter making a judgment call after reviewing the response. Whether the questionnaire itself is the filter or whether it's a downstream ATS (applicant tracking system) rule is unclear, but the pattern is too consistent across five independent attempts to be coincidence.

PM team-match stuck for 3+ months

A Google Program Manager L4 candidate in Bangalore cleared all five interview rounds plus the Hiring Committee around the end of February 2026. 8 The original hiring manager found an internal candidate instead, so the team match was reopened — and has been open for more than three months. The recruiter who was managing the candidate's profile left Google. The replacement recruiter has not been responsive.

"The sad part is that the recruiter who was handling my profile has moved out and the new one isn't very responsive or in touch." — u/Calm_Future3143 8

The candidate has an Amazon L6 offer moving toward finalization. The team-match bottleneck affecting Google SWE loops (reported in prior issues) is not specific to engineering — this report confirms it extends to non-technical roles as well.

Vague L3 feedback and an inattentive interviewer

A Google L3 early-career candidate completed two onsite rounds and received a single line of feedback across both sessions: "struggled to translate high-level concepts." 9 When the candidate asked whether that referred to communication or coding, the recruiter responded "yes" — an answer that addressed neither question.

The candidate also reported that one interviewer was visibly doing other work during the session. 9

These three reports are independent. None of the candidates appear to be connected. The xWF/Randstad cycle is a pre-screen problem, the PM team match is a post-interview problem, and the vague L3 feedback is an in-process problem — different stages, same underlying signal that Google's recruiting infrastructure is under strain.

正在加载内容卡片…

This week's question bank

Developer writing code on a laptop, overhead view — illustrating the kind of focused problem-solving Amazon evaluates across behavioral and technical rounds — Amazon's loops now mix OOD, interval scheduling, and Gen AI behavioral prompts in the same four-hour session. 5 6

Amazon SDE Fall Intern (accepted) 5

Online assessment: 1 LeetCode easy + 1 medium + a behavioral email-decision simulation + personality test. Completed April 8; interview scheduled May 12 after rolling to fall cohort.

Round 1 — Hiring manager (50/50 behavioral + technical)

Behavioral: "Tell me about a situation where you had to dig deep."
Behavioral: "Tell me about a time when you had to understand a complex problem."
Behavioral: "How do you use Gen AI, and how do you make sure it's correct?"
Technical: Design a notification system supporting email, push, and SMS. Coded on a plain notepad — not a HackerRank environment. The interviewer stayed past time to chat, which u/EEBS77 noted as a positive signal.

Round 2 — Senior engineer (50/50 behavioral + technical)

Behavioral: "Tell me about a time you received critical feedback and implemented it."
Technical: Given server log data, find the top 3 page sequences visited. Follow-ups on time and space complexity.

Result: offer extended three business days after the interview. u/EEBS77's prep note: "I can't emphasize enough that you need to subtly tie in your behavioral stories with the Amazon leadership principles." 5

Amazon Junior SWE — Seattle (did not pass) 6

Four rounds, 240 minutes total. Difficulty self-rated 6/10. Interviewer tone: neutral throughout.

Round 1 — Behavioral + coding

Behavioral: Gen AI experience.
Coding: Multi-source BFS (breadth-first search) on a graph/grid problem.

Round 2 — Behavioral + coding

Behavioral: Obstacles you've faced; handling a tight deadline with multiple competing tasks; could you think of a better solution and what are the trade-offs?
Coding: Meeting Rooms I (can one person attend all meetings? — interval overlap check) followed by Meeting Rooms II (minimum number of conference rooms required — min-heap on end times).

Round 3 — Behavioral + object-oriented design

Behavioral: "Describe a time you offered to do something outside your scope."
OOD: Design a standard deck of playing cards. Implement an in-place shuffle() and a sort() by suit (Clubs → Diamonds → Hearts → Spades) and rank (Ace → 2 → ... → King).

The card deck problem tests comparator design and in-place implementation. The shuffle component probes whether the candidate reaches for Fisher-Yates (a standard unbiased shuffle algorithm running in O(n) time) vs. a naive random-swap approach that introduces statistical bias in the distribution.

Round 4 — Pure behavioral

Described as "intense grilling" with in-depth follow-up questions. No technical component.

TC benchmark table — June 2026

The table below carries forward Levels.fyi median data from the June 1 issue. No new individual offer disclosures were reported in the June 1–8 window. The Amazon L6 offer referenced in the Google PM team-match post above was not fully disclosed.

Company	Level	Levels.fyi median TC	Last real offer on record	Notes
Google	L5 (Senior SWE)	$424K	$523.7K (Bay Area, 8 YOE) 10	+23.5% vs. median
Google	L5 (Austin)	$424K ref.	~$270K Y1 10	~43% below Bay Area same level
Meta	E5	$489K	$400K (Bay Area) 11	-18.2% vs. median
Apple	ICT3	$225K	~$230K (8 YOE, downleveled) 12	Downlevel common at Apple for lateral hires
Amazon	SDE I (L4)	$191K	~$189K (4 YOE) 13	Post-cliff vesting hits Y3–Y4
Microsoft	L63	~$219K ref.	$225K (Redmond) 11	Partial freeze continues
Netflix	L5 SWE	$538K	$650K (PM, Ads — all cash) 14	Freeze since May 12; PM figure for reference
Stripe	Senior SWE	$437K	$550K (PM) 14	Active senior hiring
Databricks	L5 (Senior SWE)	$652K	— (no individual disclosure)	Highest SaaS senior median tracked; 40/30/20/10 vesting

Google vests 38/32/20/10 (front-loaded); Amazon vests 5/15/40/40 (back-loaded). Netflix PM figure is all cash with no equity component. Stripe and Netflix figures are PM-role disclosures included for cross-company reference.

Three things to do before your next Amazon screen

1. Build a Gen AI behavioral story now. The question appeared in two independent loops within 24 hours of each other. Structure the answer as: tool used → specific task → where the AI fell short or needed validation → what you did to verify → outcome. The "how do you verify correctness" framing tells you the interviewers are looking for critical judgment, not enthusiasm.

2. Treat OOD as a first-class prep category for Amazon. The card deck design problem in the junior SWE loop is a reminder that Amazon's junior and mid-level loops include OOD rounds that many candidates underprepare. Classic OOD problems to add to the rotation: card deck (shuffle/sort comparator design), parking lot (state machine), elevator system (queue + priority), and library management (search/availability tracking).

3. If you're post-HC at Google and your recruiter has gone quiet, escalate now. The PM candidate's situation — three months of silence after a recruiter transition — is not unusual given the team-match squeeze. Send a direct follow-up to your current recruiter with a specific question ("Do I still have active team-match opportunities?") and copy the previous recruiter's manager if you have that contact. Waiting passively costs you negotiating time with competing offers.

Cover image: Thirdman / Pexels