Russell Bolles
Software Engineer 6 at Netflix
San Francisco Bay Area United States
Summary
👤
Senior🎓
Top SchoolRussell Bolles is a seasoned backend software engineer with 11 years of experience, currently driving resilient automation and tooling at Netflix as a Software Engineer 6 in the Open Connect organization. He specializes in building platforms that reduce manual toil and orchestrate large-scale appliance operations—recently authoring an OC Change Cycle service that uses Temporal for fault-tolerant workflows. Prior roles at Intuit and Northrop Grumman sharpened his skills in systems integration, emulation, and developer-facing tooling, and he has a history of improving API tooling through notable open-source contributions to the Swagger ecosystem (swagger-core, swagger-parser, swagger-codegen). Based in the San Francisco Bay Area with a CS degree from Sacramento State, he combines pragmatic engineering with a focus on measurable operational outcomes like lowering cost-per-megabit streamed. An underappreciated strength is his ability to translate complex fleet-level problems into reusable platform primitives that empower other teams to move faster.
11 years of coding experience
8 years of employment as a software developer
California State University, Sacramento
English
Github Skills (20)
open-api-v310
json10
api-rest10
apidoc10
api-design10
restful-api10
swagger10
java10
swagger-codegen10
javas10
api-specification10
code-generation10
api10
yaml10
rest-api10
Programming languages (5)
Github contributions (5)
swagger-api/swagger-core
Jan 2015 - Mar 2016
Examples and server integrations for generating the Swagger API Specification, which enables easy access to your REST API
Role in this project:
Back-end Developer
Back-end DeveloperContributions:45 commits, 10 PRs, 62 comments in 1 year 2 months
Contributions summary:Russell contributed significantly to the `swagger-core` project, focusing on enhancing the model and parameter handling capabilities of the Swagger API Specification. Their work involved implementing new classes and deserializers, specifically for parameters and references. They also made improvements to the YAML and JSON serialization processes, enhancing the accuracy and completeness of the generated API specifications. Additionally, the user refactored existing code to support relative references, enabling more flexible and maintainable API definitions.
apiopenapi-specificationspecificationapi-specificationintegrations
swagger-api/swagger-parser
Apr 2015 - Sep 2015
Swagger Spec to Java POJOs
Role in this project:Back-end Developer
Back-end DeveloperContributions:23 commits, 7 PRs, 5 comments in 4 months
Contributions summary:Russell's commits focus on enhancing the Swagger 1.0 to 2.0 conversion process within the swagger-parser project. They implemented functionality to inherit consumes and produces from the ApiDeclaration object in the conversion. The changes involve modifications to the SwaggerCompatConverter and OperationConverterTest files, demonstrating a focus on improving the compatibility and feature set of the Swagger parser. These updates likely aimed to support a more complete and accurate translation between Swagger specifications.
openapi-specificationswagger-parserspecrestswagger-spec
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.