Home / Product / Head of Product, AI (London / Dublin / Prague)

Head of Product, AI (London / Dublin / Prague)

Productboard · United Kingdom - Remote

Head of Product, AI (London / Dublin / Prague) is open at Productboard in United Kingdom - Remote (hybrid). Posted on Nov 6, 2026, and still on Productboard’s careers page when we last checked, on Nov 21, 2026.

About the role

Locations: London / Dublin / Prague

At Productboard, we're building the first agentic product management system. We're rethinking how product management is done in a world full of AI agents, and how we help our customers build what matters for their audience. AI is changing what an interface even is: static screens are giving way to conversations, generated artifacts, rich interactive UI, and open-ended workflows, often on the same screen.

The role

Head of Product, AI Product. Reports to the CTO. Based in Prague, Brno, or remote within Europe with regular time in Prague.

Productboard is the agentic product system for product teams. At its center is Spark, a product management agent that connects to a company's customer feedback, strategy, competitive intel and codebase. Spark finds the highest impact opportunities, writes delivery ready specs, and runs the workflows a team builds as Skills. More than 4,000 companies run their product work on Productboard.

We are building one picture of where a product is strong and where it is weak, from two directions at once. Top down: executives and product leaders read portfolio health by segment and capability, built from what customers say, what they do, and the revenue behind it. Bottom up: a PM starts from one piece of feedback or one feature and follows it to the insight, the capability and the revenue it touches. Both read from the same data, and both run through your domains.

You own Spark and everything agentic underneath it: the agent, the harness it runs in, the quality bar it has to clear, the insights pipeline it reads from, the specs it writes, the MCP surface other agents use to reach it, and the design system every surface of the product is built from. The PMs on those surfaces and every product designer report to you. You lead design for the whole product.

In the future, most of the work done in Productboard will run through agents, via MCP and APIs. Some UI will always stay. You decide which, and the screens that stay have to be excellent.

What you own

  1. Spark, our agent. What it does, what it asks, when it acts on its own and when it waits for a person.
  2. The agent harness and orchestration. Skills, scheduled tasks, human in the loop capability, model choices and cost per task. The runtime every agentic feature executes in.
  3. AI experience. Spark UI, human in the loop UX and generative UI. How a person sees, steers and corrects agent work.
  4. AI quality. You own the evals for Spark and every agentic feature: the eval suite, the judges, the method and tooling every team evals with, the review cadence that decides whether an output ships, and how evidence is shown to a person.
  5. Feedback analysis and insights. The pipeline that turns customer conversations into structured insight, and the views where teams read it.
  6. Product specs. Where the agent drafts with product teams, and what delivery ready means. The editor's storage and collaboration engine sit with the platform. You own the spec experience.
  7. MCP servers. The surface through which Claude, Cursor and other agents work in Productboard. The tools, skills and agents we expose there. The protocol layer itself, auth, rate limits and hosting, sits with your platform peer.
  8. Boards, roadmaps and dashboards. The views product teams work in. You own the application: what a board shows, how a roadmap reads, what a dashboard answers. The query engine underneath is your peer's platform capability.
  9. Design for the whole product. All product designers report to you, on the AI product and on the platform. You own the design bar across the product. Critique, hiring and the design career ladder run through you. You also own the design system: the component library and design language every surface of the product uses, including the platform surfaces your peer owns.

How you work

Our CEO owns product strategy and the context behind it: where the product goes and why. You own the roadmap and the decisions for your domains within that strategy. Engineering managers own the engineering side of each domain, and your PMs and designers partner with them. Initiatives are staffed from a shared roadmap, and people move with initiatives while domains and reporting lines stay put.

Our Chief AI Officer sets direction and raises the bar on anything agentic, across the company. He owns no layer and no roadmap.

Your peer is the Head of Product, Enterprise Platform. They own the capabilities underneath every surface: the data model, the query engine that boards, planning views and dashboards run on, the editor engine, permissions, security and compliance, search, notification routing, integrations and the protocol layer. You own what people see on top of it: every surface, every designer, the design system. When a capability needs a screen, your team designs it. When a surface needs a capability, their team builds it. Work that touches both is staffed across both groups through initiatives.

You bring the problem before the solution. An initiative of yours gets investment once you have made the case that the problem is worth solving. You ship it to our own workspace first and take it GA when it hits the goal you set at the start.

Why this matters for your career

Our engineers already build with agents. An engineer claims a feature, writes the spec with Spark, hands the code to Claude or Codex, steers it, and delivers. Review moved upstream to the plan. Low risk changes merge on an agent's review alone. Per engineer throughput has already doubled in the last nine months. You will help us run product the same way: the agent drafts, the PM decides what ships and everyone creates working prototypes.

