Chief Product Officer (Tax Technology)
Most product roles talk about ownership.
This one expects it.
I’m working with a UK based tax technology business building a product in a space where there’s zero tolerance for error. Their platform applies complex UK tax legislation at scale, helping accounting firms identify risks, spot opportunities, and deliver better outcomes for their clients.
It’s not a concept. It’s live, it’s being used, and now it needs focus.
They’re hiring a Chief Product Officer to take full ownership of product as a commercial function.
That means being accountable for what gets built, why it matters, whether customers will pay for it, and whether it scales. Not managing a roadmap. Not coordinating stakeholders. Owning outcomes.
You’ll be expected to bring clarity where there isn’t any today. To make decisions quickly, often with incomplete information, and to stay focused on what actually drives revenue and product-market fit.
This is a product that needs to be right. Not mostly right. Right. It’s built around deterministic logic, where correctness, repeatability and auditability matter. There’s no hiding behind experimentation or ambiguity in the core product.
You’ll work closely with engineering, but without blurring responsibilities. Product direction, prioritisation and commercial outcomes sit with you. Engineering execution sits with the CTO. It’s a clean split, and it needs to stay that way.
The reality is you’ll inherit imperfect products and competing priorities. You’ll need to decide what not to do just as much as what to do, and you’ll be expected to challenge when things aren’t working.
They’re looking for someone who has scaled B2B software and taken real ownership of commercial outcomes. Someone who can make decisions without relying on process as a safety net, and who understands the difference between what’s valuable and what’s just noise.
If you’ve worked in tax, finance or infrastructure software, that helps. If you understand how to build products that are correct, repeatable and trusted, even better.
This won’t suit everyone. It’s not a research-led product role, and it’s not about building features for the sake of it.
But if you’re motivated by owning outcomes and building something that genuinely works in a high-stakes environment, it’s worth a conversation.
Distinct Recruitment Privacy Policy