Technical screening questions
Ask for one example per question and listen for specifics.
- How many shards should an index have? A good answer: Data size, node count and growth.
- How do you handle index lifecycle? A good answer: ILM with hot, warm and delete phases.
- What makes a query slow? A good answer: Wildcards, large aggregations and mapping issues.
- How do you scale writes? A good answer: Bulk indexing, shards and refresh settings.
- How do you upgrade a cluster? A good answer: Rolling upgrades and compatibility checks.
Quick screening questions
Use these when you have only a few minutes.
- How do you design an index for a high-volume log workload?
- How do you tune slow queries?
- How do you scale and upgrade a cluster safely?
What separates the levels
Match the level to the requirement before you submit.
- Junior: builds dashboards.
- Mid: operates clusters.
- Senior: designs the search platform.
Red flags
Any of these is a reason to probe further.
- Only used Kibana.
- Cannot explain shards.
- No cluster operations.
Tools you should hear mentioned
An Elasticsearch engineer with real experience usually names several of these without prompting.
- Elasticsearch
- Kibana
- Logstash and Beats
- Query DSL
- ILM policies
- Cluster monitoring
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should an Elasticsearch engineer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.