← Sottava, jobs the hour they open
28 d agofound 5 d ago
NetDevOps - DevOps Engineer
What the posting is about
Own automation, CI/CD pipelines, and self-service tooling for network changes. Collaborate with network engineers in a NetDevOps partnership. Stabilize environment, implement GitOps workflows, and mature automation toolchain.
Read out of the posting
LevelNot stated
Experience asked5+ years
EmploymentNot stated
LocationBengaluru, Karnataka, India
RemoteNot stated
Visa sponsorshipNot stated
SalaryNot published, and most postings do not
Posted2026-09-07
Found viaworkable, direct from their system
We saw it 23 days after it went up.
The posting, as the company wrote it
About the Role
This is a DevOps-first position within a NetDevOps partnership model. Network engineers own the network configuration and policy layer; this role owns the automation, CI/CD pipelines, and self-service tooling that let those changes ship safely. You will not be doing traditional network engineering — you are the software/platform engineering counterpart in the partnership.
Key Responsibilities
Build and maintain CI/CD pipelines in Jenkins, including custom Groovy shared libraries
Deploy and manage applications on OpenShift (Kubernetes) using Helm charts
Design and support GitOps workflows that enable network engineers to self-service infrastructure changes
Write production-quality Python and Bash automation tooling
Conduct code reviews, debug pipeline failures, and maintain technical documentation
Integrate monitoring and observability using Telegraf, Prometheus, and Grafana
Required Qualifications
Jenkins expertise with Groovy scripting (non-negotiable requirement)
5+ years of production-quality Python development experience
5+ years of DevOps or platform engineering experience
Strong proficiency in Git and Linux/Bash scripting
Strong written English communication skills
Self-motivated, able to work effectively in an async-first environment
Technical Environment
Jenkins, Groovy, Python, Bash, OpenShift, Kubernetes, Helm, Ansible, Nexus, Telegraf, Prometheus, Grafana, Git
What Success Looks Like
In the first 30 days: stabilize the environment by fixing broken pipelines and deploying critical application updates.
By 90 days: GitOps workflows are fully operational, with network engineers confidently using self-service tooling.
Within 6–12 months: the automation toolchain reaches full maturity and operates with minimal maintenance overhead.
Team & Work Environment
You will join a 10-person team operating on Kanban methodology with daily standups and an async-first culture (Microsoft Teams). The role includes participation in a periodic on-call rotation (weekly or bi-weekly). This is a high-visibility opportunity to rebuild a critical automation capability supporting network operations at scale.
Copied from GSSTech Group’s own board, not rewritten. Original ↗
Also open at GSSTech Group
Why this page exists
We read companies’ own hiring systems every hour, 1,123 of them, and show a job the hour it opens instead of when a job board gets around to indexing it. We saw it 23 days after it went up.
The feed is free. No card, no trial to expire.