Engineering background
My engineering background strengthens my product decisions.
I am a Technical Product Manager. DevOps, cloud, infrastructure, CI/CD, Kubernetes, automation, observability, and APIs are the foundation that makes my product decisions sharper — not a claim that engineering is my primary identity.
Most product managers stop at requirements. Most engineers stop at systems. I work across both — so I can challenge a feature that is expensive to build, spot delivery risks early, and write requirements engineering can actually ship.
Technologies
- AWS
- Azure
- Docker
- Kubernetes
- GitHub Actions
- Jenkins
- ArgoCD
- Terraform
- Infrastructure as Code
- Prometheus
- Grafana
- APIs
- Databases
- CI/CD
Selected engineering work
GitOps-based Kubernetes Deployment
GitOps practices for continuous deployment on Kubernetes with stronger delivery consistency.
Event-driven Microservices CI/CD
Automated CI/CD for containerized services — pipelines, quality gates, and faster safe releases.
Infrastructure as Code
Cloud infrastructure defined and managed as code to reduce drift and improve repeatability.
Microservices Monitoring & Observability
Monitoring and alerting with Prometheus, Grafana, and ELK-oriented observability practices.
Verified delivery impact
From employment at Pietech Technology and Credence Technology — only metrics attributable to that work.
- → Deployment time reduced by 80% (Pietech)
- → Cloud costs reduced by 30% (Pietech)
- → Issue-resolution time reduced by 60% (Pietech)
- → Deployment reliability improved by 40% (Credence)