Technical Product Owner – Fintech Platform

Technical Product Owner – Fintech Platform Role We are looking for a hands-on Technical Product Owner to own fintech platform and applications capabilities across product, engineering, data, and operations. This is not a backlog-management role. We need someone who understands how systems actually work, can translate business needs into precise technical requirements, make trade-offs with engineering, and drive features through production. What You’ll Own Customer application and onboarding flows Decisioning, fraud, and identity workflows Payments and transaction processing Merchant and partner integrations Servicing, collections, and exception handling APIs, data flows, and internal operational tools Responsibilities Own capabilities from requirements through production. Translate business problems into clear functional and technical requirements. Define user stories, acceptance criteria, edge cases, failure handling, and business rules. Work directly with engineers and architects on APIs, data flows, integrations, and solution design. Identify dependencies and ambiguities before development starts. Drive technical and product decisions quickly. Ensure production behavior matches the intended business outcome. Use data to identify conversion issues, operational bottlenecks, and failure patterns. Design for exceptions, auditability, resilience, and operational support. What We’re Looking For 6+ years in product, technical product ownership, business systems, or software engineering. Strong experience working directly with engineering teams on production systems. Good understanding of APIs, distributed systems, databases, integrations, and software delivery. Ability to read API specs, architecture diagrams, logs, and data schemas. Strong analytical and problem-solving skills. Experience in fintech, payments, lending, lease-to-own, BNPL, e-commerce, fraud, or servicing strongly preferred. Strong Candidates Can Explain How data moves through a system What happens when an API or third-party service fails How duplicate events or inconsistent transaction states are handled How business rules are safely changed How production issues are diagnosed What edge cases must be tested before release They should be able to discuss these topics credibly with engineers and explain them clearly to business stakeholders. Success in This Role Within 6–12 months, you should: Become the clear owner of your platform domain Improve the technical quality of product requirements Reduce rework and missed edge cases Improve delivery speed and decision-making Drive measurable improvements in conversion, efficiency, reliability, or risk