Primary record

Director of Product

Weaviate Indexed employerCET, GMT or EST timezones
Source-hosted applyChecked 4h agoFull-Time
Apply at Weaviate

Weaviate receives this application through Ashby. Babu Careers does not claim delivery.

Workplace

remote

Employment

Full-Time

Published

Aug 5, 2026

Closes

No date supplied

The role

ABOUT WEAVIATE Weaviate https://weaviate.io/ is an AI startup with open source and creativity at its core. Our AI-native vector database uses machine learning to create meaningful insights from unstructured data in a completely new way. Named one of Forbes’ Top 50 AI startups, and with over a million monthly downloads, Weaviate is quickly growing in popularity with developers and enterprises alike. Our team members work remotely across the globe with the flexibility to work from anywhere and at any time. Our people experience this as a massive benefit! Operating with a strong sense of ownership and collaboration, our teams prioritize results while empowering each individual to do their best work. ABOUT THIS ROLE Weaviate has been really successful in enterprise, and we're doubling down on that by growing our enterprise-facing teams. That shifts what the product has to do. Large customers arrive with specific requirements, and someone has to decide which of those we build, in what order, and which ones we tell the customer we won't build. As Director of Product, you'll own product strategy and decision-making across the Weaviate Database, Weaviate Cloud, and our agent products. You'll spend a lot of your week with customers, and the rest of it turning what you heard into a roadmap that engineering can act on. You'll work directly with our CTO on vision and with tech leads on what's actually feasible. This is a player-coach role. You'll manage a small product team, likely one to three PMs over time, while continuing to own product areas yourself. WHO WE'RE LOOKING FOR You're comfortable in front of enterprise customers, and you go looking for those conversations rather than waiting for them to be scheduled. You can tell the difference between a request that will block a deal and a request that's a minor annoyance, and you can explain how you reached that conclusion. You make prioritization decisions using evidence. When you say one feature should ship before another,

Requirements

Department: Product; Team: Product