Strategy & Management Summer Associate Program - 2027
Bank of America · Boston, NY · 1 mo ago
Business DevelopmentVolunteer
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Bank Of America" and "Strategy and Management Program". The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. We need to include sections only when posting has real specific content.
We have content: About Bank of America (description). Could map to "About the role"? But "About the role" is generic; we have "About Bank Of America". Could use "About the role" heading and put that content. Or we could use "About Bank of America" as heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. We need to include sections only when posting has real specific content.
We have content: About Bank of America (description). Could map to "About the role"? But "About the role" is generic; we have "About Bank Of America". Could use "About the role" heading and put that content. Or we could use "About Bank of America" as heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, but we can use other headings? Probably we should stick to those examples. So we need to map content to those headings.
We have:
- About the role: description of program, what you'll do, etc. Could include the "Strategy and Management Program" description and responsibilities.
- Responsibilities: list of duties (the bullet list after "As a Strategy & Management Summer intern you will get...").
- Requirements: maybe "Required Qualifications".
- Qualifications: maybe same as Requirements? Could combine? But we need separate sections only if content exists. We have Required Qualifications and Desired Skills. So we can have "Requirements" for Required Qualifications, and "Skills" for Desired Skills.
- Benefits: not explicitly stated besides generic benefits earlier (competitive benefits). The posting mentions "offering competitive benefits to support their physical, emotional, and financial well-being." That's a benefit statement. Could include Benefits section.
- Pay: not specified (no salary). So we should not include Pay.
- Schedule: they gave Travel: On needs basis, Full/Part-time: Full time, Hours Per Week: 40.00, Shift: 1st Shift. That's schedule info. So we can include Schedule section.
We must not include headings with filler like "not specified". So we include only those with real content.
We must not include boilerplate like EEO, application instructions, etc. Remove lines like "Please note: Bank of America is unable to consider candidates that will require visa sponsorship..." That's a requirement? It's a restriction; could be part of Requirements? Might be considered a qualification/eligibility. It's substantive. Should we include? It's a note about visa sponsorship and geographic flexibility. That's relevant to eligibility. Could be part of Requirements. We'll include it under Requirements.
Also "To ensure you receive all application updates..." is application instruction, should be removed.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like numbers, etc.
We'll produce HTML:
About the role
About the role
... content about Bank of America and Strategy and Management Program ...
ThenResponsibilities
- ... each bullet ...
Requirements
- ... each required qualification bullet ...
Skills
- ... desired skills bullet ...
Benefits
... competitive benefits statement ...
ThenSchedule
- Travel: On needs basis
- Full / Part-time: Full time
- Hours Per Week: 40.00
- Shift: 1st Shift