
FAANG digest, Jul 6-13: OpenAI active
This week’s digest leads with active OpenAI and top SaaS interview loops, while treating Microsoft layoffs and Google process drift as candidate-risk context. It preserves the weekly hiring-status table, concrete question bank, TC benchmark table, offer read-through, and multiple non-table visual breaks.
OpenAI and the AI/SaaS interview boards supplied the most usable prep signal this week. OpenAI had three separate interview-process reports: a failed Senior SWE onsite built around state-machine depth, a passed Senior SWE loop where "Design Sora" became a GPU scheduling discussion, and a Data Scientist process breakdown. 1 2 3 Google, meanwhile, has enough repeated team-match-before-Hiring-Committee reports across L3/L4/L5 that candidates should treat the new ordering as a planning risk, not a one-off anomaly. 4 5 6
Coverage runs from Jul 6 at 10:30 a.m. through Jul 13 at 10:00 a.m. Eastern. Microsoft still matters, but this issue should not be read as another layoffs-led digest. Microsoft cut about 4,800 jobs on Jul 6, and the r/microsoft employment thread showed post-layoff candidate uncertainty, but the prep edge came from concrete loops at OpenAI, Databricks, Anthropic, Asana, Figma, DoorDash, Airbnb, Google, Meta, Netflix, and Amazon. 7 8
正在加载统计卡片…
Hiring status by company
| Company | Candidate status | Signal strength | What changed this week | Candidate move |
|---|---|---|---|---|
| Active, process-risky | Strong | Multiple candidates described team matching before Hiring Committee, including an L4 Infrastructure candidate who said the recruiter moved them to team matching the day after loop and would send the packet to HC after a match. 5 | Ask the recruiter to separate onsite feedback, team-match order, HC timing, and whether extra interviews can still be added. | |
| Google L5+ non-SWE | Active, higher scrutiny | Medium | One L5 non-SWE candidate reported an added "informal" skip-skip-level chat after a full onsite panel that already included a skip-level interviewer; notes were taken, and the recruiter asked for extra days. 9 | Prepare for post-onsite calibration conversations as evaluative rounds. |
| OpenAI | Active | Strong | Senior SWE reports pointed to state machines, product-to-infra reframing, and design depth; the DS megathread described a six-stage process from recruiter/HM screen through LLM/safety measurement design. 1 2 3 | Practice state transitions, partial failure, scheduling, metrics, and rollout criteria rather than generic component naming. |
| Anthropic | Active, selective | Medium | A Staff SWE report covered an image-processing pipeline coding round and a model-rollout system design round; a separate coding post described reconstructing call lifecycle events from stack snapshots. 10 11 | Pair production-style coding with infrastructure trade-offs and motivation/collaboration answers. |
| Databricks | Active signal returning | Medium | A Senior SWE full loop included dependency-based build pipeline, frozen iterators, referral ranking, behavioral, and coordinated disk-writer system design; status was awaiting feedback. 12 | Clarify whether a design round wants API/class design, concurrency implementation, or high-level architecture before coding into the wrong frame. |
| Meta | Sparse, not broadly reopened | Weak-to-medium | The only current Meta interview report was a Senior MLE onsite in Menlo Park with five rounds: two research design, one ML fundamentals, one coding, and one behavioral; the candidate failed, and ML fundamentals was the weakest signal. 13 | Treat Meta as selective and role-specific; do not infer broad reopening from one MLE report. |
| Netflix | Sparse, domain-specific | Weak-to-medium | The only Netflix report was a Senior SWE ads loop with versioned key-value store, ad pacing, publisher-side configuration, and dependency-graph questions; the post said external L6 candidates are treated as L5 at Netflix. 14 | If the role touches ads, prepare pacing, inventory, publisher configuration, and supply-side trade-offs. |
| Amazon | Active but uneven | Medium | One SDE2 candidate reported receiving a new OA inside an expected six-month cooldown window; the OA included DSA, AI-assisted SpringBoot codebase debugging, and workstyle assessment. 15 | Do not treat the OA as pure LeetCode; budget practice time for codebase debugging and workstyle consistency. |
| Microsoft | Frozen or delayed externally | Strong risk signal | A Microsoft CO+I candidate said an April interview turned into a July "Not Selected" portal update without recruiter communication, while employees in the weekly thread asked when hiring freeze would end. 8 | Ask whether the req is funded after the Jul 6 reduction and whether the team can still extend external offers. |
| Apple | Process opaque | Weak | One post described a post-interview HR call about salary expectations and general compensation structure, but the recruiter said no actual offer existed and the hiring team was still evaluating performance. 16 | Treat comp discussion as a signal to prepare numbers, not as evidence that an offer is approved. |
"The recruiter reached out to me literally the next day after the loop to say they want to move me forward. However, they are doing Team Matching first, and then sending my packet to the Hiring Committee (HC) once a match is found." 5
Question bank: practice these now
The strongest pattern across the interview reports is that familiar surfaces are hiding stricter implementation or design demands. OpenAI can ask for a familiar product, then evaluate state correctness. Airbnb can pass most rounds, then reject on an added system design tie-breaker. Figma can turn product permissions into a graph implementation. 1 17 18
| Platform / author context | Company / role | Round type | Concrete prompt or report | Outcome / reaction | Prep implication |
|---|---|---|---|---|---|
| r/OfferEngineering; author background not publicly verified | OpenAI Senior SWE | System design | "Design Sora" was reframed as GPU scheduling with queues, priorities, batching, capacity limits, retries, job state, fairness, and GPU utilization. 2 | Candidate passed and believed two coding plus two design rounds were strong. 2 | Turn broad AI product prompts into resource scheduling, reliability, and latency constraints. |
| r/OfferEngineering; author background not publicly verified | OpenAI Senior SWE | Architecture design | ChatGPT-like product, online chess platform, and offline payment system all tested state transitions, retries, durability, and correctness under partial failure. 1 | Candidate did not pass. 1 | Practice drawing state machines before drawing service boxes. |
| r/FAANGrecruiting; author background not publicly verified | Google FDE | AI/Agent plus coding | FDE format included one AI/Agent scenario with about three questions, no coding or whiteboarding, plus one LeetCode medium/hard in 20-30 lines of Python with no dynamic programming. 19 | Separate London FDE candidate heard Google had reached headcount and worried about postponing. 19 | Prepare enterprise AI discovery, MVP definition, monitoring, and strings/graphs coding. |
| r/leetcode; author background not publicly verified | Google L3 SWE | Onsite coding | One L3 onsite included heap plus hashing in round one and Codeforces 448C, a segment tree style problem, in round two. 20 | Post had 106 score and 44 comments; community reaction treated segment tree as unusually difficult for L3. 20 | Have a fallback brute-force explanation for advanced data-structure prompts, then state what would be needed to optimize. |
| r/OfferEngineering; author background not publicly verified | Anthropic Staff SWE | Coding and system design | Coding used an image-processing pipeline with file inputs and JSON-defined transformations; design used model checkpoint rollout across GPU workers under bandwidth constraints. 10 | The report framed the loop as manageable coding followed by much deeper infrastructure judgment. 10 | Practice clean production code, worker coordination, verification, slow-worker recovery, and rollback. |
| r/OfferEngineering; author background not publicly verified | Asana Mid-Level SWE | Four-round onsite | Rounds covered Product of Other Sensors, Jigsaw Puzzle OOD and Solver, LRU Cache, and MapReduce-style unique client address deduplication with skew and memory follow-ups. 21 | The post's pattern was clean modeling across arrays, OOD, cache state, and distributed deduplication. 21 | Prepare implementation rounds where the abstraction is the test. |
| r/OfferEngineering; author background not publicly verified | Figma Senior SWE | Onsite coding | Permission Reachability modeled Teams, Folders, and Files as a hierarchy; get_fewest(user_id) returned the smallest set of highest-level directly accessible objects. 18 | Candidate believed this graph round hurt the final outcome. 18 | Practice product-adjacent graph problems with clear hierarchy initialization and edge-case tests. |
| r/OfferEngineering; author background not publicly verified | DoorDash Staff SWE | Phone screen system design | First technical screen was "Design Instagram," with focus on celebrity posting, fanout strategy, feed storage, indexing, sharding, and fast reads under high write volume. 22 | Recruiter was reported as responsive and fast to schedule. 22 | Staff candidates should be ready for system design before any coding signal. |
| r/FAANGrecruiting; author background not publicly verified | Amazon SDE2 | Online assessment | New OA included DSA, AI-assisted SpringBoot codebase debugging, and workstyle assessments after the candidate had bombed a prior SDE2 DSA round. 15 | Candidate reported 15/15 tests on one DSA problem and 6/6 unit tests on the second. 15 | Add codebase reading and debugging drills to Amazon OA prep. |
"First Section was DSA and 2nd Section was AI Assisted Codebase debugging and then the typical workstyle assessments." 15
The visible interview report count this week was concentrated in Google and the AI/SaaS cohort. Google produced the largest FAANG process set, OpenAI produced three interview-process reports, and Databricks, Anthropic, Airbnb, Asana, Figma, and DoorDash supplied concrete top-SaaS loop detail. 4 1 12 10
正在加载图表…
Weekly TC benchmark
The compensation table moved in the opposite direction from the hiring-risk story. Google L5 and L6 SWE medians rose, Meta E5 rebounded, Apple ICT4 jumped sharply, Microsoft L63/L64 moved up, Netflix L5 slipped slightly, and Amazon L7 fell while Amazon L6 rose. 23 24 25 26 27 28
| Company / level | Current median TC | Weekly move | Candidate use |
|---|---|---|---|
| Google L5 SWE | $406K | +2.5% | Use $406K as the mid-level anchor, but do not ignore team-match and HC timing risk. 23 |
| Google L6 SWE | $644K | +2.3% | Senior candidates can anchor above last week's $630K baseline if the role is funded. 23 |
| Meta E5 SWE | $474K | +6.3% | The median rebound is useful for negotiation, but one MLE report does not prove broad SWE reopening. 24 |
| Apple ICT4 SWE | $349K | +20.6% | Treat the jump as an anchor to verify with offer-level data because the issue had no Apple offer post. 25 |
| Amazon L6 SWE | $419K | +3.6% | L6 moved up even as L7 moved down, so use level-specific data rather than a generic Amazon trend. 26 |
| Amazon L7 SWE | $663K | -11.7% | Separate L7 median movement from special AGI or AI-lab packages. 26 |
| Netflix L5 SWE | $499K | -0.4% | Netflix remains a high all-cash benchmark, but current interview signal is sparse and ads-specific. 27 |
| Microsoft L63 SWE | $236K | +9.5% | The comp number improved, but the hiring-status signal is weaker after the Jul 6 layoff. 28 |
正在加载图表…
The AI-lab and top-SaaS benchmark set is still above most FAANG mid-senior anchors. Levels.fyi listed OpenAI SWE median TC at $800K, Anthropic SWE median TC at $746K, and Databricks SWE median TC at $468K as of Jul 13. 29 30 31
| Offer signal | First-year TC | Structure | Candidate read |
|---|---|---|---|
| Google L5 Research Scientist, Mountain View | $740.5K | $260K base, $80K signing, $1.1M equity over 4 years, $37.5K bonus | Research Scientist is not SWE, but the package shows the AI-role premium inside Google. 32 |
| Airbnb G9 Senior SWE, San Francisco | $580K | $240K base, $50K sign-on, $700K equity over 4 years, $45K bonus | Public RSU liquidity and 35% first-year vesting make the headline easier to value than private options. 33 |
| Jane Street Senior SWE, New York | $720K | $320K base, $180K sign-on, $220K bonus, no equity listed | Almost all-cash liquidity competes directly with AI-lab upside; the candidate declined. 34 |
| Perplexity Staff SWE, SF Bay Area | $935K headline | $330K base plus $2.42M private options over 4 years | The candidate declined; strike price, valuation, tax cost, and liquidity windows matter more than headline TC. 35 |
| Tesla AI New Grad, Palo Alto | $439K | $180K base, $9K sign-on, $1M RSU over 4 years with a one-year cliff | Very high new-grad headline, but the one-year cliff makes early departure costly. 36 |
| Harvey AI Senior Research Scientist, SF Bay Area | $525K | $250K base, $25K sign-on, $1M private RSU over 4 years | Private-valuation RSUs need a discount against public RSUs or cash. 37 |
| Microsoft Azure SWE II remote | $220K | $140K base, $30K signing, $140K equity over 4 years, $15K bonus | This sits between Microsoft 62 and 63 medians and was framed by the post as a lowball. 38 |
| Amazon Lab 126 Hardware Reliability Engineer L5 | $243.5K | $159K base, $77K year-one sign-on, $150K equity over 4 years with 5/15/45/35 vesting | The candidate accepted but said they were downleveled from L6 to L5. 39 |
正在加载图表…
Candidate action plan
If your Google loop is already complete, ask for the process map in writing. The question is no longer "Did I pass onsite?" It is "What happens first: team match, HC, extra calibration, or packet expiry?" The reports now include team-match-before-HC, a skip-skip-level add-on, recruiter/interviewer feedback mismatch, and a rushed team-match rejection path. 4 9 40
If your OpenAI, Anthropic, Databricks, or DoorDash loop is coming up, start each design answer by naming the object whose state must stay correct. OpenAI reports tested cloud-credit replay, ChatGPT conversations, chess games, offline payments, and GPU jobs; Anthropic tested model-rollout safety and call-stack lifecycle reconstruction; Databricks tested a coordinated disk writer; DoorDash used celebrity fanout. 1 10 11 12 22
If your Meta or Netflix signal comes from a single report, keep the prep specific and the inference narrow. Meta's Senior MLE report says fundamentals can sink a loop even after research-design rounds, and Netflix's Senior SWE report says ads-domain depth can matter more than generic backend comfort. 13 14
If your Microsoft, SAP-adjacent, or enterprise-software process is still open, ask whether the role survived the current budget review. Microsoft's Jul 6 reduction was real, and the employment-thread signal shows candidates can sit for months before a silent portal decision. 7 8
If you are negotiating, split every number into three columns before reacting: liquid year-one cash, public RSUs, and private equity or options. Jane Street's $720K is nearly all cash, Perplexity's $935K is private options-heavy, Airbnb's $580K is public RSU-heavy with front-loaded vesting, and Amazon Lab 126's accepted L5 package has very low first-year equity because of Amazon's backloaded schedule. 34 35 33 39
"Recruiter then added a short, 'informal' follow-up chat with the skip-skip level (notes were definitely taken)." 9
The practical read: this is a week for stateful systems practice, process-management discipline, and cleaner offer math. Candidates who only add more LeetCode volume will miss the parts of the signal that changed.
Cover image: AI generated.
参考来源
- 1r/OfferEngineering: OpenAI Senior SWE Onsite Jun 2026
- 2r/OfferEngineering: OpenAI Senior SWE Full Journey Jul 2026
- 3r/OfferEngineering: OpenAI DS Interview Process Megathread
- 4r/FAANGrecruiting: Google onsite outcome and team matching before Hiring committee
- 5r/leetcode: Passed Google L4 technical loop with Team Matching first
- 6r/leetcode: Passed Google L4 top-up for Zurich/Munich
- 7r/cscareerquestions: Microsoft layoffs, 4,800 jobs cut
- 8r/microsoft: Weekly Employment Q&A July 06-13 2026
- 9r/FAANGrecruiting: Google L5 Non-SWE skip-skip level added post-onsite
- 10r/OfferEngineering: Anthropic Staff SWE May 2026
- 11r/OfferEngineering: Anthropic coding question on call lifecycle snapshots
- 12r/OfferEngineering: Databricks Senior SWE Interview Report Jul 2026
- 13r/OfferEngineering: Meta Senior MLE Interview Experience Jun 2026
- 14r/OfferEngineering: Netflix Senior SWE Interview Experience Jun 2026
- 15r/FAANGrecruiting: Amazon SDE2 candidate received new OA
- 16r/FAANGrecruiting: Apple - offer or not?
- 17r/OfferEngineering: Airbnb Senior SWE Interview Jun 2026
- 18r/OfferEngineering: Figma Senior SWE Full Journey Jun 2026
- 19r/FAANGrecruiting: Google FDE interview prep needed
- 20r/leetcode: Bombed Google onsite
- 21r/OfferEngineering: Asana Mid-Level SWE Onsite Jun 2026
- 22r/OfferEngineering: DoorDash Staff SWE Phone Screen May 2026
- 23Levels.fyi: Google Software Engineer Salary
- 24Levels.fyi: Meta Software Engineer Salary
- 25Levels.fyi: Apple Software Engineer Salary
- 26Levels.fyi: Amazon Software Engineer Salary
- 27Levels.fyi: Netflix Software Engineer Salary
- 28Levels.fyi: Microsoft Software Engineer Salary
- 29Levels.fyi: OpenAI Software Engineer Salary
- 30Levels.fyi: Anthropic Software Engineer Salary
- 31Levels.fyi: Databricks Software Engineer Salary
- 32r/OfferEngineering: Google L5 Research Scientist $740.5K TC
- 33r/OfferEngineering: Airbnb G9 Senior SWE $580K Offer
- 34r/OfferEngineering: Jane Street Senior SWE $720K offer
- 35r/OfferEngineering: Perplexity Staff SWE $935K Offer
- 36r/OfferEngineering: Tesla AI New Grad $439K Offer
- 37r/OfferEngineering: Harvey AI Senior Research Scientist $525K
- 38r/OfferEngineering: Microsoft SWE II lowball offer
- 39r/OfferEngineering: Amazon Hardware Reliability Engineer offer
- 40r/FAANGrecruiting: Google first round interview feedback makes no sense
相似内容
- 登录后可发表评论。
