Our engineering team at Rushikonda IT SEZ in Visakhapatnam is looking for a Senior RabbitMQ Engineer. This is a full-time, on-site position paying ₹122,000 a month, focused on the messaging infrastructure that connects several of our backend services together. The role reports to the platform engineering group, and the work spans both new feature builds and the ongoing upkeep of systems already running in production.
Responsibilities
- Design and maintain RabbitMQ exchange, queue, and binding configurations that fit how our services actually communicate, not a generic default setup
- Implement new messaging features as project requirements evolve, whether that's a new event type flowing between services or a change in how retries get handled after a downstream failure
- Debug and resolve issues when messages get lost, duplicated, or delayed, which usually means digging into consumer acknowledgment logic or broker configuration rather than the message content itself
- Monitor broker performance and queue depth, stepping in before a backlog turns into a service-wide slowdown
- Document configuration decisions and failure patterns so the next engineer troubleshooting a similar issue isn't starting from zero
- Participate in code reviews for anything touching the messaging layer, since a subtle mistake there tends to surface downstream rather than at the point it was introduced
Clustering and failover setup come up periodically too, particularly when we're scaling a service that depends on message delivery staying reliable even if a node goes down mid-transaction. Getting that right usually means deliberately testing failure scenarios ahead of time rather than discovering gaps during an actual outage.
What we're looking for
A bachelor's degree is required for this role. Most senior engineers on our team studied something computing-related, but what actually matters more at this stage is a track record of shipping and maintaining production systems, not the specific degree title on a transcript. We'll ask about the systems you've owned, not the coursework you completed years ago.
Six years of hands-on engineering experience is the requirement here, with a meaningful chunk of that spent working on distributed or messaging-based systems specifically. Someone at this level has typically already dealt with a production incident tied to message ordering or duplicate processing, and knows the difference between a fix that patches the symptom and one that actually addresses the root cause. That distinction shows up clearly in how someone describes a past incident during an interview, whether they focus on the immediate workaround or explain what changed structurally afterward.
Skills
RabbitMQ expertise is the core requirement, along with a solid understanding of messaging protocols more broadly and real experience working within distributed systems. Someone who's only worked with a single message queue implementation, without understanding the underlying protocol concepts, usually struggles the moment something behaves outside the documented happy path. RabbitMQ has a fair number of configuration options that interact in non-obvious ways, so knowing the theory behind the protocol often matters as much as familiarity with the tool's admin console.
Working knowledge of AMQP specifics is a genuine plus given how directly it relates to RabbitMQ's internals. Experience with Kafka is also welcome, since a few of our services use it alongside RabbitMQ for different purposes, and comfort with containerized deployments through Docker or Kubernetes would help too. On the language side, strong ability in at least one of Java, Python, or Go, whichever you've used to build producers and consumers, matters more than familiarity with any single framework. If you've written retry logic or dead-letter handling by hand at some point, that experience translates directly into this role.
The team
This role sits within a backend group that Naukri Mitra has recently listed several senior openings for, and the messaging layer touches nearly every service the company runs. That reach cuts both ways. A well-designed queue setup goes unnoticed because things just work, while a misconfigured one can cause outages that ripple across teams that have nothing directly to do with messaging. New engineers usually spend their first few weeks tracing existing message flows before making changes, which is often a faster way to build real confidence in the system than reading documentation alone. That ramp-up period also gives someone a chance to spot which parts of the current setup have accumulated small inconsistencies over time, the kind that only become obvious once you've actually traced a message from producer to consumer.
Compensation and benefits
Beyond the base salary, this role includes:
- Health insurance
- Paid time off
- Performance-linked bonuses
- Relocation assistance for candidates moving to Visakhapatnam
- Accommodation support during the transition period
For a senior on-site role like this, the relocation support is meant to cover an actual move rather than a symbolic gesture, and the accommodation piece extends far enough to give someone real time to find permanent housing. Bonuses here are tied to specific delivery milestones agreed on with your manager at the start of each cycle, rather than a single company-wide figure applied evenly across the team.
Location and pay
The position is based on-site at Rushikonda IT SEZ in Visakhapatnam, without a remote or hybrid arrangement. For experienced professionals specifically evaluating RabbitMQ engineer jobs in Visakhapatnam, this one sits well within the upper range for the local market. Rushikonda has grown into a fairly established IT hub over the past several years, with a reasonable concentration of tech employers nearby. The area is also close enough to the coast that the commute, for anyone not relocating directly into the SEZ, tends to be fairly pleasant compared to the more congested parts of the city.
Applying
Submit your application along with details of a past project where messaging reliability was a genuine concern, not just a component you configured once and left alone. The interview process includes a technical round focused on distributed systems and messaging patterns, followed by a discussion of a specific incident you've handled and how you implemented the resolution. We can generally move through both rounds within two to three weeks, so it shouldn't drag on indefinitely on your end either.
