Sector 62 in Noida has a full-time, on-site Lead RabbitMQ Engineer opening paying up to ₹1,47,000 per month. This one's built for someone who can own the messaging layer across a distributed system, not just configure a queue and move on.
What gets asked for on the background side
A bachelor's degree is required, generally in computer science or a comparable technical field, which is the norm for engineering roles at this level. 120 months of hands-on experience is what the role is looking for, and that length of time usually means having already debugged a queue backup at 3 a.m. more than once. That kind of history matters more here than any specific certification would.
The work itself
- Implementing new messaging features and integrations as different services need to talk to each other
- Debugging and resolving issues when messages get delayed, dropped, or duplicated across the system
- Documenting configuration decisions and known failure patterns so the next person troubleshooting doesn't start from scratch
- Reviewing code from other engineers touching the messaging layer, catching design issues before they reach production
Say a consumer service falls behind, and messages start piling up faster than they can be processed. Figuring out whether that's a downstream bottleneck, a misconfigured prefetch setting, or something else entirely is exactly the kind of problem this role exists to solve.
Skills needed
- RabbitMQ specifically, including exchanges, bindings, and queue configuration at a production scale
- Messaging protocols more broadly, understanding how different systems handle delivery guarantees
- Distributed systems knowledge, since a messaging layer is only as reliable as the services around it
Some background in Erlang or OTP helps when a RabbitMQ issue traces down to the broker itself rather than the application layer. Exposure to Kafka or a cloud-native alternative like AWS SQS rounds out the picture for anyone who might work across multiple messaging systems here, and comfort setting up monitoring and alerting on queue depth is close to a daily necessity in this role.
The setup
This is fully on-site at Sector 62, working closely with the platform team rather than remotely. Naukri Mitra's client here runs a fairly lean infrastructure group, so a lead engineer's architectural calls carry real weight and aren't filtered through several layers of sign-off. Routine weeks involve tuning and capacity planning; the occasional rough one involves an incident that needs the messaging layer stabilized fast.
Benefits
- Health insurance
- Paid time off
- Performance-linked bonuses
- On-site cafeteria facilities and cab or commute support
Pay and location
Compensation for this role reaches ₹1,47,000 per month, based in Sector 62, Noida. Among RabbitMQ engineer salaries in Noida, that's a strong figure, in line with the depth of distributed systems experience the role requires.
How to apply
Applicants should highlight specific messaging systems they've operated at scale, along with any major incidents they've resolved involving queues, brokers, or consumer lag. Concrete examples like that carry more weight in this review than a general list of tools.
