Financial Partnerships Operations Manager, Americas

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Airwallex", "Attributes We Value", "About The Team", "What you'll do", "Responsibilities", "Who You Are", "Minimum Qualifications", "Preferred Qualifications", "Applicant Safety Policy", "Equal opportunity", "Compensation Range". We need to use headings

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 should map content to these headings. We have: - About the role: could be "What you'll do" or "About The Team"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have content about role: "What you'll do" describes responsibilities. Also "Responsibilities" section enumerates bullet points. So we could combine them under Responsibilities heading. We have "Who You Are" includes minimum and preferred qualifications. So we could have Requirements (or Qualifications) heading. We have "Compensation Range: $100K - $170K" => Pay section. We have no explicit Benefits or Schedule. So we should not include those headings. We also have "About Airwallex" and "Attributes We Value" and "About The Team". Those could be considered "About the role"? But the instruction says do NOT repeat the job title as a heading. It doesn't forbid other headings like About the company. However the list of allowed headings is given as examples; we could still include other headings if they have content? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings for sections. It doesn't explicitly forbid other headings, but likely they want us to stick to those. However we have company overview content; maybe we can put that under "About the role" as a brief description. But "About the role" is more about the role itself, not company. However we could treat "About Airwallex" as part of "About the role". Might be okay. But we need to preserve ALL substantive information; we cannot drop company overview. So we need to include it somewhere. If we only allowed headings from list, we could put company overview under "About the role". That seems plausible. Similarly "Attributes We Value" could be part of "Requirements" or "Qualifications"? Might be better to include under "Qualifications" as they are attributes valued. "About The Team" could also be under "About the role". Thus we can structure:

About the role

... combine About Airwallex, Attributes We Value, About The Team ...

Responsibilities

list of responsibilities from "What you'll do" and the bullet list under Responsibilities. But note "What you'll do" is a paragraph describing role; we could include that as prose before the list. Thus under Responsibilities heading we can have a

for the "What you'll do" paragraph, then

• for the bullet list. Then

  Requirements

  (or Qualifications). We have Minimum Qualifications and Preferred Qualifications. We could combine them under Requirements heading, with sub-sections? But we cannot add extra headings unless they have content. Could we include a

  for Minimum Qualifications and then a

  for Preferred Qualifications? That's okay. We need to preserve all bullet points? The Minimum Qualifications are a list of items separated by periods? Actually they are sentences each starting with a bold? The text: "Minimum Qualifications Bachelor’s degree or equivalent experience.At least 4 years of experience in financial services, fintech, payments, banking operations, strategy, business operations, partnerships, consulting, or a related field. Experience in a fast-growing technology company or top-tier financial institution is preferred.Strong project-management experience, with a track record of improving processes, policies, products, or operational workflows.Excellent attention to detail and the ability to manage multiple workstreams, deadlines, dependencies, and escalations.Effective written and verbal communication skills, including the ability to communicate clearly with senior stakeholders and external partners.Strong analytical skills, including proficiency with relevant tools such as Excel, Google Sheets, Looker, or similar reporting and analysis platforms.The ability to think critically and creatively while balancing growth, customer experience, operational effectiveness, and risk.Experience collaborating with a wide range of stakeholders across functions, regions, cultures, and levels of seniority.The ability to work independently in a fast-paced and rapidly changing environment." These are sentences without line breaks. We could turn each sentence into a

