There's a full-time, on-site Cloud Security Engineer opening at IT City, Sector 82, in Mohali. The cloud environment this person secures runs real production workloads, so a misconfiguration here isn't a theoretical risk sitting in a slide deck somewhere. The role sits within the cloud and DevOps function, working alongside infrastructure engineers rather than as a standalone security silo. Pay for the position runs up to ₹102,000 per month, reflecting the specialized nature of cloud security work.
The Skills This Seat Needs
- Practical use of cloud security tools, the kind that actually flag a misconfigured resource rather than just generating a report nobody reads.
- Solid IAM knowledge, understanding not just how to grant access but when a permission is broader than it needs to be.
- Working familiarity with compliance requirements relevant to cloud environments, and enough judgment to know when a control is a genuine gap versus a paperwork formality.
- Comfort across at least one major cloud platform, deep enough to actually harden it rather than just deploy on it.
These overlap more than the list format suggests. IAM misconfigurations are frequently the root cause of vague, generic findings on compliance reports.
An AWS Certified Security Specialty or similar cloud security certification carries real weight in the screening process, though hands-on incident response experience matters just as much. Familiarity with a cloud security posture management tool such as Wiz or Prisma Cloud is a genuine plus, and any exposure to scanning infrastructure-as-code templates for security issues before they ever get deployed is worth calling out on a resume. None of these are hard requirements, but they do shorten how long it takes someone to become fully productive once they've started.
What You'd Actually Be Doing
- Set up and lock down cloud infrastructure so it's secure from the start, not patched after the fact.
- Build security checks directly into deployment pipelines to catch risky configurations before they reach production, not after.
- Keep watch over system activity for signs something's off, and dig into anything that looks like a genuine security event.
- Move fast when something breaks in the infrastructure itself, whether that's an exposed resource, a compromised credential, or traffic that doesn't look right.
- Document what was found and fixed after any incident, so the same gap doesn't quietly reopen a few months later.
A recent example worth sharing: a routine audit turned up a storage bucket that had been left publicly accessible for several days after a migration, the kind of gap that's easy to introduce during a rushed cutover and easy to miss unless someone's specifically checking for it. Catching that kind of thing before it becomes an actual data exposure is a core part of the job, not an occasional special project. Some weeks lean toward this kind of proactive auditing, and others get pulled almost entirely into responding to something that's already flagged as urgent.
Education and Experience
A bachelor's degree, most commonly in computer science or information technology, is the standard entry point for this role, with a related technical field also considered. Two years of hands-on experience with cloud infrastructure and security is expected, along with real comfort working inside a deployment pipeline rather than only reviewing one after the fact. Someone coming from a general cloud or DevOps background who's picked up security responsibilities along the way, rather than holding a security title from day one, would still be a strong candidate. What matters most is whether the security instincts are already there, even if the job title on a previous resume didn't explicitly say so.
How This Role Develops
An engineer who consistently catches real issues, not just ones flagged automatically by a tool, tends to move toward owning security architecture decisions rather than only responding to alerts. That shift depends more on judgment built through actual incidents than on years alone. Someone who's mostly worked from playbooks without much exposure to ambiguous, judgment-call situations would likely need some time closing that gap before taking on a more senior security role. Exposure to a genuine cross-team incident, one involving both infrastructure and application teams at once, tends to accelerate that growth faster than routine day-to-day work alone.
Compensation and Benefits
- A monthly salary of ₹102,000.
- Health insurance.
- Paid time off.
- Provident fund contributions.
- Relocation assistance and accommodation support for candidates moving to Mohali, since this is an on-site role.
This salary reflects a genuine security specialization rather than a general cloud engineering rate, which tracks with the added responsibility of catching problems before they turn into incidents rather than only fixing what's already broken.
Working Out of IT City
The office is in IT City, Sector 82, part of Mohali's dedicated technology corridor, and there's no remote or hybrid option built into this posting. Several established tech employers are located in the same zone, which keeps a steady pool of experienced cloud and security talent circulating locally rather than concentrated within a single company. This role was listed through Naukri Mitra. The security team here works closely with the infrastructure engineers building out new services, so much of the work happens in direct conversation rather than through tickets alone. Mohali's tech corridor has grown enough over recent years that it now draws candidates relocating from other parts of Punjab and neighboring states specifically for roles like this one. Chandigarh is close enough that some team members split their personal lives between the two cities with little added friction.
How to Apply
Submit a resume that specifies which cloud platforms and security tools you've worked with hands-on, along with any incidents you've helped investigate or resolve. The first interview round centers on a real-world misconfiguration scenario, walking through how you'd spot and fix it, followed by a conversation about your experience working specifically within CI/CD pipelines. Provide specific examples rather than general descriptions of past responsibilities; the interviewers here tend to ask follow-up questions until they hit on a concrete detail. A final conversation with the infrastructure lead usually wraps up the process for candidates who make it that far.
