Agentic Product Lead

Agentic Product Lead

What We're Looking For

• Problem-shaped thinking. You describe past work by the hard parts (the schema conflict, the regulatory constraint that broke the obvious design, the integration that looked simple and wasn't), not by phases and deliverables
• Specificity and ownership. You can name the trade-offs you made and why. You hold a view on technical choices adjacent to your work, even when provisional, and you stay close to decisions that shape your roadmap
• Empirical definitions of success. You can answer "how did you know it was working" with something concrete: a leading indicator, a falsifiable hypothesis, a behaviour that shifted, an outcome metric tied to a real decision
• Insight pulled across context. If you've worked across industries, you can name the thread that generalised and what didn't. The synthesis is the credential
• An internal engine. Curiosity that goes past the work surface. You read, build, and form genuine opinions about tools and methods
• Systems-level thinking. You guide a high-performing system rather than letting it collapse to your bandwidth and control
• Ceiling-raising. When you join a working team, the technical and strategic ceiling of the conversation goes up. You ask the question that reframes the problem or take a position the room hadn't considered

Major Responsibilities

• Discovery. Run continuous discovery: story mapping, stakeholder interviews, assumption testing. Surface the hard problems early, while there is still room to shape the response
• Delivery clarity. Own flow metrics, RAID, and clear reporting to client product and engineering leadership. Communicate progress and risk plainly, including when the news is hard
• Stakeholder partnership. Primary product voice to client product owners, engineering leads, and senior stakeholders. Build the kind of trust that lets you tell partners what they need to hear, and have it land
• Team coordination. Partner with Solution Architects on sequencing and trade-offs. Represent the product lane at the same table as design and engineering, not downstream of it
• Agentic Product Engineering. Hands-on in the prototype and feature layers. Everyone develops here, but our agentic harness engineers and agentic systems engineers (experts in system architecture, operations, and quality engineering) handle the deeper technical considerations
• Agentic and platform strategy. Drive client alignment on agentic tooling permissions, evaluation regimes, and human-in-the-loop levels. Bring a clear, defensible point of view

Skills and Experience

• 5+ years in product, with at least 2 years in platform, infrastructure, or genuine 0-to-1 work where the shape of the product was still being figured out
• Direct experience with enterprise clients in regulated or organisationally complex environments. You can describe a specific moment where a constraint forced a non-obvious product call
• Strong working knowledge of front-end architecture, API orchestration, data integration patterns, and cloud-native concepts. You don't write code, but you can engage substantively with architects and offer a real point of view when you disagree
• Continuous discovery practiced in parallel with delivery. The portfolio evidence we want includes a hypothesis you killed, not just features you shipped
• Familiarity with agentic AI tooling, LLM-assisted development workflows, and AI governance considerations. This is a working knowledge requirement, grounded in hands-on use rather than personal-task curiosity
• Consulting or significant client-facing delivery experience. Builds trust quickly with senior client stakeholders while holding your own line
• Clear written and verbal communication. You write in your own voice rather than reaching for stock product-management phrasing, and you describe work in terms specific enough that a reader can tell which engagement you mean

How We Hire

• A technical depth probe on a past engagement. You pick the engagement; we pick the layer to dig into
• A live exercise structuring an ambiguous brief. We are evaluating decomposition, what you ask first, and what you defer
• A conversation about a tool or method you've changed your mind about, and why
• References focused on whether you raised the ceiling of the rooms you were in

Working Relationships Internal: VP of Agentic Product & Platform Strategy, Principal Product Lead, Managing Director, Solution Architects, Developers, Product Designers, Director of AI Strategy

External: Client product owners, engineering leads, design leads, and senior stakeholders