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
What is The Role RevTech Engineering builds the tools Elastic's Field teams depend on every day — the conversational experiences, single-pane-of-glass portals, and AI-powered workflows that help sellers, solutions architects, customer success managers, and support teams do their best work
The AI Experiences squad is where those AI capabilities take shape in the UI. We're looking for a Software Engineer II who is as curious about how AI behaves in a product as they are about how to build it. This role isn't about training models or writing pipelines — it's about making AI interactions legible, useful, and trustworthy for the people using them
You'll work closely with a principal software engineer who brings both design and engineering depth, which means you'll have real mentorship and a high bar to grow toward. You'll also be connected to what's happening across Elastic's broader AI and design system work, contributing to consistent surfaces and bringing back patterns that raise the quality of what we ship
What You Will Be Doing Build AI components for Field-facing experiences
Develop and iterate on the front end components that surface AI capabilities — tool calling, reasoning traces, generative responses, suggestions — across RevTech's end user experiences
Lead the user experience of AI interactions
Partner with the principal engineer and RevOps team members to evaluate whether AI components are working — is the right information surfaced, is the response legible, is tool-calling output helping or overloading the user? Instrument what you build
Use OpenTelemetry to instrument AI components so the team has a signal on what's working. Track interaction patterns, identify friction points, and use that data to drive iteration
Contribute to AI UI consistency
Stay ahead of how Elastic UI and the broader Elastic AI product surface handle AI components, and apply those patterns in RevTech — or flag where RevTech's needs require something new
Support the Salesforce LWC surface
Contribute occasionally to AI component work in Elastic's Salesforce Lightnin