Senior Business Analyst - Vice President

We need to output HTML fragment with sections: h3 headings for sections present: About the role? The posting includes "Role Description", "Role Objectives", "Qualifications And Skills", "Additional Requirements". Also salary info and benefits info. Also maybe "Pay" and "Benefits" sections if present. The posting includes "The anticipated salary range for this role is between $127,000.00 and $160,000.00." and "The role may also be eligible for an annual discretionary incentive award." Also "In addition to cash compensation, SMBC offers a competitive portfolio of benefits to its employees." So we have Pay and Benefits content. Also schedule? Not mentioned. So we should not create Schedule section. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which headings to use based on content. The posting includes "Role Description" (could be About the role). "Role Objectives" could be Responsibilities. "Qualifications And Skills" could be Qualifications and Skills. Additional Requirements maybe "Additional Requirements". Also we have Pay and Benefits sections. We must not repeat job title as heading. No Job ID etc. We must preserve all substantive information. Remove boilerplate: The initial paragraph about SMBC Group is likely boilerplate? It's describing the company; maybe it's considered background but not part of role specifics. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company overview might be considered boilerplate? It's not directly about the role but could be considered background. However we need to preserve ALL substantive information; does company overview count as substantive? It's generic about the group; maybe it's considered boilerplate but not explicitly listed. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove company overview. So we should keep it? But we need to output only HTML fragment; we could include a

