Product Design Lead - Payments

📋 Description

• • Own the entire design lifecycle for Velocity’s next-generation cross-border payments platform, from early-stage discovery through pixel-perfect implementation and post-launch optimisation.
• • Translate complex, regulated payment flows—merchant onboarding, FX quoting, settlement tracking, reconciliation—into elegant, self-service experiences that delight enterprise acquirers, digital-wallet operators and global marketplaces.
• • Establish and evangelise Velocity’s first design system: tokens, components, patterns and documentation that scale across web dashboards, mobile companion apps and API reference portals.
• • Run continuous user-research programmes with CFOs, treasury teams and integration engineers across London, Singapore, Dubai and Lagos; synthesise findings into actionable insights that shape quarterly product roadmaps.
• • Partner daily with product managers to define OKRs, prioritise features and craft narrative specs; sit shoulder-to-shoulder with engineers during sprint planning, design QA and release sign-off to guarantee 1:1 execution fidelity.
• • Champion accessibility (WCAG 2.2 AA) and localisation (multi-currency, RTL languages) from day one, ensuring our platform feels native to every market we enter.
• • Design and ship experiments that move core KPIs: conversion from quote to settlement, reduction in support tickets, increase in self-serve API adoption.
• • Build the blueprint for a future design org: hiring rubrics, onboarding rituals, critique cadences and career ladders that will attract and retain top-tier talent as we grow from 20 to 200 people.
• • Present design vision and quarterly retros to investors, clients and the entire Velocity team; use storytelling to turn detailed wireframes into a compelling narrative about the future of programmable money.
• • Stay on the leading edge—stablecoin UX patterns, biometric authentication, emerging DeFi primitives—and rapidly prototype concepts that keep Velocity two steps ahead of legacy payment networks.
• • Balance craft with speed: know when a Figma prototype is enough and when only production code will prove a hypothesis, then roll up your sleeves to make it happen.
• • Cultivate a culture of feedback: run weekly design critiques, maintain a public “design debt” backlog and celebrate launches with post-mortems that make us 1 % better every cycle.