Senior Analyst - Control Management

We need to output HTML fragment with sections: About the role? The description includes "Job Description" then paragraphs about US Consumer Services team, objective, etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. 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 boilerplate, duplicated lines, application instructions. We need to parse the job description. Content: - Opening paragraph: "The U.S. Consumer Services Team is responsible for our suite of consumer products, services, and experiences in the U.S., including our premium, cobrand, cash back, and lending portfolios, Membership Rewards, Global Travel & Lifestyle Services, the Centurion Lounge network, our Global Dining and Resy businesses, U.S. Consumer Banking, and best-in-class marketing programs across customer, prospect, and partner channels. The USCS team is focused on making membership an indisputable competitive advantage and helping each other become better leaders every day. The objective of the US Consumer Services Control Management Specialized Risk Management team is to provide subject matter expertise on specific Operational Risk topics to ensure the business unit (BU) is equipped with in-depth knowledge of risk-stripes to manage and mitigate these risks effectively; supports the BU with expert guidance for topical Operational Risk intelligence. US Consumer Services is looking for a Sr. Analyst of Specialized Risk Managementfocused on ensuring control management is embedded in the day-to-day operations of our organization. It will involve extensive collaboration with multiple partners across numerous business units, functional areas, and geographies." This is about the role. Could be "About the role". We'll put that as

About the role

with

containing that paragraph. - Responsibilities: list bullet points after "Responsibilities The Senior Analyst, US Consumer Services Specialized Risk Management will:" then bullet points each starting with a verb. We'll put

Responsibilities

then

