Engineering Manager, Digital Assets

We need to output HTML fragment with sections: About the role? Actually the posting includes description paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse the posting. Let's extract: - About the role: The first paragraph: "At Ripple, we’re building a world where value moves like information does today..." That's about the company and role. Could be "About the role". We'll include. - Responsibilities: The "What You'll Do" bullet list. We'll put under

Responsibilities

with

• each bullet. - Requirements: The "What You Bring" list. That's requirements/qualifications. Could be Requirements or Qualifications. We'll decide: Use Requirements for mandatory, Qualifications for nice-to-have? The spec says we can have sections Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what to include. We have "What You Bring" with mandatory items: 7+ years..., Over 2 years..., Demonstrated ability..., Production background..., Comfort..., Strong communication..., Hands-on leadership orientation... That's requirements. Then "Nice to Have" list: deep familiarity..., Experience with XRP..., Background..., Experience integrating..., Familiarity with regulatory... Those could be Qualifications or Skills. We could put them under Qualifications. Skills: maybe we could extract specific skills: .NET, Angular/React, etc. But we already have them in requirements. Could create a Skills section for technical skills: .NET, Angular/React, etc. But we need to avoid thin sections. Might combine. Pay: The posting includes "CA Annual Base Salary Range: $212,000 USD - $265,000 USD". That's pay info. So we include Pay section. Schedule: The posting mentions "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." That's schedule info. Also maybe remote/hybrid. So we can include Schedule. Benefits: The posting lists many benefits: "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", "R&R days", "Generous wellness reimbursement and weekly onsite & virtual programming", "Generous vacation policy", "Industry-leading parental leave policies. Family planning benefits.", "Catered lunches, fully-stocked kitchens with premium snacks/beverages, and plenty of fun events". Also "professional development budget". So we have benefits. Thus we can include Benefits section. We need to avoid boilerplate like EEO etc. Remove. We need to preserve all substantive information. Not invent or summarize away detail. So we need to include each bullet point as is. We must not repeat job title as heading. Not include Job ID. We must output only HTML fragment. Let's craft. Structure:

  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. The OpportunityThis solution does not yet exist. Corporate treasury teams must choose between old treasury platforms that fail to support digital assets and crypto-native tools that lack fundamental enterprise treasury elements. You will head the engineering effort to remove this choice by incorporating Ripple's digital asset abilities into the Ripple Treasury platform in close partnership with Ripple's core digital assets team.This is a greenfield role. You will join forces with a seasoned infrastructure engineer and a product lead, forming a team of up to four full-stack developers. The direction may change day-to-day as the team finds what works best. There is no guidebook and no comparable market solution. You will determine how digital assets fit into corporate treasury workflows — and through this, help establish a new category of enterprise software.

  But note there is a weird concatenation "The OpportunityThis solution". We'll keep as is. Better to split paragraphs logically. We'll keep as one paragraph maybe. Then Responsibilities:

  Responsibilities

  • Manage the engineering process for digital asset integration by building and designing systems that join Ripple's digital asset functions (XRP, RLUSD, tokenized assets, custody, cross-border settlement) with Ripple Treasury's enterprise platform.
  • Build and manage a group of up to four full-stack .NET developers, recruiting, mentoring, and developing engineers while staying actively involved in coding.
  • Ship working software daily — lead a fast-paced Kanban workflow where the team builds, presents, iterates, and adapts direction based on findings and collaborator feedback.
  • Work closely with Ripple's core digital assets team to grasp protocol capabilities, integration points, and roadmap alignment.
  • Design full-stack solutions spanning .NET backend services and Angular or React frontends, ensuring enterprise-grade reliability, security, and auditability.
  • Navigate ambiguity with confidence — make sound engineering decisions with incomplete information, course-correct quickly, and keep the team productive through rapid pivots.
  • Partner with product, compliance, and treasury domain experts to translate emerging requirements into shippable features that meet the needs of Fortune 500 CFOs and treasurers.
  • Define engineering practices for the team — establish coding standards, review processes, testing strategies, and deployment patterns appropriate for a fast-moving, pioneering effort.
  Requirements:

  Requirements

  • 7+ years of software engineering experience with a strong full-stack background in .NET and modern frontend frameworks (Angular, React, or equivalent)
  • Over 2 years of experience in leading engineering teams, encompassing recruitment, mentoring, and development of engineering groups
  • Demonstrated ability to ship software in fast-paced, ambiguous environments — you have built products where requirements were unclear or changing rapidly
  • Production background in fintech, digital assets, or blockchain — you have delivered systems managing actual financial transactions or digital asset activities
  • Comfort with pioneering work — you thrive when the playbook hasn't been written yet and find energy in defining new approaches
  • Strong communication and collaboration skills — ability to work closely with cross-functional partners including product managers, compliance teams, and external engineering teams
  • Hands-on leadership orientation — willingness and ability to write production code alongside your team, especially in the early stages of team building
  Qualifications (nice-to-have):

  Qualifications

  • Deep familiarity with blockchain protocols, digital asset custody, tokenization, or cross-border settlement systems
  • Experience with XRP Ledger, RLUSD, or Ripple's product ecosystem
  • Background in corporate treasury, treasury management systems, or enterprise financial software
  • Experience integrating traditional financial infrastructure with digital asset platforms
  • Familiarity with regulatory requirements for digital asset products in financial services
  Skills: maybe we could list specific technical skills: .NET, Angular, React, etc. But we already have them in requirements. Could create a Skills section for "Technical Skills" but might be thin. However we could include a Skills section that lists: .NET backend, Angular/React frontend, Kanban, etc. But we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we omit Skills section and incorporate skills into Requirements/Qualifications. But we have to use headings only when posting has real specific content. The posting does not have a separate "Skills" heading; it's embedded. So we should not create a Skills section unless there is explicit content. So we skip Skills. Benefits:

  Benefits

  • 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
  • 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
  • Professional development budget to support other modes of learning
  Pay:

  Pay

  CA Annual Base Salary Range: $212,000 USD - $265,000 USD

  Schedule:

  Schedule

  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.

  We should also maybe include the bi-weekly all-company meeting etc. That's also schedule/culture. Could add to schedule paragraph: "Bi-weekly all-company meeting - business updates and ask me anything style discussion with our Leadership Team". Also "We come together for moments that matter which include team offsites, team bonding activities, happy hours and more!" That's also schedule/culture. We'll include them. Thus schedule paragraph: combine. Let's craft schedule paragraph: "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!" Now ensure we didn't include boilerplate like EEO etc. We removed. Check for any repeated lines: The posting had "Benefits listed above are for full-time employees." That's a line we could include maybe as a note but it's minor. Could include as part of benefits? Might be considered boilerplate? It's a clarification. Might keep as a sentence in benefits paragraph. But we can drop as it's not substantive benefit. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This line is not boilerplate but it's a note. Could keep but it's minor. I'd include as a sentence in benefits: "Benefits listed above are for full-time employees." as a
• maybe. Add that. Now ensure we didn't invent or summarize away detail. We kept all bullet points. Check for any missing info: The "Opportunity" paragraph includes "This solution does not yet exist." etc. We included. Check for any mention of "We get to do the best work of our career and grow our skills surrounded by colleagues who have our backs." included. Check for "If you’re ready to see your impact and unlock incredible career growth opportunities, join us, and build real world value." included. Check for "The OpportunityThis solution does not yet exist." we kept as part of paragraph. Check for "This is a greenfield role." included. Check for "You will head the engineering effort..." included. Check for "You will join forces with a seasoned infrastructure engineer and a product lead, forming a team of up to