At the time, there were no established processes for tracking work, and projects were often defined ad hoc. Everything was new, and the role came with many learning curves that ultimately helped shape a more efficient environment. As the first team member in this function, I needed to stay flexible and manage a wide range of tasks.Lead and contributed with several projects that enabled developers to deliver reliable and efficient products by building automated, scalable, and well-organized DevOps environments

At the time, there were no established processes for tracking I contributed to creating GitHub Actions workflows for our repositories, implemented automated tests through scripting, containerized applications with Docker, and set up monitoring solutions using AWS CloudWatch and Logz.io. I also utilized version control best practices to maintain and evolve our codebase.
Later, I had the opportunity to step into a management role, leading a team of three full-time engineers and two additional engineers who temporarily supported the DevOps team for a specific project.

During this time, I developed strong expertise in AWS storage services, IAM, and security. I also worked extensively with configuration management tools (Puppet, Ansible), version control (Git), and scripting languages (Bash, Python), maintaining a consistent focus on automation, integration, and operational excellence.I was later promoted to a DevOps role, where I focused on building development infrastructure, automating processes, and ensuring secure, reliable systems. In this position, I supported developers, implemented CI/CD pipelines, and delivered scalable platforms—ultimately leading a platform team centered on containerization and Kubernetes.