Senior GCP Cloud Engineer, Ganeshguri, Guwahati
A Guwahati-based technology employer is hiring a Senior GCP Cloud Engineer for an on-site role at its Ganeshguri office. The role sits within the Cloud & DevOps function and focuses on running production workloads on Google Cloud Platform, with the person owning infrastructure automation, deployment pipelines, and day-to-day platform reliability. It's a full-time position, and given the scope of systems one engineer will own, it ranks among the more senior GCP cloud engineer roles in Guwahati right now. The team is currently running a mix of managed GKE clusters and a handful of legacy VM-based services that are gradually being migrated over, so the work spans both keeping the old pieces stable and building the new ones properly from the start.
What You'll Be Doing
- Build and maintain CI/CD pipelines that move code from development into staging and production on GCP
- Automate infrastructure provisioning using Terraform, replacing manual setup wherever it still exists
- Troubleshoot issues that surface across development and production environments, sometimes under real-time pressure when something in production breaks
- Monitor the health of Kubernetes clusters and respond when workloads misbehave or scale unexpectedly
- Work with the rest of the engineering team on infrastructure standards, access controls, and cloud cost management
- Keep documentation for deployment procedures and infrastructure changes current enough that someone else could pick up the work without a handover call
- Review infrastructure-as-code changes submitted by other engineers before they reach production
Production issues in a role like this rarely announce themselves cleanly. A batch job that has run fine for months might suddenly start timing out because a downstream API changed its rate limits, and figuring that out at two in the afternoon with customers waiting is part of the actual job, not an edge case someone forgot to mention. Weeks vary quite a bit: some are mostly quiet maintenance and small provisioning requests, and others involve an afternoon spent tracing a single failure through four services before finding the actual cause.
What the Role Requires
This posting sets a bachelor's degree as the education floor, and for a senior cloud opening like this, employers usually want a cloud certification from AWS, Azure, or GCP alongside it. Most people who land roles like this studied something computing-related in college, but the exact major tends to matter less than what someone actually built and broke afterward. The experience bar is 66 months of hands-on work with cloud infrastructure, containerization, and automated deployment pipelines, and that experience needs to be current rather than a skill set picked up several roles ago and left untouched since.
On the technical side, this role targets experienced professionals rather than someone in their first cloud role, and the employer has said as much. Required skills for this position include:
- Google Cloud Platform, at a level that goes beyond following documentation for basic setups
- Kubernetes, including day-to-day cluster operation and troubleshooting
- Terraform, for both writing new modules and managing existing state
- Scripting in Python or Bash, enough to automate repetitive infrastructure tasks
Someone stepping up from a general DevOps or sysadmin background into a GCP-specialist position should expect the interview to probe fairly deep into Kubernetes internals and Terraform state management, not just surface familiarity with the tools.
Good to Have
The following aren't required, but they would make an application stronger and give the hiring manager fewer open questions to ask in the interview.
- A professional GCP certification such as Cloud Architect or Cloud DevOps Engineer
- Time spent building alerting and dashboards on a stack such as Prometheus with Grafana
- Familiarity with a CI/CD platform such as Jenkins or GitLab CI, on top of using Terraform for provisioning
- Some exposure to cost optimization or FinOps practices on a public cloud
- Prior experience working across more than one cloud provider, even where GCP was the primary one
Missing one or two of these isn't a dealbreaker if the core Terraform and Kubernetes experience is strong. This posting came to us through Naukri Mitra, and the employer has been specific about wanting someone who can operate independently rather than needing close supervision on routine infrastructure decisions.
Compensation and Benefits
This role pays up to ₹1,79,000 a month, which is toward the upper end for a senior GCP cloud engineer salary in Guwahati. Annual performance reviews also mark when compensation and scope are revisited together, so raises here tend to track the infrastructure responsibility someone has taken on over the year rather than following a fixed schedule. The benefits package includes:
- Health insurance
- Paid time off
- Performance-linked bonuses
- Relocation assistance for candidates moving in from outside Guwahati
- Accommodation support while settling in
Location and Team
The office sits in Ganeshguri, one of Guwahati's more established commercial areas, and the role is fully on-site rather than hybrid or remote. Someone already living in the city will have a shorter transition than someone relocating, though accommodation support exists specifically for the latter. Cloud and DevOps hiring in the Northeast is smaller than what you'd find in Bangalore or Hyderabad, and this employer is among the more active companies hiring GCP cloud engineers in Guwahati for infrastructure roles at this level.
The team is small by design. There isn't a large platform group to hide inside of, so decisions this person makes about infrastructure tend to stick, for better or worse, and get revisited less often than they would at a bigger company. Reporting is to the engineering lead directly rather than through a middle layer of management, which means infrastructure proposals generally get a decision within days instead of sitting in a review queue.
How to Apply
Candidates should come ready to talk in specific terms about Terraform modules they've written, Kubernetes clusters they've run day-to-day, and at least one production incident they diagnosed and resolved themselves. The interview process includes a technical discussion focused on infrastructure design choices, not just a resume walk-through. There's no fixed cutoff date attached to this listing; the employer will keep reviewing candidates until the seat is filled.
