Campus Graduate Masters Summer Internship Program - 2027 Data Analytics, Enterprise Technology Services- Charlotte, NC

We need to output HTML fragment with sections: h3 headings for sections present: About the role? Actually the description includes sections: Business Unit / Role Specific Info (maybe we treat as About the role). Then Responsibilities, Qualifications (maybe split into Minimum and Preferred? but we can combine). Also Benefits? There's a section "About The Team" describing benefits. Also Pay? There's a line: "The below represents the expected salary range for this job requisition." but no actual range given. It says "Ultimately, in determining your pay, we’ll consider your location, experience, and other job-related factors." No specific numbers. According to rules: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits: they list benefits (competitive base salaries, flexible work arrangements, free access to wellness centers, counseling, career development). That's specific content, so we can include Benefits section. Pay: they mention expected salary range but not actual numbers; they say "The below represents the expected salary range for this job requisition." but then no range given. That's placeholder? It's not a specific range; it's a statement that they will consider location etc. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Since they didn't give actual numbers, we should not create Pay section. Schedule: they mention flexible work arrangements and schedules with hybrid and virtual options with Amex Flex. That's schedule info. So we could include Schedule section? The rule: include a section ONLY when posting has real, specific content for it. They have "Flexible work arrangements and schedules with hybrid and virtual options with Amex Flex". That's specific enough? It's not a specific schedule but describes flexibility. Might be considered schedule content. However they also have "About The Team" benefits includes flexible work arrangements. Could combine into Benefits. Safer to not create separate Schedule unless explicit schedule like "Monday-Friday 9-5". We'll omit Schedule. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Remove duplicated lines. Also remove "Our team reviews applications on a rolling basis..." etc (application instructions). Also remove "Employment eligibility to work with American Express in the United States is required..." (that's eligibility, maybe keep? It's not boilerplate? It's a requirement but could be considered part of Qualifications? Might keep as part of Qualifications? It's about eligibility; but it's not a list. Could be placed in a short p under Qualifications? Might be okay but it's not a list. However it's not a responsibility or qualification; it's a condition. Could be included in a short p under Qualifications or maybe under About the role? Safer to keep as a p under Qualifications? But it's not a qualification per se; it's eligibility. Could be placed in a short p after Qualifications heading? Might be considered boilerplate? It's a standard statement but still specific. I'd keep it as a p under Qualifications (maybe as a note). However the instruction: "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." This eligibility is not minor metadata; it's a requirement. Could be part of Qualifications. We need to preserve ALL substantive information. So we need to include the description paragraphs about Enterprise Technology Services, the role, etc. Use

