Senior Manager - Data Analytics

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: About the role (description), Responsibilities, Qualifications (including Preferred Qualifications), About Us, About The Team (benefits). There's also mention of Pay: "Below represents the expected salary range for this job requisition." Actually they say "The below represents the expected salary range for this job requisition." But they didn't give the range; they just say "Ultimately, in determining your pay, we’ll consider your location, experience, and other job-related factors." No actual numbers. So we should not include Pay section because no specific content (no range). Schedule: they mention flexible working model, hybrid, onsite or virtual arrangements depending on role and business need. That's schedule info. So we can include a Schedule section with that content. Benefits: they list many benefits in About The Team. So include Benefits section. Skills: maybe not explicit separate list; but we could incorporate skills within Qualifications. The instruction: use headings for sections like Skills if there is content. There's no separate skills list; we could omit Skills. Requirements: maybe combine Qualifications and Requirements? The posting has Qualifications (required) and Preferred Qualifications. We could have a Requirements section for required qualifications, and maybe a separate Preferred Qualifications? But instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could have Qualifications for required, and maybe Preferred Qualifications could be under Qualifications as well or separate? Probably better to have Qualifications (required) and maybe a separate Preferred Qualifications not listed as heading; but we could incorporate into Qualifications with subpoints. However they said use headings for those specific names; we can have Qualifications and maybe also a separate Preferred Qualifications not required. But to keep few substantive sections, we can combine required and preferred under Qualifications. Thus sections: About the role (maybe heading About the role), Responsibilities, Qualifications, Benefits, Schedule. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to include all content from description: The initial paragraphs about American Express Global Commercial Services, SPT team, role description. That's About the role. Responsibilities: list each bullet. Qualifications: list required qualifications (5+ years experience, strong analytical..., SQL, Excel/Tableau, etc.) plus Preferred Qualifications (Python experience, leading complex cross-functional initiatives, experience supporting sales/commercial payments/lending, Master's degree, Employment eligibility to work with American Express in US required). Also note about visa sponsorship not pursued. About Us and About The Team: we can incorporate into Benefits section? Actually About Us is culture description; About The Team is benefits. We could have About the role covering the initial description; About Us could be omitted as boilerplate? It's not exactly boilerplate but it's generic culture description. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not exactly legal boilerplate but could be considered generic marketing. However it's substantive? It describes culture, values, etc. Might be considered boilerplate but it's not legal. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. About Us is not those. But we might keep it as part of About the role? However we already have About the role heading; we could include the initial description there. The About Us paragraph could be considered extra but maybe we can include under About the role as well? But we need to preserve all substantive information; we could include it under About the role as additional paragraphs. But we also have About The Team benefits; we will put those under Benefits. We must not repeat the job title as a heading. The job title is Senior Manager (implied). Not to repeat. We must not put Job ID/requisition numbers as headings. We must not include sections with filler like "commensurate with experience". Not present. Now craft HTML. Structure:

  About the role

  American Express Global Commercial Services (GCS) is a global leader in commercial payments, helping businesses manage payments and drive growth. Within GCS, the Sales Enablement, Pricing & Transformation (SPT) team translates data, business performance, and strategic priorities into actions that support lending growth, sales effectiveness, incentive strategy, and sustainable business outcomes. We are looking for a highly analytical and intellectually curious Senior Manager to support the US SME Business Line of Credit (BLOC) organization. This is an individual contributor role for someone who can independently structure complex business questions, analyze what is happening and why, and turn insights into clear, executive-ready recommendations. The role partners across Sales, Marketing, Product, Finance, Incentive Governance, and Enterprise Digital & Analytics to identify growth opportunities, improve business performance, and move high-priority initiatives from analysis through execution.

  Responsibilities

  • Analyze business, lending, and sales performance to identify trends, opportunities, risks, and key drivers of results.
  • Develop hypotheses, test assumptions, investigate root causes, and translate findings into actionable recommendations for BLOC and SPT leadership.
  • Work hands-on with structured, imperfect, and unstructured data to answer complex and ambiguous business questions.
  • Partner cross-functionally with Sales, Marketing, Product, Finance, Incentive Governance, Enterprise Digital & Analytics, and other stakeholders on strategic growth initiatives.
  • Define success measures and key performance indicators for business initiatives and establish approaches to track impact.
  • Support annual goal setting and incentive-related changes through analysis, planning, and clear stakeholder communication.
  • Lead cross-functional workstreams from problem definition and analysis through recommendation, implementation, and ongoing improvement.
  • Communicate complex analysis clearly and tailor insights, methodology, and recommendations for different audiences, including senior leaders.
  • Operate effectively in a dynamic environment, managing shifting priorities while maintaining quality and delivering against deadlines.

  Qualifications

  • 5+ years of relevant experience in business analytics, strategy, decision science, sales analytics, business intelligence, or a related analytical discipline.
  • Strong analytical and problem-solving skills, including experience identifying trends, testing assumptions, investigating root causes, and developing recommendations.
  • Hands-on SQL experience and ability to work with large and/or complex datasets.
  • Experience using Excel and Tableau to analyze data, identify insights, visualize performance, and communicate business results.
  • Ability to work with imperfect, incomplete, or unstructured data and determine a practical analytical approach.
  • Strong business judgment and ability to connect analytical findings to business strategy, lending growth, sales effectiveness, and commercial outcomes.
  • Ability to independently structure problems, determine an analytical approach, and move work forward with limited direction.
  • Strong written and verbal communication skills, including the ability to explain analytical thinking, assumptions, methodology, and recommendations clearly to business and senior stakeholders.
  • Demonstrated ability to build relationships and influence cross-functional partners without direct authority.
  • Ability to manage changing priorities while maintaining quality and delivering against deadlines.
  • Bachelor's degree or equivalent relevant experience.
  • Preferred qualifications:
  • Experience using Python for data analysis and/or automation or demonstrated ability and interest in developing Python proficiency.
  • Experience leading complex cross-functional initiatives or projects from analysis through implementation.
  • Experience supporting sales, commercial payments, financial services, lending, or other commercially focused businesses.
  • Master's degree or other relevant advanced education.
  • Employment eligibility to work with American Express in the United States is required as the company will not pursue visa sponsorship for these positions.
  But note: nested
  inside
  is not ideal but acceptable. Could instead keep as separate
  for preferred qualifications under a heading? But we only have Qualifications heading; we could have two
  sections: one for required, one for preferred with a preceding

  Preferred qualifications:

  . That might be cleaner. Let's restructure:

  Qualifications

  Required:

  • ... (list required items)

  Preferred:

  • ... (list preferred items)
  Now Benefits:

  Benefits

  • Competitive base salaries
  • Bonus incentives
  • 6% Company Match on retirement savings plan
  • Free financial coaching and financial well-being support
  • Comprehensive medical, dental, vision, life insurance, and disability benefits
  • Flexible working model with hybrid, onsite or virtual arrangements depending on role and business need
  • 20+ weeks paid parental leave for all parents, regardless of gender, offered for pregnancy, adoption or surrogacy
  • Free access to global on-site wellness centers staffed with nurses and doctors (depending on location)
  • Free and confidential counseling support through our Healthy Minds program
  • Career development and training opportunities
  Schedule: Actually flexible working model already listed under Benefits; but we could still have a Schedule section referencing that. However to avoid duplication, we could keep schedule info under Benefits only. The instruction: prefer a few substantive sections over many thin ones. So we can omit separate Schedule section and keep flexible working model under Benefits. Thus sections: About the role, Responsibilities, Qualifications, Benefits. Check if any other specific content: Pay: not specific; we omit. Now ensure we removed boilerplate: The About Us paragraph and About The Team benefits we captured benefits; we omitted About Us culture description? Actually we omitted the About Us paragraph (starting "At American Express, our culture is built...") which is not benefits. Should we keep it? It's substantive about culture, values, etc. It's not legal boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not those. It's a description of company culture. Might be considered substantive. Should we include it? We could include it under About the role as additional paragraph. But we already have About the role with the initial description; we could append the About Us paragraph there. Thus About the role will have two paragraphs: first about GCS and role, second about American Express culture (At American Express...). Let's include that. Now ensure we didn't include any duplicated lines. The posting also had "We back you with benefits that support your holistic well-being..." which we used for Benefits. Also "For a full list of Team Amex benefits, visit our Colleague Benefits Site ." That's a link; we should omit as it's a navigation/link. Also "American Express is an equal opportunity employer..." that's EEO boilerplate; remove. Also "American Express will consider for employment all qualified applicants..." that's also EEO/legal; remove. Also "For positions covered by federal and/or state banking regulations..." remove. Also "We back our colleagues with the support they need to thrive..." that's similar to benefits but we already captured benefits; could be considered boilerplate but it's not legal; but it's somewhat repetitive. Might be okay to keep but it's similar to benefits. However we already have benefits list; that paragraph is generic; we could omit as it's somewhat boilerplate. The instruction: remove duplicated lines. This paragraph is similar to benefits but not identical; but it's still generic. Safer to omit. Also "Depending on role and business needs, colleagues will either work onsite, in a hybrid model (com