This is a Senior CI/CD Engineer opening in Chennai, based out of Taramani near Tidel Park, for a Cloud & DevOps team running a full production pipeline. The role is on-site, full-time, and pays up to ₹1,25,000 a month depending on what the candidate brings to the table.
This isn't an entry point into DevOps. Whoever takes this on will already be comfortable owning a pipeline end-to-end, from a developer's first commit through to a production rollout, and will be expected to make judgment calls without someone checking every step behind them. The team is small enough that one engineer's habits show up quickly in how smoothly releases go, so this hire matters more than the job title might suggest.
People applying for CI/CD engineer jobs in Chennai often come from either a systems administration background or a development background that shifted toward automation over time. Either path works here. What matters more is whether someone has actually kept a pipeline running through a bad week, not just set one up during a calm one.
What you'll actually be doing
The pipeline work sits at the center of the job, but it doesn't stop at writing configuration files. Deployments fail, environments drift, and someone has to be the one who notices before it becomes a bigger problem.
- Build, extend, and maintain CI/CD pipelines using tools such as Jenkins and GitLab CI, covering everything from build and test stages to deployment.
- Automate infrastructure provisioning so environments can be spun up, scaled, or torn down without manual intervention.
- Troubleshoot issues across development and production environments, including failed builds, broken deployments, and configuration drift.
- Coordinate releases with development teams, timing deployments around code freezes and business-critical windows.
- Write and maintain deployment runbooks and rollback procedures so that incidents don't depend on a single person's memory.
- Monitor pipeline health and flag recurring failure patterns before they turn into outages.
Qualifications
Education-wise, the floor here is a bachelor's degree, ideally in computer science or IT, though a related engineering background works too if the practical experience backs it up. What tends to matter more at the senior level is a recognized cloud certification from AWS, Azure, or GCP, paired with genuine time spent building on cloud infrastructure, working with containers, and running automated deployment pipelines, rather than only studying them.
The certification requirement isn't there to check a box on a resume. Deployments constantly touch cloud resources in this role, and someone who's only read about a provider's networking model tends to make expensive mistakes the first time they troubleshoot a live outage at 11pm. Candidates who hold more than one cloud certification, or who've worked across providers, will stand out, though a single relevant certification paired with strong pipeline experience is enough to be considered.
On the experience side, the role calls for 84 months of direct, hands-on work in this space. That's not a number to round down or approximate; candidates should be able to walk through specific pipelines they've built or maintained when asked, including what broke, why it broke, and what they changed afterward.
Skills we're looking for
- Working fluency with CI/CD tooling, particularly Jenkins and GitLab CI
- Scripting ability in Bash or Python for automation tasks
- Solid version control practice, including branching strategies and merge workflows in Git
- Demonstrated experience automating repetitive infrastructure and deployment tasks
None of these are optional extras. They're the baseline someone would need on day one to keep the pipeline running without a ramp-up period.
Good to have
A few things aren't required but would move a candidate up the shortlist. Familiarity with Kubernetes and Docker for container orchestration is one. Exposure to infrastructure-as-code tools such as Terraform or Ansible is another, since a fair amount of the provisioning work leans on them. Some prior use of monitoring stacks like Prometheus and Grafana helps too, as does a second cloud certification beyond the one already required. None of these will disqualify someone who doesn't have them, but they do shorten the learning curve.
Life on the team
Chennai's Cloud & DevOps market remains fairly active, and CI/CD engineer jobs posted on Naukri Mitra tend to draw from a relatively experienced applicant pool, so the bar here reflects that. The team works on-site out of Taramani, close to Tidel Park, and the pace picks up noticeably around release windows. Outside of those stretches, there's more room to focus on cleanup work, documentation, and improving the pipeline itself rather than just keeping it alive.
Postmortems happen after failed deployments, and they're treated as a routine process rather than blame exercises. Someone joining this team will be expected to speak up early if a deployment plan looks risky, rather than flagging it only after something has already gone wrong. Handoffs between shifts matter too, since a pipeline issue that starts in the evening often needs context the next morning, and thin documentation makes that harder than it needs to be.
Salary for this profile is negotiable within the posted band and tends to land toward the higher end for candidates who can speak specifically about incidents they've resolved rather than tools they've merely used. Companies hiring for CI/CD engineer positions in Chennai are largely competing on exactly this: real operational depth over a long list of certifications.
Compensation and benefits
Pay for this CI/CD engineer role in Chennai ranges up to ₹1,25,000 per month, reviewed based on experience and what the candidate demonstrates during the process. Alongside the salary, the role includes:
- Health insurance coverage
- Paid time off
- Performance-linked bonuses
- On-site cafeteria facilities at the Taramani location
- Cab or commute support, standard for on-site roles at employers in this part of Chennai
How to apply
A resume for this one should show actual pipeline and infrastructure work rather than a bare list of tools. Anyone who's spent 84 months building and firefighting CI/CD systems in a senior capacity and wants full ownership of a production pipeline, not a supporting role at the edges of one, should send that resume in. Reviews happen on a rolling basis, and shortlisted candidates will hear back directly.
