IT Business Analyst, Assistant Vice President

We need to output HTML fragment with sections: About the role? The posting includes "Who We Are Looking For", "Why This Role Is Important to Us", "What You Will Be Responsible For", "What We Value", "Education & Preferred Qualifications", "Salary Range", "Benefits" (the paragraph about benefits), maybe "About State Street" but that's boilerplate? It's about company description; we should remove boilerplate like EEO, legal, etc. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also "About State Street" maybe considered company overview, not boilerplate? It's somewhat generic but could be kept? The instruction says preserve ALL substantive information; do not invent or summarize away detail. The "About State Street" is substantive about company; but it's maybe considered boilerplate? It's not EEO or legal; it's a description of the company. Might be okay to keep as a section? However they said prefer a few substantive sections over many thin ones. Could combine company description into a brief paragraph under maybe "About the Company". But they said use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list "About the Company". So we should stick to those headings only if content exists. We have content for: About the role (maybe "Who We Are Looking For" and "Why This Role Is Important to Us" combined). Responsibilities (What You Will Be Responsible For). Requirements (Education & Preferred Qualifications includes required qualifications). Qualifications (maybe separate? but we can combine). Skills (What We Value). Benefits (the paragraph about benefits). Pay (Salary Range). Schedule not present, so omit. Also we might have a short paragraph for metadata like Job ID etc - we should drop or fold into short p. We'll not include Job ID. We must not repeat job title as heading. So no heading for the title. We need to output only HTML fragment, using

for section headings,

