Principal Software Engineer - Search Relevance - Elasticsearch

<div class="content-intro"><p>Elastic, the Search AI Company, enables everyone to find the answers they need in real time, using all their data, at scale — unleashing the potential of businesses and people. The Elastic Search AI Platform, used by more than 50% of the Fortune 500, brings together the precision of search and the intelligence of AI to enable everyone to accelerate the results that matter. By taking advantage of all structured and unstructured data — securing and protecting private information more effectively — Elastic’s complete, cloud-based solutions for search, security, and observability help organizations deliver on the promise of AI.</p></div><h3><strong>What is The Role</strong></h3> <p>We're looking for a Principal Software Engineer to join the Elasticsearch - Search team. This globally-distributed team of expert engineers focuses on delivering a robust and feature-rich search experience, including contributing to improving the search experience in Lucene. This is a principal software engineering role that focuses on enhancing the vector and keyword search functionality within Elasticsearch, covering the design and implementation of new search features, enhancements to existing search functionality, and resolving bugs.</p> <p>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.</p> <h3><strong>What You Will Be Doing</strong></h3> <ul> <li>Lead initiatives within <a href="https://github.com/elastic/elasticsearch/" target="_blank">Elasticsearch</a> to produce an industry-leading search engine offering, supplying unparalleled speed and relevance in search.</li> <li>Contribute to Elasticsearch full time, building new search features 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 close to the operating system and hardware.</li> <li>Work with a globally distributed team of experienced engineers focused on the search capabilities of Elasticsearch.</li> <li>Be an expert on Elasticsearch search relevance. You'll identify and drive improvements in this area based on your questions and your instincts.</li> <li>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.</li> <li>Write idiomatic modern Java -- Elasticsearch is 99.8% Java!</li> </ul> <h3>What You Bring </h3> <ul> <li>Professional experience with search and vector databases, and you used HNSW, IVF, or other relevant algorithms and libraries on search platforms at scale.</li> <li>You have strong skills in core Java and are conversant in the standard library of data structures and concurrency constructs, as well as other features like lambdas.</li> <li>You work with a high level of autonomy, and are able to take on projects and guide them from beginning to end. This covers both technical design and working with other engineers to develop needed components.</li> <li>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.</li> <li>You've used several data storage technologies like Elasticsearch, Solr, PostgreSQL, MongoDB, or Cassandra and have some idea how they work and why they work that way.</li> <li>You have e ... (truncated, view full listing at source)