Treasury Operations Manager

We need to output HTML fragment with sections: About the role? The posting includes Overview, What You'll Do, What We're Looking For, Nice to Have, Compensation Philosophy, Benefits & Perks, Why Join Breeze, In-Office Expectations, Come Build With Us. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to these headings appropriately. We have: - Overview: description of role. Could be "About the role" (overview). Use

About the role

with

containing overview text. - What You'll Do: responsibilities. Use

Responsibilities

with

• list. - What We're Looking For: requirements/qualifications. Could be

  Requirements

  or

  Qualifications

  . We need to decide. The posting lists Bachelors Degree, 5+ years experience, deep understanding, hands-on experience, etc. That's qualifications. Use

  Qualifications

  with
  . - Nice to Have: could be

  Skills

  or maybe separate "Nice to Have" but we only have allowed headings: Skills. We could put nice-to-have under Skills. Or we could omit if not enough content? But we have content. Use

  Skills

  with
  . - Compensation Philosophy: includes Pay range. Use

  Pay

  with

  containing salary range and note. - Benefits & Perks: Use

  Benefits

  with
  . - In-Office Expectations: could be Schedule? Actually schedule is about work schedule/hybrid. Use

  Schedule

  with

  . - Why Join Breeze and Come Build With Us: could be omitted as not matching headings, but we could incorporate into About the role? But we must preserve all substantive information; we cannot drop sections unless they are boilerplate. These are substantive but not matching allowed headings. However instructions: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings for sections. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but likely they expect only those headings. However we need to preserve all substantive information; we could embed the "Why Join Breeze" and "Come Build With Us" content into existing sections like About the role or maybe a separate

  About the role

  could include that. But we must not invent headings not listed? 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 suggests we should use those. Safer to stick to those headings and place all content under them. Thus we need to distribute: - About the role: overview + maybe why join and come build? Could combine. - Responsibilities: What You'll Do. - Requirements: maybe "What We're Looking For" (mandatory). - Qualifications: maybe "Nice to Have"? But we already used Requirements for mandatory. Could use Qualifications for nice-to-have. But we have both Requirements and Qualifications headings allowed. We'll assign: - Requirements: mandatory qualifications (Bachelors, 5+ years, deep understanding, hands-on experience, multi-currency, reconciliation instincts, Excel, builder mentality, excited to use AI). - Qualifications: nice-to-have (experience building financial ops at startup, stablecoin/crypto, FBO, Modern Treasury, BigQuery, establishing banking relationships). - Skills: maybe we could put technical skills like Excel, AI, automation? But we already used those. Could combine. Better: Use Requirements for mandatory, Qualifications for nice-to-have, Skills for technical skills like Excel, AI, automation, etc. But we already placed Excel in Requirements. Could move Excel to Skills. Let's think. We have many items; we can split. Let's list mandatory items from "What We're Looking For": - Bachelors Degree in Finance or related field - 5+ years of experience in financial, treasury, or payment operations within fintech, payments, banking, or regulated financial services - Deep understanding of settlement operations, prefunding, payment cutoffs, liquidity management, and the day-to-day realities of moving money - Hands-on experience executing payments across multiple rails, including wire, ACH, SWIFT, SEPA, or local equivalents, within a controlled environment - Experience managing multi-currency and multi-entity operations, including FX execution, intercompany funding, cash positioning, and short-term forecasting - Strong reconciliation instincts and advanced Excel skills, with confidence working through large, transaction-level datasets from processors or banking systems - Builder mentality with a bias toward action—you’re comfortable getting into the details, solving problems, and creating structure where a playbook doesn’t yet exist - Excited to use AI, automation, and technology to improve workflows, reduce manual work, and build smarter, more scalable operations Nice to Have: - Experience building financial operations at an early-stage or high-growth startup - Hands-on experience with stablecoin or crypto settlements, custody platforms, exchanges, or OTC counterparties - Familiarity with FBO account structures, safeguarding requirements, or money transmitter permissible investment rules - Experience with Modern Treasury, NetSuite, or similar treasury and payment operations platforms - BigQuery or similar experience pulling, analyzing, and working directly with your own data - Experience establishing banking, payment, or custody relationships as part of launching into new markets We could put mandatory under Requirements, nice-to-have under Qualifications, and maybe Skills for Excel, AI, automation? But we already have Excel and AI in mandatory; could keep them there. Alternatively, we could put all mandatory under Requirements, and not use Qualifications. But we have Qualifications heading allowed; we could omit if no specific content? But we have nice-to-have content, so we could use Qualifications for nice-to-have. Skills heading could be used for technical skills like Excel, AI, automation, etc. But we already placed them. Could move them to Skills and keep Requirements more about experience/education. Let's decide: - Requirements: education + years experience + deep understanding + managing multi-currency + builder mentality + excited to use AI? Hmm. Better: Use Requirements for education and experience; Qualifications for deep understanding, hands-on experience, multi-currency, reconciliation instincts, Excel, builder mentality, AI excitement; Skills for nice-to-have? This is getting messy. Given the instruction: "Prefer a few substantive sections over many thin ones." So we should not create many sections with little content. Better to have maybe 4 sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's 6 sections. Could combine Requirements and Qualifications into one "Requirements" section that includes both mandatory and nice-to-have (labeled as "Nice to have" inside). But we need to use

  • for any list. We could have a single Requirements section with two sub-lists? But we cannot add headings inside? We could just list all items, maybe mark nice-to-have with a note. But we must preserve all info; we can just list them all as requirements, but that would misrepresent nice-to-have as required. However we could keep them all under Requirements and note "Nice to have" in the item text. That's acceptable. Thus we can have: - About the role (overview + why join + come build) - Responsibilities (What You'll Do) - Requirements (What We're Looking For + Nice to Have) - Benefits (Benefits & Perks) - Pay (Compensation Philosophy) - Schedule (In-Office Expectations) That's 6 sections, each substantive. Now we need to strip boilerplate: remove EEO, navigation, etc. Already we omitted. Now produce HTML. We need to ensure we don't repeat job title as heading. Not needed. We'll output:

    About the role

    At Breeze, we're building the AI-powered infrastructure layer for global commerce, making it radically simpler for businesses to sell, get paid, and operate across markets. We go far beyond traditional payment processing. Breeze combines global payments, AI, stablecoins, and a Merchant of Record-like model to take on the complexity businesses typically manage themselves, including compliance, risk, fraud, chargebacks, reconciliation, and customer support. Our goal is simple: let businesses focus on building and selling great products while Breeze handles the complexity behind getting paid. Backed by Sequoia Capital, Multicoin Capital, and The Chainsmokers, Breeze is a successful, rapidly growing, and exceptionally well-capitalized company. We have the runway to think long term while remaining early enough that every person joining today can have a meaningful impact on what we build. Overview We’re hiring a Treasury Operations Manager to join our team! You’ll be at the center of how money moves through our business. From owning merchant settlements, managing liquidity across our banking and custody network, and making sure payouts happen accurately and on time across every currency and entity we operate in. This is a hands-on role with real ownership and real-time decision-making. You’ll position cash ahead of market opens, make critical funding decisions, execute wires and on-chain transfers under dual control, and jump in to investigate when a settlement doesn’t land where it should. And you won’t just run the operation, you’ll help build what comes next. You’ll take workflows that rely on spreadsheets and tribal knowledge and turn them into scalable, repeatable processes that can keep pace with a growing payments business. If you’ve worked in treasury or payment operations within payments, banking, fintech, or crypto and love moving fast, solving problems, and building better systems as you go, you’ll feel right at home here. Make an outsized impact: We're successful and still early, with meaningful traction and strong financial foundations. Lean teams, few layers, and direct access to decision-makers mean you'll have real ownership and the autonomy to make things happen.Solve hard, meaningful problems: Work at the intersection of AI, payments, stablecoins, risk, compliance, financial infrastructure, and global commerce as we build an intelligent infrastructure layer that goes far beyond payments.Build AI-first: AI isn't an add-on. It's central to how we're building our products and how our teams operate. You'll experiment with new tools, automate the repetitive, and continuously rethink how to work smarter.Work with an exceptional team: Join ambitious, curious, low-ego people who move quickly, hold a high bar, and care deeply about what they build.Grow with Breeze: As Breeze grows, strong performers can quickly expand their scope and take on bigger problems.Build for the long term: Backed by Sequoia Capital, Multicoin Capital, and The Chainsmokers, we're exceptionally well-capitalized with the runway to think big. Come Build With Us! We offer a rare combination: the ownership and speed of an early-stage company with the traction, backing, and financial foundations of a successful business. We're building at the convergence of AI, payments, stablecoins, financial infrastructure, and global commerce. The opportunity is much bigger than building another payment processor. We're building the intelligent infrastructure layer for global commerce, and there's still an enormous amount left to build. If you want meaningful ownership, hard problems, exceptional teammates, and the opportunity to help define what comes next, we'd love to hear from you!

    But that's huge; we might be duplicating. Actually we included overview and also the "Why Join Breeze" and "Come Build With