Product Manager in Newport, Wales

Narwhal Labs is the company behind DeepBlue OS — an autonomous revenue infrastructure platform that enables any business to answer every call, follow up every lead, and log every interaction across Voice, SMS, Email and WhatsApp. As an NVIDIA Inception Program Member and Google Partner, we are a 37-person team with our platform launching in May 2026. We build the infrastructure layer for serious businesses that want enterprise-grade revenue operations at a fraction of traditional cost.

You'll own the product — the roadmap, the priorities, the trade-offs, and the bridge between what customers need and what engineering builds. DeepBlue OS is a technically complex platform (autonomous voice agents, multi-channel workflows, real-time billing, multi-tenant compliance), and the product decisions are rarely simple. You'll need to understand what the platform does well enough to make good calls about what it should do next, without needing to write the code yourself.

This is a hands-on product role in a company that runs Scrum seriously — not as a label, but as the actual way work gets planned, prioritised, committed to, and delivered. You'll participate in every ceremony, own the backlog, and be the person the engineering team turns to when they need a clear answer about what to build and why.

• Own the product roadmap and backlog
• Define and maintain the product roadmap — balancing customer requests, commercial priorities, technical debt, and platform capability gaps
• Own the JIRA backlog end-to-end: writing epics and user stories with clear acceptance criteria, prioritising ruthlessly, and ensuring the top of the backlog is always sprint-ready
• Make scope decisions — what's in, what's out, what's deferred — and communicate those decisions clearly to engineering, leadership, and customers
• Run the Scrum process
• Participate actively in all Scrum ceremonies: sprint planning, daily standups, sprint reviews, and retrospectives — not as an observer, but as the person who ensures the team is working on the right things
• Work with engineering leads to size work, identify dependencies, and plan sprints that are ambitious but deliverable
• Own the definition of done — ensure stories are complete, tested, and releasable before they're marked as done, not when they're "mostly there"
• Track velocity, identify blockers, and escalate when the sprint is at risk — early, not at the retro
• Understand customers and the market
• Talk to customers directly — onboarding calls, support escalations, feature requests, churn conversations — and translate what you hear into product priorities backed by evidence, not assumptions
• Understand the competitive landscape well enough to know where DeepBlue OS is differentiated and where it's behind, and make product decisions accordingly
• Work with the commercial team to understand which features unlock revenue, which reduce churn, and which are table stakes for enterprise deals
• Bridge engineering and the business
• Be the person engineering trusts to give them clear, well-reasoned requirements — not vague briefs that need three rounds of clarification
• Attend technical discussions (architecture reviews, design sessions) with enough context to contribute meaningfully — you don't need to code, but you need to understand the trade-offs engineers are navigating
• Communicate product decisions, timelines, and trade-offs to leadership, sales, and customer-facing teams in language that doesn't require an engineering degree to parse

• 3+ years in a product management role at a B2B SaaS or technology company — you've owned a backlog, written stories, and shipped features that customers used
• Genuine fluency in Agile and Scrum — you've run sprints, facilitated retros, groomed backlogs, and managed stakeholder expectations within a sprint cadence. You know the difference between "doing Scrum" and having a JIRA board
• Experience working directly with engineering teams — you can read a technical architecture document, understand an API contract at a high level, and have a productive conversation about trade-offs without needing everything translated
• Strong written communication — your user stories are unambiguous, your acceptance criteria are testable, and your roadmap documents don't require a follow-up meeting to understand
• Comfortable with ambiguity — in a company at this stage, not every decision has perfect data behind it. You make the best call with what's available and adjust when you learn more
• Experience with JIRA (or equivalent) as a daily working tool, not just something you log into occasionally

• Product experience in AI, voice, conversational technology, or communications platforms — you understand the domain, not just the discipline
• Experience in a company that serves regulated industries (financial services, healthcare) where compliance constraints shape product decisions
• You've worked in a company between 20–100 people where the product manager is the product team — no analysts, no researchers, no programme managers to delegate to

• Writing code or designing UI — you'll work closely with engineers and designers, but the hands-on-keyboard work is theirs
• Project management as a primary function — you'll track delivery, but your job is deciding what to build, not managing Gantt charts
• Working in a siloed product team — you'll be embedded with engineering, sitting in their standups, reading their PRs, and understanding what they're building at the feature level

DeepBlue OS is live, customers are onboarding, and the feature requests are already outpacing capacity. Someone needs to decide what gets built next, why, and in what order — and make that decision stick. That person is the Product Manager.

• Competitive salary
• Hybrid working (Bristol-based) with high autonomy
• Direct access to leadership, customers, and the engineering team — no layers of abstraction
• The opportunity to shape the product direction of an AI infrastructure company at the point where early traction turns into real scale

Send your CV and a brief note on: a product decision you made that was unpopular with at least one stakeholder group, why you made it, and what happened.

We're building something global at Narwhal, and we mean that in every sense. The work we do requires different ways of thinking — and different ways of thinking come from different people. At Narwhal, we're committed to building a diverse and inclusive team. We welcome applications from people of all backgrounds, identities, and experiences, and we actively work to ensure our hiring process is fair and accessible for everyone. Reasonable adjustments are available at every stage, just reach out and we'll make it happen.