Jobs · Arizona

Manager - Ops Risk Management

American Express · Phoenix, AZ · 1 mo ago
HybridFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "Job Description" then description, then "Responsibilities", "Qualifications", "About Us", "About The Team". According to rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have content for: Responsibilities, Qualifications (minimum and preferred), About Us (culture), About The Team (benefits). Also maybe "About the role" is covered by the initial description (Job Description). The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. The initial "Job Description" could be considered a heading? It's not a required heading; we could treat the opening paragraph as prose under maybe an

About the role? But they said use

for section headings (e.g. About the role, Responsibilities...). So we could have an

About the role

with the description paragraph(s). That seems appropriate. We must not include Pay or Schedule sections unless posting actually states them. There's a salary range mentioned: "The below represents the expected salary range for this job requisition." Actually they mention salary range but not specific numbers. It says "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." No actual numbers given. According to rule: 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 they mention salary range but not actual numbers, it's vague; likely considered placeholder. Safer to omit Pay section. Benefits: The posting includes benefits under "About The Team" with list of benefits. So we can include a Benefits section. However they already have About The Team which includes benefits list. Could we make a Benefits

with the list? The rule: Prefer a few substantive sections over many thin ones. We could combine About Us and About The Team into maybe "About the Company" or keep separate? The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About Us or About The Team as official headings, but we can still use

for any section heading; they gave examples but not exclusive. However they said use

for section headings (e.g. About the role, Responsibilities...). It implies we should use those standard headings where applicable. But we can also create other headings if needed? Safer to stick to the given list. So we need to map content to those headings. We have: - About the role: description paragraph(s) from Job Description. - Responsibilities: list. - Qualifications: we have Minimum Qualifications and Preferred Qualifications. Could combine into Qualifications section. - Skills: not explicitly listed separate; but qualifications include skills. Could we create Skills section? Might be thin. Better to not create Skills if no explicit list. - Benefits: we have benefits list under About The Team. So we can create Benefits section. - Pay: not specific; omit. - Schedule: not specific; omit. We also have "About Us" and "About The Team" content; we could incorporate that into Benefits or maybe into About the role? But About Us is culture description; could be part of About the role? Might be better to include as a separate section like "About the Company" but not in list. However rule says prefer few substantive sections over many thin ones. We could merge About Us and About The Team into Benefits? Not ideal. Perhaps we can treat About Us as part of About the role (company overview). And About The Team benefits as Benefits section. Thus sections: About the role (includes initial description + maybe About Us?), Responsibilities, Qualifications, Benefits. We need to preserve all substantive information; do not invent or summarize away detail. So we must keep all details from About Us and About The Team (benefits) somewhere. If we put About Us content inside About the role section, we must keep it. That's fine. Now format: Use

for each section heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must not include boilerplate like EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. Remove those. We need to remove lines like "American Express is an equal opportunity employer..." etc. Also remove "US Job Seekers - Click to view the “ Know Your Rights ” poster." etc. Also remove "For a full list of Team Amex benefits, visit our Colleague Benefits Site ." maybe keep? That's a reference; but it's not substantive detail; it's a link. Might be considered boilerplate? It's a referral to benefits site; could be considered part of benefits but it's just a link. Might be okay to keep? The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. That link is not exactly boilerplate but it's a reference; could be considered navigation? Probably safe to remove. Also remove "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; it's substantive? It's a requirement about eligibility. Should we keep? It's a qualification about work eligibility. Could be placed under Qualifications. It's not boilerplate; it's a specific requirement. Keep. Also remove "About Us" heading? We'll embed content. Now craft HTML. First, About the role section:

    About the role

    The Global Risk & Compliance Organization (GRC) is an independent risk management function, led by the Chief Risk Officer, with the objective of ensuring that American Express operates in a safe, sound, and fully compliant manner with all applicable regulatory expectations. GRC creates and maintains the overall risk management framework, performs independent risk management assessments, and monitors applicable risks. Colleagues at GRC are passionate about our commitment to drive the Company’s goals of growth and progress by creating a culture of risk awareness and proactivity around regulatory matters. The objective of the GRC Control Management Issues, Events & Remediation team is to ensure timely identification, response, and resolution of risk events and issues to minimize impact, as well as to prevent recurrence through effective remediation and lesson learning. GRC is looking for a Manager of Issues, Events & Remediation focused 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.

    Then maybe add About Us paragraph? Actually we already included culture description from About Us? 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." We could add that as another

    under About the role. Now Responsibilities:

    Responsibilities

    • Support end-to-end process management, including capture, assessment, enhancement and resolution, for issues, operational risk events (OREs) and remediations by influencing Business Unit teams who own and action issues, operational risk events (OREs) and remediations
    • Tracking records’ progress, validating resolution efficacy, communicating status updates to stakeholders to embed accountability along the process, and collaborating with other Operational Risk Management (ORM) teams
    • Perform quality assurance on documentation and maintenance of records of issues, OREs and remediations to ensure transparency and accountability across ORM processes
    • Analyze trends in issues and events to identify potential systemic risks or control weaknesses within BU processes
    • Provide guidance on specific control enhancements related to issues, and perform sample testing of issues to ensure resolution is complete and effective
    • Liase with key stakeholders, including business unit partners and compliance colleagues, to facilitate effective issues, OREs and remediation resolution, embedding accountability and ensuring lessons learned are integrated into future ORM practices
    • Review and advise the preparation of detailed reports on issues, OREs and remediations’ status, trends, and outcomes to senior management and governance committees and support sharing insights, better practices, themes, etc. across the enterprise
    Now Qualifications: We have Minimum Qualifications and Preferred Qualifications. Also eligibility statement. We'll create

    Qualifications

    then maybe

    for prose? But we have lists. Use

    • for each qualification item. Minimum Qualifications: - 4+ Years experience in operational risk management (e.g., within Risk and/or Internal Audit function) - Understanding of critical operational risk management lifecycle activities - Excellent project management, communication, and interpersonal skills - Experience in process governance, with an understanding of processes that align with policies, regulatory frameworks, and/or operational standards - Robust 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; advanced degrees (e.g., MBA, MSc) or certifications are advantageous. - Experience In At Least One Of The Following: - Scoping, prioritizing, and supporting remediation of operational and compliance related issues, operational risk events and remediations - Managing investigation of and conducting root cause analysis to address repeated operational risk issue and event types - Overseeing the remediation process for operational risk issues and events - Reviewing documentation and maintaining records of operational risk issues, events and remediations to ensure transparency and accountability - Overseeing the issue, event and remediation resolution processes, embedding accountability and ensuring lessons learned are integrated into future operational risk management practices - Experience in financial services industry. - Employment eligibility to work with American Express in the United States is required as the company will not pursue visa sponsorship for these positions. We need to preserve the bullet about "Experience In At Least One Of The Following Scoping, prioritizing, and supporting remediation..." It's a bit weird formatting; we can treat as a group. We'll create a
        with items; for the preferred qualifications we can have a sublist? But we can just list each as separate
      • . For the "Experience In At Least One Of The Following" we can make a
      • that contains a sublist? Might be okay to just list each bullet as separate
      • under preferred qualifications, and note that candidate needs experience in at least one of those. We'll preserve the wording. Thus:

        Qualifications

        • 4+ Years experience in operational risk management (e.g., within Risk and/or Internal Audit function)
        • Understanding of critical operational risk management lifecycle activities
        • Excellent project management, communication, and interpersonal skills
        • Experience in process governance, with an understanding of processes that align with policies, regulatory frameworks, and/or operational standards
        • Robust analytical and problem-solving skills, with an ability to analyze data, identify trends, and

Similar jobs