Treasury Senior Solutions Architect

We need to output HTML fragment with sections: About the role (maybe), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, application instructions. We need to parse the posting. Let's extract sections: - About the role: The first paragraph(s) describing role: "Join Mizuho as a Treasury Senior Solutions Architect! The Treasury Senior Solutions Architect is responsible for defining, managing, and delivering strategic Treasury and Cash Management capabilities across the bank's Treasury ecosystem. This role acts as the primary liaison between Treasury Operations, Front Office, Finance, Risk, and Technology teams to ensure Treasury platforms support evolving business, regulatory, liquidity, funding, and cash management requirements. The ideal candidate combines deep Treasury domain expertise with strong technical acumen and product management skills. The role owns the Treasury technology roadmap, backlog prioritization, business requirements, product lifecycle management, and end-to-end delivery of Treasury initiatives including Liquidity Management, Cash Positioning, Funding, Intraday Liquidity, Nostro Management, Reconciliation, Regulatory Reporting, and Open Banking integrations." That's about the role. - Responsibilities: There is a section "Principal Duties And Responsibilities" with subsections: Stakeholder Management, Strategy & Ownership, Requirements & Solution Design, Technical Leadership & Governance, Documentation & Standards. We need to capture all duties. We can combine into a list under Responsibilities. - Requirements: There's "Minimum Job Requirements Or Experience" with subheadings: Business & Domain Experience, Technical Skills (CORE – MUST HAVE, NICE TO HAVE), Education And Other Requirements. We need to capture requirements. - Qualifications: Might be overlapping with Requirements. The instruction says use headings like Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have content for: About the role, Responsibilities, Requirements (including Business & Domain Experience, Technical Skills, Education). Also we have Salary info: "The expected base salary ranges from $112k-$180k." Also mention discretionary bonus, generous employee benefits package, hybrid working program. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications (maybe Education), Skills (Technical Skills), Benefits (benefits package, hybrid work, bonus), Pay (salary range), Schedule (maybe hybrid working program? Actually schedule is about remote/in-office; we could put under Schedule or Benefits. The instruction: include a section ONLY when posting has real, specific content for it. The posting mentions hybrid working program, varying opportunities for remote work depending on nature of role, needs of department, local laws. That's schedule info. So we can have a Schedule section. We must not create sections with filler like "commensurate with experience". We have specific salary range, so Pay section is valid. Benefits: mention "generous employee benefits package", "discretionary bonus". That's specific enough? It's generic but still mentions benefits. Might be okay. We'll include Benefits. Skills: we have Technical Skills (CORE – MUST HAVE, NICE TO HAVE). That's specific. Qualifications: maybe Education And Other Requirements (Bachelor's degree, communication skills, autonomy, etc). That's qualifications. We need to avoid duplication: Ensure we don't repeat same content in multiple sections. Let's extract details precisely. First, About the role paragraph: We'll keep as

. Responsibilities: We'll list bullet points from the subsections. Let's extract each bullet: Under Stakeholder Management: - Act as Treasury Technology liaison with senior business stakeholders, Data Architecture and dependent engineer teams. - Present progress, risks, and recommendations to executive leadership and Steering Committees. - Build consensus among Treasury, Finance, Operations, Risk, Compliance, and Technology organizations. - Manage vendor relationships and product evaluations. Strategy & Ownership: - Define and maintain the strategic roadmap for Treasury platforms and services. - Own the Treasury product backlog and prioritize initiatives based on business value, risk mitigation, regulatory requirements, and operational efficiency. - Develop product vision, business cases, and investment proposals for Treasury modernization initiatives. - Partner with Treasury, Finance, Operations, Risk, Compliance, and Technology stakeholders to establish product priorities. - Serve as Product Owner within Agile delivery teams and participate in PI Planning, Sprint Planning, Reviews, and Retrospectives. Requirements & Solution Design: - Drive requirements gathering workshops with Treasury business users. - Translate business requirements into Epics, Features, User Stories, and Acceptance Criteria. - Maintain traceability from business objectives through implementation. - Collaborate with Solution Architects and Engineering teams on target-state solutions. - Validate technical designs align with Treasury operating models and business objectives. - Support creation of process flows, capability maps, architecture diagrams, and data models. Technical Leadership & Governance: - Serve as a design authority throughout project lifecycles, from concept through production deployment (note typo "deign" but we keep as is). - Review and approve solution designs, modeling artifacts, and implementation approaches. - Ensure adherence to data architecture standards, security controls, and development best practices. - Guide and mentor development teams, influencing design decisions rather than managing day-to-day coding. - Participate in data architecture review boards, technology evaluations, and vendor assessments. Documentation & Standards: - Produce and maintain data architecture diagrams, solution blueprints, interface contracts, and design specifications. - Document and maintain data maps including transition roadmaps. - Ensure artifacts are audit-ready and suitable for regulatory review. We'll put these as

