About the role
Associate DevOps EngineerExperience: 0-1 yearsLocation: Bangalore / KolkataTeam: DevOps, PrismforceEmployment type: Full-timeAbout the rolePrismforce runs its platform on AWS, Kubernetes, using GitOps and IaC priniciple. We are looking for an Associate DevOps Engineer who is early in their career, curious about how production systems work, and ready to start contributing in the first week. You will learn the platform with the team, work under review and guidance, and over time grow into owning small parts of it.What you will do
- Follow runbooks and existing patterns to update applications through Helm values, Argo CD, and Terraform.
- Open small, focused pull requests and explain each change clearly before it is applied.
- Debug workloads on Amazon EKS by reading pod status, services, logs, and events.
- Support Jenkins pipelines: investigate failed builds, create jobs, and flag recurring issues.
- Monitor environment health in Grafana and raise anomalies early before teams know about it.
- Write clear notes in tickets and PRs so the next person can follow what you did and why.
- Join incidents as a fact-gatherer: collect logs and timelines, stay on the runbook, and escalate when unsure. All production changes remain reviewed.
- Take on small automation tasks (scripts, repeated checks) as you build confidence.
- Linux commands with shell scripting
- Branching models and strategies
- Docker basics (building images, running containers, reading Dockerfiles)
- Basic networking: DNS, HTTP/HTTPS, ports, and how a request travels
- Bash or Python, enough to automate a repeated task
- AWS fundamentals: IAM, EC2, S3
- Hands-on Kubernetes exposure (minikube, kind, or a managed cluster)
- Familiarity with Terraform or any Infrastructure-as-Code tool
- Experience with CI/CD tools such as Jenkins or GitHub Actions
- Basic understanding of Prometheus/Grafana or any monitoring tool
- AWS Cloud Practitioner / Associate certification or CKA/CKAD prep
- Reviewed changes only: every production change goes through a pull request and review.
- Runbook first: you will have documented patterns to follow, plus people to ask.
- Learn in the open: questions are expected, and writing down what you learn is part of the job.
- Growth path: from following runbooks, to owning small services or pipelines, to contributing to platform improvements.
- Clear communication skills
- Comfortable working with team in cross geography.
- Bring a proactive and helpful attitude to the team.
- Careful, methodical habits around production systems
- Ownership: you finish what you start and ask when blocked
- Comfort working with a team on shared infrastructure