with that overview. However the instruction: "Prefer a few substantive sections over many thin ones." Might be okay to include a short paragraph about the company as an intro. But we also need to include sections only when posting has real, specific content for it. So we need sections: About the role (maybe from Role Description), Responsibilities (from Role Objectives), Qualifications (maybe combine Qualifications and Skills), Skills (maybe separate? The instruction list includes Skills as a possible heading. But we have Qualifications And Skills combined. Could split into Qualifications and Skills sections? But we should not invent headings if content not clearly separated. The posting has "Qualifications And Skills" heading with bullet list. Could treat that as Qualifications section (or Skills). Since both headings are allowed, we could output a single

Qualifications and Skills

with list. That's acceptable. Additional Requirements: could be a section maybe "Additional Requirements". Not in the list of headings but we can still use

for any section heading? 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. Likely we should stick to those headings; but we can also use other headings if needed? Safer to map to given headings: Additional Requirements could go under Requirements? There's a Requirements heading in examples. So we could use

Requirements

for additional requirements (like hybrid work, accommodation). But we also have Qualifications and Skills separate. So we could have Requirements (for additional requirements) and Qualifications and Skills (for qualifications). Or we could combine qualifications into Requirements. But better to follow examples: Use Requirements for any mandatory requirements (like hybrid work). Use Qualifications and Skills for qualifications. Pay: we have salary range and discretionary incentive award. Benefits: we have competitive portfolio of benefits. We need to output only HTML fragment, no /, no markdown fences. Let's extract content: Company overview paragraph: "SMBC Group is a top-tier global financial group. Headquartered in Tokyo and with a 400-year history, SMBC Group offers a diverse range of financial services, including banking, leasing, securities, credit cards, and consumer finance. The Group has more than 130 offices and 80,000 employees worldwide in nearly 40 countries. Sumitomo Mitsui Financial Group, Inc. (SMFG) is the holding company of SMBC Group, which is one of the three largest banking groups in Japan. SMFG’s shares trade on the Tokyo, Nagoya, and New York (NYSE: SMFG) stock exchanges. In the Americas, SMBC Group has a presence in the US, Canada, Mexico, Brazil, Chile, Colombia, and Peru. Backed by the capital strength of SMBC Group and the value of its relationships in Asia, the Group offers a range of commercial and investment banking services to its corporate, institutional, and municipal clients. It connects a diverse client base to local markets and the organization’s extensive global network. The Group’s operating companies in the Americas include Sumitomo Mitsui Banking Corp. (SMBC), SMBC Nikko Securities America, Inc., SMBC Capital Markets, Inc., SMBC MANUBANK, JRI America, Inc., SMBC Leasing and Finance, Inc., Banco Sumitomo Mitsui Brasileiro S.A., and Sumitomo Mitsui Finance and Leasing Co., Ltd." That's a lot but we keep. Then salary info: "The anticipated salary range for this role is between $127,000.00 and $160,000.00. The specific salary offered to an applicant will be based on their individual qualifications, experiences, and an analysis of the current compensation paid in their geography and the market for similar roles at the time of hire. The role may also be eligible for an annual discretionary incentive award." Benefits: "In addition to cash compensation, SMBC offers a competitive portfolio of benefits to its employees." Role Description paragraph: "The Vice President, Senior Business Analyst will serve as a senior functional leader supporting the strategy, analysis, design, and delivery of Treasury Services capabilities across Payments and Liquidity Management. This role will partner closely with Product Owners, Technology, Operations, Risk, Compliance, and business stakeholders to translate strategic objectives, client needs, regulatory requirements, operational processes, and technical constraints into clear business requirements and scalable solutions. The Senior Business Analyst will be responsible for leading discovery, requirements gathering, process analysis, gap assessments, impact analysis, and business readiness activities across digital channels, file-based services, APIs, reporting, liquidity solutions, and payment capabilities. The role will support delivery teams by ensuring requirements are complete, traceable, testable, and aligned with business objectives while driving consistency across regional and cross-functional initiatives. The individual will play a key role in complex transformation programs, platform modernization initiatives, client experience improvements, and regulatory-driven changes while serving as a subject matter expert for Payments and Liquidity products and associated operational workflows." Role Objectives: list of bullet points under Delivery Agile Delivery, Product Ownership, Stakeholder Partnership and Leadership. We need to convert to

• . The headings within Role Objectives are like "Delivery Agile Delivery", "Product Ownership", "Stakeholder Partnership and Leadership". Those could be subheadings but we only need to output

  for main sections. We could keep them as

  maybe but not allowed? Only

  for section headings. We could treat each as a

  but that would be many sections. Better to keep them as

  Responsibilities

  and then inside have subheadings maybe as or

  but not required. The instruction only mandates use

  for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should output only HTML fragment; we can include

  if needed. However to be safe, we can just list the responsibilities as a flat list under

  Responsibilities

  . But we would lose some structure. However the instruction says preserve ALL substantive information; we can keep the substance as list items; subheadings can be omitted as they are not essential? Might be considered losing detail. But we could embed the subheadings as inside list items. Qualifications And Skills: list of bullet points. Additional Requirements: paragraph about hybrid work, accommodation, etc. Let's extract bullet points: From Role Objectives: Delivery Agile Delivery: - Partner with Product Owners and Technology teams throughout the software development lifecycle to clarify requirements, answer functional questions, and support solution design decisions. - Develop and execute testing strategies, test scenarios, test cases, and business validation activities. - Support User Acceptance Testing (UAT), production validation, defect triage, issue resolution, and release readiness activities. - Ensure solutions meet defined business requirements, operational expectations, and control standards before deployment. - Coordinate with Operations, Servicing, Client Support, and training teams to prepare for successful implementation and adoption. Product Ownership: - Lead discovery sessions, stakeholder workshops, interviews, and process reviews to identify business needs, dependencies, gaps, risks, and solution opportunities. - Elicit, document, and manage business requirements, functional requirements, user stories, acceptance criteria, process flows, business rules, decision trees, and use cases. - Translate business objectives and product strategy into actionable requirements that can be executed by agile delivery teams. - Perform current-state and future-state process analysis, identifying opportunities for automation, simplification, control enhancement, scalability, and operational efficiency. - Ensure requirements maintain end-to-end traceability from business objectives through design, testing, implementation, and production support. - Support backlog refinement, sprint planning, story decomposition, dependency management, and delivery readiness activities. - Support initiatives related to domestic payments, international wires, ACH, real-time payments, payment approvals, file-based processing, payment workflows, and exception management. - Support liquidity management capabilities including reporting, cash positioning, balance reporting, notional pooling, cash concentration, intercompany liquidity structures, and forecasting solutions. - Analyze operational impacts, entitlement considerations, approval workflows, account structures, reporting requirements, and client onboarding needs. - Partner with product and operational teams to ensure business requirements adequately address client needs, control requirements, scalability objectives, and servicing considerations. Stakeholder Partnership and Leadership: - Build strong relationships across Product, Technology, Operations, Risk, Compliance, Legal, Data, Sales, and regional stakeholders. - Facilitate alignment across competing priorities while maintaining focus on business outcomes and client value. - Communicate business requirements, impacts, dependencies, risks, recommendations, and delivery updates in a clear and executive-ready manner. - Mentor junior Business Analysts and contribute to best practices, documentation standards, analysis methodologies, and continuous improvement initiatives. - Support executive presentations, business cases, roadmap planning, and strategic initiatives related to Treasury Services transformation. Qualifications And Skills bullet list: - 5+ years of experience in business analysis, product delivery, treasury services, transaction banking, payments, liquidity management, cash management, or related financial services disciplines. - Strong understanding of Treasury Services products, including payments, liquidity management, cash management, reporting, account services, and digital banking capabilities. - Proven experience leading requirements gathering, process analysis, business architecture, solution design support, and agile delivery initiatives. - Experience creating user stories, acceptance criteria, process maps, requirements documentation, business cases, and testing artifacts. - Deep knowledge of Agile delivery methodologies, SDLC processes, UAT execution, release management, and dependency management. - Ability to analyze complex operational processes and translate business needs into scalable, practical solutions. - Strong understanding of regulatory, operational, risk, and control considerations within banking and financial services. - Excellent stakeholder management, communication, facilitation, problem-solving, and analytical skills. - Ability