Why should you join our Analytics & Geo team in Elasticsearch engineering?

If it comes from Elasticsearch and it's beautiful, we provide the data for it.

We believe in the power of search and every day push the boundaries of what search can do. Our products power and monitor many applications that you use everyday. If you see a graph, we fed it data. From making information easily discoverable on Wikipedia to analyzing data from the Mars helicopter, Elasticsearch is so ubiquitous it was chosen to be stored for future generations as part of the Arctic Code Vault Program. But we are not done yet. If pushing the boundaries of search algorithms, while solving challenging problems in a highly distributed and scalable manner excites you, we are searching for you.

Our company is distributed by intention. We hire the best engineers we can find wherever they are, whoever they are. We collaborate across continents every day over email, GitHub, Zoom, and Slack. At our best, we write fast, scalable and intuitive software. We believe that the best way to do that is to empower individual engineers, code review every change, decide big things by consensus, and strive for incremental improvements.

What You Will Be Doing

• You'll be a full time Elasticsearch contributor, teaching Elasticsearch about the wonders of time series data and fixing intriguing bugs, all while making the code easier to understand. Sometimes you'll need to invent a new algorithm or data structure. Or find one and implement it. Sometimes you'll need to get closer to the disk or disassembly.
• You’ll work with a globally distributed team of experienced engineers focused on the summary/aggregation and geo capabilities of Elasticsearch.
• You’ll contribute to our efforts in making Elasticsearch better equipped to handle time series data. 
• You'll be an expert in several areas of Elasticsearch and everyone will turn to you when they have a question about them. You'll improve those areas based on your questions and your instincts.
• You'll work with community members from all over the world on issues and pull requests, sometimes triaging them and handing them off to other experts and sometimes handling them yourself.
• You'll be working in the open. Your code and comments and commit messages will be world readable. All of your victories and mistakes and compromises. That's hard for some folks. We hope that for you it'll be worth it.
• You'll write idiomatic modern Java. Elasticsearch is 99.8% java so you'll end up confident even if you don't start that way.

What You Bring Along

• You've worked on a time series database.
• You can talk about and implement data structures and algorithms from old standbys like heaps and merge sort to unique things customized for our problems.
• You've used several data storage technologies like Elasticsearch, PostgreSQL, Prometheus, MongoDB, or Cassandra and have some idea how they work and why they work that way.
• You work with a high level of autonomy. The distributed nature of the company offers freedom to work when and how you see fit, but also requires team members to work independently, and reach out for help when stuck.
• You're comfortable developing collaboratively. Giving and receiving feedback on code and approaches and APIs is hard! Bonus points if you've collaborated over the internet because that's harder. Double bonus points for asynchronous collaboration over the internet. That's even harder but we do it anyway because it's the best way we know how to build software. 
• You have excellent verbal and written communication skills. Like we said, collaborating on the internet is hard. We try to be respectful, empathetic, and trusting in all of our interactions. And we'd expect that from you too.

Bonus Points

• You've contributed to open source projects.
• You've worked on a distributed system. Better if distributed storage technology. 
• You've built things with our Elastic Stack before.
• You are proficient in low-level Java, standard data structures and concurrency primitives.
• You have experience with benchmarking or profiling tools like JMH, Java's async-profiler, Linux perf
• You've analyzed a java heap dump
• You are comfortable in Linux. Double bonus points for being comfortable with strace and friends.