Gautam Teja K

Project: MedLine Industries

• Role: Lead Engineer
• Environment: Git, Maven, Jenkins, Nexus, Tomcat, Linux, Ansible, Terraform, Docker, Kubernetes
• Architected and automated CI/CD pipelines using Jenkins, integrating tools like Git, Maven, SonarQube, Nexus, Docker, and Kubernetes to ensure continuous delivery across all environments.
• Provisioned and managed cloud infrastructure on AWS (EC2, S3, EBS, ELB) using Terraform, creating reusable modules to support multiple projects.
• Managed the end-to-end container lifecycle by writing Dockerfiles, building custom images, and orchestrating deployments to a Kubernetes cluster configured with kubeadm.
• Administered GitHub repositories, managing branches and tags to maintain source code integrity and a smooth release process.
• Configured Jenkins Master-Slave architecture to enable parallel builds, significantly reducing build times and increasing pipeline efficiency.
• Automated daily build and deployment processes to development, QA, and production environments, and configured nightly builds for proactive validation.

Project: BlueCross BlueShield

• Role: DevOps Engineer
• Environment: Git, Shell Scripting, Tomcat, Linux, Maven, Nexus, Jenkins, Docker, Terraform, Ansible, AWS
• Provided 24/7 support for critical production and non-production systems, ensuring high availability and a swift response to incidents.
• Utilized Dynatrace and Splunk for real-time application and infrastructure monitoring, establishing dashboards and alerts for proactive issue detection.
• Managed over 12 years of historical data within a cluster environment, ensuring data integrity and accessibility.
• Handled a high volume of ServiceNow tickets, ensuring timely resolution of infrastructure and application-related issues.
• Collaborated with the development team to assist with code deployments and ensure adherence to security and governance policies.
• Documented deployment procedures and best practices in Confluence to streamline processes and facilitate knowledge sharing.
• Participated in regular Disaster Recovery (DR) drills and maintained recovery runbooks.