Based in Marathahalli, Bangalore, this senior Cloud Infrastructure Engineer role is full-time and on-site, with a salary of up to ₹1,78,000 per month.
It's built as one of the more senior cloud infrastructure engineer jobs for experienced professionals in Bangalore, not an entry point into cloud work. Whoever takes it will own real production systems from day one, not a staging environment set aside for training. The team sits under Cloud & DevOps and supports several product lines at once, so the infrastructure decisions made here ripple out further than they would on a single-product team.
Background and experience
This one calls for a bachelor's degree at minimum, most often in computer science or information technology, though the team has hired people with adjacent technical degrees before. A handful of strong candidates over the years came from electrical or telecom engineering backgrounds instead, which turned out fine once the core cloud and networking skills were already there.
On the experience side, candidates should have around 66 months of hands-on work running cloud infrastructure in production, not just in a lab account or a personal project. A recognized certification from AWS, Azure, or GCP is expected at this level too, since it signals a baseline of platform-specific depth beyond general systems knowledge. What matters more than the certificate itself, though, is whether someone has actually carried the pager for a system they built, rather than just having helped configure it once and moved on to something else.
Skills
- Solid experience with at least one major cloud platform, whether that's AWS, Azure, or GCP
- Strong networking fundamentals, including VPC design, routing, and security group configuration
- Hands-on Terraform experience for provisioning infrastructure as code
- Comfortable working in Linux environments as a daily default
Good to have
Exposure to Kubernetes or a similar container orchestration platform counts in a candidate's favor, as does hands-on time with a CI/CD tool such as Jenkins or GitHub Actions. Some background trimming cloud costs across accounts helps too, even though none of these are required to apply. A few teams have also found it useful when someone arrives already comfortable reading Terraform state files line by line, since a fair share of production problems trace back to drift between what's written in code and what's actually running.
What the work actually looks like
- Stand up and maintain the cloud infrastructure that the company's applications run on
- Build and maintain automated pipelines, so releases go out without someone manually babysitting each one
- Track system performance in production and flag reliability issues before they turn into outages
- Respond when something in the infrastructure breaks, including outside normal working hours
That last point isn't occasional. Anyone in this role is on an on-call rotation, and a rough week can mean a 2 a.m. page about a database failover that won't wait until morning. Most weeks are calmer than that, but the rotation itself doesn't pause just because the last incident was recent. A recent example from the team: a misconfigured autoscaling rule quietly let a service run out of capacity during a traffic spike, and the engineer on call had to trace it back through three layers of infrastructure before finding the actual setting that needed to change.
Pay and benefits
Pay for this role goes up to ₹1,78,000 per month, toward the higher end of what a cloud infrastructure engineer salary in Bangalore looks like for someone at the senior level. Compensation here isn't only the base number, either. Performance-linked bonuses get paid out based on individual and team targets set at the start of each cycle, rather than as a flat annual add-on everyone gets regardless of how the year went.
- Health insurance
- Paid time off
- Performance-linked bonuses
- On-site cafeteria facilities
- Cab or commute support
Where you'd be working
The office sits in Marathahalli, on the eastern side of Bangalore, in a stretch dense enough with tech offices that peak-hour traffic is worth planning around. Naukri Mitra lists a fair number of cloud infrastructure engineer jobs in Marathahalli, Bangalore specifically, since several large tech campuses sit within a few kilometers of one another in that part of the city. Commuting from the outer ring road areas is manageable outside of the morning and evening crunch, but anyone coming from farther across the city should factor in the traffic pattern before committing to the daily trip.
Team and pace
Deployment days move fast, especially during a migration or a major platform upgrade, and quieter stretches show up in between, when the main job shifts to monitoring dashboards and clearing technical debt that piled up during the last push. The infrastructure team here is lean relative to the number of services it supports, so a fair amount of ownership falls to whoever is closest to a given system rather than being spread across a large group. That said, nobody handles a major incident alone; a second engineer joins within minutes once something is flagged as customer-facing.
Most people in this role came from a mid-level cloud or systems engineering job somewhere else and moved up once they'd carried an on-call pager through at least one serious incident on their own. From here, the natural next step tends to be either a staff-level infrastructure role focused on architecture decisions across teams, or a lead position managing a small group of engineers directly.
Applying
Interviews for this role usually include a live troubleshooting exercise, working through a broken deployment pipeline on a shared screen rather than describing the fix in the abstract. Along with a resume, bring specifics: which cloud platform you've spent the most production time on, and roughly how large the infrastructure footprint was that you were personally responsible for. It also helps to mention the worst outage you've personally handled and what changed on the infrastructure afterward, since that's usually a better indicator of hands-on depth than a list of certifications and tool names. Applications are reviewed on a rolling basis, and shortlisted candidates hear back directly for the next round.
