Investments Summer Intern
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading
4. Do NOT put Job ID / requisition numbers as headings
5. Preserve ALL substantive information
6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
7. Include a section ONLY when the posting has real, specific content for it
8. Never emit a heading followed by filler/placeholder text
9. Never create Pay/Schedule/Benefits sections unless the posting actually states them
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the content:
The posting has:
- "Who You'll Work With" - describes the investment teams (Equities, Fixed Income, Multi-Asset & Hedge Fund Solutions, Responsible Investing, Private Alternatives)
- "What You'll Do" - describes the internship program, examples of previous intern projects
- "What We're Looking For" - requirements/qualifications
- "About AB" - company description
- Salary information at the end: "Base Salary Range: $105,000.00 to $105,000.00" and benefits mentioned
- Location: "New York, New York"
I need to structure this into appropriate sections. Let me think about the sections:
1. "Who You'll Work With" could be "About the role" or "About the team" - but the rule says use specific headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". I should map to these.
Actually, the rules say: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So these are examples, not exhaustive. But I should use these standard ones where appropriate.
Let me map:
- "Who You'll Work With" → could be "About the role" or "About the team" - but "About the role" is suggested. This section describes the teams the intern will work with, so it's about the role context.
- "What You'll Do" → "Responsibilities" (but it's more about the program description and examples of projects)
- "What We're Looking For" → "Requirements" or "Qualifications"
- "About AB" → "About the company" but not in the suggested list. Could be "About the role" but that's already used. Maybe I should include it as a section since it's substantive.
- Salary and benefits → "Pay" and "Benefits" sections
The rules say: "include a section ONLY when the posting has real, specific content for it". So I should include Pay and Benefits since they are specified.
Also, the salary is given as a range: $105,000 to $105,000 (so fixed). Benefits are listed: health insurance, wellness program, life and disability insurance, retirement savings plan, paid holidays, sick and vacation time off.
Location: "New York, New York" - could be part of a "Schedule" or "Location" but not in suggested headings. Might fold into a short
or include in "Schedule" if there's schedule info. The posting says "Candidates must be able to work full-time, in-person, from June through August" - that's schedule info.
Also, there's metadata: "December 2027 through May/June 2028 bachelor's degree candidates" - that's part of requirements.
I need to remove EEO boilerplate: "All are encouraged to apply. AB does not discriminate..." - that's EEO boilerplate, should be removed.
Also remove "In accordance with applicable law, the minimum and maximum base annual salary for this role is as follows:" - that's legal boilerplate, but the salary info itself is substantive.
Now, let me structure the HTML.
I'll create sections:
1.
About the role
- for "Who You'll Work With" content
2. Responsibilities
- for "What You'll Do" content (the program description and project examples)
3. Requirements
- for "What We're Looking For" content
4. About the company
- for "About AB" (though not in suggested list, it's substantive)
5. Pay
- for salary range
6. Benefits
- for benefits list
7. Schedule
- for work schedule (full-time, in-person, June through August) and location
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "About the company" is not in the list, but it's a common section. However, the rule says "e.g." meaning examples. I think it's okay to include "About the company" as it's substantive. But to be safe, maybe I can fold "About AB" into "About the role" or a separate section. The rule says "Prefer a few substantive sections over many thin ones." So I could combine.
Alternatively, I could have "About the role" include both "Who You'll Work With" and "About AB". But they are distinct.
Let me check the content: "Who You'll Work With" describes the investment teams. "About AB" describes the firm overall. Both are about the context of the role.
I'll create:
- About the role
with two subsections? But HTML doesn't have subsections in this flat structure. I'll just use
and
under the heading.
Better to have separate headings for clarity. The rules don't forbid additional headings beyond the examples. It says "e.g." So I'll use appropriate headings.
I'll use:
- About the team
for "Who You'll Work With"
- Responsibilities
for "What You'll Do"
- Requirements
for "What We're Looking For"
- About the company
for "About AB"
- Pay
for salary
- Benefits
for benefits
- Schedule
for schedule and location
But "About the team" is not in the example list. The example list includes "About the role". I could use "About the role" for the team description. Then "About the company" for the firm description.
Let me decide: The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say I cannot use other headings. But to be consistent, I'll map to these where possible.
"Who You'll Work With" is about the teams the intern will work with, which is part of the role context. So "About the role" fits.
"What You'll Do" is responsibilities.
"What We're Looking For" is requirements/qualifications.
"About AB" is about the company - not in list, but I'll include as "About the company" or maybe fold into "About the role". Since the rule says "Prefer a few substantive sections over many thin ones", I could combine "About the role" and "About the company" into one "About the role" section with two paragraphs.
But they are distinct: one describes the investment teams, the other describes the firm. I'll keep separate but use "About the role" for the first and "About the company" for the second. The rule doesn't explicitly forbid "About the company". I think it's fine.
Now, for the content:
"Who You'll Work With" has descriptions of each team. I'll put as prose paragraphs, maybe with a list for the team names? The content is prose describing each team. I'll keep as paragraphs.
"What You'll Do" has a description of the program and then "Examples Of Previous Intern Projects Include" with a list. I'll put the description as prose, and the examples as a list.
"What We're Looking For" has a list of requirements. I'll put as a list.
"About AB" is prose.
Pay: "Base Salary Range: $105,000.00 to $105,000.00" and note about actual base salaries varying. I'll include as prose.
Benefits: list of benefits.
Schedule: "Candidates must be able to work full-time, in-person, from June through August" and location "New York, New York". I'll include as prose.
Also, there's "Must be a U.S. Citizen or Permanent Resident..." etc. Those are requirements, already in "What We're Looking For".
Now, I need to remove EEO boilerplate: "All are encouraged to apply. AB does not discriminate..." - remove.
Also remove "In accordance with applicable law, the minimum and maximum base annual salary for this role is as follows:" - that's legal boilerplate, but the salary info is needed. I'll keep the salary range but not that sentence.
Also remove "Actual base salaries may vary based on factors including but not limited to education, training, experience, past performance, and other job-related factors. Base salary is just one component of total compensation at AB, which may include, depending on eligibility, commissions, year-end incentive compensation, short- and long-term incentives and Department-specific awards." - this is also boilerplate about compensation structure. But it's specific to this role? It says "for this role". Might be considered substantive. However, the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is legal boilerplate about compensation. I think I should keep the salary range and benefits, but the explanatory text about variation and other components might be boilerplate. But it's specific to the posting. I'll keep it as part of Pay section.
Similarly, "In addition, AB provides a variety of benefits to eligible employees, including..." is substantive.
Now, let's write the HTML.
I'll start with About the role
for "Who You'll Work With".
Then Responsibilities
for "What You'll Do".
Then Requirements
for "What We're Looking For".
Then About the company
for "About AB".
Then Pay
for salary.
Then Benefits
for benefits.
Then Schedule
for schedule and location.
I'll use
for prose,
- for lists.
Now, let's extract the content precisely.
"Who You'll Work With" text:
"AllianceBernstein’s investment teams include Equities, Fixed Income, Multi-Asset & Hedge Fund Solutions, Responsible Investing, and Private Alternatives in total manage over 759 billion in assets: Equities –Manages assets for a wide variety of institutional, high-net-worth and retail clients. Investment professionals’ mange portfolios of equities ranging from small cap to mega cap stocks, spanning the style spectrum from value to core to growth, covering all geographies and including specialized portfolios
for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID / requisition numbers as headings 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include a section ONLY when the posting has real, specific content for it 8. Never emit a heading followed by filler/placeholder text 9. Never create Pay/Schedule/Benefits sections unless the posting actually states them 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the content: The posting has: - "Who You'll Work With" - describes the investment teams (Equities, Fixed Income, Multi-Asset & Hedge Fund Solutions, Responsible Investing, Private Alternatives) - "What You'll Do" - describes the internship program, examples of previous intern projects - "What We're Looking For" - requirements/qualifications - "About AB" - company description - Salary information at the end: "Base Salary Range: $105,000.00 to $105,000.00" and benefits mentioned - Location: "New York, New York" I need to structure this into appropriate sections. Let me think about the sections: 1. "Who You'll Work With" could be "About the role" or "About the team" - but the rule says use specific headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". I should map to these. Actually, the rules say: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So these are examples, not exhaustive. But I should use these standard ones where appropriate. Let me map: - "Who You'll Work With" → could be "About the role" or "About the team" - but "About the role" is suggested. This section describes the teams the intern will work with, so it's about the role context. - "What You'll Do" → "Responsibilities" (but it's more about the program description and examples of projects) - "What We're Looking For" → "Requirements" or "Qualifications" - "About AB" → "About the company" but not in the suggested list. Could be "About the role" but that's already used. Maybe I should include it as a section since it's substantive. - Salary and benefits → "Pay" and "Benefits" sections The rules say: "include a section ONLY when the posting has real, specific content for it". So I should include Pay and Benefits since they are specified. Also, the salary is given as a range: $105,000 to $105,000 (so fixed). Benefits are listed: health insurance, wellness program, life and disability insurance, retirement savings plan, paid holidays, sick and vacation time off. Location: "New York, New York" - could be part of a "Schedule" or "Location" but not in suggested headings. Might fold into a short
or include in "Schedule" if there's schedule info. The posting says "Candidates must be able to work full-time, in-person, from June through August" - that's schedule info. Also, there's metadata: "December 2027 through May/June 2028 bachelor's degree candidates" - that's part of requirements. I need to remove EEO boilerplate: "All are encouraged to apply. AB does not discriminate..." - that's EEO boilerplate, should be removed. Also remove "In accordance with applicable law, the minimum and maximum base annual salary for this role is as follows:" - that's legal boilerplate, but the salary info itself is substantive. Now, let me structure the HTML. I'll create sections: 1.
About the role
- for "Who You'll Work With" content 2.Responsibilities
- for "What You'll Do" content (the program description and project examples) 3.Requirements
- for "What We're Looking For" content 4.About the company
- for "About AB" (though not in suggested list, it's substantive) 5.Pay
- for salary range 6.Benefits
- for benefits list 7.Schedule
- for work schedule (full-time, in-person, June through August) and location But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "About the company" is not in the list, but it's a common section. However, the rule says "e.g." meaning examples. I think it's okay to include "About the company" as it's substantive. But to be safe, maybe I can fold "About AB" into "About the role" or a separate section. The rule says "Prefer a few substantive sections over many thin ones." So I could combine.
Alternatively, I could have "About the role" include both "Who You'll Work With" and "About AB". But they are distinct.
Let me check the content: "Who You'll Work With" describes the investment teams. "About AB" describes the firm overall. Both are about the context of the role.
I'll create:
- About the role
with two subsections? But HTML doesn't have subsections in this flat structure. I'll just use
and
- under the heading.
Better to have separate headings for clarity. The rules don't forbid additional headings beyond the examples. It says "e.g." So I'll use appropriate headings.
I'll use:
-
- for lists. Now, let's extract the content precisely. "Who You'll Work With" text: "AllianceBernstein’s investment teams include Equities, Fixed Income, Multi-Asset & Hedge Fund Solutions, Responsible Investing, and Private Alternatives in total manage over 759 billion in assets: Equities –Manages assets for a wide variety of institutional, high-net-worth and retail clients. Investment professionals’ mange portfolios of equities ranging from small cap to mega cap stocks, spanning the style spectrum from value to core to growth, covering all geographies and including specialized portfolios
About the team
for "Who You'll Work With" -Responsibilities
for "What You'll Do" -Requirements
for "What We're Looking For" -About the company
for "About AB" -Pay
for salary -Benefits
for benefits -Schedule
for schedule and location But "About the team" is not in the example list. The example list includes "About the role". I could use "About the role" for the team description. Then "About the company" for the firm description. Let me decide: The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say I cannot use other headings. But to be consistent, I'll map to these where possible.
"Who You'll Work With" is about the teams the intern will work with, which is part of the role context. So "About the role" fits.
"What You'll Do" is responsibilities.
"What We're Looking For" is requirements/qualifications.
"About AB" is about the company - not in list, but I'll include as "About the company" or maybe fold into "About the role". Since the rule says "Prefer a few substantive sections over many thin ones", I could combine "About the role" and "About the company" into one "About the role" section with two paragraphs.
But they are distinct: one describes the investment teams, the other describes the firm. I'll keep separate but use "About the role" for the first and "About the company" for the second. The rule doesn't explicitly forbid "About the company". I think it's fine.
Now, for the content:
"Who You'll Work With" has descriptions of each team. I'll put as prose paragraphs, maybe with a list for the team names? The content is prose describing each team. I'll keep as paragraphs.
"What You'll Do" has a description of the program and then "Examples Of Previous Intern Projects Include" with a list. I'll put the description as prose, and the examples as a list.
"What We're Looking For" has a list of requirements. I'll put as a list.
"About AB" is prose.
Pay: "Base Salary Range: $105,000.00 to $105,000.00" and note about actual base salaries varying. I'll include as prose.
Benefits: list of benefits.
Schedule: "Candidates must be able to work full-time, in-person, from June through August" and location "New York, New York". I'll include as prose.
Also, there's "Must be a U.S. Citizen or Permanent Resident..." etc. Those are requirements, already in "What We're Looking For".
Now, I need to remove EEO boilerplate: "All are encouraged to apply. AB does not discriminate..." - remove.
Also remove "In accordance with applicable law, the minimum and maximum base annual salary for this role is as follows:" - that's legal boilerplate, but the salary info is needed. I'll keep the salary range but not that sentence.
Also remove "Actual base salaries may vary based on factors including but not limited to education, training, experience, past performance, and other job-related factors. Base salary is just one component of total compensation at AB, which may include, depending on eligibility, commissions, year-end incentive compensation, short- and long-term incentives and Department-specific awards." - this is also boilerplate about compensation structure. But it's specific to this role? It says "for this role". Might be considered substantive. However, the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is legal boilerplate about compensation. I think I should keep the salary range and benefits, but the explanatory text about variation and other components might be boilerplate. But it's specific to the posting. I'll keep it as part of Pay section.
Similarly, "In addition, AB provides a variety of benefits to eligible employees, including..." is substantive.
Now, let's write the HTML.
I'll start with About the role
for "Who You'll Work With".
Then Responsibilities
for "What You'll Do".
Then Requirements
for "What We're Looking For".
Then About the company
for "About AB".
Then Pay
for salary.
Then Benefits
for benefits.
Then Schedule
for schedule and location.
I'll use
for prose,