Microservices Developer, Kochi
Infopark, Kakkanad, in Kochi is where this Microservices Developer role is based, full-time and on-site, with pay going up to ₹71,500 a month depending on what a candidate brings to the table technically. The team builds and maintains a set of interconnected services rather than one large application, and this hire will own pieces of that system directly rather than shadowing someone else's work.
What you'll need to bring
- Practical experience with microservices architecture, not just familiarity with the concept
- Docker for building and running containerized services
- Comfort designing and consuming REST APIs
- Strong programming ability in Java or Python
It helps considerably if a candidate has also worked with Kubernetes for orchestration, has touched a message queue system like Kafka or RabbitMQ, or has set up a CI/CD pipeline from scratch rather than just using one someone else built. None of that is required to apply, but candidates with that background tend to move faster once they're on the team.
Testing experience matters more here than at many shops, mostly because a bug in one service can quietly break something in another before anyone notices. Familiarity with a testing framework in whichever language a candidate codes in, whether that's JUnit for Java or pytest for Python, is treated as close to essential even though it isn't listed as a hard requirement. Some exposure to API gateways or service mesh tools like Istio is a plus, though it's rare to find candidates at this experience level who've worked with them directly.
Experience and education
The role calls for 42 months of relevant experience, and a bachelor's degree in computer science, information technology, or a comparable field is the standard requirement here. Beyond the degree itself, interviewers actually probe for depth in the specific languages, tools, and frameworks a candidate claims to know, since a resume listing five frameworks means little without follow-up questions to back it up.
Candidates coming from a monolithic background aren't automatically ruled out, but they should expect questions about how they'd approach breaking a large application into smaller services, since that kind of architectural thinking is part of the actual job rather than a nice theoretical exercise. Someone who spent three and a half years maintaining a single large codebase without ever touching service boundaries will need to speak to how they'd adapt, not just to what they've already done.
Day-to-day
- Write and maintain application code across the services this team owns
- Collaborate with cross-functional teams when building new features
- Fix bugs surfaced during testing before they reach production
A microservices setup means bugs don't always stay contained to one place. A recent example: a change to how one internal service handled retry timeouts ended up slowing down three unrelated services downstream, and it took a developer most of a day tracing the chain before the actual fix, a two-line change, went in. That kind of debugging, where the symptom and the cause live in completely different parts of the system, comes up often enough that it's worth mentioning upfront rather than discovering it later.
Feature work tends to move in short cycles, usually with a product owner or another engineering team involved in shaping requirements before code gets written. Naukri Mitra has seen this pattern across most on-site development roles in Kochi's Infopark corridor, where teams stay small, and communication happens face-to-face rather than through long written specs.
Code review is treated as a normal part of shipping, not an afterthought squeezed in before a deadline. Pull requests here typically get feedback within a day, and developers are expected to respond to review comments the same way, rather than letting a change sit for a week. This matters more in a microservices setup than it might elsewhere, since a service that gets deployed independently can affect other teams' work almost immediately if something slips through unreviewed.
Compensation and benefits
Pay for this microservices developer role in Kochi tops out at ₹71,500 per month. Alongside that:
- Health insurance coverage
- Paid time off
- Provident fund contributions
- Relocation assistance for candidates moving to Kochi
- Accommodation support while settling in
Because this is an on-site role in Infopark, Kakkanad specifically, candidates from outside Kerala should plan for that relocation rather than treat it as an afterthought once an offer is made.
The wider context
Kochi has developed a genuine cluster of software companies within Infopark over the last decade, and microservices developer job openings in Kochi have become fairly common as more teams move away from monolithic codebases toward smaller, independently deployable services. That shift is part of why this role exists in the first place. Someone joining now won't be maintaining legacy architecture so much as extending a system that was already built with this pattern in mind.
Team size here stays deliberately small, which means individual contributions are visible quickly, for better and for worse. A poorly tested change gets noticed fast, but so does a well-built feature that actually solves the problem it was meant to solve.
Kerala's IT hiring has picked up noticeably in Kochi over the past few years, with Infopark now housing dozens of companies developing backend systems similar to this one. For a developer with a few years of experience already under their belt, moving between companies in the same corridor is common enough that many hiring managers here have worked alongside candidates before, even informally. It's a smaller world than the job title might suggest.
Applying
Expect at least one technical round focused on system design at the microservices level, plus a coding round covering Java or Python fundamentals. Bring a specific example of a service you've built or maintained, since interviewers here would rather talk through a real project than run through a checklist of buzzwords. There's usually a brief discussion round after the technical stages, too, mostly to confirm expectations around how the on-site schedule and relocation timeline align on both sides. Shortlisted candidates are usually contacted within ten working days of applying.
