Eric Li
Product Security Engineer at Splunk
Vancouver, British Columbia, United States
Summary
🤩
Rockstar🎓
Top SchoolEric Li is a Product Security Engineer with four years of hands-on experience bridging low-level systems programming and applied security, currently at Splunk in Vancouver. He built an OS from scratch during undergrad, fixed dozens of kernel defects at Wind River (including deterministic POSIX-aligned IO and posix_spawn), and now applies that reverse-engineering rigor to product security and vulnerability automation. At Splunk he transitioned from writing test frameworks and large-scale dependency scanners to securing production services, and contributes backend reliability work to the widely used OpenTelemetry Collector. Comfortable in C and Python and fluent with debuggers and emulators, he pairs deterministic thinking about machine-level behavior with practical tooling to reduce real-world CVE risk.
4 years of coding experience
Bachelor of Science - BS, Computer Science, Bachelor of Science - BS, Computer Science at University of California, DavisMaster of Science - MS, Computer and Information Systems Security/Information Assurance, Master of Science - MS, Computer and Information Systems Security/Information Assurance at Carnegie Mellon UniversityHigh School Diploma, High School Diploma at Beijing National Day School
English, Chinese, Japanese
Github Skills (10)
persistent-storage10
opentelemetry10
observability10
go10
telemetry10
metric10
queue9
testing9
queuing9
feature-flags8
Programming languages (2)
Github contributions (5)
open-telemetry/opentelemetry-collector
Mar 2022 - Jan 2023
OpenTelemetry Collector
Role in this project:
Back-end Developer
Back-end DeveloperContributions:46 reviews, 4 commits, 5 PRs in 10 months
Contributions summary:Eric primarily contributed to the backend infrastructure of the OpenTelemetry Collector. They implemented feature flags for internal metrics and refactored the code to use these flags. They also worked on closing persistent storage clients upon stopping the service, ensuring data consistency, and preventing potential data loss during restarts. Furthermore, the user addressed issues related to persistent queue operations and error propagation in the retry sender, thereby enhancing the reliability of the collector.
opentelemetry-collectortracingtempoobservabilitytelemetry
splunkericl/opentelemetry-collector
Feb 2022 - Oct 2024
OpenTelemetry Collector
Contributions:2 releases, 81 pushes, 6 branches in 2 years 8 months
opentelemetry-collectoryangtracingobservabilityotel
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.