Staff Data Scientist - Core Revenue Retention

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, maybe Benefits? There's a salary range given: "$163,400 - $220,000 a year". That's Pay. So we need a Pay section. Also maybe Benefits? Not mentioned. So only include sections with real content: About the role, Responsibilities, Requirements, Pay. Also maybe "Nice to Have" could be part of Requirements? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We have "Nice to Have" but not a standard heading; we could incorporate into Requirements or maybe a separate "Qualifications"? But we should not create sections without real content. The posting includes "Nice to Have:" list. That's substantive. Could treat as part of Requirements or maybe a separate "Qualifications" heading. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have a "Qualifications" section containing both Requirements and Nice to Have? But they'd be separate lists. Better to have Requirements and Nice to Have as subheadings? Not allowed. Could combine into Requirements with both required and nice-to-have items? Might lose nuance. Could create a "Qualifications" section and put both required and nice-to-have there, maybe separate lists with headings inside? But only allowed headings are those listed; we cannot add custom headings like "Nice to Have". Could embed nice-to-have as a

note? Might be okay to include within Requirements as a separate

with a note? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings. We have content for About the role, Responsibilities, Requirements, Pay. Also we have "Nice to Have" which could be considered part of Requirements or Qualifications. Since we have a Requirements heading, we could put required items under that, and nice-to-have maybe as a separate

after the list? But that might be considered filler? Better to include nice-to-have under Requirements as a separate list with a preceding note like "Nice to have:" inside a

then a

. That preserves info. We must not include boilerplate like EEO, AI tools, privacy, etc. Also remove duplicated lines, navigation, etc. We need to preserve all substantive information: About HighLevel description? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About HighLevel section is part of the job posting but not under a heading. Should we include it? The instruction says we should not repeat the job title as a heading, but we can include other content. The About HighLevel is descriptive about company; it's substantive. Should we include it? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't say to strip the About HighLevel. It said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About HighLevel is not boilerplate; it's company overview. So we should include it, maybe as a

before the About the role heading? Or we could put it under a heading like "About HighLevel"? Not in allowed headings list. But we could just put it as a

before the About the role heading. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. Probably we should only use those headings for sections we create; other content can be in

. So we can have a

with the About HighLevel paragraph(s). Then

About the role