• items. Requirements: We'll have Business & Domain Experience, Technical Skills (CORE – MUST HAVE, NICE TO HAVE), Education And Other Requirements. But we might split into Requirements (experience) and Qualifications (education, soft skills). Skills separate. Let's extract Business & Domain Experience: - 10+ years of experience within Treasury, Liquidity Management, Cash Management, Payments, or Financial Services Technology. - 5+ years serving as a Treasury or Finance lead engineer or architect Lead. - Experience delivering large-scale transformation. - Experience operating within Agile project monument (typo: "monument" maybe "management"? We'll keep as given). Technical Skills CORE – MUST HAVE: - Proven experience owning program roadmaps, backlogs, and strategic initiatives for Treasury, Finance, data management, reporting, or analytics platforms. - Demonstrated ability to partner with senior stakeholders across Treasury, Finance, Operations, Risk, Compliance, Technology, Data Architecture, and Engineering organizations to drive consensus and delivery. - Strong experience leading requirements gathering workshops and translating business requirements into epics, features, user stories, acceptance criteria, and implementation roadmaps. - Extensive experience managing large-scale data sourcing, integration, warehousing, aggregation, and data homogenization initiatives across multiple enterprise platforms. - Proven ability to collaborate with Solution Architects and Engineering teams to define target-state architectures and ensure technology solutions align with business and operational objectives. - Experience serving as a design authority, reviewing and approving solution designs, data models, architecture artifacts, and implementation approaches throughout the project lifecycle. - Strong background developing and implementing data governance frameworks, data quality controls, lineage management, security standards, and audit-ready documentation. - Hands-on experience designing and supporting enterprise data management, reporting, analytics, and regulatory reporting platforms. - Technical expertise with Snowflake, Databricks/Lakehouse Architecture, SQL, and Power BI, including data modeling, reporting, and analytics solution design. - Familiarity with Treasury and Finance processes, including liquidity management, cash management, funding, regulatory reporting, and financial data domains. NICE TO HAVE: - Experience with Sub ledgers and accounting principles - Swift standards - Advanced technologies such as AI and Cloud Computing (Azure) Education And Other Requirements: - Bachelor’s degree in Computer Science, Engineering, or Finance ideal - Strong written and verbal communication skills, with the ability to influence senior stakeholders - Demonstrated ability to operate with high autonomy and accountability - Comfortable working across business, technology, risk, and operations teams - Strong analytical mindset with a focus on enterprise value, risk stewardship, and long-term sustainability We'll treat Education And Other Requirements as Qualifications. Skills: we can put Technical Skills (CORE – MUST HAVE and NICE TO HAVE) as Skills section. Benefits: "In addition to salary and a generous employee benefits package, successful candidates are eligible to receive a discretionary bonus." Also "Mizuho has in place a hybrid working program, with varying opportunities for remote work depending on the nature of the role, needs of your department, as well as local laws and regulatory obligations." That's more schedule/benefits. We'll create Benefits section with bullet points: generous employee benefits package, discretionary bonus. Pay: salary range $112k-$180k. Schedule: hybrid working program, varying remote opportunities. We must not include boilerplate like EEO, legal, company overview (maybe we can keep company overview? It's substantive but not required sections; but we could include as About the role? Already have about role. Company overview is extra but could be omitted as not fitting headings. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep company overview info somewhere. Where to put? Could be part of About the role? Might be separate section like "Company Overview". But allowed headings list includes only those specific ones; we could add a section with heading

  About the Company

  but not in allowed list? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should fit company overview into one of those sections, maybe About the role. We can incorporate company overview into About the role paragraph. Thus About the role will include both role description and company overview. We must not repeat job title as heading. Already not. We must not include Job ID/requisition numbers. We must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. We need to ensure we don't include the NOTE about job description not exhaustive, etc. That's boilerplate; remove. Also remove "Other Requirements Mizuho has in place a hybrid working program..." we already used for Schedule. We must not include "Company Overview" paragraph separate; we'll merge. Now craft HTML. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...
  But we have multiple subcategories; we could keep as list items. Better to keep Requirements as list of experience items. Qualifications: list education and other requirements. Skills: list technical skills (core and nice to have) maybe as two sublists? Could just list all. Benefits: list. Pay:

  The expected base salary ranges from $112k-$180k.

  Schedule:

  Hybrid working program with varying opportunities for remote work depending on role, department needs, and local laws.

  Make sure to preserve all specifics: numbers, etc. Let's write About the role paragraph: "Join Mizuho as a Treasury Senior Solutions Architect! The Treasury Senior Solutions Architect is responsible for defining, managing, and delivering strategic Treasury and Cash Management capabilities across the bank's Treasury ecosystem. This role acts as the primary liaison between Treasury Operations, Front Office, Finance, Risk, and Technology teams to ensure Treasury platforms support evolving business, regulatory, liquidity, funding, and cash management requirements. The ideal candidate combines deep Treasury domain expertise with