Campus Undergraduate Summer Internship Program - 2027 Digital Product Management, Enterprise Technology Services- New York, NY
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: About the role? There's "Business Unit / Role Specific Info" and "About The Team". Could treat as "About the role" maybe. There's "Responsibilities" section. There's "Qualifications" (minimum and preferred). There's "Skills"? Not explicit but qualifications include skills. Could combine into Qualifications. There's "Benefits" section: "About The Team We back you with benefits..." includes list of benefits. There's "Pay": mention "Competitive base salaries" but no specific range; also later: "The 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 provide the range in the text? It says "Ultimately, in determining your pay, we’ll consider your location, experience, and other job-related factors." No actual numbers. So we should not create Pay section because no specific numbers. Schedule: mention flexible work arrangements, hybrid/virtual options, Amex Flex. That's schedule info. So we can include Schedule section.
We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, legal, application instructions, etc.
We need to preserve all substantive information. So we need to include content from sections: About the role/team, Responsibilities, Qualifications (minimum and preferred), Benefits, Schedule.
We need to format lists with - . Use
for prose.
We need to avoid filler like "commensurate with experience". Not present.
Let's extract content.
First, "Business Unit / Role Specific Info" paragraph: The Enterprise Technology Services organization partners... etc. That's substantive. We'll put under
About the role
maybe.
Then "About The Team" paragraph: Enterprise Technology Services teams build and support technology... That's also about team. Could combine with About the role? Might be separate but we can put under same heading or separate. Since we prefer few substantive sections, we could combine both paragraphs under About the role.
Then Responsibilities: list of bullet points (each sentence). We'll make - for each.
Qualifications: Minimum Qualifications list (multiple bullet-like sentences). Preferred Qualifications list.
We could split into Minimum Qualifications and Preferred Qualifications as subheadings? But only allowed headings are the listed ones; we could still use
for Qualifications and then inside have
for intro and
- for each bullet. Could separate minimum and preferred as separate
maybe with headings inside? Not allowed to add extra headings beyond those? The instruction: 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 those for section headings. Probably we should stick to those headings only. So we can have one Qualifications section containing both minimum and preferred, maybe with
intro and then two
with labels like Minimum Qualifications: inside - ? But that would be mixing. Better to have two
with preceding stating "Minimum Qualifications:" and "Preferred Qualifications:" as plain text inside
then list.
But we must not invent headings like "Minimum Qualifications". That's okay as plain text inside
.
Skills: Not explicitly separate; we could omit Skills section.
Benefits: list from "About The Team We back you with benefits..." includes: Competitive base salaries, Flexible work arrangements and schedules with hybrid and virtual options with Amex Flex, Free access to global on-site wellness centers staffed with nurses and doctors (depending on location), Free and confidential counselling support through our Healthy Minds program, Career development and training opportunities. Also maybe "For a full list of Team Amex benefits, visit out Colleague Benefits Site ." We'll include the list.
Schedule: mention flexible work arrangements etc. Already covered in benefits; but schedule is about flexible work arrangements and schedules with hybrid and virtual options with Amex Flex. Could be separate Schedule section. However benefits already includes that. To avoid duplication, we could put schedule info under Benefits? But instruction: include a section ONLY when posting has real specific content for it. It does have schedule content. We could make Schedule section with that info. Benefits section can still have other benefits.
Pay: Not specific numbers, so omit.
Now we need to strip boilerplate: remove EEO, equal-opportunity, legal, scam-warning, application instructions, cookie/navigation, duplicated lines. Also remove "Our team reviews applications on a rolling basis..." etc. That's application instructions? It's about process; maybe we should remove as it's application instructions. 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 maybe a requirement but could be considered substantive? It's about eligibility; could be considered a requirement. However it's more like a condition. Might keep as part of Qualifications? But it's not a qualification per se. Might be considered boilerplate? Not sure. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The eligibility statement is not exactly those; it's a requirement about work authorization. Could keep as part of Qualifications? Might be okay.
Also remove "Candidate Value Proposition" etc? That's substantive about internship value; we could include maybe under About the role? It's more like value proposition. Could keep as part of About the role? Might be okay.
But we need to preserve all substantive information. So we should keep the Candidate Value Proposition paragraph.
Also "About Us" paragraph about culture; could be part of About the role? Might be okay.
We need to avoid duplication: there are repeated paragraphs like "About The Team" appears twice. We'll deduplicate.
Let's extract substantive blocks:
1. Business Unit / Role Specific Info (first paragraph)
2. About The Team (first occurrence) - about team building technology etc.
3. Responsibilities (list)
4. Qualifications (Minimum and Preferred)
5. Candidate Value Proposition
6. About Us (culture)
7. About The Team (second occurrence) - benefits paragraph (starting with "We back you with benefits...")
8. Maybe also "Our team reviews applications..." (remove)
9. Employment eligibility statement (maybe keep as requirement)
10. The below represents the expected salary range... (no actual range) - we can omit as no specific range.
We need to avoid duplication: The second About The Team includes benefits list; we will use that for Benefits section.
Now craft HTML.
Structure:
About the role
... combine first two paragraphs (Business Unit / Role Specific Info and About The Team first) plus maybe Candidate Value Proposition and About Us? Might be too much. Better to have separate sections: About the role, About the team? But only allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the team". So we need to fit team info under About the role or maybe under Qualifications? Not appropriate. Could put under About the role.
Thus About the role section will contain: Business Unit / Role Specific Info, About The Team (first), Candidate Value Proposition, About Us (culture). That's a lot but okay.
Then Responsibilities section.
Then Qualifications section (with minimum and preferred).
Then Benefits section (from second About The Team benefits list).
Then Schedule section (flexible work arrangements etc). However schedule info already in benefits; but we can still have schedule section with that detail, and benefits section without that detail to avoid duplication. Let's split: Benefits section includes competitive base salaries, free access to wellness centers, free counselling, career development and training opportunities. Schedule section includes flexible work arrangements and schedules with hybrid and virtual options with Amex Flex.
Now we need to ensure we don't lose any info: The benefits paragraph also mentions "Competitive base salaries" and "Flexible work arrangements and schedules with hybrid and virtual options with Amex Flex". We'll split accordingly.
Now let's write.
First, About the role paragraph:
"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. At American Express, we empower future technologists to learn, innovate, and make an impact from day one. As an Associate Digital Product Management Intern in Enterprise Technology Services, you’ll join a 10-week Summer Internship Program and contribute to product, platform, and delivery initiatives that help shape seamless customer and colleague experiences. Product Management interns sit at the intersection of business, technology, data, design, delivery, and customer experience. In this role, you’ll help teams understand customer needs, document requirements, prioritize work, track delivery outcomes, manage risks and dependencies, and support Agile planning activities that help technology teams deliver value responsibly and at enterprise scale. You’ll collaborate with Product Managers, Engineers, Designers, Data Analysts, Architects, Delivery Leads, and business partners to learn how products and technology initiatives are envisioned, built, launched, measured, governed, and continuously improved."
Next, About The Team first paragraph:
"Enterprise Technology Services teams build and support technology that enables trusted, secure, and customer-first experiences across American Express. Product and delivery teams help define strategy, prioritize investments, coordinate execution, and improve delivery practices across digital products, platforms, internal tools, developer experiences, AI enabled capabilities, and enterprise technology solutions. As a Product Management Intern, you’ll contribute at an early-career level while learning how modern product teams balance customer needs, business outcomes, technical feasibility, delivery execution, operational resilience, and responsible innovation."
Candidate Value Proposition:
"Backed by Amex, Product Management Interns gain hands-on experience working on meaningful technology initiatives while learning from experienced product leaders, engineers, designers, delivery leads, and business partners. This internship offers exposure to product strategy, customer experience, technology delivery, Agile execution, AI-enabled delivery practices, data-informed decision-making, and modern enterprise product management. You’ll build a strong professional network, develop practical product and delivery skills, and learn how American Express creates exceptional customer and colleague experiences responsibly and at scale. Your contributions matter. You’ll have the opportunity to help shape products, improve delivery practices, influence experiences, and learn how technology enables the future of payments."
About Us (culture):
"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."
Now Responsibilities list items (each sentence):
- Support Product Managers and delivery teams in defining, refining, and prioritizing product requirements, features, user stories, acceptance criteria, and support documentation.
- Assist with customer discovery, stakeholder interviews, user research activities, usability testing, and analysis of feedback to help inform
for prose. We need to avoid filler like "commensurate with experience". Not present. Let's extract content. First, "Business Unit / Role Specific Info" paragraph: The Enterprise Technology Services organization partners... etc. That's substantive. We'll put under
About the role
maybe. Then "About The Team" paragraph: Enterprise Technology Services teams build and support technology... That's also about team. Could combine with About the role? Might be separate but we can put under same heading or separate. Since we prefer few substantive sections, we could combine both paragraphs under About the role. Then Responsibilities: list of bullet points (each sentence). We'll make- for each.
Qualifications: Minimum Qualifications list (multiple bullet-like sentences). Preferred Qualifications list.
We could split into Minimum Qualifications and Preferred Qualifications as subheadings? But only allowed headings are the listed ones; we could still use
for Qualifications and then inside have
for intro and
- for each bullet. Could separate minimum and preferred as separate
- maybe with headings inside? Not allowed to add extra headings beyond those? The instruction: use
- ? But that would be mixing. Better to have two
- with preceding
stating "Minimum Qualifications:" and "Preferred Qualifications:" as plain text inside
then list. But we must not invent headings like "Minimum Qualifications". That's okay as plain text inside
. Skills: Not explicitly separate; we could omit Skills section. Benefits: list from "About The Team We back you with benefits..." includes: Competitive base salaries, Flexible work arrangements and schedules with hybrid and virtual options with Amex Flex, Free access to global on-site wellness centers staffed with nurses and doctors (depending on location), Free and confidential counselling support through our Healthy Minds program, Career development and training opportunities. Also maybe "For a full list of Team Amex benefits, visit out Colleague Benefits Site ." We'll include the list. Schedule: mention flexible work arrangements etc. Already covered in benefits; but schedule is about flexible work arrangements and schedules with hybrid and virtual options with Amex Flex. Could be separate Schedule section. However benefits already includes that. To avoid duplication, we could put schedule info under Benefits? But instruction: include a section ONLY when posting has real specific content for it. It does have schedule content. We could make Schedule section with that info. Benefits section can still have other benefits. Pay: Not specific numbers, so omit. Now we need to strip boilerplate: remove EEO, equal-opportunity, legal, scam-warning, application instructions, cookie/navigation, duplicated lines. Also remove "Our team reviews applications on a rolling basis..." etc. That's application instructions? It's about process; maybe we should remove as it's application instructions. 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 maybe a requirement but could be considered substantive? It's about eligibility; could be considered a requirement. However it's more like a condition. Might keep as part of Qualifications? But it's not a qualification per se. Might be considered boilerplate? Not sure. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The eligibility statement is not exactly those; it's a requirement about work authorization. Could keep as part of Qualifications? Might be okay. Also remove "Candidate Value Proposition" etc? That's substantive about internship value; we could include maybe under About the role? It's more like value proposition. Could keep as part of About the role? Might be okay. But we need to preserve all substantive information. So we should keep the Candidate Value Proposition paragraph. Also "About Us" paragraph about culture; could be part of About the role? Might be okay. We need to avoid duplication: there are repeated paragraphs like "About The Team" appears twice. We'll deduplicate. Let's extract substantive blocks: 1. Business Unit / Role Specific Info (first paragraph) 2. About The Team (first occurrence) - about team building technology etc. 3. Responsibilities (list) 4. Qualifications (Minimum and Preferred) 5. Candidate Value Proposition 6. About Us (culture) 7. About The Team (second occurrence) - benefits paragraph (starting with "We back you with benefits...") 8. Maybe also "Our team reviews applications..." (remove) 9. Employment eligibility statement (maybe keep as requirement) 10. The below represents the expected salary range... (no actual range) - we can omit as no specific range. We need to avoid duplication: The second About The Team includes benefits list; we will use that for Benefits section. Now craft HTML. Structure:
About the role
... combine first two paragraphs (Business Unit / Role Specific Info and About The Team first) plus maybe Candidate Value Proposition and About Us? Might be too much. Better to have separate sections: About the role, About the team? But only allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the team". So we need to fit team info under About the role or maybe under Qualifications? Not appropriate. Could put under About the role. Thus About the role section will contain: Business Unit / Role Specific Info, About The Team (first), Candidate Value Proposition, About Us (culture). That's a lot but okay. Then Responsibilities section. Then Qualifications section (with minimum and preferred). Then Benefits section (from second About The Team benefits list). Then Schedule section (flexible work arrangements etc). However schedule info already in benefits; but we can still have schedule section with that detail, and benefits section without that detail to avoid duplication. Let's split: Benefits section includes competitive base salaries, free access to wellness centers, free counselling, career development and training opportunities. Schedule section includes flexible work arrangements and schedules with hybrid and virtual options with Amex Flex. Now we need to ensure we don't lose any info: The benefits paragraph also mentions "Competitive base salaries" and "Flexible work arrangements and schedules with hybrid and virtual options with Amex Flex". We'll split accordingly. Now let's write. First, About the role paragraph: "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. At American Express, we empower future technologists to learn, innovate, and make an impact from day one. As an Associate Digital Product Management Intern in Enterprise Technology Services, you’ll join a 10-week Summer Internship Program and contribute to product, platform, and delivery initiatives that help shape seamless customer and colleague experiences. Product Management interns sit at the intersection of business, technology, data, design, delivery, and customer experience. In this role, you’ll help teams understand customer needs, document requirements, prioritize work, track delivery outcomes, manage risks and dependencies, and support Agile planning activities that help technology teams deliver value responsibly and at enterprise scale. You’ll collaborate with Product Managers, Engineers, Designers, Data Analysts, Architects, Delivery Leads, and business partners to learn how products and technology initiatives are envisioned, built, launched, measured, governed, and continuously improved." Next, About The Team first paragraph: "Enterprise Technology Services teams build and support technology that enables trusted, secure, and customer-first experiences across American Express. Product and delivery teams help define strategy, prioritize investments, coordinate execution, and improve delivery practices across digital products, platforms, internal tools, developer experiences, AI enabled capabilities, and enterprise technology solutions. As a Product Management Intern, you’ll contribute at an early-career level while learning how modern product teams balance customer needs, business outcomes, technical feasibility, delivery execution, operational resilience, and responsible innovation." Candidate Value Proposition: "Backed by Amex, Product Management Interns gain hands-on experience working on meaningful technology initiatives while learning from experienced product leaders, engineers, designers, delivery leads, and business partners. This internship offers exposure to product strategy, customer experience, technology delivery, Agile execution, AI-enabled delivery practices, data-informed decision-making, and modern enterprise product management. You’ll build a strong professional network, develop practical product and delivery skills, and learn how American Express creates exceptional customer and colleague experiences responsibly and at scale. Your contributions matter. You’ll have the opportunity to help shape products, improve delivery practices, influence experiences, and learn how technology enables the future of payments." About Us (culture): "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." Now Responsibilities list items (each sentence): - Support Product Managers and delivery teams in defining, refining, and prioritizing product requirements, features, user stories, acceptance criteria, and support documentation. - Assist with customer discovery, stakeholder interviews, user research activities, usability testing, and analysis of feedback to help inform
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those headings only. So we can have one Qualifications section containing both minimum and preferred, maybe with
intro and then two
- with labels like Minimum Qualifications: inside
- ? But that would be mixing. Better to have two
- for each bullet. Could separate minimum and preferred as separate