for prose. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll choose headings that match content: About the role (maybe "About the role" or "About the team"? The posting has "Business Unit / Role Specific Info". We'll use "About the role". Then "Responsibilities". Then "Qualifications" (maybe split into Minimum and Preferred? but we can keep as one with subpoints? Use

• for any list of duties/requirements/benefits. So we need to turn responsibilities into a list. Qualifications: we have Minimum Qualifications and Preferred Qualifications; we can make two subheadings? But only allowed headings are the listed ones; we could still use

  for Minimum Qualifications and Preferred Qualifications? Not in list but could be considered as subheadings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

  for section headings (e.g. those). Likely we should stick to those. So we can have a single Qualifications section and within it we can have paragraphs describing minimum and preferred. Or we could split into two

  sections: Minimum Qualifications and Preferred Qualifications, but they are not in the list; risk of being considered not allowed. Safer to keep one Qualifications section and include both. Similarly Skills: we could have a Skills section if there are specific skills listed; but we have many skills within qualifications. Could create a Skills section but might be thin. Better to keep Qualifications. Benefits: we have benefits listed; we can make Benefits section. We need to remove duplicated lines: e.g., "Exposure to financial modeling, dashboard development, key performance indicator reporting, forecast reconciliation, cost analysis, or operational analytics." appears twice? Actually appears in Preferred Qualifications and also later in "Exposure to financial modeling, dashboard development, statistical analysis, scenario analysis, model documentation, data quality review, metadata, or data lineage concepts." Slightly different. We'll keep both but ensure not duplicate identical lines. We must not invent or summarize away detail. Keep all specifics. Let's extract content. First paragraph: "Business Unit / Role Specific Info The Enterprise Technology Services organization partners with every part of the American Express business to power the company’s growth and innovation with trust and efficiency, and drive competitive differentiation with speed. We support the delivery and operations of technology, digital, and data capabilities, platforms, and services globally. Specifically, our team is responsible for the company’s technology engineering, architecture, and infrastructure, providing 24x7 support to ensure an uninterrupted, high-quality experience for customers and colleagues. We also provide product management for core enterprise platforms, and lead technology risk and information security, enterprise data governance and platforms, digital product and design, and enterprise AI platforms on behalf of the company." Second paragraph: "At American Express, we empower early career data and analytics interns to learn, innovate, and make an impact from day one. As an Analyst Data Analytics intern in Enterprise Technology Services, you will support analytics work that helps technology teams understand portfolio performance, delivery progress, financial trends, resource utilization, and operational outcomes. This role sits at the intersection of technology, finance, portfolio management, reporting, and data analytics. You may gather and validate data, build reports, analyze financial or delivery metrics, support dashboards, develop insights, and prepare clear recommendations that help leaders and teams make informed technology decisions." Then "Responsibilities Responsibilities and What Type of Work to Expect" then list bullet points (but in prose). We'll convert each sentence to

  . List items: - Collect, clean, validate, and organize data from portfolio, project, financial, operational, and technology delivery sources to support analysis and reporting. - Analyze portfolio performance, budget, forecast, resource, delivery, schedule, quality, and risk information to identify trends, insights, and areas for follow up. - Create and maintain dashboards, reports, key performance indicators, recurring analytics outputs, and leadership ready summaries for technology stakeholders. - Develop financial models, cost views, forecast summaries, scenario analyses, and variance insights that support technology portfolio and project decision making. - Partner with technology, finance, product, project, and business teams to understand reporting needs and translate them into accurate analytical outputs. - Support Software Development Lifecycle and Agile delivery reporting by analyzing delivery metrics, progress data, dependencies, and execution patterns. - Prepare presentations, narratives, and stakeholder updates that communicate data backed insights to technical and non technical audiences. - Use Agentic AI, reporting, data analytics, and productivity tools to support research, summarization, analysis, workflow efficiency, and human validated outputs. Then "Qualifications Minimum Qualifications" list: - Must have earned a Master’s degree in Business Administration, Finance, Information Technology, Information Systems, Business Analytics, Data Analytics, Computer Science, Economics, or another relevant field before the full time start date. - Interest or experience in data analytics, financial management, portfolio reporting, technology delivery, business intelligence, or data informed decision making. - Foundational knowledge of data analytics concepts, including data collection, validation, analysis, visualization, and insight generation. - Foundational understanding of financial management principles such as budgeting, forecasting, cost tracking, variance analysis, or financial modeling. - Awareness of Software Development Lifecycle and Agile methodology concepts within a technology delivery environment. - Foundational understanding of Generative AI concepts, responsible use, appropriate use contexts, prompt based workflows, and human validation of AI generated outputs. - Strong analytical thinking, attention to detail, communication, organization, problem solving, and collaboration skills. Then "Preferred Qualifications" list: - Master’s degree candidates with an expected graduation date between December 2027 and June 2028. - Coursework, projects, internships, student organizations, or extracurricular experience related to data analytics, finance, business analysis, reporting, portfolio management, or technology delivery. - Experience using analytical, reporting, or presentation tools such as Excel, PowerPoint, SQL, Python, Tableau, Power BI, or similar platforms. - Exposure to financial modeling, dashboard development, key performance indicator reporting, forecast reconciliation, cost analysis, or operational analytics. - Interest in technology portfolio management, project performance reporting, resource planning, process improvement, or business intelligence modernization. - Familiarity with project or portfolio tools such as Jira, Rally, Confluence, SharePoint, Microsoft Project, or related workflow platforms. - Coursework, projects, research, or internship exposure to data requirements, source-to-target mapping, data quality and controls, metadata, lineage, or data governance. - Exposure to financial modeling, dashboard development, statistical analysis, scenario analysis, model documentation, data quality review, metadata, or data lineage concepts. - Interest in AI governance, model risk management, responsible AI, explainability, enterprise data architecture, predictive analytics, or quantum computing research. - Curiosity about Agentic AI reporting, AI enabled analytics, productivity tools, automated insight generation, and responsible validation of AI generated recommendations. - Ability to build clear narratives from data, communicate findings clearly, and work effectively across finance, technology, architecture, risk, product, and business teams. Then "Our team reviews applications on a rolling basis..." (application instructions) remove. Then "Employment eligibility to work with American Express in the United States is required as the company will not pursue visa sponsorship for these positions." Keep as a p maybe under Qualifications or separate note. Then "Ideal Candidate Profile We are seeking curious and analytical students who enjoy working with data, solving complex problems, and learning how analytics can support responsible technology decisions. Successful candidates will combine quantitative thinking, business curiosity, strong communication skills, and a commitment to accuracy, integrity, and continuous learning." This could be part of Qualifications or a separate section? Could be considered as part of Qualifications (desired traits). We'll incorporate into Qualifications as a paragraph. Then "About Us 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