Mistakes to Avoid

BAD: Spending the first 30 days polishing a product roadmap that never reaches an engineering team. GOOD: Running a live latency experiment with the Alexa team and sharing results in the TGIF Sync.

BAD: Treating the Netflix “Freedom & Responsibility” weekly as a social event, posting a meme instead of a decision log. GOOD: Publishing a concise “Decision Log” after each autonomous code push, with rollback procedures attached.

BAD: Assuming compensation bumps are automatic after day 90. GOOD: Explicitly request the Level Review or Keeper Test agenda, and prepare the impact data that will trigger the raise.

---

FAQ

Did the candidate’s technical answer outweigh cultural missteps in the Amazon debrief?
No. The debrief was 4‑2‑0; two senior TPMs vetoed the hire because the candidate failed to demonstrate “Bias for Action” beyond a 50 ms latency claim. Cultural alignment trumps a decent technical answer.

Can a Netflix manager skip the 30‑day culture immersion and still succeed?
No. All five managers who omitted the Day 2 immersion failed the Keeper Test, receiving 0‑5‑0 votes. The immersion is the first cultural signal.

Is the 90‑day compensation bump guaranteed if KPI targets are met?
No. Amazon ties the bump to a formal Level Review and a documented rubric; Netflix ties it to a cultural outcome that the Keeper Test panel must approve. Both require documented evidence, not just KPI hits.amazon.com/dp/B0GWWJQ2S3).