Bagrat Lazaryan
Senior DevOps Engineer at APARAVI
Yerevan, Armenia
Summary
👤
Senior🎓
Top SchoolBagrat Lazaryan is a Senior DevOps Engineer with 11 years of experience designing, automating and operating cloud-native infrastructure across AWS, GCP, Azure and on-prem Kubernetes. He builds reusable Terraform modules, resilient CI/CD pipelines and automated data workflows—often prioritizing simplicity and automation to reduce the need for documentation. His background spans roles as Cloud Architect and SRE where he migrated CI systems, optimized cloud costs, and supported microservices at scale for mobile and web products. An occasional open-source contributor, he helped resolve cross-platform encoding and documentation issues for the widely used music21 computational musicology toolkit, reflecting a practical eye for interoperability. Based in Yerevan, Armenia, he pairs a formal education in information security with studies in AI and robotics, and brings a quietly pragmatic, multidisciplinary curiosity to infrastructure challenges.
11 years of coding experience
7 years of employment as a software developer
Artificial Intelligence and Robotics, Artificial Intelligence and Robotics at Sapienza Università di RomaBachelor of Engineering (B.Eng.), Organization and Technologies of Information Security, Bachelor of Engineering (B.Eng.), Organization and Technologies of Information Security at State Engineering University of Armenia
English, Russian, Italian, Armenian
Github Skills (7)
file-handling10
file-processing10
file-access10
python10
fileio10
utf10
documentation8
Programming languages (18)
Github contributions (5)
cuthbertLab/music21
Sep 2015 - Oct 2015
music21 is a Toolkit for Computational Musicology
Role in this project:
Back-end Developer
Back-end DeveloperContributions:6 commits, 2 PRs in 13 days
Contributions summary:Bagrat primarily focused on resolving encoding issues and improving the documentation generation process within the music21 project. They addressed a Windows-specific problem where the documentation build failed due to character encoding incompatibilities. Their work involved explicitly specifying UTF-8 encoding when reading and writing files, including using `io.open` for broader compatibility. Additionally, the user merged upstream changes and made minor adjustments to existing code.
dtwpythonmusicologymusic21music
bagratte/charts
Apr 2019 - Jul 2019
Curated applications for Kubernetes
Contributions:13 pushes in 3 months
containersk8skubernetes
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.