Deputy Treasurer

We need to output HTML fragment with sections: About the role? The posting includes "About MoonPay", "About The Opportunity", "What You Will Do", "About You", "Salary", "Benefits & Perks". Also maybe "About MoonPay" is not a heading per list: headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. We should not repeat job title. We need to include sections only when posting has real specific content. We have content for About the role? The posting includes "About MoonPay" and "About The Opportunity". That could map to "About the role". We'll combine that into About the role section. Responsibilities: "What You Will Do" is responsibilities. Requirements/Qualifications/Skills: "About You" includes experience, skills. Could split into Requirements and Qualifications and Skills. But we can combine into Requirements maybe. However we need to avoid thin sections. Could have Requirements (experience) and Skills (specific skills). But we have both experience and skills listed. Might be better to have Requirements (experience) and Skills (specific skills). Qualifications maybe similar to Requirements. To avoid many thin sections, we could have one "Requirements" covering experience and qualifications, and maybe a "Skills" for specific skill items. But the list includes many bullet-like sentences. We'll decide: Use "Requirements" for experience and qualifications, and "Skills" for specific skill areas (like digital asset treasury operations, liquidity and capital management, etc). However the content overlaps. Simplify: Use "Requirements" for the experience and qualifications, and "Skills" for the skill-based bullet points. But we need to ensure we don't create empty sections. We also have Pay: Salary range given. So we need a Pay section with that. Benefits: Benefits & Perks list. Schedule: Not mentioned; we have hybrid working schedule mentioned under Benefits & Perks. Could we create Schedule section? The posting mentions "Hybrid working schedule: work fully remotely or from your nearest Moonbase". That's schedule info. According to rule, we should create Schedule section only if posting actually states them. It does state hybrid working schedule. So we can create a Schedule section with that detail. However the benefit list also includes hybrid working schedule; we could move it to Schedule and keep Benefits for other perks. But we must not duplicate. We'll extract hybrid working schedule into Schedule section. Thus sections: - About the role (h3) containing About MoonPay and About The Opportunity paragraphs. - Responsibilities (h3) containing What You Will Do paragraphs (maybe multiple paragraphs). - Requirements (h3) containing About You experience/qualifications paragraphs. - Skills (h3) containing specific skill bullet points from About You (maybe list). Could also combine with Requirements but okay. - Pay (h3) containing Salary range. - Benefits (h3) containing benefits list (excluding hybrid working schedule). - Schedule (h3) containing hybrid working schedule. We must not include boilerplate like cookie/navigation/legal/EEO etc. Remove duplicated lines like the research about women etc repeated twice. We should keep only one instance? The instruction: remove duplicated lines. So we should keep only one occurrence of that research note. It appears twice: once after About MoonPay paragraph, and again after About You. We'll keep one instance maybe after About You? But it's basically a note encouraging applications. It's not boilerplate? It's a statement about diversity. It's not cookie/legal/EEO? It's more like an encouragement note. It's not explicitly listed as boilerplate to remove, but it's a duplicated line. We'll keep one copy. Also remove the line about AI tools in hiring process etc (that's boilerplate? It's about hiring process, maybe not needed). It's near the end: "We may use artificial intelligence (AI) tools to support parts of the hiring process..." That's likely boilerplate; we should remove. Also remove "Research has shown that women are less likely..." duplicate. We need to preserve all substantive information. So keep the diversity encouragement note once. Now craft HTML. We'll need to wrap paragraphs in

. For lists, use

• . Let's extract content. About MoonPay paragraph: "MoonPay is for builders with something to prove. This isn't a "work on cool crypto stuff" company. It's a high-standards, high-velocity, high-accountability company building the operating system for value movement. If the internet moves information, we move value: crypto, stablecoins, tokenized assets, and whatever comes next. Four offerings make that real: fund, tokenize, trade, and spend. 30M+ customers and 500+ ecosystem partners run on us. Licensed in the U.S. Regulated across the UK, EU, Canada, and Australia. AI is the default operating mode here. It's woven into every role, and we expect you to use it daily. It handles the manual work so you can deliver on what actually matters. You'll thrive here if outcomes excite you more than process, if impact motivates you more than titles, and if you want hard problems, real ownership, and teammates who love winning, building, and doing it together. The bar is high. The pace is real. We're building for what's next, for humans and agents. Recent recognition: Forbes' America's Best Startup Employers 2026 . 2nd in Crypto Services on Fortune's inaugural Crypto 100 The Sunday Times Best Places to Work two years running" We can keep as one or multiple paragraphs. We'll keep as one

  . About The Opportunity: "As Deputy Treasurer you will report to the Treasurer, serving as their senior counterpart and shaping and executing MoonPay's treasury strategy as the business continues to scale. You will play a critical role across regulatory expansion, liquidity and capital management, treasury reporting, and trading-related activities. This is a high-impact role requiring strong financial judgment and the ability to operate effectively in a complex, fast-moving environment. You will work across Finance and other key functions to ensure MoonPay has the liquidity, capital structure, controls, and treasury capabilities required to support its strategic ambitions and expansion into new markets." We'll put that in About the role section after the MoonPay paragraph maybe separate

  . Responsibilities (What You Will Do): list of bullet points: - Partner closely with the Treasurer to develop and execute MoonPay's treasury strategy, translating company priorities into effective liquidity, capital, risk, and treasury plans. - Lead liquidity and capital management activities, including forecasting requirements, optimizing deployment of capital, and identifying emerging constraints or opportunities. - Support regulatory and geographic expansion by assessing treasury implications, capital and liquidity requirements, banking considerations, and relevant regulatory requirements (e.g., NYDFS trust company and payment stablecoin frameworks, GENIUS Act, FFIEC reporting, state money transmitter/BitLicense regimes). - Oversee treasury analysis, scenario modelling, and reporting, translating liquidity, capital, and risk data into clear recommendations for senior stakeholders. - Provide senior oversight of trading-related treasury activities, including counterparty risk assessment across OTC and exchange trading relationships, applying disciplined risk management and financial analysis to decision-making, execution, and performance. - Build scalable treasury infrastructure, controls, processes, and external partnerships that enable MoonPay to operate effectively as the business grows in scale and complexity. We'll put each as

