A team based in Mahindra World City, Jaipur, is hiring a Lead Elasticsearch Engineer for a full-time, on-site role. Pay runs up to 148,000 INR per month, and the position sits at the senior end of the software development track.
Required background
The role calls for a bachelor's degree. Most candidates come from computer science or IT backgrounds, though the degree title matters far less than real project experience, which the team wants nine years of. Coursework alone won't satisfy that requirement. Strong command of the languages, tools, and frameworks this job actually touches on matters as much as the degree itself, and for a lead position, that command needs to extend to explaining technical trade-offs to people who weren't in the room when a decision was made.
Core skills for this role:
- Elasticsearch, including cluster design, indexing strategy, and shard management
- Logstash, for building and maintaining data ingestion pipelines
- Kibana, for dashboards and search-driven visualizations
- Query optimization, since a slow query at scale becomes everyone's problem fast
A candidate who's also worked with the wider Elastic ecosystem will have an easier time here. Experience with Beats agents for lightweight log shipping is useful, as is familiarity with a managed offering like Elastic Cloud or AWS OpenSearch Service, since a fair amount of lead-level work involves deciding when self-hosting still makes sense and when it doesn't. Comfort scripting in Python for pipeline automation helps too, and any exposure to security layers like index-level access controls rounds things out nicely, though none of this replaces the four core skills above.
What the work looks like
Most of the job is building software components that other teams and, eventually, end users depend on, which in this case usually means search and logging infrastructure that has to hold up under real traffic. That work happens alongside product managers who shape requirements and QA engineers who try to break things before customers do. Code review is a constant, not a formality, and a lead is expected to catch the subtle mistakes junior engineers might miss, the kind that only show up once a cluster is under load. When a search index starts returning stale results at nine on a Tuesday morning and support tickets start piling up, tracing that back to a misconfigured refresh interval or a bad mapping change becomes the immediate priority.
- Design and build the software components that power search and log analytics infrastructure
- Work closely with product and QA throughout each release
- Review code from the team to keep quality high before anything ships
- Diagnose and fix production issues flagged by users
None of this is unusual for a senior engineering role. What's specific to this one is the sheer volume of data Elasticsearch clusters tend to accumulate, and how quickly a small misconfiguration compounds once you're indexing millions of documents a day.
Where it's based
Mahindra World City has become a fairly established hub for IT and manufacturing companies on the outskirts of Jaipur, and the office is on-site, so there's no remote-work option available for this listing. Naukri Mitra carries a handful of similar Elasticsearch roles across Jaipur, and this one is priced toward the top of that range given the nine years of experience it expects. Anyone weighing a move should factor in commute time from central Jaipur, since Mahindra World City sits a fair distance outside the city core.
Benefits
- Health insurance
- Paid time off
- Performance-linked bonuses
- Relocation assistance for candidates moving to Jaipur
- Accommodation support during the transition
These are fairly standard for a lead-level, on-site software role in this part of the country, and the relocation piece, in particular, matters given how many candidates for a role this senior are likely to be coming from outside Rajasthan entirely.
Applying
A resume should lead with specific Elasticsearch work, not just "worked with ELK stack" as a bullet point buried among other tools. Cluster sizing decisions, indexing strategies that held up under real load, or a query optimization problem actually solved will carry more weight than a general systems background. Interviews for this role tend to include a technical deep dive into cluster architecture, so it's worth having a concrete project ready to walk through in detail.