The practice you will run is ahead of what most product orgs describe in decks. Opportunity reviews before solution reviews. Specs and implementation plans in one place, where any person or any agent picks up the full context. Initiatives that ship to our own workspace first and go to GA against a goal set at the start. Evals and a written quality bar as product tools you own. You get the best tools we can buy and the support to use them. You will use Claude, the IDE you prefer, and our MCP server every day, and you can prototype a change and ship it to our own workspace yourself, without waiting on an engineer.

Our north star: get from idea to learning twice as fast. Then twice as fast again. Halving the cycle once is easy. Halving it every time is the job. Faster learnings. Better outcomes. We win by deciding faster with better evidence.

First six months

  1. Spark has a written quality bar, an eval suite that runs on every change, and a weekly review you chair.
  2. Customer feedback attaches to the right capability and feature on its own, at a precision product teams trust. Executives read portfolio health on top of it.
  3. For every place Spark shows up in the product, you have decided whether people use it through our UI, headless via MCP from an agent like Claude, or both.
  4. Spark behaves the same way on every surface. One written document says when it acts, when it asks, how it shows its work, and how a person corrects it. Nothing new ships until critique has held it to that document.
  5. The design team has a critique cadence, a hiring plan and a written ladder, run by you.
  6. The Productboard MCP server is listed as a connector in the directories that matter: the Claude Connectors directory, the ChatGPT app directory, Grok, and the Cursor marketplace. MCP monetization runs on a clear, written strategy.
  7. You know what share of Productboard work runs headless, through MCP and APIs, against what runs through our UI. You report it monthly and it is moving toward headless.

Who you are

In one line: a very strong PM domain and use case expert who has shipped a trusted agent, with great UX DNA. In the order we weight it:

  1. You know the product management job cold. You have run product management, or built products for product teams, and you understand discovery, prioritization, planning and roadmap communication from the inside. You know the use cases in detail: how feedback becomes insight, insight becomes a spec, and a spec becomes a roadmap, and where each step breaks today.
  2. You start with the customer, not the solution. You run discovery yourself, keep close relationships with the product leaders who use what you ship, and bring their problems to the team before anyone designs an answer.
  3. You take what you ship to market and prove it worked. You work with marketing on positioning and launches, build in public, and tell our story on stages, podcasts and in writing, so Spark is the name product teams think of for AI. After launch you measure adoption and outcomes against the goal you set, and you change or retire what missed it.
  4. You have shipped an agent where the hard problem was trust. What the agent shows, when it asks, how a person reviews its work, and what happens when it is wrong. You can argue, with evidence, when an agent should act and when it should wait.
  5. You run AI quality as a product discipline. You have owned evals for a shipped agent. You can read a trace, write a judge, and tell a model problem from a prompt problem from a product problem. You have held a release because the eval said no.
  6. You have great UX DNA. You notice the experience problem before the designer flags it, and you have agent design work you can show. UX here means the product experience, not visual or brand design. You manage designers directly, hire them, and run critique, and you have contributed design work of your own that shipped, not only reviewed theirs.
  7. You build with agents every day. You use Claude or its equivalent for real work, not to edit text. You have connected it to your own tools and data, built skills and multi step workflows that other people use, and you know where the model fails and how to fix the prompt, the context or the workflow.
  8. You are fluent in headless. You understand that the product will be used through agents, via APIs and MCP, and you can decide which screens stay and which go.
  9. You have a computer science or engineering background. You own the harness, the evals and the MCP surface, and those conversations go faster when you can read the code and the trace yourself.

Not a fit if

  • Your AI experience is model tuning or research. We need someone who has shipped agent behavior to customers.
  • You are a platform PM. The platform has its own Head, and that search is open too.
  • You are a brand or visual design leader. This role leads product design for the whole product, agent first.
  • You cannot judge product design work yourself and rely on your designers to tell you what is good.

Our benefits include:

Shared benefits (all EMEA)

  • 5 weeks of paid time off per year
  • 9 paid sick days per year, also for mental-health days
  • 1 paid Volunteer Day per year
  • Stock options
  • USD 300 per year professional development stipend
  • Mental wellness program with online therapy sessions
  • Carrot: fertility, adoption and family-forming support for you and your partner (pregnancy, postpartum and menopause support in the UK and Ireland)
  • One-off home-office stipend (amount by location)

The employer’s own description, as published on Productboard’s careers page.

Hiring at Productboard

Productboard has 29 open roles right now, 13 of them remote. Most are in Engineering, Product and Design. See all its roles

✓ Actively hiring 7 roles posted in the last 7 days✓ Few old postings 10% open 90 days or moreWhat the marks mean

Similar Product jobs

All Product jobs
Apply on company site