Intern - Product Management
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's see if posting mentions Pay, Benefits, Schedule. It mentions internship details: start date Jan 11 2027, based in New York office, expected to work onsite, 20-25 hrs per week during school year, up to 40 hrs per week during academic breaks. That's schedule info. So we can have a Schedule section with that detail. Benefits? Not mentioned explicitly. Pay? Not mentioned. So we should not include Pay or Benefits sections. About the role: we have a paragraph about role. Responsibilities: we have "What You'll Do:" bullet list. Requirements: we have "Required Qualifications:" list. Qualifications? There's also "Preferred Qualifications". Could combine into Qualifications section? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we can have Requirements and Qualifications separate. We have Required Qualifications and Preferred Qualifications. Also there is "Educational Experiences That Stand Out" and "What Sets You Apart: Top Interns Consistently Demonstrate ..." and "What You'll Gain:" and "Why Start Your Career at Acxiom?" Those could be considered Skills? Not exactly. Might be better to put them under Skills or maybe under a separate section like "What You'll Gain". But the allowed headings list includes Skills. Could put "What You'll Gain" under Skills? Or maybe treat as Skills. However we must not create sections with filler. We need to decide which sections have substantive content.
We have:
- About The Role: paragraph.
- What You'll Do: list of duties (Solution Engineering & Business Analysis, Sales Support & Revenue Enablement, Proposal Development & Content Management, Market Research & Strategic Insights, Cross-Functional Collaboration). That's responsibilities.
- Required Qualifications: list.
- Preferred Qualifications: list.
- Educational Experiences That Stand Out: list.
- What Sets You Apart: list of traits.
- What You'll Gain: list.
- Why Start Your Career at Acxiom?: paragraph.
- Internship Details: start date, location, hours.
- Possibly also "Primary Location City/State: New York, New York" and "Additional Locations (if applicable):" etc. That's location info.
We need to map these to allowed headings.
We could have:
About the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
- for any list of duties/requirements/benefits. So we can have a single
- with all these items, or separate
- for any list of duties/requirements/benefits. It doesn't forbid nested headings inside? Probably we can keep subheadings as plain text or maybe . But we must output only HTML fragment; we can include
for subheadings? Not in allowed list but maybe okay. Safer to just list all items in one
- without subheadings. But we risk losing structure. However we must preserve ALL substantive information; not summarizing away detail. If we flatten, we still preserve each bullet point. Subheadings are not required to be preserved as headings; they are just formatting. We could keep them as plain text before each group, maybe using
- for any list,
for prose. It doesn't forbid other tags like or
. So we can include for subsection titles. Thus Responsibilities section:
Responsibilities
then maybeSolution Engineering & Business Analysis
- ...
Solution Engineering & Business Analysis
then- ... but that adds extra tags not prohibited. The instruction only says use
for section headings,
- for any list,
- per subsection? The rule: use
- for any list of duties/requirements/benefits. It doesn't forbid nested headings inside? Probably we can keep subheadings as plain text or maybe . But we must output only HTML fragment; we can include