Transaction Management Implementation Analyst, Assistant Vice President

We need to output only HTML fragment, using

for section headings,

• for lists,

  for prose. No job title heading. No Job ID. Remove boilerplate: EEO, legal, application instructions, etc. Keep substantive info. We need sections: About the role? The posting includes "Who We Are Looking For", "Key Responsibilities", "Why this role is important to us", "What You Will Be Responsible For", "What We Value", "Education & Preferred Qualifications", "Salary Range", "Benefits", "About State Street". Also maybe "What You Will Be Responsible For" duplicates responsibilities but we can combine. We must only include sections when posting has real specific content. We have content for many. We need to format headings exactly as: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map our content to those headings. Probably we should use those exact headings. If a section doesn't have content, omit. Thus we need to decide which headings to use: About the role (intro), Responsibilities (key responsibilities + what you will be responsible for), Requirements (maybe experience/skills), Qualifications (education), Skills (maybe specific technical skills), Benefits, Pay (salary range), Schedule (if any travel mention? Could be schedule? Not really schedule; maybe we can omit Schedule if no specific schedule info). The posting mentions domestic/international travel may be required - that could be considered schedule? But schedule heading is for work schedule (e.g., full-time, part-time). Not present. Better omit Schedule. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay: salary range present. Benefits: benefits described. So include Pay and Benefits. Now we need to extract content. Let's parse: Who We Are Looking For: description of role, team, purpose. That's About the role. Key Responsibilities: list bullet points. Why this role is important to us: prose. What You Will Be Responsible For: more responsibilities (maybe duplicate). We'll combine into Responsibilities. What We Value: list of qualifications/experience/skills. Education & Preferred Qualifications: education and experience. Salary Range: Pay. Benefits: description. About State Street: company overview (could be part of About the role? maybe separate but we can incorporate into About the role or maybe omit as boilerplate? It's not EEO; it's generic but still substantive about company. Could be included under About the role. We must preserve all substantive information; not invent or summarize away detail. So we need to keep details. We need to avoid duplication but can combine similar content. Let's craft sections:

  About the role

  ... combine Who We Are Looking For, Why this role is important to us, About State Street maybe.

  But we must not repeat job title as heading. Already not. We need to ensure we don't include boilerplate like EEO, legal, Job ID, application instructions, etc. Now list responsibilities: combine Key Responsibilities and What You Will Be Responsible For. List items: - Oversee due diligence activities to ensure a thorough understanding of client requirements and operational environments. - Identify gaps in current operating models and drive the design of client solutions, including trade and architecture flows, operational processes, and business system functionality. - Manage the implementation and onboarding plan, including project timelines, conversion strategies, and post-go-live activities for client onboarding and implementation projects. - Analyze post go-live change requests, collaborating with all stakeholders to define solutions, supervise testing, and oversee deployment in the live production environment. - Drive the delivery of cross-operations, high priority projects across all typical project phases. - Work with external clients and portfolio managers to configure the Alpha platform for client-specific workflows. - Project initiation and scoping – including plan definition and managing realistic expectations for successful delivery with project stakeholders. - Manage business analysis and requirements definition. - Support ongoing project management – including progress monitoring, reporting and quality assurance throughout the project. - Build and manage strong relationships with project sponsors and stakeholders in Operations, Technology and the business, understanding competing priorities across these groups. - Work with Operations business units to assess and streamline processes in order to mitigate risk, cost or service issues and generate efficiencies. - Collaborate with other teams to share approaches, develop best practices and improve team capabilities to successfully migrate clients. - Domestic and/or international travel may be required. Now Requirements/Qualifications/Skills: we have "What We Value" list and "Education & Preferred Qualifications". We need to map to headings: Requirements, Qualifications, Skills. Possibly combine. We could put Requirements: 5+ years industry experience with front, middle, back office integration, functionality, electronic trading platforms; strong understanding of Transaction Management Middle Office services; subject matter expertise in standard financial services static data as it applies to middle office trade processing; strong knowledge of financial instruments and asset classes such as Equities, Fixed Income, Derivatives, structured products including TBAs and Repos; in-depth understanding and prior experience with industry utilities such as DTCC CTM, DTCC Alert, FX Connect, other Middle Office vendor applications, and messaging protocols like XML and SWIFT; proven history of understanding and analyzing complex client use cases and large data sets; ability to create visual dashboards using tools such as Microsoft PowerBI; expertise in Power Query for data transformation, cleansing, preparation, and integration from multiple sources and formats; ability to analyze large data setups using Microsoft Co-Pilot is highly desirable; ability to interpret client requirements and translate those requirements into State Street-specific data configuration tasks; exceptional communication, problem-solving, and analytical skills; attention to detail and organization – able to independently troubleshoot and gather supporting evidence; ability to work on multiple projects concurrently and prioritize work accordingly; expertise in MS Office, including MS Visio, Project, and PowerPoint; competency in SDLC & Agile Methodology and tools (i.e., JIRA, Rally, RTC). Qualifications: BS degree in Business, Finance, Economics or Engineering; 5+ years of industry experience with front, middle, and back office integration, functionality, and electronic trading platforms (duplicate). Could combine. Skills: maybe the technical skills like PowerBI, Power Query, Co-Pilot, MS Office, etc. But we already included many. Given instruction to prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section maybe "Requirements". But headings list includes Requirements, Qualifications, Skills. We could use all three if we have content. Let's allocate:

  Requirements

  • 5+ years of industry experience with front, middle, and back office integration, functionality, and electronic trading platforms
  • Strong understanding of Transaction Management Middle Office services and operating models; subject matter expertise in standard financial services static data as it applies to middle office trade processing
  • Strong knowledge of financial instruments and asset classes such as Equities, Fixed Income, Derivatives, and structured products including TBAs and Repos
  • In-depth understanding and prior experience with industry utilities such as DTCC CTM, DTCC Alert, FX Connect, other Middle Office vendor applications, and messaging protocols like XML and SWIFT
  • Proven history of understanding and analyzing complex client use cases and large data sets; ability to create visual dashboards using tools such as Microsoft PowerBI
  • Expertise in Power Query for data transformation, cleansing, preparation, and integration from multiple sources and formats
  • Ability to analyze large data setups using Microsoft Co-Pilot is highly desirable
  • Ability to interpret client requirements and translate those requirements into State Street-specific data configuration tasks
  • Exceptional communication, problem-solving, and analytical skills; attention to detail and organization – able to independently troubleshoot and gather supporting evidence
  • Ability to work on multiple projects concurrently and prioritize work accordingly
  • Expertise in MS Office, including MS Visio, Project, and PowerPoint
  • Competency in SDLC & Agile Methodology and tools (i.e., JIRA, Rally, RTC)

  Qualifications

  • BS degree in Business, Finance, Economics or Engineering
  • 5+ years of industry experience with front, middle, and back office integration, functionality, and electronic trading platforms
  But that duplicates experience. Could keep but it's okay. Alternatively we could merge Qualifications into Requirements and omit Qualifications heading. But instruction says prefer few sections; we could omit Qualifications if content is thin. However we have BS degree which is substantive. Could put under Requirements as well. But we need to follow headings list; we can still include Qualifications if we have content. Skills: maybe we could list specific technical skills: PowerBI, Power Query, Co-Pilot, MS Office, XML, SWIFT, DTCC utilities, etc. But many already in Requirements. Could create Skills heading for those. Let's decide: We'll have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Omit Skills if redundant. Or we could include Skills for technical tools. Given we have many technical skills, we could put them under Skills. Let's allocate: Requirements: experience years, understanding of middle office, knowledge of instruments, experience with utilities, ability to analyze data sets, interpret requirements, communication skills, ability to manage multiple projects. Qualifications: BS degree. Skills: expertise in PowerBI, Power Query, Co-Pilot, MS Office (Visio, Project, PowerPoint), SDLC/Agile tools (JIRA, Rally, RTC), messaging protocols XML/SWIFT, etc. But we need to avoid duplication. Let's think. Better: Use Requirements for experience and knowledge; Qualifications for education; Skills for specific tools and methodologies. Let's craft: Requirements: - 5+ years of industry experience with front, middle, and back office integration, functionality, and electronic trading platforms - Strong understanding of Transaction Management Middle Office services and operating models; subject matter expertise in standard financial services static data as it applies to middle office trade processing - Strong knowledge of financial instruments and asset classes such as Equities, Fixed Income, Derivatives, and structured products including TBAs and Repos - In-depth understanding and prior experience with industry utilities such as DTCC CTM, DTCC Alert, FX Connect, other Middle Office vendor applications, and messaging protocols like XML and SWIFT - Proven history of understanding and analyzing complex client use cases and large data sets - Ability to interpret client requirements and translate those requirements into State Street-specific data configuration tasks - Exceptional communication, problem-solving, and analytical skills; attention to detail and organization – able to independently troubleshoot and gather supporting evidence - Ability to work on multiple projects concurrently and prioritize work accordingly Qualifications: - BS degree in Business, Finance, Economics or Engineering Skills: - Ability to create visual dashboards using tools such as Microsoft PowerBI - Expertise in Power Query for data transformation, cleansing, preparation, and integration from multiple sources and formats - Ability to analyze large data setups using Microsoft Co-Pilot is highly desirable - Expertise in MS Office, including MS Visio, Project, and PowerPoint - Competency in SDLC & Agile Methodology and tools (i.e., JIRA, Rally, RTC) Now Benefits: list from description. Benefits: - retirement savings plan (401K) with company match - insurance coverage including basic life, medical, dental, vision, long-term disability, and other optional additional coverages - paid-time off including vacation, sick leave, short term disability, and family care responsibilities - access to Employee Assistance Program - incentive compensation including eligibility for annual performance-based awards (excluding certain sales roles subject to sales incentive plans) - eligibility for certain tax advantaged savings plans Pay: - Salary Range $80,000 - $140