• for lists,

  for prose. We need to preserve all substantive information; not invent or summarize away detail. So we need to include details from each section. Let's extract content. **Who We Are Looking For** paragraph: "We are seeking an experienced IT Business Analyst to support enterprise Legal, Governance, and Security application platforms and associated data ecosystems. This role will focus on translating legal operations, eDiscovery, governance, and security workflows into scalable, integrated technology solutions. The ideal candidate brings strong experience across Legal Operations platforms (e.g., ONIT – matter & spend management), eDiscovery solutions (e.g., Everlaw, Vanderbilt – legal hold/records management), Governance platforms (e.g, Diligent Boards), and Security/Access platforms (e.g, AccessIt, Viakoo), along with expertise in business analysis artifacts, data analysis, and cross-functional delivery." **Why This Role Is Important to Us**: paragraphs: "Legal, Security, and Compliance teams operate across multiple SaaS platforms managing matters, litigation, governance, access control, and regulatory data. Ensuring seamless integration, accurate data flow, and efficient workflows is critical for operational effectiveness, compliance, and audit readiness. This Role Is Essential In Enabling End-to-end legal and security process digitizationStandardized business process documentation and traceabilityData consistency across integrated platformsImproved reporting, analytics, and regulatory compliance" Note there is missing spaces; we should preserve as is but maybe we can keep the text; it's a bit garbled but we must not alter meaning. We'll keep as is. **What You Will Be Responsible For**: a long list of responsibilities. We need to turn into

  • . The text includes multiple sentences; we can break into bullet points per sentence or per clause. We'll preserve all details. Let's parse: - Business Analysis & Solution Delivery - Capture, analyze, and document business, functional, and technical requirements - Translate legal workflows (matter management, legal hold, eDiscovery) and security processes (access control, monitoring) into: - User stories - Functional specifications - Acceptance criteria - Create process flow diagrams (current state / future state) using Visio or similar tools - Develop and maintain: - Business Requirement Documents (BRDs) - Functional Specification Documents (FSDs) - Test Plans, Test Cases, and UAT documentation - Support Agile ceremonies (backlog grooming, sprint planning, reviews) - Coordinate and support testing cycles, defect tracking, and release validation - Analyze and resolve functional and data-related issues across systems - Systems & Data Integration - Support integration across enterprise platforms including Legal Operations, Governance and Global Security / Access - Develop and maintain data mapping documents across systems and interfaces - Define source-to-target mappings and transformation rules - Validate and reconcile data using SQL and formats such as JSON and XML - Ensure data accuracy, lineage, and consistency across integrated platforms - Troubleshoot and resolve data integration and interface issues - Project Management & Coordination - Plan and coordinate cross-functional Legal and Security initiatives - Track project milestones, dependencies, risks, and deliverables - Facilitate collaboration across: - Business stakeholders - Engineering teams - Vendor partners - Provide status reporting, risk escalation, and executive-level updates - Governance, Risk & Compliance Alignment - Ensure solutions align with legal, regulatory, and security standards - Support audit readiness through strong documentation and traceability - Maintain process and data governance practices - Partner with compliance and security teams to address control and risk requirements - Stakeholder Engagement - Act as the primary liaison for Legal and Security application needs - Collaborate with: - Legal Operations & Compliance - Security & Risk teams - Data & Engineering teams - External vendors - Communicate complex requirements clearly to both technical and business audiences We'll output as a single
    with
    • items; nested lists maybe? The instruction: Use
      • for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can keep flat. However nested lists would be
        • ...
          • ... which is still using
            • . Might be okay. But to keep simple, we can flatten each bullet as a separate
            • and include sub-points as part of the same sentence. That might lose some structure but still preserve info. Better to keep nested lists to preserve hierarchy. We'll do nested
              • . **What We Value**: bullet list: "Strong analytical and problem-solving capabilities", "Expertise in creating process flows, data mappings, and structured documentation", "Ability to translate business processes into system and data requirements", "Strong stakeholder communication and coordination skills", "Experience working in regulated, audit-driven environments". We'll output as
                • . **Education & Preferred Qualifications**: includes Education bullet and Required Qualifications and Preferred Qualifications and Nice To Have. We need to preserve all. We'll structure maybe as
                  • for each item. Education: "Bachelor’s degree in Business, Information Systems, Computer Science, or related field" Required Qualifications: list: - 7+ years of experience in Business Analysis, Application Delivery, or Product Ownership - Experience working with enterprise platforms across: - Legal Operations: Legal Matter management, Spend Management - eDiscovery & Records Management: Litigations, Investigations, Legal Holds - Governance: Board Management, GRC - Security & Access Management: Access Monitoring, Identity Mgmt, Device Monitoring - Strong experience with: - Process modeling tools (Visio or equivalent) - Test management (test plans, test cases, UAT coordination) - Data mapping and data analysis - Proficiency in SQL for data validation and reconciliation - Understanding of APIs, integrations, and data formats (JSON/XML) - Experience with Agile tools such as Jira and Confluence Preferred Qualifications: - Experience in Legal, Compliance, or Financial Services environments - Familiarity with: - Legal data constructs (matters, contracts, legal hold records) - Security workflows (access control, monitoring systems) - Experience with data visualization tools (Power BI, Tableau) - Exposure to data governance and audit/compliance frameworks - Knowledge of ServiceNow and Change Management process Nice To Have: - Familiarity with security and risk tools (e.g., IAM, CyberArk, SIEM platforms like Splunk/Datadog) - Exposure to AI/ML use cases in legal We'll keep as nested lists. **Salary Range**: "$80,000 - $140,000 Annual". Also note about location variation; we should preserve that sentence: "The range quoted above applies to the role in the primary location specified. If the candidate would ultimately work outside of the primary location above, the applicable range could differ." We'll include as

                    . **Benefits**: paragraph about benefits: "Employees are eligible to participate in State Street’s comprehensive benefits program, which includes: our 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 our Employee Assistance Program; incentive compensation including eligibility for annual performance-based awards (excluding certain sales roles subject to sales incentive plans); and, eligibility for certain tax advantaged savings plans. For a full overview, visit https://hrportal.ehr.com/statestreet/Home." We'll output as

                    . We should also include maybe a short paragraph for "About State Street"? It's company description; but not in the prescribed headings. Could we include as a section? The instruction: "Use

                    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exhaustive, but we should prefer those headings. It didn't forbid other headings, but says prefer a few substantive sections over many thin ones. Including About State Street might be okay but could be considered boilerplate? It's not EEO or legal; it's a description of the company. Might be considered substantive. However the instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is not that. So we could keep it. But to stay safe, maybe we omit it because it's not requested and could be considered filler. The instruction: "Prefer a few substantive sections over many thin ones." Adding another section may be thin. I'd omit. Also we need to drop duplicated lines, application instructions, etc. We'll not include "Job ID: R-790399". Also drop "Read our CEO Statement", "Discover more information on jobs at StateStreet.com/careers", "Job Application Disclosure", etc. Now construct HTML. We'll start with

                    About the role

                    then

                    combine Who We Are Looking For and Why This Role Is Important to Us? Could be two paragraphs. We'll keep as two

                    under that heading. Then

                    Responsibilities

                    then
                    with nested lists. Then

                    Requirements

                    maybe combine Education & Required Qualifications? But we have separate headings for Requirements and Qualifications. The instruction list includes Requirements and Qualifications separate. We could put Education under Requirements, and Required Qualifications also under Requirements? Or we could have Requirements for required qualifications, Qualifications for preferred/nice-to-have. Let's follow: Requirements = Required Qualifications (including education?). Qualifications = Preferred Qualifications + Nice To Have. But Education is separate; maybe we put Education under Requirements as well. We'll decide. We'll do:

                    Requirements

                    Education