name: Nikhil Anand
role: DevOps Intern @ Telangana Police Academy
education: B.Tech Data Science | SNIST | Diploma in Cloud Computing & Big Data
focus: [ DevOps, MLOps, LLMOps ]- Deploying, automating, and monitoring internal government platforms on on-premise infrastructure
- Designing and implementing CI/CD pipelines for reproducible, zero-downtime deployments
- Building observability stacks with Prometheus, Grafana, and ELK for production systems
- Engineering containerized workloads with Docker and Kubernetes
- Focused on high availability, reliability engineering, and infrastructure automation
DevOps & Infrastructure
CI/CD & Version Control
Cloud Platforms
Monitoring & Observability
Programming
Databases
| Domain | Technologies |
|---|---|
| Operating Systems |    |
| Containers & Orchestration |   |
| CI/CD |    |
| Web & Reverse Proxy |  |
| Monitoring |   |
| Log Management |    |
| IaC & Config Mgmt |   |
| Version Control |    |
To enable the snake animation, add this GitHub Actions workflow to your profile repo at
.github/workflows/snake.yml
- Scaling DevOps automation across CI/CD, provisioning, and configuration management
- Optimizing on-prem infrastructure for government platforms with zero-downtime deployment patterns
- Engineering containerized workloads with Docker and Kubernetes for production environments
- Embedding Infrastructure as Code mindset across every layer of the stack
- Designing reliability-first architecture with observability, alerting, and failure recovery baked in
- Building observability and monitoring pipelines with Prometheus, Grafana, and ELK
More About My Engineering Philosophy
"Production is sacred. Every deployment should be reproducible, every system observable, every failure recoverable."
- I believe infrastructure must be codified, version-controlled, and peer-reviewed — no manual changes in production, ever.
- Observability is not optional. If you can't measure it, you can't improve it. Metrics, logs, and traces are first-class citizens in every system I build.
- Automation exists to eliminate toil, not to replace understanding. I automate deliberately and document the why behind every pipeline.
- Reliability engineering starts at design time, not incident time. I architect for failure because failures are inevitable — downtime is not.
- The best infrastructure is invisible — engineers ship features, not fight deployments.
Infrastructure Philosophy
"Treat infrastructure as a product — with users, SLAs, and continuous improvement."
- Automation over manual processes. If a task is done more than once, it should be scripted. If it's done more than twice, it should be a pipeline.
- Observability before scaling. Instrument first, optimize second. You cannot scale what you cannot see.
- Reproducibility in deployments. Every release must be versioned, every deployment traceable and repeatable.
- Infrastructure as a product. Internal platforms deserve the same rigor as customer-facing services — documentation, testing, and iteration.
- Reliability as a feature. Uptime is not luck. It is engineered through redundancy, graceful degradation, and relentless testing.