Oleksii Khliupin
Senior Software Engineer at Amazon
New York, New York, United States
Summary
🤩
Rockstar🎓
Top SchoolOleksii Khliupin is a Senior Software Engineer with 11 years of experience building backend systems and scalable web platforms, currently at Amazon in New York. He has driven performance and reliability improvements for high-traffic services, including sub-second paywall optimizations for The New York Times during his EPAM tenure. A pragmatic backend specialist, Oleksii contributes to well-known open-source projects such as nytimes/gizmo and go-swagger, where he fixed memory leaks, enhanced metrics and Prometheus instrumentation, and improved code generation and schema parsing. His work reflects a strong focus on observability, error handling, and accurate API specification generation—skills that reduce production surprises and speed up delivery. Trained with a master’s in computer science from Kharkiv Aviation Institute, he blends deep systems knowledge with hands-on engineering across startups and large enterprises. Colleagues rely on him for thoughtful refactors that boost long-term maintainability as much as short-term performance gains.
11 years of coding experience
20 years of employment as a software developer
Master's degree Computer Science, Master's degree Computer Science at National Aerospace University -'Kharkiv Aviation Institute'
English, Ukrainian, Russian
Github Skills (15)
golang10
http-server10
code-generator10
swagger10
context-api10
go10
prometheus10
api10
metric10
schema9
parsing9
microservices-application9
microservices9
testing8
google-cloud8
Programming languages (4)
Github contributions (5)
nytimes/gizmo
Jan 2016 - May 2019
A Microservice Toolkit from The New York Times
Role in this project:
Backend Developer
Backend DeveloperContributions:16 commits, 14 PRs, 1 branch in 3 years 4 months
Contributions summary:Oleksii focused on implementing and improving the backend infrastructure of the gizmo microservice toolkit. Their contributions involved adding context-aware features to the simple server, improving error handling, and enhancing the metrics capabilities by enabling custom registry and prometheus instrumentation. The user also addressed memory leaks within the context service, further demonstrating their understanding of the project's architecture and performance optimization.
yorkgoogle-pubsubgizmogooglecloudtimes
go-swagger/go-swagger
Mar 2016 - Jun 2017
Swagger 2.0 implementation for go
Role in this project:Back-end Developer
Back-end DeveloperContributions:28 commits, 14 PRs, 28 comments in 1 year 3 months
Contributions summary:Oleksii primarily contributed to the `go-swagger/go-swagger` repository by fixing issues related to the code generation process and schema parsing. They addressed problems like unknown primitive types, the handling of array pointers, and map types, demonstrating a focus on improving the library's ability to accurately reflect Go code in Swagger specifications. The user also merged master branch changes and added test cases for features such as map types and security definitions, indicating a good grasp of the project's architecture and testing practices.
golangapiswagger-2code-generatorswagger-codegen
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.