I build automation-first delivery workflows, internal platforms, and secure backend services that reduce manual effort and make software delivery more reliable.
My work sits at the intersection of software engineering, platform operations, system integration, and security. I am especially interested in turning repetitive operational work into documented, observable, and reusable automation.
- CI/CD, release automation, and delivery guardrails
- Internal developer platforms and workflow automation
- DevOps and DevSecOps toolchain integration
- Java and Spring Boot APIs, services, and microservices
- Containerized applications and reproducible environments
- Infrastructure as Code, platform engineering, and cost-aware operations
- Practical NoOps through automation, observability, and safe recovery
| Area | Technologies |
|---|---|
| Backend | Java, Spring Boot, Python, REST APIs, PostgreSQL |
| CI/CD | GitLab CI/CD, GitHub Actions, Jenkins |
| Containers & platforms | Docker, Kubernetes, OpenShift, Quay |
| Infrastructure & systems | Terraform, Linux, Vagrant, Nginx |
| DevSecOps | SonarQube, JFrog Artifactory, JFrog Xray |
| Current interests | NoOps, platform engineering, FinOps, AI-assisted operations |
A lightweight, containerized Next.js API with health checks, persistent Docker volumes, environment-based configuration, a multi-stage build, and a non-root runtime.
A reproducible local infrastructure project that provisions a virtual machine and Apache web server through Vagrant and automated shell-based setup.
A hands-on workspace for experimenting with Spring Boot services, microservice patterns, and backend proof-of-concepts.
A growing collection of PowerShell utilities for everyday automation and repeatable engineering tasks.
- Automate recurring work: if a task repeats, it should become a reliable workflow.
- Design security in: controls and evidence belong inside the delivery process.
- Keep systems understandable: simple, documented systems are easier to operate and improve.
- Build for recovery: automation needs observability, guardrails, and a safe failure path.
- Focus on outcomes: tools matter when they reduce delays, risk, and manual checkpoints.
- Moving from task-level automation toward event-driven, policy-aware NoOps
- Internal developer portals that centralize requests, approvals, and delivery workflows
- FinOps and GreenOps practices for cost- and resource-aware platforms
- AI-assisted operations that keep humans in control of risk and production decisions
I share practical notes, experiments, and project walkthroughs on Hashnode and Medium, covering DevOps, Linux, Git, Terraform, automation, and backend engineering.
I enjoy discussing DevOps, DevSecOps, platform engineering, internal tooling, backend systems, and the path toward NoOps.
Connect with me on LinkedIn or explore my repositories.