SDC Senior Business Systems Analyst, Banking Platforms

We need to output HTML fragment with sections: About the role? The posting includes description. We need headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. So we need to extract substantive info. Let's parse the posting: Location: Dallas, Alpharetta (two locations). At EY, we’re all in to shape your future... The Opportunity As a Senior Business Systems Analyst, you will play a key role... This is description. Then "Your Key Responsibilities" list many bullet-like sentences. Then "Banking Platform Experience" with details. Then "Relevant Platform Experience" with examples. Then "Preferred Additional Experience" Then "To Qualify for the Role, You Must Have" list of qualifications. Then "Banking Domain Knowledge" Then "What We Look For" Then "What We Offer You At EY" includes compensation and benefits package, base salary range for this job with location-based ranges, total rewards includes medical/dental, pension/401(k), paid time off, flexible vacation policy, etc. Then "Are you ready..." etc (call to action) - we should remove application instructions. Also there is EEO statement etc - remove. Thus sections: - About the role: could be the introductory paragraph describing opportunity. - Responsibilities: the "Your Key Responsibilities" list. - Requirements/Qualifications: maybe combine? The posting has "To Qualify for the Role, You Must Have" which is qualifications. Also "Banking Platform Experience" and "Relevant Platform Experience" and "Preferred Additional Experience" could be part of Requirements or Skills. We need to decide sections. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content. We have content for About the role (intro). Responsibilities (list). Requirements (maybe the qualifications list). Qualifications (maybe same as Requirements? Could split but we need to avoid duplication). Skills (maybe the skills like analytical, problem-solving, facilitation, etc). Benefits (medical/dental, pension/401(k), paid time off, flexible vacation). Pay (salary ranges). Schedule (maybe not present; no explicit schedule info). So we omit Schedule. We must not create sections with filler like "not specified". So we omit Schedule. Now we need to preserve all substantive information, not invent or summarize away detail. Must not lose details. We need to format using

for section headings. Use

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

  for prose. We need to ensure we don't repeat job title as heading. We need to output only HTML fragment. Let's extract content precisely. First, About the role: The paragraph after "The Opportunity". It says: "The Opportunity As a Senior Business Systems Analyst, you will play a key role in delivering business and technology transformation initiatives for Banking & Capital Markets clients. You will lead analysis activities for banking platform implementation, modernization, migration, integration, and enhancement initiatives, translating business needs into implementable platform requirements and partnering with product owners, platform vendors, architects, developers, testers, data teams, operations professionals, and client stakeholders across the delivery lifecycle. This role requires banking domain knowledge, hands-on banking platform experience, structured business analysis, technical understanding, and delivery discipline" We can keep that as prose in

  . Maybe also include location? The location line "Location: Dallas, Alpharetta" could be included as metadata in a short

  . The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include location in a short

  before About the role. Now Responsibilities: The list under "Your Key Responsibilities". It's a series of sentences each starting with a verb. We need to put each as

