Senior Cloud Migration Engineer – Ahmedabad (Thaltej, SG Highway)
Thaltej, off SG Highway in Ahmedabad, has a full-time, on-site opening for a Senior Cloud Migration Engineer, paying up to ₹1,75,500 a month. The role centers on moving workloads onto cloud infrastructure and making sure they actually run well once they get there, not just technically completing the move. Cloud migration engineer jobs in Ahmedabad at this compensation level typically carry real ownership over how a migration gets planned and executed, and this one's no exception.
What's expected to get considered
This one asks for a bachelor's degree at minimum, and beyond that, a recognized cloud certification, whether AWS, Azure, or GCP, is part of the standard bar for this seat. The certification isn't a box-checking formality here; migration work touches enough platform-specific detail that certified knowledge often shows up directly in how fast someone can diagnose an issue during a cutover. A candidate without the certification but with a strong track record of completed migrations can still be competitive, though they should expect the interview to probe platform specifics more closely to compensate.
Eight years of hands-on experience is required. Candidates should have spent a meaningful share of that time on cloud infrastructure work specifically, containerization and automated deployment pipelines included, rather than general systems administration with occasional cloud exposure. What matters most in screening isn't total years, but how much of that time was spent moving workloads rather than maintaining ones already in the cloud.
What the work involves
- Plan and execute migrations of existing workloads onto cloud infrastructure, coordinating with application teams on timing and dependencies
- Automate infrastructure provisioning for migrated environments so they don't end up hand-configured and undocumented after the fact
- Troubleshoot issues that surface across development and production during and after a migration, since problems don't always show up on day one
The timing of a migration matters as much as the technical execution. A database migration scheduled during a client's peak sales period, even if technically flawless, causes real damage if it wasn't coordinated with the business side beforehand. Part of the job is knowing when a technically ready migration still needs to wait, and being willing to say so even when a project timeline is already under pressure.
Core skills
- Deep familiarity with at least one major cloud platform, with working knowledge of others valued
- Migration tools specific to moving workloads between on-premises and cloud environments, or between cloud providers
- Networking fundamentals, since migrations frequently expose gaps in how systems were originally networked together
- Scripting ability for automating repetitive migration and validation tasks
These skills come together most visibly during a cutover weekend. Validating that a migrated database actually holds the same data as the source, checking network routes still resolve correctly, and scripting a rollback plan in case something goes wrong all happen within the same tight window.
Good to have
Experience with a specific migration tool like AWS Application Migration Service or Azure Migrate speeds up onboarding considerably, since the general concepts transfer but tool-specific quirks take real time to learn otherwise. Some background in cost optimization is useful too, given how often a migration project also becomes an opportunity to right-size infrastructure that was over-provisioned for years. Neither is required, but both tend to shorten the time before someone contributes at full capacity.
Compensation and benefits
Cloud migration engineer salary in Ahmedabad for this senior role tops out at ₹1,75,500 monthly. The position includes health insurance and paid time off, with performance-linked bonuses tied to migration outcomes and post-launch system stability. Given the on-site setup, employees also get access to the on-site cafeteria and cab or commute support around Thaltej. For anyone commuting from other parts of Ahmedabad, that support can make a real difference, given how much traffic builds up along SG Highway during the workweek.
Working near SG Highway
Thaltej has grown into a genuinely active stretch for IT companies along SG Highway, and this employer's cloud and infrastructure team operates from an office in that corridor. Naukri Mitra has recently carried several Cloud & DevOps postings from this same area, and the day-to-day setup tends to be consistent across them: standard business hours, an established infrastructure team rather than a brand-new function still finding its footing, and close coordination with client-facing project managers on migration timelines.
Cloud migration engineer jobs for experienced professionals in Ahmedabad at this level typically come with responsibility for the technical side of client relationships during a project, not just internal infrastructure work, and this seat follows that pattern. That means presenting migration plans and risk assessments directly to client stakeholders, in plain enough language that a non-technical decision-maker can weigh the tradeoffs.
Who tends to succeed here?
Engineers who've run a full migration project from planning through post-launch stabilization, not just the technical cutover itself, tend to bring the right instincts to this role. It also suits someone who's comfortable pushing back on unrealistic migration timelines when the technical risk doesn't support them, since that pushback often has to happen with a client directly, not just internally. Candidates who prefer narrowly scoped technical work without client-facing responsibility may find the coordination side of this role heavier than expected. There's genuine responsibility that comes with the seat, and someone who wants that authority will likely find it more rewarding than someone who'd rather stay purely behind the scenes.
Applying
Send a resume that names specific migration projects you've led, the platforms involved, and roughly the size of the migrated environment. Interviews for this seat typically include a walkthrough of a real migration you managed, with particular attention to how you handled something that didn't go according to plan. Candidates who can describe a migration that hit a real snag, and how they worked through it under time pressure, tend to leave a stronger impression than those who only have clean, uneventful projects to point to. Decisions on this kind of senior seat usually take a couple of weeks after the final round.
