Director, Financial Institution Sales

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. The posting includes: - Intro: "What We Need Corpay is seeking an experienced and highly motivated Director, Financial Institution Sales to join our Cross-Border Payments business." That's about the role. - Description: "Corpay Cross-Border is a global leader..." etc. - "How We Work Corpay Will Set You Up For Success By Providing Assigned workspace at home office set up Company-issued equipment Formal, hands-on training" - "Who you'll sell to Regional and community banks — Institutions under $100 billion in assets looking to offer international wires, cross-border payments and FX risk management to their business customers, and to grow non-interest income without adding infrastructure or headcount.Credit unions — Retail and business-services credit unions serving members and member businesses with international payment, foreign currency and remittance needs, including institutions building out commercial and member business services." - Then "Key Responsibilities" with bullet points. - Then "Revenue ownership and monetization" etc. - Then "Cross-functional collaboration" - Then "Deal and pipeline management" - Then "Required Qualifications" list. - Then "Preferred Experience" - Then "Benefits & Perks" list. - Then "Equal Opportunity/Affirmative Action Employer" (boilerplate, remove) - Then "Pay Transparency" with salary range. We need to map sections: - About the role: likely the intro paragraphs describing role, mission, etc. - Responsibilities: combine all bullet points under Key Responsibilities, Revenue ownership, Cross-functional collaboration, Deal and pipeline management. - Requirements: maybe Required Qualifications. - Qualifications: maybe Preferred Experience? But they said use sections: Requirements, Qualifications, Skills. We need to decide mapping. Usually "Required Qualifications" is Requirements. "Preferred Experience" could be Qualifications or Skills. "Skills" could be derived from abilities listed (consultative selling, business acumen, etc.) but we should not invent. We can put skills under Skills if present. The posting includes abilities like "Ability to manage complex, multi-stakeholder sales cycles", "Consultative selling approach with strong business acumen", "Highly self-motivated and entrepreneurial", "Willingness to travel", "Working knowledge of Salesforce". Those could be considered skills. But we need to avoid duplication. Perhaps we put Required Qualifications under Requirements, Preferred Experience under Qualifications, and the skill-like statements under Skills. But we must not create sections with filler. If we put Skills, we need actual content. The posting includes skill-like statements; we can extract them. Also Benefits: we have Benefits & Perks list. Pay: we have salary range. Schedule: not mentioned; no schedule info (like full-time, remote). There's mention of "Assigned workspace at home office set up" but that's about remote work setup, not schedule. No explicit schedule. So we should not include Schedule section. We must not repeat job title as heading. So no heading for Director, Financial Institution Sales. We must not include Job ID etc. We must remove boilerplate: EEO, etc. We must output only HTML fragment, no /, no markdown fences. We need to use

