Growth Product Manager

About Fasset:

Fasset is building the ownership bank: real assets (gold, backed dollars, global markets) on regulated rails across the Gulf, South Asia, and Southeast Asia. $100M+ raised, 2M+ users.

About the Role:

A committed H2 roadmap with dated releases: referral relaunch and affiliate program (August), rewards marketplace and mission center (September), pre-dormancy save flows (hard November date), win-back ladder, a recurring-execution rail that serves three future products, and a Q4 slate including round-ups into gold, a seasonal gifting mechanic with a fixed religious-calendar deadline, and a remittance corridor pilot. Underneath: a user state machine (8 states, 11 numbered edges) that sets priorities, and a metrics canon that sets definitions. You can change the plan if the data supports the change.

Responsibilities:

Ship the releases. Specs, sequencing, engineering coordination, QA handoff, release notes. Dates hold, or slip with advance notice. Several releases gate each other; two have external deadlines.

Work against the state machine. Every initiative names the state transition it moves and the loop it feeds before it enters the roadmap. You know the current transition numbers and adjust the roadmap when they change.

Pair with the Growth Analyst. Every release ships with pre-registered success criteria (target, guardrail, kill threshold, read date) agreed with the Analyst before launch. Post-reads happen on the read date. Kills execute when thresholds say so. The Analyst certifies numbers independently; you do not grade your own launches.

Guard payout definitions. Referral, affiliate, and gifting features pay out on qualified user behavior, not raw counts. You design against gaming and abuse before launch.

Coordinate growth work across pods. Cards, Earning, Lending, network, and market teams ship features that touch acquisition, activation, or retention. You keep a single view of growth-relevant releases company-wide, run a light cross-pod cadence, and catch overlaps before they ship.

Prioritize marketing rails against feature work. The pod builds infrastructure marketing runs on: promo engine, deep links, segmentation, campaign onboarding paths. You sequence these against features.

Run lifecycle mechanics until that seat is filled. Save flows, win-back ladders, and messaging journeys ship through the pod. You spec and oversee their operation in the interim.

Drive user segmentation and journey experimentation. Build a scalable process leveraging Mixpanel to more granularly define our target users, their use cases and optimize their onboarding and engagement funnels.

Requirements:

Right for this if:

• You have shipped growth mechanics at a consumer fintech, crypto platform, marketplace, or high-volume consumer app: referral programs, incentives, onboarding flows, retention journeys.
• You have run a roadmap where releases gated each other. You can name a date you saved and a date you slipped, and the difference.
• You can look at a funnel and name the transition that matters most now, with numbers.
• You have worked beside an independent analytics function: pre-registered criteria, honest post-reads, features killed on their stated thresholds.
• You have coordinated across teams without authority over them and shipped anyway.
• Emerging-market or Islamic-finance product context is a strong plus. Our mechanics include gifting, gold, remittance corridors, and Shariah-reviewed features.

Not a fit if:

• Your portfolio is strategy and discovery without shipped mechanics.
• You need a blank page. This role inherits a dated plan.
• You treat measurement as post-launch reporting.
• You cannot explain how a feature you built was or would be gamed.
• Cross-team coordination reads to you as politics.