← Back to Directory

Elastic

Large Enterprises

Screna has 4 Elastic interview write-ups. The most reported round is the technical phone screen (4).

4 interview notes · updated Jul 2026

Elastic·Software Engineer·Technical Phone Screen

Jul 2026
Elastic coding round for a software engineer role, one question the whole time: build a live log aggregation view in React. More involved than it sounds once you get into the timestamp handling and state update edge cases.
  • Build a React component that consumes a stream of log events one at a time, aggregates them by category in memory, and renders a live-updating table showing each category's event count and most recent timestamp.

“The core part wasn't hard to sketch out but I kept second-guessing the state structure.”

View Post

Elastic·Software Engineer·Technical Phone Screen

Jun 2026
Elastic technical screen for a software engineer role, basically a live PR review on a recursive flatten utility. The whole thing was more nuanced than I expected, less about writing code and more about finding cracks in someone else's.
  • Given a pull request implementing a recursive array flatten function, what correctness bugs and edge cases does the implementation fail to handle?
  • What API and contract questions would you raise before approving this PR, for example around how non-array objects, null values, strings, and sparse arrays should be handled?
  • How would you improve this implementation for readability, performance, and safety, including the risk of a stack overflow on deeply nested input?
  • Propose a revised implementation approach and describe the minimal set of tests you would require before approving this PR.

“The `for...in` loop was the first thing I flagged because it iterates over enumerable properties, not just numeric indices, so anything added to Array.prototype would silently get included.”

View Post

Elastic·Software Engineer·Technical Phone Screen

Jun 2026
Elastic N.V. full-stack round focused on a buggy JavaScript flatten implementation. You had to read broken code, find the issues, and fix them live while talking through edge cases. Pretty dense for a single session.
  • You're given a JavaScript flatten(arr) function that recursively flattens nested arrays. Find and fix all the bugs in it.
  • Walk through test cases for the fixed flatten function: empty arrays, deeply nested input, and mixed types.

“The bugs they were fishing for: not recursing into non-array elements, misusing concat so it mutates or doesn't spread correctly, and circular reference handling causing infinite recursion.”

View Post

Elastic·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a full-stack role at Elastic and got a fairly focused coding problem around log stream processing. Not a brutal round but it had enough nuance to trip you up if you weren't thinking carefully about edge cases.
  • Given a stream of log entries, design a solution that tracks the frequency count per category and the timestamp of the most recent update for each category. How would you handle out-of-order timestamps efficiently?

“I went straight for a hash map keyed by category, which felt obvious.”

View Post