for section headings. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. We need to include a section ONLY when posting has real, specific content for it. Thus we will produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Check each: About the role: we have introductory paragraphs describing role, mission, etc. We'll combine them into prose

  maybe multiple

  . Ensure we keep all details. Responsibilities: we have bullet points under Key Responsibilities, Revenue ownership and monetization, Cross-functional collaboration, Deal and pipeline management. We'll combine into a single

  with
  • items. Requirements: Required Qualifications list. Qualifications: Preferred Experience list. Skills: we need to extract skill statements from Required Qualifications? Actually Required Qualifications includes ability statements etc. But we already used those for Requirements? The Required Qualifications list includes items like "5+ years of enterprise sales experience..." etc. Those are qualifications, not skills. The skill-like statements appear within Required Qualifications as well: "Ability to manage complex, multi-stakeholder sales cycles including C-level, business line and technical buyers." "Consultative selling approach with strong business acumen and the ability to translate technical and operational concepts into commercial value." "Highly self-motivated and entrepreneurial, comfortable in a fast-paced, growth-oriented environment." "Willingness to travel for client meetings and industry events." "Working knowledge of Salesforce or a similar CRM." Those could be considered skills. But we already used Required Qualifications for Requirements section; we could split: Requirements = years of experience, selling to banks, etc. Skills = abilities. However the instruction says we can have sections Requirements, Qualifications, Skills. It's ambiguous. To be safe, we could put all Required Qualifications items under Requirements (as they are qualifications). Then Preferred Experience under Qualifications. Then we could still have Skills section if there are distinct skill statements not covered elsewhere. But we might duplicate if we put same content in two sections. Better to not create Skills if no distinct skill content beyond what's already in Requirements/Qualifications. However the posting does have skill-like statements; but they are part of Required Qualifications. If we put them under Requirements, that's fine. Then we may not need Skills section. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Skills if not needed. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check Benefits: we have list. Pay: we have salary range. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to format. Let's extract content precisely. About the role: combine: "What We Need Corpay is seeking an experienced and highly motivated Director, Financial Institution Sales to join our Cross-Border Payments business. Corpay Cross-Border is a global leader in international payments, embedded payment technologies, and foreign exchange risk management, moving money in 145+ currencies to more than 200 countries. This role sits within our Payment Solutions Group and focuses on regional and community financial institutions — banks and credit unions under $100 billion in assets that want to serve their clients’ international needs without building the capability themselves. The Director owns the full sales lifecycle, from prospecting and solution design through contract execution and commercialization. This is a quota-carrying individual contributor role with no direct reports. Corpay is already integrated with many of the software platforms that power banking cores and the digital interfaces clients and members use every day. Where that connectivity exists, a bank or credit union can launch on a proven path instead of funding a custom build. Finding those openings and converting them is the core of this role." Also "How We Work Corpay Will Set You Up For Success By Providing Assigned workspace at home office set up Company-issued equipment Formal, hands-on training" This is about how they set you up for success; could be part of About the role or maybe separate but we can include in About the role as prose. Also "Who you'll sell to Regional and community banks — Institutions under $100 billion in assets looking to offer international wires, cross-border payments and FX risk management to their business customers, and to grow non-interest income without adding infrastructure or headcount.Credit unions — Retail and business-services credit unions serving members and member businesses with international payment, foreign currency and remittance needs, including institutions building out commercial and member business services." We could include that as part of About the role as well. Thus About the role will be a few paragraphs. Now Responsibilities: list items: From "Key Responsibilities": - Sales execution: Proactively source, develop and close new financial institution relationships across the assigned asset segments — banks and credit unions seeking to add cross-border payments and FX capabilities for their clients and members. - Lead complex, consultative sales cycles that run through executive leadership, treasury management, commercial and member business services, digital and technology, risk and compliance, and vendor management — including board or committee approval where required. - Navigate third-party risk and due diligence processes, coordinating with Corpay risk, compliance, information security and legal to move institutions through vendor review efficiently. - Revenue ownership and monetization: - Own and exceed assigned revenue targets, generating income through FX spreads, transaction fees and value-added services under agreed revenue-share economics. - Expand revenue per institution beyond the payment leg — multi-currency accounts, deposits and liquidity, and FX and rate hedging — within the relationships this role brings on. - Build and maintain a pipeline that balances near-term opportunities against longer-cycle strategic institutional relationships. - Cross-functional collaboration: - Work with product, solution engineering, implementation, risk and compliance, and marketing to scope solutions, accelerate deal velocity, and ensure successful go-lives. - Partner with implementation and relationship management to enable the institution's commercial banking, treasury and member business teams, so the program is adopted and used after launch. - Support development of case studies, partner enablement materials and go-to-market plans. - Deal and pipeline management: - Track all opportunities, forecasts and partner activity in Salesforce, maintaining accurate and actionable reporting. We need to preserve all details. We'll create
    with each bullet as
    • . Might need to keep sub-bullets? The original had sub-bullets under each heading. We could flatten but preserve meaning. Could keep headings inside
    • as bold? But we cannot add extra tags beyond

      ,

      • ,

        . We could embed headings as plain text inside

      • . Eg:
      • Sales execution: Proactively source...
      but is not allowed per rules? The rules only specify using those tags; they didn't forbid other tags, but to be safe we should stick to only those tags? It says "Use

      for section headings ... Use

      • for any list of duties/requirements/benefits, and

        for prose." It doesn't forbid other tags, but to be safe we can avoid extra tags. We can incorporate the heading as part of the sentence. Thus each

      • will contain the full sentence. We'll list each bullet as separate
      • . For sub-bullets we can make separate
      • items. Thus list: - Proactively source, develop and close new financial institution relationships across the assigned asset segments — banks and credit unions seeking to add cross-border payments and FX capabilities for their clients and members. - Lead complex, consultative sales cycles that run through executive leadership, treasury management, commercial and member business services, digital and technology, risk and compliance, and vendor management — including board or committee approval where required. - Navigate third-party risk and due diligence processes, coordinating with Corpay risk, compliance, information security and legal to move institutions through vendor review efficiently. - Own and exceed assigned revenue targets, generating income through FX spreads, transaction fees and value-added services under agreed revenue-share economics. - Expand revenue per institution beyond the payment leg — multi-currency accounts, deposits and liquidity, and FX and rate hedging — within the relationships this role brings on. - Build and maintain a pipeline that balances near-term opportunities against longer-cycle strategic institutional relationships. - Work with product, solution engineering, implementation, risk and compliance, and marketing to scope solutions, accelerate deal velocity, and ensure successful go-lives. - Partner with implementation and relationship management to enable the institution's commercial banking, treasury and member business teams, so the program is adopted and used after launch. - Support development of case studies, partner enablement materials and go-to-market plans. - Track all opportunities, forecasts and partner activity in Salesforce, maintaining accurate and action