In Qualcomm's Secure Systems group, I worked on making premium video apps like Netflix able to safely play protected content on Snapdragon devices. Content owners require that video keys, decrypted frames, and the playback path stay protected by hardware — Google (Widevine) and Microsoft (PlayReady) define the rules, and Qualcomm implements the low-level hardware and secure-software pieces that make those rules work on new chips. That secure playback pipeline was my job.
- Single-handedly enabled HWDRM on Qualcomm's newest Windows chipsets — integrated Microsoft PlayReady Porting Kit 4.0 and implemented the OEM platform functions
- Platform bring-up on early silicon: flashing builds, booting devices, and debugging protected playback failures across secure-world services, media, display, and firmware layers
- Built Hardware Key Manager (HWKM): keys never exist in clear text, even inside the security chip — closing a gap where attackers had fully recovered private keys from Qualcomm Secure Storage
- Designed HWKM as a firmware driver so Bluetooth, Wi-Fi, and other modules could reuse it directly — saving each team weeks of development and testing
The one-line fix that reached Netflix users worldwide
A small percentage of users on older Qualcomm-based phones saw green screens and glitches during Netflix playback. The fix turned out to be one line — a display-layer configuration mismatch — but finding it meant reproducing the issue, tracing the playback path across the media and display stack, and isolating the exact setting. It shipped in Qualcomm platform code and improved playback for an estimated ~2% of affected users worldwide. The lesson stuck with me: impact is not proportional to code size.