Technology Product Management Lead Analyst, Vice President

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We have content for About the role (intro paragraph). Responsibilities: many bullet points under "Key Responsibilities" etc. Requirements: maybe "Required Qualifications". Qualifications: maybe "Preferred Qualifications". Skills: maybe "Most Relevant Skills" etc but they say see above; but we can include Skills if there is content. Benefits: they mention benefits: medical, dental & vision coverage; 401(k); life, accident, disability insurance; wellness programs; paid time off packages. Also mention discretionary incentive awards. So we have Benefits content. Pay: they have salary range: $138,720.00 - $208,080.00. So include Pay section. Schedule: they have Time Type: Full time. That's schedule info. So include Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. Remove duplicated lines. Remove application instructions. Remove "Most Relevant Skills Please see the requirements listed above." and "Other Relevant Skills For complementary skills, please see above and/or contact the recruiter." Also remove "Anticipated Posting Close Date", "Automated Processing and AI", EEO statements, etc. We need to preserve all substantive information. So we need to keep the description paragraphs, responsibilities bullet list, required qualifications bullet list, preferred qualifications bullet list, benefits bullet list, pay line, schedule line. We need to format using

headings and

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

  for prose. We need to decide which content goes under which heading. About the role: The initial paragraphs describing role: "The Business Analysis Lead is a senior leadership role...". Could be multiple paragraphs. We'll put that as prose under About the role. Responsibilities: The "Key Responsibilities" section with subheadings: Enterprise Business Analysis & Transformation Leadership, Agile Delivery & Release Management, Enterprise Systems & Integration Analysis, Retail Banking & Servicing Expertise, Estimation, Budgeting & Program Governance, Leadership & Stakeholder Management, AI-Enabled Business Analysis, Risk & Control Management. Each has bullet-like sentences. We'll treat each bullet as

