Elastic's Software Engineer interviews typically open with a recruiter screen, move into a practical coding round or take-home (JavaScript, Java, or a live PR review), and may add a technical discussion and behavioral round before a hiring-manager wrap-up.
$148K
Avg. Base Comp
$225K
Avg. Total Comp
4 rounds
Typical Rounds
3-4 weeks
Process Length
If you're prepping for a Software Engineer role at Elastic, expect the loop to start with a recruiter or HR screen that covers your background, the technologies you've used, and why you want to work at Elastic. From there, the coding round tends to test a specific, practical pattern rather than a broad algorithm bank. One candidate hit a JavaScript recursion problem to flatten a nested object even though the screen was billed as a TypeScript assessment. Another completed a Java take-home with three coding challenges graded partly on data-structure choices. A Platform Software Engineer I candidate described a domain-specific live coding round followed by a live pull-request review, where the task was to spot functional issues in a small codebase. Solving the problem is not always enough, so be ready to explain why you chose a given structure or approach.
Later stages can include a technical discussion with no coding. One candidate was asked about the semantics of volatile in Java, the concurrency tools the Java SDK offers, and how to describe a distributed system and its advantages. Behavioral rounds are taken seriously, particularly on remote-first teams. Expect STAR-style questions about workplace experience and long-term projects, what kinds of colleagues you want to work with or avoid, and how you operate across teams in a matrix organization. The process typically wraps with a hiring-manager conversation that is largely a chance to ask your own questions. Communication quality varies: some candidates praised organized coordinators and a scheduled feedback session, while others dealt with rescheduling and slow feedback, so build in some patience for the back half of the process.
Synthesized from 16 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Elastic process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Elastic
Given a json string with nested objects, write a function that flattens all the objects to a single key-value dictionary.
| Question | |
|---|---|
| DDoS Attack Response | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Random SQL Sample | |
| String Shift | |
| Comments Histogram | |
| Raining in Seattle | |
| Rolling Bank Transactions | |
| Prime to N | |
| Minimum Change | |
| Customer Orders | |
| Upsell Transactions | |
| Top 3 Users | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Find the First Non-Repeating Character in a String | |
| Rectangle Overlap | |
| Largest Salary by Department | |
| Bagging vs Boosting | |
| Flight Records | |
| The Brackets Problem | |
| Project Pairs | |
| Level Of Rain Water In 2D Terrain | |
| Download Facts |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter or HR conversation covering technical background, tools used, and motivation for joining Elastic. One candidate described the recruiter as thorough but conversational and clear about what to expect next, though others found later-stage communication less consistent than this first call.
Technical rounds vary by team and tend to be practical rather than generic. Candidates report: - A JavaScript recursion problem to flatten a nested object, on a screen billed as a TypeScript assessment. - A Java take-home with three coding challenges, evaluated partly on data-structure choices. - Easy LeetCode-style live coding with two team members. - A domain-specific live coding round followed by a live pull-request review.
One candidate described a technical discussion with two interviewers and no coding. It covered the semantics of volatile in Java, what the Java SDK offers for concurrency (with deeper follow-ups), and describing a distributed system and its advantages. This stage explores reasoning and trade-offs, and it may not appear in every loop.
Behavioral questions show up in several reports. Examples include STAR-style questions about workplace experience and long-term projects, what kinds of colleagues you would want to work with or avoid, and how you function in a matrix organization. One candidate on a remote-first team found this round weighted more heavily than expected.
Where candidates reached it, the loop closed with a hiring manager conversation that one candidate described as mostly a chance to ask questions. Follow-up after this stage was inconsistent in some reports, so ask about feedback timing directly.
