Junior Cloud Migration Engineer, Bhubaneswar
This is a full-time, on-site opening for a Junior Cloud Migration Engineer at the Infocity office in Chandrasekharpur, Bhubaneswar. The role sits within the Cloud & DevOps team and pays up to ₹58,500 per month, with the final amount determined after the interview based on what a candidate can already do rather than what's written on the resume.
Six months of hands-on experience is expected going in. That could come from a first job, a structured internship, or serious project work completed during coursework, as long as it involved real cloud infrastructure rather than just tutorials. Among the cloud migration engineer jobs in Bhubaneswar right now, this one is aimed squarely at someone at the start of that path who's already touched containerization and deployment automation, not someone who needs those concepts explained from scratch.
What the job actually involves
Workloads here are being migrated from older on-premises setups to cloud environments, and the junior engineer directly supports most stages of that process.
- Provision and manage cloud infrastructure for applications going through migration
- Build and maintain automated deployment pipelines so releases don't depend on manual steps
- Monitor system performance and reliability once a workload is live in its new environment
- Respond to infrastructure incidents, tracing the cause and getting service restored
Some weeks lean heavily toward migration planning and scripting; others are quieter on that front and busier with keeping already-migrated systems stable. A junior engineer six months in typically isn't the first responder for a major outage, but will be pulled into diagnosing smaller incidents under supervision from day one.
A typical migration project starts with an inventory of what's running on the legacy server, followed by a plan for which pieces move first. A recent example involved a billing application that had been running on a single physical server for years; the junior engineer on that project spent most of the first two weeks documenting its dependencies before a single component was touched, because moving a database connection before its downstream service was ready would have taken the whole thing offline. That kind of sequencing work, unglamorous as it sounds, is a large part of what this job actually looks like week to week.
There's also a fair amount of coordination involved. Migrations rarely happen in isolation, so the engineer will often sync with whoever owns the application being moved, confirm maintenance windows, and ensure rollback steps are documented before any change goes live in production.
Education and background
A bachelor's degree is the baseline for this role, generally in computer science, information technology, or a closely related discipline. What matters more in practice is whether that degree was paired with actual exposure to cloud platforms and automated pipelines, since the qualification on its own won't carry someone through the technical rounds.
Interviewers here tend to spend more time on a candidate's final-year project or internship work than on transcripts. Someone who set up a small CI/CD pipeline for a college project, or who spent an internship shadowing a cloud team even in a limited capacity, is usually in a stronger position than someone with a higher grade point average and no applied work to point to.
Skills the team is hiring for
- Working knowledge of at least one major cloud platform (AWS, Azure, or Google Cloud)
- Familiarity with migration tools used to move workloads and data between environments
- Solid networking fundamentals, including VPCs, subnets, and basic firewall configuration
- Scripting ability in Python or Bash for automating repetitive infrastructure tasks
None of these need to be at an expert level for a junior opening, but a candidate should be able to speak concretely about a project where they used them, not just list them on a resume.
A few things aren't required but will help an application stand out: exposure to infrastructure-as-code tools like Terraform, any hands-on time with Kubernetes or Docker beyond a course exercise, and progress toward an associate-level cloud certification from AWS or Microsoft. None of these are dealbreakers if missing, and Naukri Mitra has placed candidates in similar roles without them, but they do shorten the ramp-up time considerably.
Pay and benefits
The role pays up to ₹58,500 per month, which puts this cloud migration engineer salary in Bhubaneswar toward the upper end for a junior-level DevOps position in the city. Beyond the paycheck, the benefits attached to this opening include:
- Health insurance coverage
- Paid time off
- Provident fund contributions
- Relocation assistance for candidates moving to Bhubaneswar for the role
- Accommodation support during the initial settling-in period
The relocation and accommodation pieces matter here because this is strictly an on-site position in Infocity, Chandrasekharpur, so anyone applying from outside the city should factor that move into their planning early rather than after an offer lands.
Team and location
Bhubaneswar's Infocity area has grown into one of the more active tech corridors in Odisha, and several companies hiring cloud migration engineers in the city are based within a short distance of each other in the same district. Working on-site here means daily access to the rest of the Cloud & DevOps team, rather than relying on remote handoffs, which, for a junior engineer, usually translates into faster feedback when something in a migration doesn't go as planned.
This is also, realistically, a good entry point among cloud migration engineer jobs for freshers in Bhubaneswar who already have some practical grounding but haven't had the chance to work at production scale. Mistakes during a live migration have real consequences, and the team expects a junior engineer to understand that, ask questions before making risky changes, and escalate rather than guess when something looks off.
Where this role can lead
Junior engineers who stay in this team for a year or two generally move toward an Associate-level Cloud or DevOps title, taking on larger migration projects with less oversight along the way. The path isn't automatic and depends on how quickly someone builds independent judgment around production changes, but it's a well-worn one within this Cloud & DevOps group specifically, and a couple of engineers currently in senior roles started in this exact position a few years back.
How to apply
Candidates should be prepared to walk through at least one past project involving cloud infrastructure or deployment automation in detail during the interview, including what went wrong and how it got fixed. Applications are reviewed on a rolling basis, and shortlisted candidates will typically hear back within a couple of weeks of applying.
