+ Post Job +
Home Software Development

Senior Kafka Developer

📍 mohali 🏷️ Software Development 💰 ₹121,000 / month

Overview

Mohali's IT City, Sector 82 campus needs a Senior Kafka Developer to take ownership of event-streaming infrastructure for a growing software development team. The role is full-time and on-site, and it's built for someone who has already spent real years in production Kafka environments rather than someone looking to learn the basics on the job. The team supports several downstream applications that depend on data arriving in the right order, at the right time, without anyone noticing the machinery underneath.

Responsibilities

The work centers on building and maintaining the systems that move data reliably across the company's applications.
  • Build and maintain the codebase behind the platform's messaging and data pipelines
  • Work alongside teams outside engineering to shape and deliver new product features
  • Track down and resolve defects that surface during QA before they ship
Expect to spend a fair amount of time reasoning about partition strategy, consumer group behavior, and what happens when a downstream service falls behind. Kafka work rewards people who think in terms of throughput and ordering guarantees rather than just getting a message from one place to another. A topic that looks fine at ten thousand messages a day can fall over at ten million, and part of the job is anticipating that before it happens rather than firefighting it afterward.

Requirements

The minimum academic bar is a four-year degree in computer science, IT, or a comparable technical field, paired with real, verifiable time spent building distributed systems in production, at least six and a half years of it. What carries more weight in the interview than the degree itself is whether a candidate can speak concretely about the tools and frameworks this role runs on day-to-day, since that's a much better predictor of fit than credentials alone. A candidate coming from a background heavy on batch processing rather than streaming should expect some questions in the interview about how that experience transfers, since the two disciplines share some concepts but diverge quickly once ordering and replay semantics come into play.
  • Apache Kafka
  • Distributed systems design
  • Java or Scala
  • Messaging patterns
Experience with schema registries, exactly-once semantics, or running Kafka at scale in a cloud environment will set a candidate apart. None of these are hard requirements if the core fundamentals are genuinely solid, but they shorten the ramp-up period considerably for someone joining an existing streaming setup.

Compensation and Location

This position offers up to ₹1,21,000 per month and is based on-site at IT City, Sector 82, Mohali. Naukri Mitra has seen steady interest in Kafka developer jobs in Mohali over the past year, and openings at this seniority and pay level in the region often fill within the first few weeks of being posted. Because the role requires on-site presence, the company often provides relocation assistance and accommodation support to candidates joining from outside Punjab.

Benefits

  • Health insurance
  • Paid time off
  • Performance-linked bonuses
  • Relocation assistance and accommodation support for candidates relocating to Mohali

Team Structure

The Kafka platform is maintained by a small group embedded within the wider software development team rather than a separate infrastructure org, which means this developer will work directly with the engineers building the applications that consume the data rather than sitting several layers removed from them. Code review here tends to be thorough since a mistake in a shared pipeline can ripple across multiple services at once, and a senior hire is expected to catch those issues before they reach a pull request rather than after. New joiners typically pair with an existing engineer for the first few weeks on live incidents and design discussions, both to get oriented and to bring outside perspective into decisions the team has been making on its own for a while.

What the Day Looks Like

Mornings usually start with a review of overnight consumer lag and any alerts that fired while the team was offline. From there, the work splits between writing new pipeline code, reviewing pull requests from the rest of the team, and sitting in on planning sessions where a product team explains what data they need and when. Afternoons often shift toward deeper investigation work: tracing why a particular consumer group keeps rebalancing, or figuring out whether a spike in latency traces back to a noisy neighbor on the cluster or something in the application code itself. A recurring part of the job at this level is catching a bad partitioning decision before it turns into six months of technical debt, which is a quieter kind of contribution than shipping a visible feature but matters just as much over the life of the platform.

Why This Role

Kafka developer jobs for experienced professionals in Mohali aren't especially common outside a handful of larger tech campuses, which makes this a reasonable option for someone who wants senior-level responsibility without relocating to a bigger metro. The team here is still building out its streaming architecture rather than maintaining a fully mature system, so there's real room to shape decisions that will outlast any single project. Someone joining now will likely have a say in choices around schema evolution, retention policy, and cluster topology that a later hire simply won't get to make. For a developer who has spent the last several years maintaining someone else's architecture, that difference alone is worth weighing seriously.

How to Apply

Candidates who meet the requirements above should apply directly through this listing with an updated resume. Including a short note on the scale of the Kafka deployments you've worked with- message volume, cluster size, number of consumers- will give the hiring team a faster read on fit than a generic list of technologies. Interviews generally involve a technical discussion built around a real streaming design problem rather than a whiteboard algorithm exercise, so it helps to walk in having already thought through how you'd design a pipeline from scratch, including where it might break under load. Candidates relocating from outside Punjab are welcome to ask about the accommodation support during the process rather than waiting until an offer is on the table, since it's easier to plan a move once those details are settled.
Apply Now