Account Manager, Loyalty & Rewards

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements (or Qualifications?), Benefits, Pay, etc. Must not repeat job title. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. Include only sections with real content. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Sections present: - About The Company (but we might not need a heading? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we must include About the Company, but we could include if there is content. However they said "Prefer a few substantive sections over many thin ones." The About The Company may be considered boilerplate? It's substantive but not required headings list. Might include as a section with heading "About the Company"? Not in list but could be okay. However they gave examples; not strict. Safer to include only those headings that have content: About the role, Responsibilities, Requirements (or Qualifications), Benefits, Pay. Also maybe Skills? The posting includes "WHAT YOU BRING" which is qualifications/requirements. Could map to Requirements or Qualifications. Also "NICE TO HAVE" could be Skills? But we can combine. We need to avoid filler like "commensurate with experience". Not present. We need to include Pay section: they gave Compensation Range: $135K - $165K. So include Pay heading with that. Benefits: they list many benefits: Unlimited time off, Flexible working, stipend for home workspace, health coverage, 401(k) match, equity plan, health and wellness stipend, in-office meals, team summits. So Benefits section. Schedule: Not mentioned explicitly. No schedule info. So omit Schedule. Responsibilities: from "WHAT YOU WILL DO:" list. So Responsibilities. Requirements/Qualifications: from "WHAT YOU BRING:" and "NICE TO HAVE". Could separate Required vs Preferred but we can combine into Requirements (maybe with subheadings?). But instruction: use

  for section headings; we can have multiple sections. Could have Requirements (required) and Preferred Skills (nice to have). But they said prefer few substantive sections over many thin ones. Could combine into one Requirements section with both required and nice-to-have as lists. We also have About The Role paragraph before WHAT YOU WILL DO. Could include that as part of About the role section. Thus sections: - About the role (includes intro paragraph about Uptop etc.) - Responsibilities (list of WHAT YOU WILL DO items) - Requirements (includes WHAT YOU BRING required and NICE TO HAVE) - Benefits (list of benefits) - Pay (compensation range) We need to ensure we don't repeat job title. Not needed. We must not include metadata like Job ID. We must output only HTML fragment, no /, no markdown fences. Let's craft. About the role: combine the paragraphs: "About The Role Uptop is one of the fastest-growing pieces of Rain's platform..." plus maybe the ethos? Actually ethos is under OUR ETHOS but that's about company. Could be part of About the Company. But we can ignore ethos as it's fluff but still substantive. Might include in About the Company section if we add. But we can skip to keep sections few. Better to include About the Company? Not required but could be included as a section heading "About the Company". However they didn't list that as example but it's okay. But they said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The e.g. implies those are examples, not exclusive. So we can add About the Company. But to keep few sections, maybe we combine About the Company into About the role? Not ideal. I'll include About the Company as a section. Thus sections: About the Company, About the role, Responsibilities, Requirements, Benefits, Pay. Now craft HTML. Use

  About the Company

  then

  ...

  with company description. Company description: "Rain is the global stablecoin payments platform for enterprises, neobanks, platforms, developers, and AI agents. Our technology allows partners to move, store, and use stablecoins instantly and compliantly through global payment cards, rewards, on/offramps, wallets, and cross-border rails. As both a Visa and Mastercard Principal Member, Rain issues cards that work at more than 175 million merchant locations in over 220 countries and territories. Built natively for stablecoins and trusted by more than 100 organizations worldwide, Rain delivers secure, scalable infrastructure that makes money move freely and instantly around the world. You will have the opportunity to deliver massive impact at a hypergrowth company backed by some of the top investors in fintech, crypto, and SaaS. In January 2026, we closed a $250M Series C led by ICONIQ, valuing Rain at $1.95B, with Sapphire Ventures, Dragonfly, Bessemer Venture Partners, Galaxy Ventures, FirstMark, Lightspeed, Norwest, and Endeavor Catalyst also participating. If you're curious, bold, and excited to help shape a borderless financial future, we'd love to talk. OUR ETHOS Operating at the epicenter of stablecoin innovation means moving fast and thinking globally. Our team reflects the diverse, international audiences we serve. We hire people who stay agile as the tide ebbs and flows, fix what's broken without waiting, chase trends before they peak, and remember to have fun through it all." We need to preserve all substantive info; we can keep that. Now About the role: combine paragraphs: "Uptop is one of the fastest-growing pieces of Rain's platform. Our sports and entertainment partners use our rewards infrastructure to launch loyalty programs that change how their fans spend — combining everyday earn mechanics with merchant-funded offers and premium redemption experiences that people actually want. Every one of those programs is a complex, cross-functional launch: program design, offer and merchant supply, technical integration, compliance review, marketing coordination, and a partner team that is often building a loyalty program for the first time. We're looking for an Account Manager to own that experience end to end. You will be the core interface between Rain and our partners from the moment a deal is signed — driving program design, coordinating launch, and then owning the relationship as the program scales. This is not a ticket-queue support role. You will run complicated, multi-month processes across many moving parts, hold the details that no one else is holding, and become the person our partners trust to get things done. You'll own a portfolio of roughly five enterprise programs, with room to grow to ten as the business scales. This role is based in New York City, reports to the GMs of Rain's rewards business, and works closely with our Product, Engineering, BD, and Compliance teams." Now Responsibilities: list from WHAT YOU WILL DO: each bullet. - Own the post-sale relationship for a portfolio of loyalty and rewards partners, from kickoff through launch and into ongoing growth - Translate a signed deal into a concrete program: earn structures, redemption catalogs, offer strategy, funding model, and success metrics - Run launch as a project manager would — build the plan, drive the timeline, chase down blockers, and keep every stakeholder honest about what's due and when - Serve as the single point of contact for partner teams, coordinating internally across Product, Engineering, BD, Compliance, and Marketing so partners get one clear answer instead of five - Lead recurring business reviews: report on program performance, surface insights on spend lift and engagement, and recommend changes that make the program work harder - Surface expansion opportunities within your accounts and hand them to BD with the context they need to run - Maintain accurate account documentation, launch trackers, and internal reporting so the state of every program is legible at a glance - Bring partner feedback back into Rain, and advocate for the roadmap changes that will make the next launch easier than the last Now Requirements: combine WHAT YOU BRING required and NICE TO HAVE. Required (WHAT YOU BRING): - 3–7 years in Account Management, Customer Success, Implementation, Partner Management, or Program Management — ideally in sports, fintech, payments, or loyalty - A track record of managing complex, multi-stakeholder programs to a deadline, with real ownership of the outcome - Exceptional attention to detail; you are the person on the team who catches the thing everyone else missed - Outstanding written and verbal communication, and genuine enjoyment of building relationships with partner teams - Comfort operating with ambiguity and without a playbook — you'd rather build the process than wait for one - Strong commercial instincts: you understand that a healthy account is one where the partner is getting measurable value - Fluency with the tools of the job (CRM, project tracking, spreadsheets) and comfort getting into data to answer your own questions - You won't carry a sales quota — BD is owned by a dedicated team — but if you want to contribute to business development or product, there's plenty of room to do it. Nice to have (NICE TO HAVE, BUT NOT MANDATORY): - Direct experience with loyalty, rewards, card-linked offers, or experiential/fan engagement programs - Understanding of card payments economics — interchange, merchant funding, program P&L - Experience working with fintechs, neobanks, issuers, or card program managers - Experience coordinating with brand, entertainment, or merchant partners - Familiarity with stablecoins, crypto, or digital assets We can combine into one list with headings? But we must use
  • for any list. Could have two lists: one for Required, one for Nice to have, each preceded by a

    maybe. But we can't have headings inside the list; we could have a

    preceding each list. That's okay. Now Benefits: list from THINGS THAT ENABLE A FULFILLING, HEALTHY, AND HAPPY EXPERIENCE AT RAIN: - Unlimited time off 🌴 Unlimited vacation can be daunting, so we require Rainmakers to take 10 days minimum for themselves. - Flexible working ☕ We support a flexible workplace – work from home, come into an office, or both. We want everyone to work in an environment where they're their most confident and productive selves. - New Rainmakers receive a stipend to set up a comfortable home workspace. - Easy to access benefits 🧠 For US Rainmakers, we cover 95% of your health, dental, and vision plan costs and 90% for your dependents, plus a 100% company-subsidized life insurance plan. - Retirement goals 💡 Plan for the future with confidence. We offer a 401(k) with a 4% company match. - Equity plan 📦 Every Rainmaker gets an equity option plan so we all benefit from our success. - Health and Wellness 📚 High performance begins from within. Rainmakers receive a monthly stipend to be used for eligible health and wellness spending like gym memberships/fitness classes, massages, acupuncture - whatever recharges you! - In-office meals 🍜 Rainmakers working from the office enjoy lunch and dinner on us, covered with a DoorDash credit. - Team summits ✨ Summits play an important role at Rain. Time together helps us build relationships and a common destiny. Expect team and company offsites, both domestic and international. We need to preserve the emojis? They are part of text; we can keep