Senior Data Scientist
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate etc.
We need to parse the job posting.
Content:
- Intro paragraph about Ripple (repeated). That's about the company, maybe "About the role"? Actually "About the role" could be the description of the role. The posting includes "The work:" then description. Also "What you’ll do:" list of responsibilities. Then "What you'll bring:" list of qualifications/requirements. Then salary info for NY. Then benefits description under "WHO WE ARE:" sections: "Do Your Best Work", "Take Control of Your Finances", "Take Care of Yourself". Those are benefits and culture.
We need to produce sections: maybe "About the role" (intro), "Responsibilities" (What you’ll do), "Requirements" or "Qualifications" (What you'll bring), "Benefits" (benefits listed), "Pay" (salary range). Possibly "Schedule" not present (no schedule info). So omit Schedule.
We must not repeat job title as heading. No Job ID.
We must not include boilerplate like EEO, privacy notices, etc.
We need to preserve all substantive information; do not invent or summarize away detail. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which content goes where.
Let's extract:
Intro: "At Ripple, we’re building a world where value moves like information does today. It’s big, it’s bold, and we’re already doing it. Through our crypto solutions for financial institutions, businesses, governments and developers, we are improving the global financial system and creating greater economic fairness and opportunity for more people, in more places around the world. And we get to do the best work of our career and grow our skills surrounded by colleagues who have our backs. If you’re ready to see your impact and unlock incredible career growth opportunities, join us, and build real world value."
That's duplicated twice in posting but we should include once.
That's about the company and role; could be "About the role" or maybe "About Ripple". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" heading for that intro.
Then "The work:" paragraph: "We're looking for a Senior Data Scientist to drive analytics across Ripple's product and business portfolio. You'll build the scientific frameworks teams use to evaluate product and business performance, and use AI tooling to accelerate the speed and reach of your analysis.In this role, you'll partner with product and business leads to frame the right questions, bring rigor to how they're answered, and make sure decisions rest on a consistent, thorough foundation. You'll take on ambiguous, high-impact problems, build analyses and tooling others can reuse, and raise the analytical bar of the teams you work with."
That could be part of responsibilities or overview. Might fit under "About the role" as well, but we already have intro. Could also be part of responsibilities. However we have a separate "What you’ll do:" list which is more detailed responsibilities. So maybe we keep the "The work:" as a brief overview under About the role.
Then "What you’ll do:" bullet list (actually sentences each starting with a capital). We need to turn each into
- . The list:
- Serve as the data science lead for one or more product or business areas — Payments, Stablecoin, or Custody — applying strong methodology and tackling the hardest analytical problems in your domain.
- Partner with product and business leads to shape roadmap decisions: which initiatives to prioritize, what success looks like, and how we'll measure it.
- Build the scientific frameworks your teams rely on: product and network health metrics, causal inference approaches, and forecasting that holds up across institutional and developer surfaces.
- Apply AI to accelerate analytics — using LLMs and agentic workflows to scale insight generation, automate routine analysis, and make data more self-serve for non-DS partners.
- Drive evidence-based evaluation of growth across customers, corridors, and on-chain activity, surfacing the causal drivers behind adoption and volume.
- Define and communicate the metrics your teams and leadership run on, translating complex results into clear narratives for senior stakeholders.
- Raise the bar for the DS function through mentorship and by modeling strong analytical practice for the data scientists around you.
That's responsibilities.
Then "What you'll bring:" list:
- 7+ years in data science or quantitative analysis, with a track record of measurable impact on product and business decisions.
- Experience as the data science partner to cross-functional teams, shaping roadmaps and helping leaders make better-informed calls.
- Track record designing analytics and measurement frameworks that other teams adopt and build on.
- Hands-on experience applying AI to accelerate analytics workflows — agentic analysis, AI-assisted insight generation, natural-language data interfaces.
- Strong expertise in experimentation, causal inference, forecasting, and statistical modeling.
- Expertise in Python or R, fluency in SQL, and experience with large-scale data tech (Databricks).
- Experience with FinTech, payments, crypto, or blockchain data is a strong plus.
- Advanced degree (MS, PhD) in a quantitative field preferred.
- Excellent communication skills — able to translate technical depth into clear narratives for senior stakeholders.
These are qualifications/requirements. Could be under "Requirements" or "Qualifications". We'll pick "Requirements" heading.
Then salary: "For positions that will be based in NY, the annual salary range for this position is below. Actual salaries may vary based on numerous factors including, among other things, an individual applicant’s experience and qualifications for the position. This range does not include equity or additional compensation, such as bonuses or commissions. NY Annual Base Salary Range: $164,000 USD - $205,000 USD"
We need a Pay section with that info. Use
for prose.
Then benefits: Under "WHO WE ARE:" there are subheadings: "Do Your Best Work", "Take Control of Your Finances", "Take Care of Yourself". Each contains bullet points (some are sentences). We need to extract benefits.
Let's parse:
"Do Your Best Work"
- The opportunity to build in a fast-paced start-up environment with experienced industry leaders
- A learning environment where you can dive deep into the latest technologies and make an impact.
- A professional development budget to support other modes of learning.
- Thrive in an environment where no matter what race, ethnicity, gender, origin, or culture they identify with, every employee is a respected, valued, and empowered part of the team.
- In-office collaboration for moments that matter is important to our culture, and we give managers and teams the flexibility to decide which 10+ days a month they come in.
- Bi-weekly all-company meeting - business updates and ask me anything style discussion with our Leadership Team
- We come together for moments that matter which include team offsites, team bonding activities, happy hours and more!
"Take Control of Your Finances"
- Competitive salary, bonuses, and equity
- Competitive benefits that cover physical and mental healthcare, retirement, family forming, and family support
- Employee giving match
- Mobile phone stipend
"Take Care of Yourself"
- R&R days so you can rest and recharge
- Generous wellness reimbursement and weekly onsite & virtual programming
- Generous vacation policy - work with your manager to take time off when you need it
- Industry-leading parental leave policies. Family planning benefits.
- Catered lunches, fully-stocked kitchens with premium snacks/beverages, and plenty of fun events
- Benefits listed above are for full-time employees.
We need to output a Benefits section with these items as list items. Should we separate into subcategories? The instruction says use
- for any list of duties/requirements/benefits. So we can just flatten all benefit items into a single list under Benefits heading. Or we could keep subheadings but they'd be headings not allowed? Only allowed headings are the specified ones; we could still use
for subheadings but not in list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but better to stick to those. We can just have a Benefits section with a list.
We must not include boilerplate like "Ripple is an Equal Opportunity Employer..." etc. So omit that.
Also remove duplicated lines.
Now construct HTML:
About the role
At Ripple, we’re building a world where value moves like information does today. It’s big, it’s bold, and we’re already doing it. Through our crypto solutions for financial institutions, businesses, governments and developers, we are improving the global financial system and creating greater economic fairness and opportunity for more people, in more places around the world. And we get to do the best work of our career and grow our skills surrounded by colleagues who have our backs. If you’re ready to see your impact and unlock incredible career growth opportunities, join us, and build real world value.
We're looking for a Senior Data Scientist to drive analytics across Ripple's product and business portfolio. You'll build the scientific frameworks teams use to evaluate product and business performance, and use AI tooling to accelerate the speed and reach of your analysis. In this role, you'll partner with product and business leads to frame the right questions, bring rigor to how they're answered, and make sure decisions rest on a consistent, thorough foundation. You'll take on ambiguous, high-impact problems, build analyses and tooling others can reuse, and raise the analytical bar of the teams you work with.
Then Responsibilities:
Responsibilities
- Serve as the data science lead for one or more product or business areas — Payments, Stablecoin, or Custody — applying strong methodology and tackling the hardest analytical problems in your domain.
- Partner with product and business leads to shape roadmap decisions: which initiatives to prioritize, what success looks like, and how we'll measure it.
- Build the scientific frameworks your teams rely on: product and network health metrics, causal inference approaches, and forecasting that holds up across institutional and developer surfaces.
- Apply AI to accelerate analytics — using LLMs and agentic workflows to scale insight generation, automate routine analysis, and make data more self-serve for non-DS partners.
- Drive evidence-based evaluation of growth across customers, corridors, and on-chain activity, surfacing the causal drivers behind adoption and volume.
- Define and communicate the metrics your teams and leadership run on, translating complex results into clear narratives for senior stakeholders.
- Raise the bar for the DS function through mentorship and by modeling strong analytical practice for the data scientists around you.
Then Requirements:
Requirements
- 7+ years in data science or quantitative analysis, with a track record of measurable impact on product and business decisions.
- Experience as the data science partner to cross-functional teams, shaping roadmaps and helping leaders make better-informed calls.
- Track record designing analytics and measurement frameworks that other teams adopt and build on.
- Hands-on experience applying AI to accelerate analytics workflows — agentic analysis, AI-assisted insight generation, natural-language data interfaces.
- Strong expertise in experimentation, causal inference, forecasting, and statistical modeling.
- Expertise in Python or R, fluency in SQL, and experience with large-scale data tech (Databricks).
- Experience with FinTech, payments, crypto, or blockchain data is a strong plus.
- Advanced degree (MS, PhD
for prose. We need to decide which content goes where. Let's extract: Intro: "At Ripple, we’re building a world where value moves like information does today. It’s big, it’s bold, and we’re already doing it. Through our crypto solutions for financial institutions, businesses, governments and developers, we are improving the global financial system and creating greater economic fairness and opportunity for more people, in more places around the world. And we get to do the best work of our career and grow our skills surrounded by colleagues who have our backs. If you’re ready to see your impact and unlock incredible career growth opportunities, join us, and build real world value." That's duplicated twice in posting but we should include once. That's about the company and role; could be "About the role" or maybe "About Ripple". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" heading for that intro. Then "The work:" paragraph: "We're looking for a Senior Data Scientist to drive analytics across Ripple's product and business portfolio. You'll build the scientific frameworks teams use to evaluate product and business performance, and use AI tooling to accelerate the speed and reach of your analysis.In this role, you'll partner with product and business leads to frame the right questions, bring rigor to how they're answered, and make sure decisions rest on a consistent, thorough foundation. You'll take on ambiguous, high-impact problems, build analyses and tooling others can reuse, and raise the analytical bar of the teams you work with." That could be part of responsibilities or overview. Might fit under "About the role" as well, but we already have intro. Could also be part of responsibilities. However we have a separate "What you’ll do:" list which is more detailed responsibilities. So maybe we keep the "The work:" as a brief overview under About the role. Then "What you’ll do:" bullet list (actually sentences each starting with a capital). We need to turn each into
for prose. Then benefits: Under "WHO WE ARE:" there are subheadings: "Do Your Best Work", "Take Control of Your Finances", "Take Care of Yourself". Each contains bullet points (some are sentences). We need to extract benefits. Let's parse: "Do Your Best Work" - The opportunity to build in a fast-paced start-up environment with experienced industry leaders - A learning environment where you can dive deep into the latest technologies and make an impact. - A professional development budget to support other modes of learning. - Thrive in an environment where no matter what race, ethnicity, gender, origin, or culture they identify with, every employee is a respected, valued, and empowered part of the team. - In-office collaboration for moments that matter is important to our culture, and we give managers and teams the flexibility to decide which 10+ days a month they come in. - Bi-weekly all-company meeting - business updates and ask me anything style discussion with our Leadership Team - We come together for moments that matter which include team offsites, team bonding activities, happy hours and more! "Take Control of Your Finances" - Competitive salary, bonuses, and equity - Competitive benefits that cover physical and mental healthcare, retirement, family forming, and family support - Employee giving match - Mobile phone stipend "Take Care of Yourself" - R&R days so you can rest and recharge - Generous wellness reimbursement and weekly onsite & virtual programming - Generous vacation policy - work with your manager to take time off when you need it - Industry-leading parental leave policies. Family planning benefits. - Catered lunches, fully-stocked kitchens with premium snacks/beverages, and plenty of fun events - Benefits listed above are for full-time employees. We need to output a Benefits section with these items as list items. Should we separate into subcategories? The instruction says use
- for any list of duties/requirements/benefits. So we can just flatten all benefit items into a single list under Benefits heading. Or we could keep subheadings but they'd be headings not allowed? Only allowed headings are the specified ones; we could still use
for subheadings but not in list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but better to stick to those. We can just have a Benefits section with a list. We must not include boilerplate like "Ripple is an Equal Opportunity Employer..." etc. So omit that. Also remove duplicated lines. Now construct HTML:
About the role
At Ripple, we’re building a world where value moves like information does today. It’s big, it’s bold, and we’re already doing it. Through our crypto solutions for financial institutions, businesses, governments and developers, we are improving the global financial system and creating greater economic fairness and opportunity for more people, in more places around the world. And we get to do the best work of our career and grow our skills surrounded by colleagues who have our backs. If you’re ready to see your impact and unlock incredible career growth opportunities, join us, and build real world value.
We're looking for a Senior Data Scientist to drive analytics across Ripple's product and business portfolio. You'll build the scientific frameworks teams use to evaluate product and business performance, and use AI tooling to accelerate the speed and reach of your analysis. In this role, you'll partner with product and business leads to frame the right questions, bring rigor to how they're answered, and make sure decisions rest on a consistent, thorough foundation. You'll take on ambiguous, high-impact problems, build analyses and tooling others can reuse, and raise the analytical bar of the teams you work with.
Then Responsibilities:Responsibilities
- Serve as the data science lead for one or more product or business areas — Payments, Stablecoin, or Custody — applying strong methodology and tackling the hardest analytical problems in your domain.
- Partner with product and business leads to shape roadmap decisions: which initiatives to prioritize, what success looks like, and how we'll measure it.
- Build the scientific frameworks your teams rely on: product and network health metrics, causal inference approaches, and forecasting that holds up across institutional and developer surfaces.
- Apply AI to accelerate analytics — using LLMs and agentic workflows to scale insight generation, automate routine analysis, and make data more self-serve for non-DS partners.
- Drive evidence-based evaluation of growth across customers, corridors, and on-chain activity, surfacing the causal drivers behind adoption and volume.
- Define and communicate the metrics your teams and leadership run on, translating complex results into clear narratives for senior stakeholders.
- Raise the bar for the DS function through mentorship and by modeling strong analytical practice for the data scientists around you.
Requirements
- 7+ years in data science or quantitative analysis, with a track record of measurable impact on product and business decisions.
- Experience as the data science partner to cross-functional teams, shaping roadmaps and helping leaders make better-informed calls.
- Track record designing analytics and measurement frameworks that other teams adopt and build on.
- Hands-on experience applying AI to accelerate analytics workflows — agentic analysis, AI-assisted insight generation, natural-language data interfaces.
- Strong expertise in experimentation, causal inference, forecasting, and statistical modeling.
- Expertise in Python or R, fluency in SQL, and experience with large-scale data tech (Databricks).
- Experience with FinTech, payments, crypto, or blockchain data is a strong plus.
- Advanced degree (MS, PhD