Frequently asked questions
Is this job still open?
GMI Jobs is currently showing this Lead Product Manager, Family Safety role at MoneyLion as an active listing from employer-controlled hiring sources. Always confirm final availability on the employer application page before applying.
How do I apply for this role?
Use the application link on this page to apply directly with MoneyLion. GMI Jobs keeps the canonical job page, company context, and market links together so candidates can compare before leaving the site.
What should I compare before applying?
Compare the role location USA - New York, NY, any listed pay signal, company profile, related crypto jobs, and salary context before applying. Listed pay signals are not guaranteed offers; confirm compensation with the employer.
Job Description
About the Role We're looking for a Product Lead to own the Family Safety capability domain—spanning household protection across multiple consumer needs and life stages. You'll think about how to protect different household members, what features matter for each scenario, and what customers care about most. You'll define the capability roadmap, set product requirements, and drive alignment across engineering, design, and business teams to ship what matters. This is a high-ownership role. You'll own the capability roadmap, define product requirements that engineering builds from, work closely with the UX team on how capabilities surface, and make decisions on what to build in-house, what to extend from existing products, and what to vendor. You'll navigate device OS complexity and regulatory constraints, and move decisions forward without needing formal authority. Key Responsibilities Product Ownership & Roadmap Own the Family Safety capability roadmap. Prioritize the backlog and make decisions on what ships when. Define what capabilities the product needs to ship. Balance competing priorities across multiple household protection scenarios. Make build vs. extend vs. vendor decisions. Own the strategic and economic case: distinguish table-stakes capabilities from differentiators, and build the argument for where to own vs. where to vendor based on competitive positioning, integration benefits, and economics. Requirements & Specification Write product requirements that define what capabilities engineering builds. Own the details: edge cases, device constraints, cross-surface implications. Close open questions on capability definition. Work with the UX team on how features surface, with engineering on feasibility, with legal/privacy on compliance. Define success metrics for each capability. Cross-Functional Execution Serve as the connective tissue between the UX team, engineering, legal/privacy, business stakeholders, and partner product leadership. Run planning and alignment sessions. Keep decisions moving without formal authority. Work with partner product teams to structure capabilities in ways that are integrable via APIs and SDKs—ensuring partners can build on what you define without requiring heavy custom engineering. Navigate device OS fragmentation, cross-device enforcement complexity, and the different constraints across platforms. Regulatory Navigation Work with legal, privacy, and government relations teams to navigate baseline compliance (COPPA, GDPR) and fast-moving regional mandates (age verification, time-limited access, parental control interoperability requirements across EU, UK, France, and other jurisdictions). Define how regulatory evolution shapes capability roadmap and sequencing. Navigate platform-specific constraints (Apple MDM exceptions, browser limitations, OS-level enforcement) as they interact with regulatory requirements. Support business development by translating regulatory requirements into capability features