Elastic Coding Interview Questions
25 Elastic coding interview problems with full optimal solutions — 8 easy, 12 medium, 5 hard. Every problem ships with multiple approaches (brute-force first, then the optimal), complexity tables for each, company-specific tips on what an Elastic interviewer values, and a FAQ section.
Showing 14 problems of 25
- #15mediumfrequently asked
15. 3Sum
Find all unique triplets in an array that sum to zero. Elastic uses this to assess whether candidates can combine sorting and two-pointer techniques without double-counting — the same deduplication challenge that arises when Elasticsearch merges results from replicated shards.
- #20easyfrequently asked
20. Valid Parentheses
Determine whether a string of brackets is balanced. Elastic reaches for this in phone screens because the stack-based parse pattern is directly analogous to query-string and JSON document validation that Elasticsearch performs on every indexed document.
- #21easyfrequently asked
21. Merge Two Sorted Lists
Merge two sorted linked lists into one sorted list. Elastic interviews this because it is the atomic merge step in merge sort — and merge sort is the exact mechanism Elasticsearch uses when combining sorted posting lists during multi-term query execution.
- #42hardfrequently asked
42. Trapping Rain Water
Compute how much water is trapped between elevation bars after rain. Elastic uses this problem as a hard two-pointer question that tests the ability to reason about running maximums from both directions — the same prefix/suffix scan pattern underlies Elasticsearch's range-scoring and gap-detection in time-series anomaly detection.
- #49mediumfrequently asked
49. Group Anagrams
Group a list of strings so that anagrams appear together. This is a canonical Elastic question — the sorted-string or frequency-vector canonical key pattern is exactly the normalization step Elasticsearch's token filters apply before building the inverted index.
- #53easyfrequently asked
53. Maximum Subarray
Find the contiguous subarray with the largest sum. Elastic reaches for Kadane's algorithm because it illustrates how a single-pass decision — keep accumulating or restart — is the same greedy insight driving Elasticsearch's segment-level scoring and relevance windowing.
- #56mediumfrequently asked
56. Merge Intervals
Merge all overlapping intervals into a minimal non-overlapping set. Elastic frequently asks this because merging time-range queries, log time spans, and APM trace windows are everyday operations in Elasticsearch and Kibana — getting the overlap condition exactly right under edge cases is a real engineering concern.
- #121easyfrequently asked
121. Best Time to Buy and Sell Stock
Find the maximum profit from a single buy-low-sell-high transaction. Elastic uses this pattern to test sliding-window and running-minimum thinking — the same mental model used when computing rolling aggregations over time-series log data in Elasticsearch.
- #139mediumfrequently asked
139. Word Break
Determine if a string can be segmented into words from a dictionary. Elastic interviews this because token segmentation is at the core of Elasticsearch's text analysis pipeline — understanding which substrings can be valid tokens is exactly what analyzers compute before indexing.
- #200mediumfrequently asked
200. Number of Islands
Count connected components of '1' cells in a 2D grid. Elastic reaches for this problem because BFS/DFS on a grid is a direct analogue of cluster connectivity analysis — the same reasoning applies when determining which Elasticsearch nodes belong to the same cluster partition after a network split.
- #206easyfrequently asked
206. Reverse Linked List
Reverse a singly-linked list in place. Elastic uses pointer-manipulation questions like this to verify that candidates can reason about mutable state without a garbage-collection safety net — critical intuition for writing correct segment merging and linked-structure traversal in distributed search engines.
- #207mediumfrequently asked
207. Course Schedule
Determine if you can finish all courses given prerequisite dependencies — essentially cycle detection in a directed graph. Elastic interviews this because topological ordering and DAG validation are fundamental to Elasticsearch's pipeline processor chains and ingest node dependency resolution.
- #238mediumfrequently asked
238. Product of Array Except Self
Return an array where each element is the product of all other elements, without using division. Elastic uses this to test prefix/suffix scan thinking — the same cumulative-scan pattern drives Elasticsearch's pipeline aggregations that compute running totals across document sets.
- #642hardfrequently asked
642. Design Search Autocomplete System
Design a system that returns top-3 historical search suggestions as you type. This is arguably the most Elastic-aligned hard coding question: Elasticsearch's completion suggester is a production implementation of exactly this design, combining a Trie with frequency-ranked retrieval — candidates who know both the data structure and the ranking heuristic stand out immediately.