Lead AI product management, project

The work

Decides what to build, for whom, and how to tell whether it worked.

A defined outcome with a defined end. The scope is agreed before you start, and changing it is a new conversation rather than a favour.

The bar

You have owned delivery and you have set the standard others worked to, including saying no to work that was already funded.

Why this one is hard to judge. The discipline is barely five years old, so titles say very little about what someone has actually shipped.

What we ask to see

• A product decision you made about what not to automate, and what happened
• How you decided what good looked like, before you shipped
• A feature you killed after launch

One solid item beats five vague ones. A referee we can actually call beats a link to a landing page.

What gets an application declined

• The only evidence offered is a certification, a course, or a job title
• Every piece of evidence is under an NDA and no sanitised version or referee is offered
• The work described is entirely a demonstration, a proof of concept, or a hackathon
• More than six disciplines are claimed, which we read as a signal that none has been assessed

If we decline you, the reason is written down and sent to you. The software refuses a decline without one.

What it pays

Nothing is published for this discipline in the UK advertised market, so there is no figure to give you and we are not going to invent one.

Nothing published for AI product management as a distinct title. Product roles that are entirely AI are advertised as product roles, so their figures are indistinguishable from product work generally.