• . Let's extract them: - Lead requirements elicitation and analysis for banking platform projects and transformation initiatives. - Facilitate stakeholder interviews, discovery sessions, requirements workshops, fit-gap assessments, process-design sessions, platform demonstrations, and solution-validation meetings. - Document current-state and future-state processes, functional and nonfunctional requirements, user stories, use cases, acceptance criteria, business rules, platform configurations, data flows, and system interactions. - Translate banking business and operational requirements into detailed functional specifications that platform, engineering, integration, and testing teams can implement. - Evaluate requirements for clarity, completeness, feasibility, traceability, dependencies, and alignment with business objectives and platform capabilities. - Perform fit-gap analysis across business requirements, out-of-the-box platform capabilities, configurable features, customization requirements, and integration dependencies. - Lead business and system analysis activities for core banking modernization, digital banking transformation, platform replacement, product migration, and banking technology transformation programs, translating objectives into platform capabilities, functional requirements, and target-state operating processes. - Define and document requirements for platform migration and data conversion initiatives, including source-to-target mapping, business rules, reconciliation requirements, data-validation controls, cutover planning, migration testing, and post-conversion verification. - Analyze and document system integration requirements across core banking platforms, digital channels, payment hubs, lending systems, customer onboarding platforms, CRM systems, data warehouses, and downstream reporting applications. - Support banking platform implementation and modernization programs by evaluating platform capabilities, identifying configuration versus customization requirements, and recommending scalable solutions aligned with business, operational, and technology objectives. - Partner with platform vendors, product specialists, solution architects, engineering teams, and business stakeholders to evaluate and validate proposed solutions. - Analyze APIs and interfaces, including REST services, JSON or XML payloads, validations, error handling, integration dependencies, and business-process impacts. - Perform source-to-target data mapping, conversion analysis, data-lineage analysis, data validation, reconciliation, migration support, and implementation-readiness activities. - Manage requirements traceability throughout discovery, design, development, testing, conversion, implementation, and post-production support. - Support backlog refinement, estimation, sprint planning, release readiness, defect triage, production validation, and continuous-improvement activities. - Define business scenarios, acceptance criteria, test conditions, and expected outcomes; support SIT, UAT, regression testing, and end-to-end testing. - Mentor junior analysts, review deliverables for quality and completeness, and contribute to reusable templates, accelerators, and business-analysis best practices. We'll put each as
• inside
  . Now Requirements: The "To Qualify for the Role, You Must Have" list. Let's extract: - Bachelor’s degree in Computer Science, Information Systems, Engineering, Business, Finance, or a related discipline. - At least 3 years of experience as a Business Analyst, Business Systems Analyst, Technical Business Analyst, Product Analyst, or comparable techno-functional professional. - Hands-on banking platform implementation, migration, modernization, conversion, or integration experience. - Strong understanding of the Software Development Life Cycle and Agile/Scrum delivery methodologies. - Experience creating business requirements, functional specifications, user stories, use cases, process flows, acceptance criteria, interface specifications, data mappings, and traceability artifacts. - Experience analyzing APIs, integrations, data flows, system interactions, validations, and business rules. - Experience supporting SIT, UAT, regression testing, defect triage, release readiness, and production implementation activities. - Strong analytical, problem-solving, facilitation, written communication, presentation, and stakeholder-management skills. - Experience working with cross-functional, distributed, offshore, and vendor teams. We'll put each as
  • . Now Qualifications: Could be the "Banking Domain Knowledge" section? Or maybe "Banking Platform Experience" etc. But we already used Requirements for qualifications. The heading "Qualifications" could be used for "Banking Platform Experience" and "Relevant Platform Experience" and "Preferred Additional Experience". However we need to avoid duplication. Let's think: The posting has sections: Banking Platform Experience, Relevant Platform Experience, Preferred Additional Experience, Banking Domain Knowledge, What We Look For. These could be considered as Skills or Qualifications. We have headings: Skills, Benefits, Pay. We could put Skills for the skill-based items (analytical, problem-solving etc) but we already put those in Requirements. Maybe better to treat Requirements as the mandatory qualifications, and Skills for the skillset (analytical, problem-solving etc). But we already included those skills in Requirements list. Could split: Requirements list includes education, experience, etc. Skills list includes analytical, problem-solving, facilitation, written communication, presentation, stakeholder-management skills, experience working with cross-functional teams etc. However the posting lumps them together. Given the instruction to prefer a few substantive sections over many thin ones, we might combine Requirements and Qualifications into one section called "Requirements". But we have both headings available; we need to decide which to use. We could use "Requirements" for the mandatory qualifications (education, experience, etc.) and "Skills" for the skill-based abilities (analytical, problem-solving, etc.) and "Benefits" for benefits, "Pay" for salary. But we also have "Banking Platform Experience" etc. That could be part of Requirements as well (experience). Might be redundant. Let's see if we can create sections: - About the role (intro) - Responsibilities (list) - Requirements (education, experience, domain knowledge) - Skills (analytical, problem-solving, facilitation, communication, presentation, stakeholder management, cross-functional team experience) - Benefits (medical/dental, pension/401(k), paid time off, flexible vacation policy, holidays, etc.) - Pay (salary ranges) We need to ensure we don't lose any substantive info: Banking Platform Experience details, Relevant Platform Experience examples, Preferred Additional Experience, Banking Domain Knowledge, What We Look For. We could incorporate those into Requirements or Skills as appropriate. Let's extract Banking Platform Experience details: "Candidates must have hands-on experience supporting one or more banking platform implementation, modernization, migration, integration, conversion, or enhancement initiatives. General awareness or conceptual understanding of banking platforms alone is not sufficient. Relevant experience should include one or more of the following: Banking platform requirements gathering, discovery, fit-gap analysis, solution-design support, configuration analysis, testing, implementation, and production support. Platform migration, conversion, and data-transformation initiatives, including source-to-target mapping, reconciliation, cutover planning, migration testing, and post-conversion validation. API and integration analysis involving banking platforms, digital channels, payment systems, lending systems, customer onboarding solutions, CRM platforms, data warehouses, and downstream applications. Platform modernization, digital transformation, product migration, core replacement, platform consolidation, or banking technology transformation programs." That's essentially experience details; could be part of Requirements. Relevant Platform Experience: list of platforms: FIS Profile, FIS Systematics, Temenos Transact (T24), Infosys Finacle, Fiserv Finxact, Backbase, Alkami, NCR Digital One, ACI Worldwide Payment Hub, Volante, FIS Open Payments Framework, Loan IQ or comparable platforms. Preferred Additional Experience: Cloud-based banking modernization, API-led architecture, microservices, event-driven integration, or platform-transformation programs. Platform selection, vendor assessment, proof-of-concept, product conversion, or large-scale implementation programs. Banking consulting, system integration, managed services, or large transformation programs. Banking Domain Knowledge: Working knowledge of banking products, operational processes, risks, controls, and stakeholders is required. Relevant experience may include retail banking, commercial banking, payments, deposits, lending, customer onboarding, account servicing, treasury services, financial crime and regulatory compliance, or capital markets. Banking domain knowledge should complement, not replace, hands-on banking platform implementation experience. What We Look For: description of techno-functional professionals. We could incorporate What We Look For into Skills or maybe a separate section but we have limited headings. Could put under Skills as narrative. But we need to avoid filler. Let's decide to create sections: - About the role (intro) - Responsibilities