Senior Elasticsearch Engineer — Taramani, Chennai (Tidel Park)
A full-time, on-site Senior Elasticsearch Engineer position is open in Taramani, Chennai, Tamil Nadu 600113, based at Tidel Park, paying ₹1,23,500 a month. The team runs a search and logging platform built around the Elastic stack, and this role owns keeping it fast and reliable as data volume keeps climbing. Several internal teams depend directly on this platform for both customer-facing search and internal observability, so changes here tend to have a wider blast radius than most backend work.
Responsibilities
- Writing and maintaining application code that interacts with the Elastic stack, from ingestion pipelines to the query layer applications rely on.
- Collaborating with cross-functional teams on new features, translating product requirements into indexing strategies and query designs that actually perform at scale.
- Fixing bugs identified during testing, including the trickier ones that only surface once real production data volume hits a query.
Five years of experience in this space usually means you've already been burned by a poorly designed mapping that had to be reindexed under pressure, or a query that worked fine in staging and fell over the moment it hit production traffic. This role expects that kind of scar tissue. Whoever takes it will be the person other engineers come to when a search feature returns results that are technically correct but somehow feel wrong to users, since diagnosing relevance issues takes a different kind of intuition than fixing a straightforward bug.
Education and experience
A bachelor's degree is the baseline qualification, generally in computer science or information technology, along with genuine hands-on project experience rather than purely academic exposure to the stack. We expect 60 months of relevant experience, ideally with a meaningful chunk of that time spent specifically on Elasticsearch rather than search work in general. Candidates from a broader backend background who developed deep Elasticsearch expertise along the way are absolutely in scope, provided that expertise is demonstrable rather than incidental.
Skills required
- Elasticsearch. Deep working knowledge of indexing strategy, sharding, and cluster management under real load, not just writing queries against a small local instance.
- Logstash. Building and maintaining ingestion pipelines that handle malformed or unexpected data gracefully rather than silently dropping it.
- Kibana. Comfortable building dashboards that stakeholders can actually read, and troubleshooting through Kibana when something in the pipeline looks off.
- Query optimization. Reading a slow query's profile output and knowing whether the fix is in the mapping, the query structure, or the cluster's resource allocation.
Beyond the four core skills, exposure to the broader Elastic ecosystem such as Beats or Fleet, experience running Elasticsearch on Kubernetes, and any background with vector search or semantic search features will strengthen an application. None of these are required, though semantic search experience has become more relevant as more teams layer it on top of traditional keyword search. Familiarity with cross-cluster replication is another plus, since disaster recovery planning for the platform is an ongoing conversation the team is still working through.
Compensation and benefits
Along with the ₹1,23,500 monthly salary, the role includes:
- Health insurance covering the employee and dependents.
- Paid time off following the standard company calendar.
- A performance-linked bonus tied to platform reliability and delivery milestones agreed each cycle.
- On-site cafeteria facilities and cab or commute support, both standard for employers based out of Tidel Park.
Team and working style
The platform team is six engineers, with two focused specifically on the Elastic stack and the rest split across the broader logging and observability pipeline. You'd report to the platform engineering lead and work closely with application teams whenever a new feature needs search or logging support. Naukri Mitra carries this listing alongside a wider set of Chennai-based backend and infrastructure roles, and Taramani's concentration of IT parks has made it one of the city's more active hubs for specialized engineering roles like this one.
Cluster upgrades and version migrations happen a couple of times a year and tend to be the most demanding stretch of work on the calendar, since they require careful planning to avoid downtime on a system multiple teams depend on. Outside of those windows, the pace is steadier and leaves real room for deeper optimization work that often gets deprioritized during normal sprints. You have reasonable autonomy to propose and drive those improvements rather than waiting for them to be assigned.
How to apply
Send a resume along with details of the scale you've worked at, index sizes, cluster node counts, query volume, whatever paints an accurate picture. The interview process runs three stages: a technical screening on Elasticsearch fundamentals, a hands-on exercise involving a real-world query optimization problem, and a final conversation with the platform engineering lead. The full process typically takes about two to three weeks, with all interviews conducted on-site at Tidel Park. Bringing a specific example of a performance problem you diagnosed and fixed tends to make the technical conversation far more productive than a general walkthrough of your resume.
