Quantitative Risk, Assistant Vice President

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Why this role is important to us" maybe part of About the role? The posting includes "Who We Are Looking For" then description, then "Why this role is important to us", then "What You Will Be Responsible For", then "What We Value", then "Education And Preferred Qualifications", then "Salary Range", then benefits description, then "About State Street", then EEO etc. We need to map to sections. We need to decide which sections to include: - About the role: could combine "Who We Are Looking For" and "Why this role is important to us" maybe as About the role. Must have substantive content. We'll include a

About the role

with paragraphs describing role purpose. - Responsibilities: from "What You Will Be Responsible For" bullet list (actually sentences separated by periods). We'll need to convert to

• items. Each sentence is a responsibility. We'll split by periods? Better to keep each bullet as a responsibility. The text includes many responsibilities separated by periods. We'll create list items for each distinct responsibility. - Requirements: maybe combine "Education And Preferred Qualifications" and "What We Value"? Actually "What We Value" seems like skills/attributes. Could be Skills section. Requirements could be education and experience. Qualifications could be preferred qualifications. But we have to avoid duplication. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which to include based on content. We have content for: - About the role: yes. - Responsibilities: yes. - Requirements: maybe the core requirements: "Bachelor’s degree in a quantitative or related discipline... Three or more years of relevant experience..." etc. That's education and experience. Could be Requirements. - Qualifications: maybe "Preferred Qualifications" etc. Could be Qualifications. - Skills: "What We Value" includes analytical thinking, problem solving, communication, etc. That's skills. - Benefits: yes, description of benefits. - Pay: Salary Range $110,000 - $177,500 Annual. - Schedule: not mentioned. So we should not include Schedule. We must not include sections with filler like "commensurate with experience". Pay is specific, so include Pay. We must not repeat job title. Must not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can reformat into HTML. Must not omit any substantive info. That is a lot. We need to ensure we include all details from sections we include. We must not include boilerplate like EEO, About State Street, etc. Those are boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO paragraph, About State Street, etc. Also remove "Discover more information on jobs at StateStreet.com/careers Read our CEO Statement Job Application Disclosure". Also remove the Massachusetts lie detector test disclosure. Also remove "Job ID: R-797909". Also remove "As an Equal Opportunity Employer..." etc. We must keep the substantive content: Who We Are Looking For, Why this role is important to us, What You Will Be Responsible For, What We Value, Education And Preferred Qualifications, Salary Range, Benefits description. We need to ensure we don't lose any detail from those sections. Let's extract the substantive paragraphs. Original text: Who We Are Looking For This role is an AML Transaction Monitoring Lead Analyst responsible for the continued design, development, testing, implementation, and ongoing monitoring of suspicious activity monitoring models and analytical solutions within the Financial Crimes Compliance function. The successful candidate will combine quantitative and analytical expertise with practical knowledge of AML transaction monitoring, financial products, customer activity, and regulatory expectations. The role requires hands-on experience in data analysis or data modeling and the ability to translate AML typologies and business risks into clear, scalable monitoring approaches. You will help develop effective models, methods, features, and proofs of concept; evaluate data and technology solutions; and document, monitor, and report model performance to key stakeholders. You will also partner with business units, AML subject matter experts, data stewards, technology teams, and operational stakeholders to understand customer and transaction journeys across multiple lines of business and align business priorities with Financial Crimes Compliance requirements. Why this role is important to us The team plays an important role in strengthening the organization’s ability to identify, assess, and manage financial crime risk. In this role, you will support the development of practical, transparent, and scalable AML monitoring solutions; coordinate across global stakeholders; and help ensure that model and analytical deliverables are well controlled, clearly documented, and fit for purpose. What You Will Be Responsible For Support AML and business stakeholders in the design, development, testing, implementation, documentation, and enhancement of suspicious activity monitoring models and analytical solutions.Perform model owner or model lead responsibilities, including development documentation, implementation planning, change governance, performance assessment, and ongoing monitoring.Translate AML typologies, regulatory red flags, business risks, and operational requirements into model features, scenario logic, user stories, and analytical specifications.Conduct data exploration, profiling, feature analysis, segmentation, threshold or parameter assessment, testing, and results interpretation using appropriate quantitative techniques.Assess model effectiveness, limitations, assumptions, and performance; develop metrics and evidence to support model governance, challenge, validation, audit, and regulatory review.Partner with business, operations, investigations, KYC, sanctions, risk assessment, data governance, model risk management, and technology teams to identify appropriate data sources and monitoring solutions.Drive process efficiency and investigative effectiveness through workflow analysis, analytical tool design, automation, and proof-of-concept development.Communicate complex analytical findings, risks, and recommendations clearly to technical and non-technical stakeholders, including senior management.Maintain high-quality, auditable documentation and support timely remediation of identified model, data, or control issues.Provide guidance and technical leadership to analysts and project teams and contribute to the development of consistent AML modeling standards and practices. What We Value Strong analytical thinking, problem solving, research, and quantitative reasoning skills.Solid understanding of AML transaction monitoring concepts, suspicious activity typologies, customer and transaction risk, and the broader financial crime compliance framework.Ability to connect business domain knowledge with data, model design, and monitoring outcomes across financial products and services.Ability to produce high-quality work products under regulatory, audit, governance, or management deadlines.Strong written and verbal communication skills, with the ability to explain technical concepts and analytical results in clear business language.Demonstrated ownership, sound judgment, attention to detail, and the ability to negotiate, influence, and build consensus across a complex global organization.Ability to manage multiple priorities and work effectively with cross-functional and geographically distributed teams. Education And Preferred Qualifications Bachelor’s degree in a quantitative or related discipline, such as Mathematics, Statistics, Data Science, Computer Science, Economics, Finance, Engineering, or a comparable field; an advanced degree is preferred.Three or more years of relevant experience in AML transaction monitoring, quantitative risk, financial crime analytics, data analysis, model development, or a related discipline.Demonstrated experience with data analysis, data modeling, risk identification, model testing, or performance monitoring in a regulated financial services environment.Strong hands-on SQL skills and working proficiency in Python or a comparable analytical programming language.Experience with large-scale data platforms, cloud or distributed analytics environments, and database technologies; experience with Databricks or similar tools is preferred.Prior experience serving as a model owner, model developer, quantitative analyst, or analytical lead is preferred.Working knowledge of model risk management, data governance, Agile delivery, and software development lifecycle practices is preferred.Knowledge of related financial crime areas, including KYC, sanctions, customer risk assessment, investigations, and regulatory reporting, is preferred.Experience supporting one or more financial services domains, such as asset servicing, custody, payments, securities, wealth management, or transfer agency, is beneficial. Salary Range $110,000 - $177,500 Annual 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. 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 need to keep the benefits description as is (including the list). The sentence about "For a full overview, visit ..." maybe considered a link; we can keep it as part of benefits. We must not include the About State Street paragraph, EEO, etc. Now we need to map to sections. Potential sections: - About the role: combine "Who We Are Looking For" and "Why this role is important to us". Could be two paragraphs. - Responsibilities: list from "What You Will Be Responsible For". We'll split each sentence (separated by periods) into
• . Need to ensure we keep all content. - Requirements: maybe "Education And Preferred Qualifications" but that includes both education and preferred qualifications. However we also have a separate "Qualifications" heading maybe for preferred qualifications? But we have both education and experience etc. Could treat "Education And Preferred Qualifications" as Requirements (minimum) and maybe also include some of the "What We Value" as Skills. But we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Education and Preferred Qualifications into Requirements (or Qualifications). But we also have Skills separate. Let's decide: - About the role: as described. - Responsibilities: as list. - Requirements: include education (Bachelor's degree ...) and experience (Three or more years ...) and maybe also "Demonstrated experience with data analysis, data modeling, risk identification, model testing, or performance monitoring in a regulated financial services environment." That seems like a requirement. - Qualifications: maybe include the preferred qualifications: advanced degree preferred, experience with Databricks, prior experience as model owner, working knowledge of model risk management, knowledge of related financial crime areas, experience supporting financial services domains. But the line "Experience supporting one or more financial services domains, such as asset servicing, custody, payments, securities, wealth management, or transfer agency, is beneficial." That's also a qualification. But we have to avoid duplication: The Education And Preferred Qualifications paragraph includes both minimum and preferred. We could split: Requirements = minimum (Bachelor's degree, 3+ years experience, hands-on SQL, Python proficiency, experience with large-scale data platforms). Qualifications = preferred (advanced degree, Databricks, model owner experience, model risk management knowledge, knowledge of related financial crime areas, experience supporting financial services domains). However the paragraph also includes "Strong hands-on SQL skills and working proficiency in Python or a comparable analytical programming language." That could be a requirement. Also "Experience with large-scale data platforms, cloud or distributed analytics environments, and database technologies; experience with Databricks or similar tools is preferred." That mixes requirement and preferred. We need to preserve all detail; we can keep the whole paragraph under either Requirements or Qualifications, but we need to avoid creating thin sections. Perhaps we can have one section "Requirements and Qualifications" but headings are fixed list