DB Dashboard
Centralised database access and governance portal: automated DB user creation, role-based access requests, scheduled expiry tracking, email alerts and PII data-classification schemas.
I'm a DevOps engineer at Bajaj Finserv Health, running Azure infrastructure for two organisations (BFHL and Vidal Health): 3–5 AKS clusters and 100+ microservices.
Most of my work is on the network. When something can't reach something else, I'm the one tracing it: NSGs, UDRs, Azure Firewall policies, IPSec tunnels, ingress. I design hybrid connectivity, debug it when it breaks, and led the Nginx-to-Traefik migration across every service with zero downtime.
I take part in most architecture-level discussions on the team, handle incident escalations, and trained 3 interns from zero to shipping on Kubernetes, CI/CD and Azure.
Off the clock: F1 on race weekends, the bike when the roads are clear, and Arch Linux on my machine.
| NAME | NAMESPACE | READY | STATUS |
|---|
Walked into a pipeline that worked by habit and left one that worked by design.
A part-time remote role for a US team, running on the other side of the clock.
Where it started. The first time my code touched real infrastructure.
This is what most of my days look like. A request is failing somewhere on the path. Inspect each hop, read the evidence, then name the culprit.
Centralised database access and governance portal: automated DB user creation, role-based access requests, scheduled expiry tracking, email alerts and PII data-classification schemas.
Visual CI/CD workflow builder. Drag and drop pipeline steps and it generates GitHub Actions YAML, taking pipeline setup for non-technical users from hours to minutes.
The pager went off. The city is asleep. The bats are out.
Some engineers sleep. Some are on-call.