
Two candidates describe Elastic's Cloud & Platform Engineer-style interviews: a fast, wide technical round on Kubernetes, Linux and observability, and a panel on migrating on-premises systems to the cloud. Both ended without an offer.
$134K
Avg. Base Comp
$176K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Two candidates describe Elastic interviews for cloud and platform roles. They had different experiences, so prepare for both styles instead of assuming one format.
One candidate for the Cloud & Platform Engineer role went through an HR interview, a conversation with two team managers, and a technical interview with two engineers. The technical round was time-limited and moved quickly across many topics: debugging, Kubernetes, Docker, observability, Java, sysadmin work, networking, Linux, AAD, SQL, cloud, Elastic, SSL certificates and JVM garbage collection. One concrete question asked what a Kubernetes DaemonSet is. This candidate advised talking through your real experience on each topic for as long as the interviewers let you, because the pace is so quick that a short or hesitant answer can make you look less knowledgeable than you are.
The other candidate, who interviewed for Platform Engineer II, reports video stages: a 30-minute recruiter screen, an hour with the hiring manager, and a 60-minute technical deep dive on how Elastic fits into cloud architectures. The final panel ran about 90 minutes and combined a presentation with a solutions walkthrough on migrating an on-premises architecture to the cloud. That candidate felt the technical bar was high and wished they had prepared a coherent end-to-end migration story rather than a list of cloud services.
Both candidates described friendly recruiters, and both were rejected after the technical stages. A practical plan is to rehearse grounded explanations of core platform topics that draw on your own experience. Also build one full migration presentation with tradeoffs and justifications that you can deliver in about an hour, Q&A included.
Synthesized from 2 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.
What stood out to me most was how fast the technical round moved. The process was pretty straightforward overall: first an HR interview, then a conversation with two team managers, and finally a technical interview with two engineers. The atmosphere was genuinely friendly throughout, and the HR contact kept me updated at every step, which I appreciated a lot because the feedback came back quickly and there wasn’t much guessing about where I stood.
The technical interview was the part that felt the most compressed. It was limited by time, so they covered a lot of ground in a rush: debugging, Kubernetes, Docker, observability, Java, sysadmin topics, networking, Linux, AAD, SQL, cloud, Elastic, SSL certificates, and JVM GC. It was less about going deep on one area and more about seeing how broadly I could speak across the stack. One of the concrete questions I got was about what a DaemonSet is in Kubernetes. My advice would be to talk through your real experience on each topic as long as they let you, because the pace is so quick that a short or hesitant answer can make it seem like you know less than you do. I didn’t get an offer, but the people were very pleasant and the process itself was smooth.
Prep tip from this candidate
Be ready to explain Kubernetes basics like DaemonSets clearly and quickly, and review practical details across Docker, observability, Linux, networking, SSL certificates, and JVM GC since the technical round jumps between those topics fast.
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 | |
| Merge Sorted Lists | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Find Bigrams | |
| String Shift | |
| Find the First Non-Repeating Character in a String | |
| N-gram Dictionary | |
| Rectangle Overlap | |
| Minimum Change | |
| Prime to N | |
| Get Top N Frequent Words | |
| Good Grades and Favorite Colors | |
| The Brackets Problem | |
| Priority Queue Using Linked List | |
| Recurring Character | |
| Level Of Rain Water In 2D Terrain | |
| Nearest Common Ancestor | |
| Basic Regex | |
| Data Pipelines and Aggregation | |
| Optimal Host | |
| Hurdles In Data Projects | |
| Friendship Timeline | |
| Integer to Roman | |
| LRU Cache 1 | |
| Permutation Palindrome | |
| Customer Analysis | |
| Weekly Aggregation | |
| Cyclic Detection |
Synthesized from candidate reports. Individual experiences may vary.
Both candidates describe a friendly opening conversation with HR or a recruiter. One reports a 30-minute video screen, and the other says the HR contact gave quick updates at each step. Expect it to be a background and fit conversation, though the exact content isn't detailed in the reports.
One candidate reports a conversation with two team managers. The other reports an hour-long hiring manager screen on video. Candidates don't detail the questions, so prepare to walk through your platform and cloud experience and explain why the role fits.
One candidate faced two engineers in a time-limited round that jumped across Kubernetes (including DaemonSets), Docker, observability, Linux, networking, SSL certificates, JVM GC and more. The other describes a 60-minute deep dive on Elastic within cloud architectures. Prepare for either breadth or product-focused depth.
One candidate reports a final panel combining a presentation and a solutions walkthrough on migrating an on-premises architecture to the cloud, with detailed questions on their plan. This stage was not reported by the other candidate, so it may vary by role. Practice a structured migration story with tradeoffs.