• inside
  . Requirements (About You): paragraphs: "You have 7+ years of experience in treasury, financial services, fintech, payments, digital assets, banking, or another highly regulated and financially complex environment, including at least 2 years of experience working with digital assets or stablecoins. You have hands-on experience with digital asset treasury operations, including stablecoin reserve management, custody and wallet considerations, and exchange or on-chain counterparty risk. You bring advanced expertise in liquidity and capital management, treasury risk management, forecasting, and scenario analysis, with experience navigating complex and high-impact decisions. You have strong knowledge of financial regulation, particularly across banking, payments, money transmission, or digital asset and stablecoin frameworks, and experience evaluating the treasury implications of regulatory or market expansion. You have demonstrated the ability to influence senior and cross-functional stakeholders while operating with significant autonomy and ambiguity, balancing competing priorities, challenging assumptions, and building scalable approaches" We'll put as

  maybe multiple paragraphs. Skills: Could list specific skill areas: digital asset treasury operations, stablecoin reserve management, custody and wallet considerations, exchange or on-chain counterparty risk, liquidity and capital management, treasury risk management, forecasting, scenario analysis, financial regulation knowledge, influencing stakeholders, autonomy, ambiguity, balancing priorities, challenging assumptions, building scalable approaches. But many overlap with requirements. To avoid duplication, maybe we skip Skills section and just have Requirements. But the instruction says prefer a few substantive sections over many thin ones. Having both Requirements and Skills might be thin. Better to combine into Requirements and maybe not have Skills. However we need to follow heading list: we can omit Skills if no distinct content. The About You already covers skills. So we can omit Skills section. Thus sections: About the role, Responsibilities, Requirements, Pay, Benefits, Schedule. Now Pay: "Salary: $180,000 - $300,000 (based on state, and experience level)". We'll put as

  . Benefits: list from Benefits & Perks, excluding hybrid working schedule. Let's extract: - Competitive salary package - Equity package: financial freedom starts with our employees, so all employees have ownership at MoonPay - Pay-for-performance equity bonus: those who drive outsized outcomes receive outsized rewards - Moonshot award: we honor exceptional impact. 20 employees a year, each earning a $250,000 equity grant - Pension: employer contributions from day one - Employee referral program: refer great people, earn 10K in USDC - Flexible Time Off: choose when to work and when to switch off - Recharge Period: end-of-year company-wide time off to rest and reset - Birthday leave: take the day off to celebrate you - Enhanced parental leave: more time with family, no second thought - Commuter benefits: public transport to and from the office - Private healthcare benefits: to protect you and your loved ones - Wellhub wellness membership: access to gyms, studios, classes, and wellness apps in one membership - Enterprise access to the latest AI tools: Claude, ChatGPT, Gemini and whatever's next - Lunch credit: meals covered on the days you're in the office - Home office setup allowance: build the home office of your dreams - Remote working allowance: those working fully remotely get a little extra for utilities - Monthly product budget and zero-fee crypto transactions - $1,000 Annual training budget: we support your learning journey - High Potential Program: structured development, mentorship, and stretch opportunities - Regular remote company offsites: high-impact in-person sessions and hackathons - (Ireland) Cycle to Work scheme: tax-efficient bike, gear, and safety kit - (UK) EV Salary Sacrifice: lease an electric vehicle through pre-tax salary We'll put each as

  • . Schedule: hybrid working schedule: "Hybrid working schedule: work fully remotely or from your nearest Moonbase". We'll put as

    . Now also include the diversity encouragement note once: "Research has shown that women are less likely than men to apply for this role if they do not have experience in 100% of these areas. Please know that this list is indicative, and that we would still love to hear from you even if you feel that you are only a 75% match. Skills can be learned, diversity cannot." We'll place it maybe after Requirements or at end of About the role?