Company prep
Company-specific interview guides
Google, Amazon, Meta, Microsoft, Netflix, Uber, AI labs, and enterprise patterns.
Company guides below are distilled from publicly discussed interview patterns (candidate reports, engineering blogs). They are preparation heuristics, not leaked questions.
- Coding: Prefer patterns over memorization — graphs, BS on answer, hard DP. Labs: Islands, Word Ladder, Alien Dictionary, Median/rotated search family.
- Design: Crawler, Maps, Drive, YouTube, rate limiter, KV. Emphasize scale + freshness + failure.
- AI roles: RAG eval, serving, retrieval quality.
- Evaluating: Clarity, generalization, testing mindset.
Amazon
- Behavioral first: Leadership Principles with STAR — Ownership, Customer Obsession, Dive Deep, Bias for Action, Disagree and Commit. See Behavioral.
- Coding: Speed + working code. OA favorites: Two Sum family, LRU, islands, rotting oranges, stock, top-k.
- Design: Shortener, rate limiter, Dynamo-style KV, payments, notifications.
Meta
- Coding: Often two mediums in one round — windows, trees, intervals, heaps. Min window, meeting rooms, serialize tree.
- Design: News feed, chat, Instagram stories adjacency, counters.
- Speed + product sense matter.
Microsoft
- Coding similar to FAANG mediums; design often Teams/Azure flavored: chat, storage, identity.
- Expect collaboration and debugging narratives.
Netflix
- Video edge + recommendations + resilience culture (circuit breakers, chaos).
- Labs: YouTube/video Q6, recsys AI Q6, caching Q9, comparisons CDN/cache.
Uber / Lyft
- Geo, marketplace dispatch, ETA, city sharding — SD Q5. Kafka-heavy data paths Q16.
OpenAI-adjacent / AI platforms
- Full AI Lab: RAG, agents, eval, serving, tenancy, security.
Red Hat / enterprise open source
- Expect Linux/Kubernetes, operators, observability, and design for on-prem constraints.
- Map to scaling, queues, and reliable upgrades — emphasize operable systems.