hiring for infra · devops · sre · /infra
Hiring an Infrastructure / DevOps / SRE Engineer?
Terraform-first AWS, GitOps delivery, and observability that pays for itself.
I own infrastructure end to end: multi-environment Terraform with remote state and drift detection, GitHub Actions with OIDC and no long-lived keys, Ansible for the last mile, and an LGTM observability stack I open-sourced. I've cut a cloud bill by 76% and deployment cycles by 40%, and I'm moving services to Kubernetes with ArgoCD, Istio and Vault.
DevOps EngineerPlatform EngineerCloud Engineer (AWS)Site Reliability EngineerInfrastructure Engineer
76%
AWS spend reduction, zero downtime
40%
faster deployment cycles
0
long-lived cloud credentials (OIDC)
3
environments under one IaC platform
// 01 — relevant experience
Where I did this before.
- Own infra provisioning across dev/staging/prod with Terraform (VPC, EC2, RDS, IAM) as Infrastructure-as-Code; GitHub Actions pipelines enforce plan-before-apply, drift detection, and SSM/OIDC-backed secrets with zero long-lived credentials.
- Architected infra-ops, a centralized multi-environment IaC platform: S3 remote state, DynamoDB state locking, reusable Terraform modules (networking/compute/storage/IAM) and Ansible roles for PostgreSQL/PostGIS, Nginx+Certbot and PM2 deploys.
- Built lgtm-sidecar, a resource-capped observability stack (Grafana Alloy, Loki, Tempo, Prometheus, Pyroscope, Alertmanager) as a decoupled EC2 sidecar with distributed tracing and rate-capped tail sampling.
- Built an AI-powered BaaS platform generating full-stack e-commerce apps (RESTful APIs, DB schemas, frontend) from prompts, deployed on AWS (EC2, ECS, Lambda, Step Functions, DynamoDB, Valkey, CloudWatch).
- Re-architected monolithic AWS infra into event-driven, containerized microservices, cutting monthly cloud spend by 76% with a zero-downtime migration.
- Owned observability and on-call readiness with CloudWatch alarms and structured logging, reducing mean-time-to-detect and accelerating root-cause resolution.
2025-11 → present
Software Engineer
RaghuvarTech (Raghuvar IT Solutions LLP)
Own infrastructure, CI/CD and observability for a multi-service platform; lead architecture reviews across backend, infra and agentic-AI systems.
2025-06 → 2025-10
Software Development Engineer
InkHub.in / BRMH.ai
Built an AI-powered backend-as-a-service that generates full-stack e-commerce apps from prompts, and re-architected its AWS footprint.
// 02 — selected case studies
Proof, with numbers.
// 03 — skills for this role
The toolbox.
IaC & cloud
- Terraform (modules, remote state, locking)
- Ansible
- AWS: VPC, EC2, ECS, RDS, S3, IAM, SSM, Lambda
- cost optimisation
Delivery
- GitHub Actions
- OIDC auth
- plan-before-apply
- environment gates
- drift detection
- health-check rollbacks
Containers & platform
- Docker
- Kubernetes
- Helm
- ArgoCD (GitOps)
- Kustomize
- Istio
- Vault / External Secrets
Observability & SRE
- Grafana
- Prometheus
- Loki
- Tempo
- Pyroscope
- OpenTelemetry / Alloy
- Alertmanager
- SLOs, on-call runbooks
// 04 — relevant writing
How I think about it.
012 min
Infrastructure as Code: Bridging Terraform and Ansible
A deep dive into how Terraform and Ansible complement each other in modern infrastructure provisioning and configuration management.
devopsterraformansibleinfrastructure
023 min
Zero long-lived cloud keys: GitHub Actions → AWS with OIDC
How to delete every AWS access key from your CI and your laptop, replace them with short-lived roles, and make the blast radius of a leaked secret exactly zero.
awsiamoidcgithub-actions
033 min
Terraform drift detection that opens GitHub issues
Drift is not a Terraform problem, it's a feedback-loop problem. Here is the nightly job that re-plans every environment and files an issue when reality disagrees with code.
terraformdevopsgithub-actionsinfrastructure
// 05 — recruiter faq
The questions you were going to ask.
What does your Terraform setup look like?
Directory-per-environment with shared, versioned modules (networking, compute, storage, IAM), S3 remote state with DynamoDB locking, PR-triggered plans, auto-apply to dev, manual gates for staging/prod, and a nightly drift job that opens GitHub issues.
How do you handle secrets and credentials?
No long-lived keys: GitHub Actions assumes AWS roles via OIDC, runtime secrets live in SSM Parameter Store / Vault, and I'm rolling out External Secrets Operator for Kubernetes workloads.
What is your observability stack?
The LGTM stack (Loki, Grafana, Tempo, Prometheus) plus Pyroscope and Alertmanager, collected by Grafana Alloy with OpenTelemetry. I open-sourced it as lgtm-sidecar: resource-capped, tail-sampled, S3-backed.
Do you hold cloud certifications?
AWS Certified Solutions Architect – Associate (SAA-C03), June 2026.
Where are you based and can you work remotely?
Based in Mumbai, India (IST). Remote-first; I've shipped with a Seattle team across time zones and I keep 4+ hours of overlap with US Pacific or any EU zone.
What is your notice period?
Currently employed; I can start within 30 days, sooner for contract work.
// talk to me about a infra · devops · sre role
Book a 15-min call
Pick a time that fits you, or just
email me at hi@nikhilsahu.dev