DirectJobHub
Jobs · Marketing

Senior Product Manager, Analytics Features

RevenueCat · United States · 1 mo ago
RemoteRemoteMarketing$207k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove application instructions. The posting includes many paragraphs; we need to extract relevant content. We need sections: About The Role (already a heading). Then maybe "About You" includes Skills & Experience, Values And Abilities. Could map to Requirements, Qualifications, Skills sections. Also "What You'll Do" could be Responsibilities. "What we offer" includes Benefits. Pay: salary given $207,000 USD. Also mention Compensation Range: $230K (maybe a range?). There's also "Compensation Range: $230K" maybe max? We'll include Pay section with salary and maybe note compensation range. Schedule: not mentioned; remote-first, flexible time off. Could infer schedule? Not explicit. So we should not create Schedule section unless posting actually states it. It mentions remote-first, flexible time off, but not schedule like hours. Probably not include Schedule. Benefits: "Competitive equity ... 10-year window to exercise vested equity options A fully remote environment ... 4-5 weeks of flexible time off annually Paid desk at a co-working space Workspace budget and continuous learning stipend". Also maybe mention remote-first. So Benefits section. Qualifications: maybe "Skills & Experience" and "Values And Abilities". Could split into Requirements (must-haves) and Qualifications (nice-to-haves). But we need to follow instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content. We need to preserve all substantive info; not invent or summarize away detail. So we need to include details like bullet points. We must use
  • for any list of duties/requirements/benefits, and

    for prose. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment. Let's structure:

    About the role

    ... (the paragraph about role)

    Responsibilities

    • Own the product strategy and roadmap for RevenueCat's Analytics products.
    • Be obsessed with your customers.
    • Triage and investigate complex data and analytics problems deeply, instead of fully delegating to engineering.
    • Dig deep to understand what developers really want — distill signal from noise and good ideas from bad ones.
    • Recommend, develop and maintain new benchmarks and metrics that deliver value to our developers, and help them make more money.
    • Be the go-to person when a number looks off.
    • Set the vision. Create a plan that is cohesive, intentional, and impactful. Break that down into meaningful chunks on a reasonable timeline. Get it done.
    • Collaborate closely with engineering, data science, and GTM teams to bring robust analytics and experimentation tools to market.
    But note some of these are prose sentences; we could keep as list items.

    Requirements

    Maybe combine Skills & Experience and Values And Abilities as requirements. But we also have Skills section separate. Could do:

    Skills

    • 5+ years of product management or adjacent experience, with meaningful time shipping complex products.
    • Analytical; proficient in SQL (or similar tools); love diving deep into data.
    • Experienced in developing robust and scalable metrics.
    • Technical; able to prototype with code using preferred AI stack.
    • Ability to discuss APIs, data models, and risk logic with engineering partners.
    • Excellent communicator; express complex ideas clearly and succinctly across timezones and mediums.

    Qualifications

    Maybe values and abilities:
    • Act like an owner; roll up sleeves, dive into logs, get things done.
    • Thrive in ambiguity; comfortable making low-information, high-stakes decisions.
    • Systems thinker; step back from specific customer request to see broader system.
    • Build things that scale; deep on details; care about user experience.
    • Know when it's good enough; bias toward shipping; love building, discovery, experimentation, rapid iteration.
    • Passionate about great data visualization; chart sins grind your gears; visualizations deliver meaningful insights.
    But we need to ensure we don't duplicate content. The posting also includes "About You Skills & Experience" and "Values And Abilities". We'll treat Skills as the bullet list of skills, Qualifications as values and abilities. Now Benefits:

    Benefits

    • Competitive equity in a fast-growing, Series C startup backed by top-tier investors, including Y Combinator.
    • 10-year window to exercise vested equity options.
    • Fully remote environment designed around autonomy and flexibility.
    • 4-5 weeks of flexible time off annually.
    • Paid desk at a co‑working space.
    • Workspace budget and continuous learning stipend.
    Pay:

    Pay

    The salary for this role is $207,000 USD.

    Compensation range: $230K (as noted).

    But we need to avoid filler like "not specified". This is specific. We might combine into one

    with both. Schedule: not present, so omit. Also we need to include maybe "About The Role" heading exactly as "About the role" (lowercase after About?). The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should match exactly those strings (case-sensitive?). We'll use exactly as given: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay". No Schedule. Now ensure we preserve all substantive information: we missed some details like "You will oversee all of the Analytics features at RevenueCat — our charts, benchmarking, dashboard, and predictive LTV." That's part of About the role maybe. Also "You'll partner directly with leadership, collaborate across engineering and data teams, and act as the primary driver for how our customers understand and grow their revenue." Also "As product manager on this team, you are responsible for working with your team to set the vision and roadmap, delivering on it, launching new functionality, and increasing the impact of the team." Also "This role requires: being technical to understand how our analytics system works and its constraint being analytical to be able to define how to show data as well as debugging issues and edge cases being customer obsessed to understand what information app developers need for their decisions and how we can provide this information to them having an understanding of the app ecosystem, how the economics of app businesses work, and what success means for app developers". We need to include these. We should incorporate them into About the role paragraph or maybe responsibilities. Let's craft About the role paragraph that includes all that. We'll produce:

    About the role

    RevenueCat gives app businesses the infrastructure and tools to build, run, and improve their monetization. Since graduating from YC's S18 batch, we've grown into the default monetization platform for mobile. We're in 50%+ of newly shipped subscription apps, we process $16B+ in annual purchase volume, and we help everyone from a solo developer to the OpenAI mobile team understand and grow their revenue. We're a remote-first team of 150+ people across 25+ countries, guided by values we actually practice: Customer Obsession, Always Be Shipping, Own It, and Balance. This isn't the right fit for everyone. The systems you’ll build here manage billions of dollars and touch hundreds of millions of end users, and we don’t take that lightly. You'll be expected to work hard and hold a high bar for what you ship, alongside some of the sharpest, most driven people you've worked with. If that sounds energizing rather than exhausting, keep reading.

    We're looking for a Senior Product Manager to join the team working on analytics features in RevenueCat. RevenueCat is the monetization engine for 40% of new subscription apps shipped — and the number of apps shipped is growing exponentially. We are uniquely positioned not only to give individual developer impactful information into the performance of their own apps, but also deliver truly unique data and insight given our position in the market; we know what good looks like, and we can not only put numbers in context, but give specific recommendations on metrics to target, experiments to run and anomalies to investigate. Our analytics features help app developers make better decisions that improve the monetization of their apps. As product manager on this team, you are responsible for working with your team to set the vision and roadmap, delivering on it, launching new functionality, and increasing the impact of the team. This role requires: being technical to understand how our analytics system works and its constraints, being analytical to be able to define how to show data as well as debugging issues and edge cases, being customer obsessed to understand what information app developers need for their decisions and how we can provide this information to them, having an understanding of the app ecosystem, how the economics of app businesses work, and what success means for app developers. You will oversee all of the Analytics features at RevenueCat — our charts, benchmarking, dashboard, and predictive LTV. You'll partner directly with leadership, collaborate across engineering and data teams, and act as the primary driver for how our customers understand and grow their revenue.

    That covers About the role. Now Responsibilities: we already have list from "What You'll Do". Also include earlier bullet points like "Own the product strategy and roadmap for RevenueCat's Analytics products." etc. We'll combine. Let's extract responsibilities from "What You'll Do" section: - Own the product strategy and roadmap for RevenueCat's Analytics products. - Be obsessed with your customers. - You will triage and investigate complex data and analytics problems deeply, instead of fully delegating to engineering. - Dig deep to understand what developers really want — distill signal from noise and good ideas from bad ones. - Recommend, develop and maintain new benchmarks and metrics that deliver value to our developers, and help them make more money. - Be the go-to person when a number looks off. - Set the vision. Create a plan that is cohesive, intentional, and impactful. Break that down into meaningful chunks on a reasonable timeline. Get it done. - Collaborate closely with engineering, data science, and GTM teams to bring robust analytics and experimentation tools to market. Also earlier: "You will oversee all of the Analytics features at RevenueCat — our charts, benchmarking, dashboard, and predictive LTV." maybe part of responsibilities. We'll include that as a responsibility. Now Requirements: maybe we can treat as "Requirements" the hard requirements: 5+ years experience, analytical, SQL, etc. But we already have Skills section for those. However the instruction says we can have both Requirements and Qualifications sections. We'll allocate: Requirements: mandatory experience/skills. Qualifications: values and abilities. But we also have Skills section separate. Could combine Requirements and Skills? The instruction list includes both Requirements and Skills as possible headings. We need to decide what goes where. We could put:

    Requirements

    • 5+ years of product management or adjacent experience, with meaningful time shipping complex products.
    • Analytical; proficient in SQL (or similar tools); love diving deep into data.
    • Experienced in

Similar jobs