Purchasing Intern (Year-Round)

We need to output HTML fragment with sections: About the role? The posting includes "About the Purchasing Internship:" which is a heading. Use

for section headings. We need to include sections only if there is real content. We have: About the Purchasing Internship (maybe heading "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map "About the Purchasing Internship" to

About the role

or maybe keep the exact heading? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid using other headings, but suggests those as examples. Probably we should use those standard headings. So we need to decide which sections apply. Content: - About the Purchasing Internship: description of hands-on experience etc. That's about the role. So we can put under

About the role

with paragraphs. - Program structure: includes Schedule, Location, Start Date, Duration. Schedule is given: Part-time (15-20 hours/week) during academic year and full-time (40 hours/week) during summer. Location: Cleveland, OH. Start Date: January 2027. Duration: Year-round internship. We should include Schedule section if posting actually states it. Yes schedule is given. So

Schedule

with

Part-time (15-20 hours/week) during the academic year and full-time (40 hours/week) during the summer

. Location maybe not a standard heading; could be part of About the role or separate? Not in list. Could embed in About the role paragraph. Probably include location in About the role paragraph. Start Date and Duration maybe not separate headings; could be in About the role or Schedule? Not in list. Could embed in About the role. - What we're looking for: list of qualifications. That's Requirements/Qualifications. Use

Requirements

with

• items. List: Enrollment in a four-year degree program in Supply Chain Management, Business or a related field with current status of at least a Sophomore level; Cumulative GPA of 2.75 or higher; Proficient in Microsoft Office software: Excel, Word, and PowerPoint; Strong verbal and written communication skills; Strong interpersonal and relationship building skills; Ability to succeed in a team environment; Ability to handle multiple tasks. - Preferred experience: ERP experience; Purchasing experience; Lean manufacturing, Six Sigma, 5S tools. That could be under

  Preferred qualifications

  but not in list. Could be under Requirements or Skills. Maybe combine into Requirements as "Preferred experience". But we can create a section "Preferred qualifications" but instruction says use those examples; but we can still create a heading if content exists. Safer to put under Requirements as separate bullet points labeled "Preferred". But we need to preserve all info. Could create a

  Preferred qualifications

  even if not in examples; but 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 suggests those as examples. I'd stick to those. So we can put preferred experience under Requirements as well, maybe separate bullet list with note "Preferred". Or we could have a

  Skills

  for skills like communication, interpersonal, teamwork, etc. But we already have those in Requirements. Could separate: Requirements (education, GPA, Office proficiency) and Skills (communication, interpersonal, teamwork, multitasking). Preferred experience could be under Qualifications? Hmm. Better: Use

  Requirements

  for education, GPA, Office proficiency.

  Skills

  for communication, interpersonal, teamwork, multitasking.

  Preferred qualifications

  for ERP, purchasing, Lean/Six Sigma/5S. But "Preferred qualifications" not in examples; maybe we can use

  Qualifications

  for both required and preferred? The examples include Qualifications. So we could have

  Qualifications

  containing both required and preferred? But we need to not repeat headings unnecessarily. Could have one Qualifications section with sub-bullets marking required vs preferred. That might be acceptable. Simplify: Use

  About the role

  for description.

  Schedule

  for schedule.

  Requirements

  for all bullet points (including preferred). That covers all. We must not include Benefits, Pay sections because not specified. Also remove boilerplate like "#CharterSteel Internship positions are not benefits-eligible." That's a benefits statement but says not benefits-eligible. According to instruction: do NOT create Benefits section unless posting actually states them. It states they are not benefits-eligible, which is a statement about benefits. Should we include? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about benefits (not eligible). So we could include a Benefits section stating that interns are not benefits-eligible. However, they said "Interns are not benefits-eligible." That's a statement about benefits. So we could include a Benefits section with that sentence. But we need to check if we should include it. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." Since they state that interns are not benefits-eligible, we can include a Benefits section with that info. However, they also said "Prefer a few substantive sections over many thin ones." So maybe we can incorporate that into About the role or Schedule? But it's about benefits. Could add a Benefits section with

  Interns are not benefits-eligible.

  . That seems appropriate. Also we need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's a hashtag line "#CharterSteel Internship positions are not benefits-eligible." That's basically the benefits statement. We'll keep the substance but remove the hashtag. Now produce HTML fragment. Structure:

  About the role

  ... paragraphs ...

  Maybe we need to split description into multiple paragraphs? Could keep as one

  with sentences. Content for About the role: "You’ll gain hands-on experience across the end-to-end procurement lifecycle, including strategic sourcing, supplier relationships, RFPs, bid analysis, and spend analysis. You’ll also strengthen your analytical, project management, problem-solving, and communication skills while collaborating with suppliers and cross-functional teams to support real business needs." Also mention location? Could add "Located in Cleveland, OH." Also mention schedule? Already separate. We'll include location and maybe start date/duration in About the role? But we have schedule separate; location could be in About the role. Let's craft:

  You’ll gain hands-on experience across the end-to-end procurement lifecycle, including strategic sourcing, supplier relationships, RFPs, bid analysis, and spend analysis. You’ll also strengthen your analytical, project management, problem-solving, and communication skills while collaborating with suppliers and cross-functional teams to support real business needs. This internship is based in Cleveland, OH.

  Now Schedule section:

  Schedule

  Part-time (15-20 hours/week) during the academic year and full-time (40 hours/week) during the summer.

  Now Requirements section:

  Requirements

  • Enrollment in a four-year degree program in Supply Chain Management, Business or a related field with current status of at least a Sophomore level
  • Cumulative GPA of 2.75 or higher
  • Proficient in Microsoft Office software: Excel, Word, and PowerPoint
  • Strong verbal and written communication skills
  • Strong interpersonal and relationship building skills
  • Ability to succeed in a team environment
  • Ability to handle multiple tasks
  • Preferred experience: ERP experience, Purchasing experience, Lean manufacturing, Six Sigma, 5S tools
  We could split preferred into separate bullet but it's okay. Now Benefits section:

  Benefits

  Interns are not benefits-eligible.

  Check if any other content: "Program structure: Schedule: Part-time (15-20 hours/week) during the academic year and full-time (40 hours/week) during the summerLocation: Cleveland, OHStart Date: January 2027Duration: Year-round internship". We used schedule and location; we omitted start date and duration. Should we include them? They are substantive. Could add them to About the role or Schedule? Since we have Schedule section, we could add start date and duration there as well. But schedule section is specifically about schedule; start date and duration are not schedule but program structure. Could add another section like "Program details" but not in examples. Could add to About the role paragraph: "Start date: January 2027; Duration: Year-round internship." That would preserve info. Let's update About the role paragraph to include location, start date, duration. Thus:

  You’ll gain hands-on experience across the end-to-end procurement lifecycle, including strategic sourcing, supplier relationships, RFPs, bid analysis, and spend analysis. You’ll also strengthen your analytical, project management, problem-solving, and communication skills while collaborating with suppliers and cross-functional teams to support real business needs. This internship is based in Cleveland, OH, with a start date of January 2027 and a year‑round duration.

  Now schedule remains as before. Now ensure we didn't repeat job title as heading. We didn't. Check for any boilerplate removed: The hashtag line removed. Also removed "Charter Manufacturing is a fourth-generation family-owned business..." etc. That's descriptive but maybe considered boilerplate? It's about company; could be considered part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not boilerplate per se; it's substantive about the company. Could keep it? It might be considered fluff but it's about the company. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info. However, we already have About the role section focusing on internship. Could we include company description in About the role? Might be appropriate to add a sentence about the company. But we already have a paragraph about internship; we could add another paragraph about company. Let's include a second paragraph under About the role: "Charter Manufacturing is a fourth-generation family-owned business where our will to grow drives us to do it better. Charter Steel is a leading American supplier of carbon and alloy steel bar, rod and wire products, and the largest steel coil processor in North America. As a fully integrated steelmaker with locations in Ohio and Wisconsin, Charter Steel offers a full range of grade and size coiled products and vast technical service experience. Charter Steel is a member of the Charter Manufacturing family of companies." That preserves company info. Now ensure we didn't include any duplicated lines. Looks fine. Now output HTML fragment only. Let's craft final HTML:

  About the role

  You’ll gain hands-on experience across the end-to-end procurement lifecycle, including strategic sourcing, supplier relationships, RFPs, bid analysis, and spend analysis. You’ll also strengthen your analytical, project management, problem-solving, and communication skills while collaborating with suppliers and cross-functional teams to support real business needs.

  Charter Manufacturing is a fourth-generation family-owned business