Growth Product Manager - Remote

Responsibilities

• Move predicted revenue per install and per web-funnel visitor. That’s the number you own. Everything else is a means to it.
• Run monetization experiments end to end. Paywall placement and design, pricing, packaging, offers, trial mechanics, subscription flows — hypothesize, ship an A/B test, read it straight, and scale the winners.
• Start from a playbook. You’ve run enough of these to know what usually works and what usually doesn’t, so you begin from patterns, not from zero.
• Reach into activation or retention when the numbers say so. If a change there is the fastest path to more revenue, make the case and ship it, but monetization remains the center of gravity.
• Keep a steady cadence of tests live. Size each opportunity before you spec it, prioritize by expected revenue impact, and always have the next tests ready, so the pipeline never goes quiet, even when engineering is the bottleneck.
• Write short, clear specs: what triggers it, how it's A/B tested, and the rule for calling it. Engineering should be able to build it without a dozen follow-up questions.
• Keep an honest record. Log every experiment, what you expected and what actually happened, and say so early when a call was wrong.
• Partner with GTM. Revenue per install is shared with UA and web. You don't run ads or user acquisition, but you work closely with the people who do, and feed monetization signal back into how we acquire and price.
• Work directly with product, engineering, and the CEO. You’ll be in the room when ideas form, not waiting for a brief.

Languages