A Lead Cloud Migration Engineer position is open in Gachibowli, Hyderabad, full-time and on-site, paying 228,000 rupees a month within the Cloud & DevOps track.
Qualifications
Candidates need a bachelor's degree in computer science, information technology, or a related field. A recognized cloud certification is also required, whether that's AWS, Azure, or GCP, since the role expects someone who can speak fluently to at least one of the major platforms rather than a generalist who's dabbled in all three without depth in any.
Eight years of hands-on experience is the bar here, specifically with cloud infrastructure, containerization, and automated deployment pipelines. That's a long enough track record to have led at least one full migration project, not just contributed to someone else's.
The certification requirement is worth being specific about. It doesn't need to be the newest badge available, and the hiring team won't quiz anyone on exam trivia. They want evidence that the candidate has gone deep enough on one platform to understand its failure modes, not just its feature list. Someone who's spent years on AWS but never touched Azure or GCP is a perfectly fine fit here; breadth across all three is not the point of this role.
What You'll Own
- Building and maintaining CI/CD pipelines across multiple services
- Automating infrastructure provisioning so environments can be stood up and torn down without manual intervention
- Troubleshooting issues that show up across both development and production environments
- Leading migration efforts, from planning the cutover sequence to validating that nothing broke on the other side
A cutover rarely goes exactly to plan. Something like a legacy database that's been quietly writing to a deprecated storage bucket for two years tends to surface only once the migration window is open, and the project lead decides whether to pause, patch, or push through.
Most weeks, the work splits between pipeline maintenance that keeps existing services deploying smoothly and forward planning for whatever the next migration phase looks like. Documentation matters more here than in many engineering roles, mainly because a migration plan that lives only in one person's head becomes a serious liability the moment that person is out sick during a cutover window.
Skills
Strong command of at least one major cloud platform is non-negotiable, alongside real experience with migration tooling, networking fundamentals, and scripting for automation.
- Cloud platform administration (AWS, Azure, or GCP)
- Migration tooling for large-scale infrastructure moves
- Networking, including VPC design and DNS cutover planning
- Scripting for automation, typically Python or Bash
Nice to Have
Experience with infrastructure-as-code tools such as Terraform, container orchestration through Kubernetes, and some background in cost optimization work will all set a candidate apart. None of these are dealbreakers on their own, but a candidate who can talk through a real cost-reduction project during a cloud migration will stand out from one who can only describe the migration itself.
Multi-cloud migration experience, meaning a move between two different providers rather than just scaling up within one, is also useful, though it's rare enough that the hiring team doesn't expect most applicants to have it. If a candidate has it, mention it early in the interview rather than saving it for the end.
Compensation and Benefits
The role pays 228,000 rupees monthly, and the wider package builds on that base figure. Employees are covered under the company's health insurance plan, accrue paid time off throughout the year, and become eligible for bonuses tied to how their projects land, not just a flat annual number. Because the position is on-site in Gachibowli, there's also a subsidized on-site cafeteria and support for the daily commute, which matters given how much Hyderabad traffic can eat into a workday if you're driving yourself in from further out.
The performance bonus structure is tied to migration milestones as much as general performance reviews, so someone who leads a project through a clean cutover typically sees that reflected directly rather than waiting for an annual cycle to catch up with what they delivered.
Life in Gachibowli
Gachibowli has become one of Hyderabad's busier tech corridors, and this office sits close enough to the main IT hub that many engineers have moved between companies within a few kilometers over the years. Naukri Mitra sees steady interest in cloud migration engineer jobs in Gachibowli, Hyderabad, and this particular listing draws a fair number of applicants specifically because the pay sits well above the median for similar cloud migration engineer jobs in Hyderabad right now. The commute support genuinely helps here, since the area's traffic can turn a fifteen-kilometer drive into an hour without much warning. Several larger tech campuses nearby run similar shift patterns, which means the roads around Gachibowli get predictably heavy at the same two windows every day, and planning around that becomes second nature after the first few weeks.
Team and Working Style
This is a lead role, which means part of the job is technical and part of it is making sure less senior engineers on the team aren't stuck waiting on a decision. Migrations tend to cluster: quiet weeks planning and testing, followed by an intense stretch during the actual cutover window, then another quiet stretch while the new environment stabilizes. Anyone applying should be comfortable with that rhythm rather than expecting a flat, identical week every time.
The team currently has a handful of engineers plus the DevOps function this role reports into, and much of the day-to-day coordination happens through short standups rather than long status meetings. New leads generally get paired with the outgoing project owner for one migration cycle before running one independently, so there's a built-in handover period rather than being expected to take over cold.
How to Apply
Applicants who meet the education, certification, and experience requirements above should submit their application through the process listed with this posting. Given the seniority of the role, candidates should be ready to walk through at least one past migration project in detail during the interview. We review applications as they come in, so there's no advantage to waiting. Candidates should also be prepared to discuss how they'd approach a rollback if a migration step failed midway, since that scenario comes up in most technical interviews for this role.
