Senior Product Manager

We are seeking a Senior Product Manager to help us professionalise and scale our product function.

Today, much of Diesta’s product thinking sits across leadership, engineering, implementation, design, and customer-facing teams. As the company grows, we need someone who can bring these inputs together and turn them into clear product requirements, strong specifications, well-organised backlog items, and implementation-ready detail for engineering and design.

This person will work closely with leadership, the Head of Engineering, the CTO, implementation consultants, account management, customer-facing teams, designers, QA, and engineers.

The role is especially focused on specification, product structure, edge-case discovery, and internal orchestration. The Senior Product Manager should be client-aware and commercially aware, but the role is expected to be more internally focused than externally sales‑led.

Over time, this person could grow into a broader product leadership role.

Product Specification: Own the creation of clear, structured, implementation‑ready product specifications for new features, platform improvements, workflows, reports, and operational capabilities.

Edge‑Case Discovery: Obsess over edge cases, exception flows, data integrity risks, permissions, reconciliation scenarios, operational failure modes, and non‑happy‑path behaviour.

Requirement Shaping: Gather and synthesise inputs from customer‑facing teams, implementation consultants, account managers, leadership, engineers, designers, operations, and clients where appropriate.

Product Coherence: Help protect Diesta from becoming a collection of bespoke customer‑specific features. Challenge requests constructively and ensure new functionality fits the broader platform direction.

Internal Product Ownership: Maintain and improve Diesta’s internal product request process, product backlog, discovery notes, and specification workflows across tools such as Notion, Atlassian/Jira, Google Drive, or future systems.

Engineering Readiness: Ensure that engineering teams receive sufficiently clear, well‑considered requirements before build work starts, reducing ambiguity, rework, and last‑minute changes.

Design

Collaboration:

Work closely with design to translate complex product requirements into usable workflows, screens, buttons, states, and user journeys.

Customer Context: Where needed, work with customer‑facing colleagues to clarify client needs, validate proposed solutions, and support sign‑off on feature scope.

AI‑Leveraged Product Work: Use AI tools to accelerate research, requirement analysis, document review, specification drafting, backlog organisation, and cross‑tool knowledge retrieval.

Scenario Mapping: Map out different user journeys, operational scenarios, permissions, data states, integrations, reporting needs, and exception cases before features enter development.

Backlog Quality: Build and maintain a backlog of properly thought‑through product opportunities so that available engineering capacity can be directed toward high‑value, well‑defined work.

Cross‑Functional Alignment: Act as the connective tissue between product direction, implementation reality, customer requirements, design, and engineering execution.

Operational Awareness: Understand how product choices affect implementation, customer success, payments operations, reconciliation, reporting, support, and internal workflows.

Developing Product Function: Help define how product management should work at Diesta as the company grows, including documentation standards, discovery processes, specification quality, and collaboration rhythms.

Experience: Significant product management experience in a B2B software, fintech, insurtech, payments, banking, financial infrastructure, or similarly complex operational software environment.

Specification Strength: Proven ability to write clear, detailed product specifications that engineering and design teams can use without excessive back‑and‑forth.

Logical Thinking: Strong ability to structure complex problems, break them into scenarios, identify dependencies, and reason through consequences.

Edge‑Case…