Lead Product Manager, Platform

<div class="content-intro"><p>Flex is a growth-stage, NYC headquartered FinTech company that is creating the best rent payment experience. It’s hard to believe that it’s 2026 and paying rent on time is expensive, inflexible, and difficult. We’re here to change that! Flex enables our users to pay rent throughout the month on a schedule that better fits their finances and budget. Our mission is to empower as many renters as possible with flexibility over their most significant recurring expense. After deliberately keeping a stealth profile as we built up unprecedented investor support and an enthusiastic user base, we are looking for motivated individuals to help us keep our mission growing. Will you be a part of the team?</p></div><h3><strong>About the Role</strong></h3> <p>Flex is expanding beyond rent into utilities, and other new biller verticals — and the platform needs to scale with it. Platform core services owns the foundational layer that every Flex product runs on: fulfillment, identity, tagging, biller gateway, and auto-pay. As the Platform PM for these services, you'll define the architecture that enables Flex to rapidly build and scale new products.&nbsp;&nbsp;</p> <p>This is a high-leverage platform product role. The decisions you make here create or remove optionality for every squad at Flex. You'll work directly with senior engineering leads and interface regularly with other product and operations teams and leaders.</p> <h3><strong>Responsibilities</strong></h3> <ul> <li><strong>Fulfillment Flexibility &amp; Exception Handling:</strong> Own the roadmap for making Flex's fulfillment engine configurable across product types without hardcoded portal logic. Define exception-handling flows for portal failures, partial payments, and settlement mismatches, and establish SLA contracts with clear failure recovery playbooks.</li> <li><strong>Identity Service &amp; Acquisition Channel Extensibility</strong>: Extend Flex's identity service to support new customer acquisition channels, including embedded, partner, and employer-sponsored flows. Define the canonical customer graph — deduplication, merge logic, tombstone records, and lifecycle state transitions&nbsp;</li> <li><strong>Auto-pay Configurability for Multi-Bill Flows</strong>: Make auto-pay a durable, configurable service capable of handling multi-bill payment flows as Flex expands to utilities and move-in costs. Design payment schedule logic that manages mixed due dates, variable bill amounts, and payment method fallback — and own the consent and mandate model for recurring payment authorization.</li> <li><strong>Customer Tagging &amp; State Management</strong>: Own the tagging and segmentation service used by product, CS, and growth teams. Define