Emily Burns
Senior Software Engineer at Netflix
Mountain View, California, United States
Summary
🤩
Rockstar🎓
Top SchoolEmily Burns is a Senior Software Engineer based in Mountain View with a decade of experience building and improving large-scale cloud-native systems, currently contributing to Spinnaker and Netflix. She specializes in backend services, orchestration, and integrations across CI/CD, cloud providers (OpenStack, Kubernetes), and eventing systems, with hands-on work spanning API gateways, pub/sub, and UI touchpoints. Known for jumping into unfamiliar technologies and complex codebases, she focuses on making development workflows easier and more reliable for her teammates through pragmatic process improvement. Her open-source contributions to core Spinnaker components (gate, orca, clouddriver, echo, front50, deck) reflect a deep operational understanding of delivery pipelines and infrastructure. Optimistic and collaborative, she pairs curiosity-driven learning with practical engineering to ship durable solutions that reduce friction for developers.
10 years of coding experience
5 years of employment as a software developer
Pioneer High SchoolBachelor of Science and Engineering, Industrial Engineering, Bachelor of Science and Engineering, Industrial Engineering at University of Michigan
Github Skills (52)
api-rest10
caching10
kubernetes10
javascript10
docker10
back-end-development10
redis10
apidoc10
api-design10
groovy10
restful-api10
fest10
load-balancing10
dockers10
networking10
Programming languages (10)
Github contributions (5)
spinnaker/echo
Feb 2018 - Jan 2021
Spinnaker Eventing Service
Role in this project:
Back-end Developer & DevOps Engineer
Back-end Developer & DevOps EngineerContributions:45 releases, 3 reviews, 52 commits in 2 years 11 months
Contributions summary:Emily primarily focused on enhancing the Spinnaker Eventing Service, particularly the pubsub functionality. Their contributions include adding support for AWS SQS/SNS, integrating Redis for message handling and implementing a method for processing duplicate messages. They also refactored the pubsub modules and addressed aspects of AWS SQS, including SQS worker startup and permissions. The user's work encompassed both backend logic and deployment considerations within the context of a cloud-native eventing service.
eventingspinnaker
spinnaker/clouddriver
Jun 2016 - Jun 2019
read and write operations across cloud providers
Role in this project:Back-end Developer
Back-end DeveloperContributions:44 releases, 1 review, 65 commits in 3 years
Contributions summary:Emily contributed to the `clouddriver` repository, specifically focusing on OpenStack and Kubernetes integrations. Their commits include adding functionality for cloning OpenStack server groups, adding null checks in the Kubernetes provider to improve caching performance, and improving the consul integration. They also made various bug fixes, including correcting the autoscaling type server group caching agent and null checks for image filtering.
gcpproviderscloudcloud-providersazure
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.