I'm Himanshu Kumar - a Senior Automation QA Engineer from Noida, India, actively transitioning into DevOps Engineering.
I spent 5+ years making sure software doesn't break - writing test frameworks, CI pipelines, and automation suites that run thousands of validations before a single line reaches production. Now I'm channeling that same obsession with reliability into the infrastructure layer: building pipelines, containerizing workloads, provisioning cloud infrastructure, and making deployments something you look forward to, not dread.
Most DevOps engineers learn to care about quality. I already do - from the other side of the wall.
π Noida, India Β |Β π’ Bhavna Software India Pvt Ltd Β |Β π¬ himanshu.kumar244@gmail.com
QA Automation (5+ yrs) DevOps Transition (Now) Target Role
ββββββββββββββββββββββ ββββββββββββββββββββββββββββββββββ βββββββββββββββββββββ
β
Selenium / TestNG π Docker + Kubernetes π― DevOps Engineer
β
CI with Jenkins π Terraform (AWS IaC) π― Platform Engineer
β
API Testing π Ansible Automation π― SRE / Cloud Engineer
β
Git workflows π GitHub Actions CI/CD
β
Java / Python π Shell Scripting (production-grade)
β
Postman / REST π Linux deep-dive
π AWS (EC2, S3, IAM, VPC)
| βοΈ Cloud & IaC |
|
| π³ Containers & Orch. |
|
| βοΈ CI/CD & GitOps |
|
| π» Languages |
|
| π§ͺ QA & Testing |
|
| π₯οΈ OS & Tools |
|
π³ Docker DevSecOps LabProduction-grade container portfolio covering the full Docker lifecycle β from Dockerfiles to security scanning. Highlights:
β 3 stars Β· 146 commits |
βΎοΈ DevOps Learning LabEnd-to-end DevOps practice covering the full toolchain β from pipeline automation to cloud infrastructure. Highlights:
β 2 stars Β· 76 commits |
|
Real-world shell scripts for sysadmin automation, monitoring, and DevOps tasks. Highlights:
β 2 stars |
π€ Jenkins CI/CD LabHands-on Jenkins learning from declarative pipelines to advanced CI/CD patterns. Highlights:
β 1 star |
Most DevOps engineers focus on speed of delivery. I bring quality thinking into the pipeline itself:
| QA Mindset I Bring | How It Helps in DevOps |
|---|---|
| π Failure-mode thinking | I design pipelines that handle edge cases, not just happy paths |
| π Test coverage awareness | I know what needs validation before code ships to prod |
| π Regression prevention | I build gates that catch regressions at the pipeline level |
| π Root cause analysis | Debugging prod issues is my natural habitat |
| π Observability instinct | I've always needed to know if something broke β and why |
focus_areas:
- "AWS Solutions Architect concepts (EC2, VPC, IAM, S3, RDS)"
- "Kubernetes: Deployments, Services, Ingress, HPA, Helm charts"
- "Terraform: Multi-resource AWS infrastructure provisioning"
- "GitHub Actions: Full CI/CD pipeline (build β test β push β deploy)"
- "Monitoring: Prometheus + Grafana observability stack"
next_projects:
- "End-to-end CI/CD pipeline: GitHub β Docker β ECR β EKS"
- "Terraform AWS: Full VPC + EC2 + RDS + ALB infrastructure"
- "Grafana dashboard: Application + infrastructure observability"
certifications_target:
- "AWS Certified Cloud Practitioner"
- "AWS Certified DevOps Engineer β Professional"
- "Certified Kubernetes Administrator (CKA)"π¬ "I used to find bugs before they reached users. Now I build the infrastructure that makes sure they never reach production in the first place."

