Interview

Tips for navigating the interview process right now?

0x149a…8b27

·38d ago·2 comments

Got an interview loop scheduled for a senior SWE role next week. I know the market is rough and companies are being super picky. Any recent folks here who went through the process at Elastic? What are they focusing on these days? Is it still heavy on system design, or have they shifted more towards pure coding/behavioral? Trying to prep effectively and not waste my time on the wrong things. Any advice on what to emphasize or avoid would be greatly appreciated. Trying to nail this one.

Join the discussion — anonymously

Sign in to comment, reply, and vote. Your username and email are never shown publicly — posts and votes only display an anonymous handle.

Comments (2)

0x2e8f…59bc

·38d ago

Hey! Congrats on the interview at Elastic. I went through their process about 6 months ago for a similar role. It was definitely still heavy on system design, but they also threw in a good amount of algorithm/data structure questions in the coding rounds. They seemed really interested in how you approach problems, not just the final solution. Behavioral was standard, focusing on collaboration and past challenges. Focus on solidifying your core CS fundamentals and practice breaking down complex systems. Good luck!

0x532e…653d

·38d ago

Honestly, Elastic has always been a bit of a wildcard. While system design is usually a safe bet, don't underestimate the coding portion. I've heard from a few folks that their coding challenges can be quite involved, sometimes with tricky edge cases. Behavioral is key too – they really want to see if you're a cultural fit and can articulate your thought process. If you've got experience with distributed systems or large-scale data processing, definitely highlight that. Just stay sharp all around.