2027 Summer Internship - Supply Chain (Arizona)

We need to output HTML fragment with sections: About the role? Actually the posting is about internship. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse content: The posting includes: - Intro: "Whether you’re a recent grad or a seasoned professional..." but that's generic. Might be considered "About the role"? Actually it's about company. Could be "About the role" maybe not. But we need to preserve substantive info. We have sections: "About The Program" (description of internship). That could be "About the role". Then "What You'll Gain" maybe "Responsibilities"? Actually responsibilities are duties. "What You'll Gain" is more like benefits/learning outcomes. Could be "Responsibilities"? Not exactly. "What We Look For" is requirements/qualifications. "What You Bring To Us" is qualifications/skills. "Working Conditions" maybe schedule? Not exactly. There's no explicit Pay, Benefits, Schedule. There's mention of paid 12 week internship, full benefits, Employee Stock Ownership Plan, competitive compensation. So we have some benefits and pay info: "paid 12 week hands-on experience", "competitive compensation", "full benefits", "Employee Stock Ownership Plan". So we can create Benefits section with those details. Pay section maybe "competitive compensation" but not specific amount; we should not create Pay section if only vague like "competitive compensation" (that's not specific). The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits: full benefits, ESOP. So Benefits section is okay. Pay: "competitive compensation" is vague but still states compensation. However rule says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "competitive compensation" is somewhat vague but still a statement. Might be okay to include Pay section with that phrase. But better to avoid if it's not specific. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive compensation". So we can include Pay section with that sentence. Schedule: It says "paid 12 week hands-on experience". That's schedule (duration). So we can include Schedule section with that. Now we need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content: - About the role: Could be the introductory paragraph about Rosendin and internship program description. Use "About The Program" as content. - Responsibilities: Could be "What You'll Gain"? Actually responsibilities are duties: "Apply classroom learning while exploring career paths and taking on meaningful responsibilities alongside industry leaders." Also "You'll gain exposure to the electrical construction industry by working on real projects alongside experienced professionals across areas such as: Project Management Engineering BIM (Building Information Modeling) Estimating & Preconstruction Procurement & Supply Chain". That's more like responsibilities/exposure. So we can list those as responsibilities. - Requirements: Could be "What We Look For" (coachability, curiosity, accountability, etc.) That's more like requirements/qualifications. - Qualifications: Could be "What You Bring To Us" (currently pursuing bachelor's degree, expected graduation Dec 2027 or later, rising junior/senior preferred, fields, etc.) - Skills: Could be "What You'll Need To Be Successful" (interest in procurement, supply chain, logistics, construction operations; strong organizational skills; analytical; communication; ability to build relationships; proficiency in MS Office; positive attitude). That's skills. - Benefits: "competitive compensation, full benefits, an Employee Stock Ownership Plan and more." Also maybe mention paid internship. We'll include those. - Pay: "competitive compensation". Could be same as benefits but we can separate. - Schedule: "paid 12 week hands-on experience". Also maybe mention summer internship program. We need to avoid boilerplate: remove EEO, legal, etc. At end there is EEO statement; we must remove that. Also remove navigation, cookie, etc. Not present. We must preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

Whether you’re a recent grad or a seasoned professional, you can experience meaningful career growth at Rosendin. Enjoy a true sense of ownership as you work with a proven industry leader on some of the most exciting and high-profile projects in the nation. We offer a wide range of job opportunities, competitive compensation, full benefits, an Employee Stock Ownership Plan and more. Why Rosendin? Committed. Innovative. Engaged. Come build your experience with us! At Rosendin, our interns are more than participants; they are contributors. Our internship program is designed to give you meaningful, hands-on experience in the electrical construction industry while helping you build the foundation for a successful career.

About The Program

maybe not needed if we used About the role. But we need to follow rule: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings. Not "About The Program". So we need to map content under those headings. So we will not use "About The Program" heading; we will put that content under About the role. Thus we need to decide what goes under each heading. Let's extract content: About the role: The introductory paragraph about Rosendin and internship program purpose. Responsibilities: The bullet list of areas (Project Management, Engineering, BIM, Estimating & Preconstruction, Procurement & Supply Chain) and maybe "Apply classroom learning while exploring career paths and taking on meaningful responsibilities alongside industry leaders." Also "You'll gain exposure to the electrical construction industry by working on real projects alongside experienced professionals". So we can list responsibilities as bullet list. Requirements: "What We Look For" bullet list: Coachability & Curiosity, Accountability & Work Ethic, Learning Agility & Adaptability, Collaboration & Communication. Qualifications: "What You Bring To Us": currently pursuing bachelor's degree with expected graduation Dec 2027 or later, rising junior or rising senior preferred, fields aligned (Supply Chain Management, Business Administration), previous internship experience in procurement/supply chain a plus. Skills: "What You'll Need To Be Successful": Interest in procurement, supply chain, logistics, construction operations; Strong organizational skills with attention to detail and accuracy; Strong analytical and problem-solving; Professional verbal and written communication skills; Ability to build collaborative relationships with internal teams and external partners; Proficiency in, or willingness to learn, Microsoft Office applications (Outlook, Word, Excel) and other business technologies; Positive attitude and commitment to continuous learning. Benefits: "competitive compensation, full benefits, an Employee Stock Ownership Plan and more." Also maybe mention paid internship? But that's schedule/pay. Pay: "competitive compensation". Could be same as benefits but we can still include. Schedule: "paid 12 week hands-on experience". Also maybe mention Summer Internship Program is a paid 12 week hands-on experience. We need to avoid duplication. If we put competitive compensation in both Benefits and Pay, that's duplication. Better to put compensation under Pay, and benefits under Benefits (full benefits, ESOP). The phrase "competitive compensation, full benefits, an Employee Stock Ownership Plan and more." includes compensation and benefits together. We could split: Pay: competitive compensation. Benefits: full benefits, Employee Stock Ownership Plan. Also maybe mention paid internship as part of schedule. Thus: Pay: competitive compensation. Benefits: full benefits; Employee Stock Ownership Plan. Schedule: paid 12 week hands-on experience (Summer Internship Program). Now we need to ensure we don't include filler like "and more". That's vague but it's part of the original; we can keep "and more" as part of benefits? Might be considered vague but it's from posting. We'll keep. Now we need to format lists: Use

• for any list of duties/requirements/benefits. For prose use

  . Thus: - About the role: prose

  . - Responsibilities: list of duties: maybe combine the exposure areas and the statement about applying classroom learning. We'll make a

  with items: "Apply classroom learning while exploring career paths and taking on meaningful responsibilities alongside industry leaders." "Gain exposure to the electrical construction industry by working on real projects alongside experienced professionals in areas such as:" then sublist? But we cannot nest? We can just list each area as separate
  • . We'll include a
  • for the statement, then each area. - Requirements: list from What We Look For: each bullet. - Qualifications: list from What You Bring To Us: each bullet. - Skills: list from What You'll Need To Be Successful: each bullet. - Benefits: list: full benefits; Employee Stock Ownership Plan; maybe also mention competitive compensation? No that's Pay. - Pay: prose: competitive compensation. - Schedule: prose: paid 12 week hands-on experience (Summer Internship Program). We must not include headings with empty content. All have content. Now we need to remove boilerplate: EEO statement at end, also maybe "We fully comply with the ADA..." that's a substantive? It's about working conditions and accommodation. Could be part of Working Conditions but we don't have a heading for Working Conditions. We could include it under Responsibilities? Not really. It's about working conditions and ADA compliance. Since we don't have a Working Conditions heading, we could incorporate it into Responsibilities or maybe under a generic paragraph? The instruction says we can only use those headings; we cannot add other headings. So we need to decide where to place that info. It's substantive: "Working Conditions General work environment - sitting for extended periods, standing, walking, typing, carrying, pushing, bending. Work is conducted primarily indoors with varying environmental conditions, such as fluorescent lighting and air conditioning. Noise level is typically low to medium; it can be loud on a job site. Occasional lifting of up to 30 lbs. We fully comply with the ADA and applicable state law, including considering reasonable accommodation measures that may enable qualified disabled applicants and employees to perform essential functions." We could put this under Responsibilities? Not exactly. Could be under a separate paragraph after Skills maybe as prose without heading? But we must use headings for sections; we can still have prose outside headings? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

    • for any list of duties/requirements/benefits, and

      for prose." It doesn't forbid having prose outside headings, but likely they expect sections with headings. However we could include a paragraph under a heading like "Responsibilities" that includes working conditions? Not ideal. Maybe we can treat working conditions as part of "Responsibilities" or "Skills"? Not really. Alternatively, we could create a section "Schedule"? No. We could create a section "Benefits"? No. We could create a section "Pay"? No. We could create a section "Requirements"? No. We could create a section "Qualifications"? No. We could create a section "About the role"? Could include working conditions there as part of description. Probably best to add a paragraph under About the role that includes working conditions? But that would mix. Alternatively, we could create a heading "Schedule" and include working conditions there? Not correct. Given the instruction to preserve ALL substantive information, we must include that working conditions info somewhere. Since we don't have a specific heading for it, we could add a

      after the last heading without a heading? The instruction says "