[Your Name] · [Email] · [Phone] · [City, ST]
April 21, 2026
Dear Hiring Manager,
I'm applying for the Senior Software Engineer role on the Playback Experience team. The recent Tech Blog post on the adaptive bitrate rewrite for live events read like a design review I'd want to be in — particularly the decision to decouple the client-side ladder from the manifest-delivery cadence, which is a choice I made the opposite of two years ago at Hulu and have been thinking about since.
At Hulu I owned — and I mean owned, in the Netflix sense — the live-sports playback pipeline across web, iOS, Android TV, and Roku. No one asked me to take on the web stack; the team didn't have the capacity and the tail-latency numbers were the worst of any surface, so I picked it up. Over 9 months I rewrote the ABR controller, shipped a per-session model that predicts the next three segment bitrates from recent throughput variance, and cut rebuffering ratio from 1.8% to 0.4% during NFL Thursday Night Football — about 180M viewing hours per season. I made two calls I still think about: (1) I killed a six-week effort by a partner team because early A/B data showed it was regressing startup time, and (2) I shipped the rewrite without a formal design review, after pre-aligning with the three engineers whose systems it touched. Both decisions would have been harder with more process; neither would have been possible without context from the VP on what actually mattered to the business.
Before Hulu I was engineer #9 at a small video infrastructure company (Mux), where I wrote the first version of the encoding service and on-called for it alone for a year. That range — from 'I am the pager' to leading a 5-person playback team — is the working style Netflix describes in the culture memo, and it's the only one I enjoy. I'm not looking for a role with a roadmap handed to me; I'm looking for context and the freedom to figure the rest out.
I'd welcome a first conversation about where the team sees the biggest open problems on live playback — particularly around origin-side resilience during peak events. Happy to share a technical write-up of the Hulu ABR rewrite if it's useful for the loop.
Sincerely,
[Your Name]