Salt Lake Sector V in Kolkata has a Senior Microservices Developer opening, full time, on site, with a software team that's spent the last two years migrating a monolith into independently deployable services. Six years of hands-on experience is the expectation, and the team is specifically interested in people who've lived through a migration like this before, not just built greenfield microservices from day one with no legacy baggage to work around.
The work covers designing and building software components as services, working closely with product and QA teams on each release, reviewing code from other developers to keep architectural consistency across a growing number of services, and troubleshooting production issues that, in a distributed system, are rarely as simple as they first appear. A bug that looks like it lives in one service often turns out to be a timing issue between two services that only shows up under real production load.
Required skills are microservices architecture, Docker for containerization, REST API design, and strong proficiency in either Java or Python. A developer who's only worked within a monolith, even a well-structured one, will find the operational mindset shift here real: service boundaries, contract versioning, and failure isolation all matter in ways they simply don't inside a single deployable application.
A bachelor's degree in computer science, information technology, or a related field is expected, along with practical, hands-on project experience and proven proficiency in the languages and frameworks this role actually uses. The team has said clearly that a candidate with three years of real microservices experience is preferred over one with six years that's entirely monolith-based.
Salt Lake Sector V is one of Kolkata's most established tech corridors, and the office here supports a product used by a genuinely large user base, which means performance and reliability concerns aren't theoretical; a slow service during peak hours shows up in support tickets within minutes. That immediacy shapes a lot of the engineering culture, favoring monitoring and observability work that some developers coming from smaller-scale projects initially underestimate.
Naukri Mitra has carried software development roles from this employer before, and past hires describe the migration project itself as still ongoing, with roughly a third of the original monolith left to break apart. That means a senior developer joining now gets to shape real architectural decisions rather than just maintaining a system someone else already fully designed.
Interviews include a system design round focused specifically on service boundaries and failure handling, plus a coding round in your stronger language of the two. Candidates who can talk through how they'd handle a partial failure across services, not just the happy path, tend to stand out in that system design conversation.
Onboarding for this role runs roughly two to three weeks, split between shadowing a current team member and working through a small, low-risk real task under review before moving to independent ownership. The team has found that a slower, more deliberate ramp-up produces fewer costly mistakes down the line than throwing someone straight into full ownership from day one.
The engineering team holds a biweekly architecture review specifically for changes touching service boundaries, since a boundary drawn in the wrong place tends to cause cascading coupling problems that are expensive to unwind later, far more expensive than the extra review time costs upfront.
This role is based at Salt Lake Sector V, Kolkata, pin code 700091, five days a week on site. Pay runs up to ₹1,21,000 a month. The team hopes to fill this seat within five to six weeks.