• . Could group under Responsibilities heading with nested lists? Simpler: just a flat list of responsibilities items. We'll extract each sentence that starts with a verb. But we need to preserve all substantive information; we can keep the subheadings as part of list items? Might be okay to keep them as part of
• text. Requirements: Could be "Required Qualifications". We'll put that under Requirements heading (or Qualifications?). The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have both Requirements and Qualifications sections. Likely Requirements = Required Qualifications, Qualifications = Preferred Qualifications. We'll split accordingly. Skills: There's "Most Relevant Skills" and "Other Relevant Skills" but they say see above. Could still include a Skills section with maybe no content? But we should only include section if posting has real specific content. The posting says "Please see the requirements listed above." and "For complementary skills, please see above and/or contact the recruiter." That's not specific content. So we should omit Skills section. Benefits: we have details about benefits. Pay: salary range. Schedule: Time Type: Full time. We must not include placeholder text like "commensurate with experience". Not present. Now craft HTML. Structure:

  About the role

  ... paragraphs ...

  Responsibilities

  • Enterprise Business Analysis & Transformation Leadership: Lead business analysis activities across complex, high-impact Retail Banking and enterprise transformation programs. Partner with business, product, operations, architecture, and technology stakeholders to define strategic solutions aligned with business objectives and target-state operating models. Drive business process reengineering initiatives aimed at improving customer experience, operational efficiency, scalability, and regulatory compliance. Analyze current-state processes, systems, data flows, and customer journeys to identify optimization and modernization opportunities. Develop business cases, requirements strategies, and solution recommendations that support enterprise and business goals.
  • Agile Delivery & Release Management: Lead business analysis activities within Agile and hybrid delivery models supporting large-scale enterprise banking platforms. Collaborate closely with Product Owners, Scrum Masters, Engineering Leads, Architects, and Operations teams to deliver incremental business value through release-based delivery cycles. Manage requirements decomposition from strategic initiatives into epics, features, user stories, and acceptance criteria. Support release planning, backlog prioritization, MVP definition, sprint execution, and go-live readiness activities. Drive impact analysis and requirement traceability across multiple releases, ensuring alignment between business priorities and delivery commitments. Manage dependencies, risks, and scope across complex programs involving multiple teams and applications. Ensure business requirements and customer outcomes are effectively delivered through iterative and continuous delivery practices.
  • Enterprise Systems & Integration Analysis: Lead analysis and solution definition across complex front-end, middle-tier, and backend banking platforms. Demonstrate strong expertise in: API-driven integrations, Service-oriented and microservices architectures, Real-time and batch processing ecosystems, Core banking and customer servicing platforms, CRM and workflow management systems, Enterprise data exchange and integration patterns. Partner with architects and engineering teams to assess system impacts, integration dependencies, interface requirements, and data transformation needs. Evaluate solution alternatives by balancing business objectives, technical constraints, cost considerations, and implementation risk.
  • Retail Banking & Servicing Expertise: Drive initiatives supporting Retail Banking products, customer servicing capabilities, and operational transformation programs. Apply deep understanding of: Assisted servicing channels, Branch servicing operations, Contact center and customer support functions, Digital channel integration, Account servicing and maintenance processes, Customer lifecycle management and fulfillment workflows. Ensure seamless customer and employee experiences across multiple servicing and engagement channels.
  • Estimation, Budgeting & Program Governance: Contribute to project planning, estimation, budgeting, and business case development activities. Support program delivery by assessing requirements complexity, resource needs, project costs, and timeline impacts. Provide leadership with data-driven recommendations regarding scope, priorities, risks, and investment decisions. Establish governance processes that ensure consistency, quality, and traceability across the requirements lifecycle.
  • Leadership & Stakeholder Management: Lead, mentor, and develop a team of Business Analysts across multiple programs and releases. Establish best practices, standards, and governance frameworks for business analysis activities. Influence senior business and technology leaders through strong analytical thinking, communication, and stakeholder management skills. Facilitate executive-level discussions, decision-making forums, and strategic planning sessions.
  • AI-Enabled Business Analysis: Champion the adoption of AI-powered tools and intelligent automation across the business analysis lifecycle. Leverage AI capabilities to improve: Requirements elicitation and documentation, User story creation and backlog refinement, Process mapping and workflow analysis, Impact assessment and traceability, Estimation and planning activities, Executive reporting and stakeholder communications. Drive productivity improvements by incorporating AI-assisted analysis techniques into day-to-day delivery practices.
  • Risk & Control Management: Proactively identify business, operational, technology, and delivery risks. Assess impacts of business and technology decisions within complex enterprise environments. Ensure adherence to regulatory, compliance, governance, and control requirements. Demonstrate sound risk management practices while maintaining transparency and accountability throughout program execution.

  Requirements

  • 10+ years of Business Analysis experience with significant experience leading enterprise-scale banking initiatives.
  • Strong domain expertise in Retail Banking, customer servicing, and banking operations.
  • Proven experience working within complex enterprise banking platforms involving multiple interconnected systems and applications.
  • Demonstrated experience delivering large transformation initiatives using Agile, Scrum, SAFe, or hybrid delivery methodologies.
  • Deep understanding of release-based delivery models, backlog management, and iterative product development.
  • Strong experience in API-based integrations, backend processing platforms, batch ecosystems, and enterprise architecture concepts.
  • Experience leading requirements management across multiple concurrent releases and cross-functional teams.
  • Expertise in estimation, budgeting support, business case development, and resource planning.
  • Proven leadership experience managing and mentoring Business Analysts.
  • Excellent stakeholder management, communication, negotiation, and influencing skills.

  Qualifications

  • Experience in core banking modernization and enterprise reengineering initiatives.
  • Knowledge of customer servicing platforms, CRM solutions, workflow management systems, and digital banking ecosystems.
  • Experience with microservices, cloud-native architectures, event-driven integration patterns, and API management platforms.
  • Hands-on experience utilizing Generative AI tools to improve business analysis and delivery outcomes.
  • CBAP, PMI-PBA, SAFe, Agile, Scrum, or equivalent certification preferred.
  • Bachelor's Degree in Business, Technology, Computer Science, Engineering, Finance, or related discipline.

  Benefits

  • Medical, dental & vision coverage
  • 401(k)
  • Life, accident, and disability insurance
  • Wellness programs
  • Paid time off packages, including planned time off (vacation), unplanned time off (sick leave), and paid holidays
  • Discretionary and formulaic incentive and retention awards (for eligible employees)

  Pay

  Primary Location Full Time Salary Range: $138,720.00 - $208,080.00

  Schedule

  Time Type: Full time

  We need to ensure we didn't include any boilerplate like "Job Family Group: Technology". Remove that. Also remove "Primary Location: Irving Texas United States". That's location info but not under any heading; maybe we could include location in About the role? But instructions: do not put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Location is minor metadata; we could fold into About the role paragraph or a short p. But we already have About the role paragraph; we could add location there. However we must preserve ALL substantive information; location is substantive. So we should include it somewhere. Could add a short

  after About the role: "Primary Location: Irving, Texas, United States." Or incorporate into About the role paragraph. Let's add a separate short p under About the role? But we already used

  for prose; we could have multiple

  under same heading. That's fine. Thus after About the role heading, we can have two

  s: first the description, second the location. Similarly, we might include "Job Family Group: Technology" and "Job Family: Technology Product Management" as minor metadata; could fold into a short p as well. But maybe we can drop them as they are not critical? The instruction: "fold minor metadata into a short

  or drop it." So we could include them in a short p. But we need to preserve ALL substantive information; is job family substantive? Probably yes but minor. We'll include a short p: "Job Family Group: Technology; Job Family: Technology Product Management." We also have "Time Type: Full time" already in Schedule. Good. We also have "Anticipated Posting Close Date: Sep 16, 2026" - that's metadata; could be folded into a short p but maybe we can drop as it's not essential? The instruction says preserve ALL substantive information; posting close date is substantive for applicants. So we should include