• each. - Qualifications: there is "Qualifications Required Qualifications:" then bullet list of required qualifications. Then "Preferred Qualifications" bullet list. Also there is "Employment eligibility to work with American Express in the United States is required as the company will not pursue visa sponsorship for these positions." That's a requirement. Also maybe "Bachelor's Degree in Finance, Business, Risk Mgmt., or related field or certifications are advantageous" is preferred. We need sections: Requirements, Qualifications, Skills? The instruction says use headings for: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include based on content. We have responsibilities (yes). We have qualifications (required and preferred). We have skills? The required qualifications include "Project management, communication, and interpersonal skills", "Sound analytical and problem-solving skills". Could be placed under Skills section. But we also have Qualifications section for degrees/experience. The instruction says we can have multiple sections; we should prefer a few substantive sections over many thin ones. So maybe combine qualifications and skills into one Qualifications section? But they gave separate headings; we can include both if content exists. However we must not create thin sections with filler. Let's see. We have required qualifications: 2+ years experience in operational risk management, understanding critical operational risk management lifecycle activities; Project management, communication, and interpersonal skills; Experience in process governance, establishing and overseeing robust decision-making processes that align with policies, regulatory frameworks, and/or operational standards; Sound analytical and problem-solving skills, with an ability to analyze data, identify trends, and evaluate risk scenarios effectively. Preferred qualifications: Bachelor's Degree in Finance, Business, Risk Mgmt., or related field or certifications are advantageous; Experience in at least one of the following: (two bullet subpoints). Also employment eligibility requirement. Thus we could have a Qualifications section containing both required and preferred qualifications (maybe split into Required and Preferred subheadings? But we only allowed h3 headings; we could still use

  or

  inside. The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

    for prose. So we can have a Qualifications section with

    Qualifications

    then maybe

    Required Qualifications:

    then
    etc. Or we could have separate sections Requirements and Qualifications. But we need to decide based on content. We have "Requirements" maybe could be the eligibility to work in US etc. But we also have required qualifications. The instruction says we can include a section ONLY when the posting has real, specific content for it. So we need to see if there is distinct content for "Requirements" separate from "Qualifications". The posting has "Required Qualifications:" and "Preferred Qualifications:" plus eligibility statement. There's no separate "Requirements" heading besides that. So we could treat "Requirements" as the eligibility statement? But that's also a qualification. Might be better to have a single Qualifications section that includes required, preferred, and eligibility. Then we don't need a separate Requirements section. Similarly Skills: we could extract skills from required qualifications (project management, communication, interpersonal, analytical, problem-solving). But those are already listed under qualifications. Could we create a Skills section? Might be thin if we just list those skills. But we could combine them into Qualifications. Benefits: The posting includes a long "About The Team" paragraph describing benefits: Competitive base salaries, Bonus incentives, 6% Company Match on retirement savings plan, Free financial coaching, Comprehensive medical, dental, vision, life insurance, disability benefits, Flexible working model, 20+ weeks paid parental leave, Free access to global on-site wellness centers, Free and confidential counseling support through Healthy Minds program, Career development and training opportunities. Also mention "For a full list of Team Amex benefits, visit our Colleague Benefits Site." That's substantive content for Benefits. So we should include a Benefits section. Pay: The posting includes "The below represents the expected salary range for this job requisition. Ultimately, in determining your pay, we’ll consider your location, experience, and other job-related factors." However no actual salary range numbers are given. It says "expected salary range" but not provided. The instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Since the posting does not give actual numbers, just says expected salary range but not stated, we should NOT create a Pay section because it's not specific. So omit Pay. Schedule: The posting mentions flexible working model: "Depending on role and business needs, colleagues will either work onsite, in a hybrid model (combination of in-office and virtual days) or fully virtually." Also earlier: "Flexible working model with hybrid, onsite or virtual arrangements depending on role and business need". That's schedule info. So we have specific content about schedule: flexible working model, hybrid, onsite, virtual. So we can include a Schedule section. Thus sections: About the role, Responsibilities, Qualifications (maybe combine required/preferred), Benefits, Schedule. Possibly also Skills? But we can incorporate skills into Qualifications. The instruction says we can use Skills heading if we have content. We have project management, communication, interpersonal, analytical, problem-solving skills. That's specific. Could make a Skills section. But then Qualifications would be about experience/degrees. Might be better to split: Qualifications (education/experience) and Skills (specific skills). Let's see if we have enough content for each to avoid thin sections. Qualifications content: Required: 2+ years experience in operational risk management, understanding critical operational risk management lifecycle activities. Preferred: Bachelor's Degree in Finance, Business, Risk Mgmt., or related field or certifications are advantageous. Also experience in assisting day-to-day activities to support compliance with enterprise policies... etc. Also eligibility to work in US. That's decent. Skills content: Project management, communication, and interpersonal skills; Sound analytical and problem-solving skills, with an ability to analyze data, identify trends, and evaluate risk scenarios effectively. Also maybe "Experience in process governance, establishing and overseeing robust decision-making processes that align with policies, regulatory frameworks, and/or operational standards" could be considered skill but it's more experience. We'll keep skills as those two bullet points. Thus we can have Qualifications and Skills sections both substantive. Now we need to strip boilerplate: The "About Us" paragraph about American Express culture, etc. That's not about the role specifically but could be considered "About Us" but not a heading we have. We should remove it as it's boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Us" paragraph is not explicitly listed as boilerplate but it's generic company description. Might be considered not substantive to the job? However it's part of the job description. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it if it's substantive. But we don't have a heading for "About Us". We could put it under About the role? But About the role already has description of team and objective. The About Us paragraph is more about company culture, values, benefits? Actually benefits are later. The About Us paragraph: "At American Express, our culture is built on a 175-year history of innovation, shared values and Leadership Behaviors, and an unwavering commitment to back our customers, communities, and colleagues. From delivering differentiated products to providing world-class customer service, we operate with a strong risk mindset, ensuring we continue to uphold our brand promise of trust, security, and service. As part of Team Amex, you’ll experience our powerful backing with comprehensive support for your holistic well-being and many opportunities to learn new skills, develop as a leader, and grow your career. Here, your voice and ideas matter, your work makes an impact, and together, you will help us define the future of American Express." This is generic but still part of job description. We could include it as a paragraph under About the role or maybe a separate section "About the company"? Not in allowed headings. So we could incorporate it into About the role paragraph. Similarly "About The Team" paragraph about benefits we already captured for Benefits section. That's fine. We also need to remove duplicated lines, EEO boilerplate etc. The posting includes a lot of EEO statement at the end: "American Express is an equal opportunity employer..." etc. That's boilerplate; we should remove it. Also the "US Job Seekers - Click to view the “ Know Your Rights ” poster." etc. Remove. Also the sentence about "Employment eligibility to work with American Express in the United States is required as the company will not pursue visa sponsorship for these positions." That's not boilerplate; it's a requirement. Keep. Now we need to format. We'll produce:

    About the role

    ... (combined intro + About Us maybe)

    Responsibilities

    • Act as a compliance risk advisor and support to front-line business teams, helping them understand and comply with applicable regulatory obligations
    • Support the execution of compliance risk assessments and ongoing monitoring activities within the business unit
    • Monitor business activities for compliance with laws, regulations, and internal standards (e.g., BSA/AML)
    • Track and remediate compliance issues and control gaps identified through monitoring, audits, or regulatory exams
    • Maintain and update business-level compliance documentation, including procedures, control descriptions,