Product Owner - Observability

Natterbox builds AI communications that elevate human-led customer conversations, integrated with Salesforce and the wider CRM stack. This role owns the commercial vision for Observability, which is a platform rather than a single product. You will own both the portfolio of apps we build on it and the data products beneath them: the services that capture, model and expose signal from AI-assisted conversations. Those same data services also power our AI agents through the agent builder programme.

What You'll Own

• The commercial product vision for the Observability platform, and the roadmap to deliver it
• The portfolio of apps on the platform, and the data products beneath them: the services that capture, model and expose conversational signal for those apps, other teams and our agents to consume
• Discovery and delivery with engineering, from problem framing through to shipped product, along with the market and revenue case for the track

How We Work

Product at Natterbox is a small, senior team with a flat structure. You will own your track from end to end, work directly with Engineering and Go-To-Market, and be trusted to make the decisions. Our engineering is AI-accelerated, which raises the standard expected of product judgement rather than lowering it.

Requirements

What you must have

• Owned a commercial product vision, shaping where a product goes and why, and managed the backlog to deliver it
• Built data products, such as data models, pipelines or services that other products and teams consume, not only the apps that sit on top of them
• A genuine commitment to design-led product development and good UX, across both the apps you ship and the experience of the teams who build on your data products
• Enough technical credibility to work closely with engineering on data, modelling and telemetry

Benefits

• Competitive salary and bonus
• Hybrid working, based in the UK. In person meet-ups in London approximately one day a quarter
• The opportunity to shape a product line rather than inherit a backlog