etc. We must not include the job title as a heading; the job title is "Staff Data Scientist, Core Revenue Retention". Not to be used as heading. We must not put Job ID/requisition numbers as headings; none present. We must not include sections like Benefits, Schedule unless present. Not present. We must not include filler like "commensurate with experience". Not present. Now craft HTML. We need to include About HighLevel text: It's a few paragraphs. Let's copy: "About HighLevel: HighLevel is an AI-powered business operating system that gives agencies, entrepreneurs and SMBs the infrastructure to build, automate and scale. Today, HighLevel supports SMBs across 150+ countries, fueling community-driven growth rooted in real customer outcomes. To date, businesses operating on HighLevel have generated over $7 billion in ecosystem value, demonstrating the impact of shared infrastructure at scale. By centralizing conversations, automation and intelligence into one system, we help businesses move faster, reduce complexity and execute efficiently. Behind the platform, HighLevel powers more than 4 billion API hits and 2.5 billion message events daily. With 250 terabytes of distributed data, 250+ microservices and over 1 million domain names supported, our architecture is built for performance, resilience and long-term scalability. Our People With over 2,000 team members across 10+ countries, HighLevel operates as a global, remote-first organization built for speed and ownership. We value initiative, clarity and execution, creating space for ambitious people to build systems that support millions of businesses worldwide. Here, innovation thrives, ideas are celebrated and people come first, no matter where they call home. Our Impact Every month, HighLevel enables more than 1.5 billion messages, 200 million leads and 20 million conversations for the more than 1 million businesses we support. Behind those numbers are real people building independence, expanding opportunity and creating measurable impact. We’re proud to be a part of that. Learn more about us on our YouTube Channel or Blog Posts ." We need to preserve all that. Might be long but okay. Now About the role section: copy the paragraph after "About the Role:" until before "Responsibilities:". Let's extract: "We're hiring a Staff Data Scientist, Core Revenue Retention to own one outcome — keeping and growing revenue from existing customers — across every team that shapes it. Revenue retention isn't the property of a single product: it spans CPaaS (phone, SMS, email, WhatsApp) as our largest MRR surface, add-on monetization including emerging AI features, the Customer Success motions that protect accounts, and Finance's forecasts. This is a broad, cross-functional role. You'll work closely with Communications/CPaaS, Customer Success, the AI teams pursuing add-on revenue, Finance, and other revenue-driving product teams; you report centrally to Product Analytics & Data Science for craft and standards and carry the revenue-retention outcome across organizational boundaries. You'll build the retention/value model, separate real churn signal from data-maturity and mix artifacts, and turn diagnosis into a prioritized, evidence-based retention and add-on-monetization agenda. You'll work amid a data foundation still being built, consuming governed sources rather than rebuilding them, and raising the bar as you go. This is a hands-on, direction-setting Staff role — you advise Customer Success, Finance, and CPaaS leaders and set retention-measurement standards that analysts on adjacent teams adopt, with a path to grow a pod as the mandate scales." Now Responsibilities: list bullet points after "Responsibilities:" until before "Requirements:". Let's capture each bullet: - Own the causal read on core revenue retention and add-on monetization — gross and net revenue retention, MRR churn (voluntary vs involuntary), attach and usage of add-ons — across CPaaS, AI add-ons, and other revenue surfaces - Quantify add-on revenue opportunity across CPaaS and emerging AI features, and the drivers behind attach and consumption - Apply rigorous causal inference (matching, diff-in-diff, survival/hazard, synthetic control) where clean experiments aren't feasible — separating real signal from selection bias, seasonality, and mix - Partner with Finance/RevOps on single-source-of-truth definitions and forecasting inputs; drive the revenue-retention insights - Partner with the Product Strategy & Growth org on the TTP/churn charter, and with the Experimentation lead to test retention interventions rigorously - Act as a trusted analytical advisor to Customer Success, Finance, and Communications/CPaaS leaders, and set the analytical standards that DS and analysts on adjacent teams adopt — raising the bar without direct authority - Set the technical direction for how revenue retention is measured company-wide — own the canonical GRR/NRR, churn, and add-on metrics on governed, certified data that other teams build on; shape the taxonomy retention analytics depends on with Analytics Engineering - Build the retention and causal-inference framework — the standards and reusable methods (survival/hazard, diff-in-diff, synthetic control) that Analytics Engineering and adjacent DS teams reuse beyond this mandate - Use AI tooling (Claude and similar) to move faster on exploration, documentation, and analysis Now Requirements: after "Requirements:" until before "Nice to Have:". List: - 9+ years in revenue/retention analytics, data science, or applied statistics, with deep experience on churn, retention, and monetization - Practical causal inference with sound judgment about when a result is causal vs. an artifact of how the data was generated - Comfort untangling messy financial/billing/usage data and defining metrics that survive scrutiny from Finance and product alike - Strong SQL and working proficiency in Python; comfort in a Snowflake + dbt environment - Track record where a retention or monetization diagnosis changed a product, pricing, CS, or lifecycle decision - Comfort amid imperfect, in-progress data — you consume governed sources and raise the bar rather than rebuilding pipelines - Cross-functional influence — you align product, Customer Success, Finance, and leadership on shared numbers without direct authority Nice to Have: after that until before "Success in this role looks like:". List: - CPaaS (telephony/messaging) or usage-based/consumption revenue experience - B2B SaaS or CRM background; experience with MRR/subscription billing, dunning, and involuntary-churn recovery - Familiarity with Statsig or a comparable experimentation platform - Exposure to AI-assisted analytics workflows; experience mentoring analysts Success in this role looks like: bullet points until before "$163,400 - $220,000 a year". List: - CPaaS, AI add-ons, and Customer Success act on your model, and drives strong positive business results. - Finance/RevOps and Product Analytics report the consistent metrics with clear insight and recommendations. - Leaders across the revenue domain make roadmap and spend calls off your analysis, not gut feel - The revenue-retention mandate has reusable patterns and the foundation to scale beyond one IC Then Pay: "$163,400 - $220,000 a year". We'll put under

Pay

with a

. We should not include the EEO statement etc. Now produce HTML. We'll wrap About HighLevel in

maybe multiple

but we can keep as one

with line breaks? Better to split into paragraphs for readability but not required. We'll keep as

with the text. Then

About the role

...

Then

Responsibilities

with each
• . Then

  Requirements

  for required items, then maybe a

  for Nice to have heading? But we cannot create a heading. Could add a

  Nice to have:

  then
  . That's okay as it's not a heading. Or we could