After 9 years in IT support, I learned one thing clearly:

The best support is the support that never needs to happen.

So I moved from manually fixing issues to building automated, self-healing systems that reduce incidents instead of reacting to them.

Auto-detects failures and recovers services without human intervention.
Tech: Prometheus, Alertmanager, Flask (Python), Ansible, AWS EC2
Impact: Auto-recovery in < 60 seconds, no manual restarts
👉 View Project

End-to-end automated build, test & deployment for Node.js applications.
Tech: GitHub Actions, Docker, DockerHub, Node.js
Impact: Zero-touch deployments from commit to production
👉 View Project

Production-ready static site with automated deployments and global delivery.
Tech: S3, CloudFront, GitHub Actions
👉 View Project

• 9 years handling real production incidents in IT support roles
• Applying the same troubleshooting mindset to cloud infrastructure & automation
• Focused on reliability, monitoring, and reducing manual intervention

• AWS Certified Solutions Architect – Associate (Valid till Nov 2026)
• Microsoft DevOps Engineer Expert (AZ-400)
• Microsoft Azure Administrator (AZ-104)

Dell (2015–2021): High-volume production troubleshooting & documentation
Capgemini (2021–2022): Monitoring (New Relic), incidents, SLA ownership
2023–Present: Cloud & DevOps transition with hands-on, production-style projects

• Cloud Support / Cloud Operations roles
• Junior / Entry-level DevOps Engineer roles
• Freelance cloud automation projects

• 9 years real-world production troubleshooting experience
• Monitoring-first mindset (New Relic, Prometheus)
• Strong documentation & incident-handling skills
• Clear communication with clients & stakeholders

Users don’t care about your tech stack.
They care if the system works when they need it.

Support taught me how systems break. DevOps taught me how to prevent it.

⭐ Star repos if useful | 🤝 Open to collaboration