Role Summary

We have been running PostHog for a few months and have real event data flowing across all six platforms. What the setup is missing is a dedicated owner — someone who guards the event taxonomy, digs into the data unprompted, and turns it into a clear case for what we should change, and why. As the first dedicated product analytics hire, you will define how this function works rather than inherit it. You will not run a reporting service desk. Your output is decisions,

not dashboards, measured on two outcomes: revenue (subscription conversion, renewals, payment success) and user experience (friction removed, journeys shortened, confusion eliminated).

Key Responsibilities

Drop-off Analysis

- Map every meaningful journey on every platform and find the exact step where users leave: onboarding, login and signup, search, content discovery, playback start, and the subscription funnel
- Own the subscription funnel end to end — app open → paywall viewed → plan selected → payment initiated →payment success — split by platform, geography and payment method
- For every drop-off found, report how many users and how much revenue it costs, why it's happening, and what specifically should change
- Distinguish a genuine UX problem from a tracking artefact, a platform-specific bug, or a payment-gateway failure, and route each to the right team
- Analyse payment failures and retry behaviour alongside the payments team
- Track whether each recommended fix moved the number, and report plainly if it didn't

Retention, Churn & Cohorts

- Build and maintain retention and cohort views — day-1/7/30, trial-to-paid, renewal and cancellation
- Identify first-session and first-week behaviours that predict a subscriber sticking around, and recommend how to engineer more of them

Content & Programming Analytics

- Report on content performance — tray impressions and clicks,



play starts, completion rates, drop-off curves, and search behaviour
- Feed insights back to the programming team on what to promote, tray order, and whether an underperforming release was a content or merchandising issue
- Support the internal Programming Analyst tooling built on top of PostHog

Experimentation

- Set up and read A/B tests and feature-flag rollouts in PostHog — paywall variants, onboarding flows, tray layouts
- Define success metrics and guardrail metrics up front, and call results honestly, including flat ones

Reporting Rhythm

- Run a weekly product metrics review that people actually read, and a monthly deep dive on one problem area of your choosing
- Deliver release-impact analysis after every major app release

Must-Have Qualifications

- 4–6 years in product analytics, growth analytics, or data analysis on a consumer (B2C) product — app or web, including experience mentoring or setting standards for others
- Hands-on ownership of a product analytics tool (PostHog, Mixpanel, Amplitude, CleverTap or similar) — has defined events, built funnels, and debugged bad data, not just consumed dashboards someone else built
- Demonstrated ability to find drop-offs and act on them, with a concrete example of a funnel fixed, what was found, what changed, and what it was worth
- Solid grasp of funnels, cohorts, retention curves and segmentation, and the judgement to know when a number is real versus a tracking artefact
- Comfortable working with AI tooling day to day — specifically the PostHog MCP server with Claude — and able to get MCP running within a week if current to it
- Willing to check the data and then take a decision: form a view, recommend it clearly, and own the outcome
- Able to write a clear recommendation — what the data says, what to do about it, and how confident to be
- Self-directed, arriving with questions rather than waiting for answers

📌 Senior Product Analyst (India)
🏢 Hoichoi
📍 India