DevOps Engineer
I keep systems running — servers, deployments, and everything that has to survive contact with real traffic.
I got into programming young — Python art in 10th grade, then a run of small builds through school and college: an HTML/CSS/JS calculator clone, Java forms in JFrame, a hostel management app in Python and Tkinter.
My final-year project, Loco, was meant to be a location-based social app — a React frontend, with a serverless AWS backend on Lambda, DynamoDB, and SQS. I never got around to actually hosting it, but building it taught me something: I cared a lot less about the interface and a lot more about what was running underneath it. That's also where I first ran into the idea of DevOps, and it stuck.
I ended up as a DevOps intern at CloudHouse Technologies, which runs its own hosting control panel, Cloudstick — hands-on with Linux servers, client support, and hardening Nginx with a custom WAF. It was a solid grounding in server administration, and around six months in, I knew I wanted to go deeper into DevOps specifically — automation, CI/CD, infrastructure as code — rather than stay in general server support. I moved on to focus on that, even though I'd been offered a promotion to stay.
I'm back to sharpening my skills properly now — currently building a tool that scans Docker and Terraform configs for security issues and comments directly on pull requests. I'm looking for a full-time DevOps role where I can go deeper into the infrastructure and security side of things.
Describe what you need built — I'll learn whatever it takes to get there.
No system is fully secure to me — I'll notice a flaw that might never actually happen, and I still think it's worth naming.
I default to working through a problem alone before it occurs to me to just ask. That's slowly changing.
also comfortable scripting in shell and python when the infrastructure needs it.
Where it started
My final-year project — meet people nearby through location-gated groups and chat. React frontend, AWS Lambda backend, DynamoDB and SQS underneath, Google Maps for geolocation. I never got around to actually hosting it. But building the backend is what made me realize infrastructure was what I actually cared about — and where I first heard the word 'DevOps.'
Catches security issues in Docker and Terraform configs before they ever reach production.
A tool that scans pull requests for security issues in Docker and Terraform files and comments the findings directly on the PR.
A fully containerized microservice platform, deployed to production-style infrastructure entirely through code.
Containerized Go, Java, and Python microservices with Docker. Provisioned an EKS cluster inside a custom VPC with Terraform, with remote state in S3. Deployed via Kubernetes manifests, exposed through an ALB Ingress Controller with a custom domain on Route 53. Built a GitHub Actions CI pipeline to validate and update manifests on pull requests, deployed continuously through ArgoCD.
A pipeline that tests for security issues before anything reaches the cluster.
Built Jenkins pipelines to build, test (OWASP, SonarQube), scan (Trivy), and deploy Docker images using Jenkins Shared Libraries. Automated Kubernetes manifest updates and GitOps deployment via ArgoCD on AWS EKS. Managed Kubernetes deployments for frontend, backend, Redis, and MongoDB. Set up Prometheus and Grafana for real-time monitoring.
Multi-environment infrastructure that tears itself down when it's not needed.
Automated multi-environment AWS infrastructure with Terraform. Built environment-specific CI/CD pipelines in GitHub Actions, with secrets and configs managed via S3 and GitHub Secrets. Implemented auto-shutdown policies to control cloud costs, and automated Java 21 deployment on EC2 via Maven.
Something I believe
Nothing is fully secure. During my internship, I updated the company's Nginx stack and implemented a Web Application Firewall using the OWASP Core Rule Set. I'm carrying that further now, building a tool that scans Docker and Terraform configs for security issues before they ever reach production.
2026 — Present
Independent
Back to focused work after a short break — building a tool that scans Docker and Terraform configs for security issues, while applying for full-time DevOps roles.
Jan 2026 — Jun 2026
CloudHouse Technologies
2020 — 2024
Kerala Technical University (KTU) — 7.06 CGPA
2018 — 2020
Kerala State Board
First real programming exposure — Python art in 10th grade led me to pick Computer Science for +2, where I picked up HTML, CSS, and JavaScript, built a basic calculator app modeled on the iPhone's, and scored 200/200 in C++.
Open to full-time DevOps opportunities. I usually reply within a day.
or email directly at nihaltp101@gmail.com