• for clarity. The instruction: Use
  • for any list of duties/requirements/benefits. So we should convert these into list items. Similarly Preferred Qualifications list. Thus under Requirements heading we could have:

    Requirements

    Minimum Qualifications:

    • ...
    ...

    Preferred Qualifications:

    • ...
    ...
    But we need to avoid extra headings like "Minimum Qualifications". That's okay as a

    preceding list. Now Pay section:

    Pay

    Compensation Range: $100K - $170K

    We should not include Benefits or Schedule. We must remove boilerplate: Applicant Safety Policy, Equal opportunity, etc. So drop those. Now ensure we don't repeat job title as heading (we aren't). No Job ID. Now output only HTML fragment. Let's craft content. About the role paragraph: combine About Airwallex, Attributes We Value, About The Team. We need to preserve all substantive information; we can paraphrase? Must not invent or summarize away detail. We can keep sentences as is but combine into paragraphs. Let's extract: About Airwallex: "Airwallex is the only unified payments and financial platform for global businesses. Powered by our unique combination of proprietary infrastructure and software, we empower over 250,000 businesses worldwide – including Brex, Navan, Qantas, SHEIN and many more – with fully integrated solutions to manage everything from business accounts, payments, spend management and treasury, to embedded finance at a global scale. Proudly founded in Melbourne, we have a team of over 2,300 of the brightest and most innovative people in tech across 27 offices around the globe. Valued at US$11 billion and backed by world-leading investors including T. Rowe Price, Visa, Mastercard, Robinhood Ventures, Sequoia, Salesforce Ventures, DST Global, and Lone Pine Capital, Airwallex is leading the charge in building the global payments and financial platform of the future. If you’re ready to do the most ambitious work of your career, join us." Attributes We Value: "We hire successful builders with founder-like energy who want real impact, accelerated learning, and true ownership. You bring strong role-related expertise and sharp thinking, and you’re motivated by our mission and operating principles. You move fast with good judgment, dig deep with curiosity, and make decisions from first principles, balancing speed and rigor. You're humble and collaborative; turn zero‑to‑one ideas into real products, and you “get stuff done” end-to-end. You use AI to work smarter and solve problems faster. Here, you’ll tackle complex, high‑visibility problems with exceptional teammates and grow your career as we build the future of global banking. If that sounds like you, let’s build what’s next." About The Team: "The Financial Partnerships Operations team supports smooth day-to-day collaboration with Airwallex’s banking partners across our global entities. We work closely with Financial Partnerships Managers, external financial institutions, and internal teams to improve processes, manage partner requirements, support new market expansion, and deliver high-impact results across Airwallex’s products." We can combine into a few paragraphs. Now Responsibilities: "What you'll do Reporting to the Director, Partnerships Strategy & Operations, you will help support the day-to-day operations of the Financial Partnerships team and the continued growth of the organisation. You will play a significant role in our communications with external banking and financial partners, while helping ensure compliance with applicable regulations and maintaining the trust of our customers and stakeholders. You will work with teams and partners across Airwallex’s product offerings, including Issuing, Online Payments, and Global Treasury & Payment Network. This is an opportunity to join a growing team, improve how we operate at scale, and help shape the next phase of Airwallex’s global growth. This role is based in New York, NY." Then bullet list under Responsibilities: - Collaborate with the Financial Partnerships team as Airwallex expands into new markets and grows its network of banking, payment, and financial-institution partners. - Support the operational relationship with financial partners throughout their lifecycle with Airwallex, from onboarding and due diligence through integration, launch, steady state, and expansion. - Track prevailing rules, regulations, scheme requirements, and upcoming changes affecting banks, payment service providers, card schemes, and alternative payment methods. - Develop continuous process improvements to enhance operational efficiency and effectiveness. This may involve building new processes, streamlining existing workflows, leveraging technology, and implementing best practices. - Own the triage of partner escalations, operational requests, and internal dependencies, ensuring issues are routed to the right teams and resolved in a timely manner against agreed KPIs. - Coordinate regular due diligence sessions with Financial Crime Compliance and other relevant control functions, ensuring partner requirements are understood, documented, and completed on time. - Partner with financial institutions on change management, ensuring new releases, scheme requirements, regulatory changes, and partner requests are executed properly by Product, Engineering, and Operations teams. - Generate and present reports to senior management and financial partners, providing clear visibility into partner health, implementation progress, operational risks, and areas for improvement. - Contribute to scalable operating mechanisms, including partner scorecards, governance forums, QBRs, intake processes, playbooks, and performance dashboards. Now Requirements: Minimum Qualifications list (convert each sentence to li). Let's split: - Bachelor’s degree or equivalent experience. - At least 4 years of experience in financial services, fintech, payments, banking operations, strategy, business operations, partnerships, consulting, or a related field. - Experience in a fast-growing technology company or top-tier financial institution is preferred. - Strong project-management experience, with a track record of improving processes, policies, products, or operational workflows. - Excellent attention to detail and the ability to manage multiple workstreams, deadlines, dependencies, and escalations. - Effective written and verbal communication skills, including the ability to communicate clearly with senior stakeholders and external partners. - Strong analytical skills, including proficiency with relevant tools such as Excel, Google Sheets, Looker, or similar reporting and analysis platforms. - The ability to think critically and creatively while balancing growth, customer experience, operational effectiveness, and risk. - Experience collaborating with a wide range of stakeholders across functions, regions, cultures, and levels of seniority. - The ability to work independently in a fast-paced and rapidly changing environment. Preferred Qualifications list: - Experience working directly with banking partners, sponsor banks, payment processors, card schemes, payment service providers, local payment methods, or other regulated financial institutions. - Familiarity with payment flows, acquiring or issuing, network rules, scheme mandates, KYC or KYB, due diligence, or technical integration processes. - Experience building scalable operating mechanisms such as governance forums, partner scorecards, dashboards, QBRs, intake processes, or global playbooks. - Experience coordinating cross-functional implementation across Product, Engineering, Treasury, Risk, Legal, Financial Crime Compliance, Finance, Commercial, and Operations teams. - Experience identifying opportunities to automate manual processes, improve partner economics,