2027 Summer Internship - Construction Management (Arizona))

We need to output HTML fragment with sections for headings where content exists. The posting includes: About The Program, What You'll Gain, What We Look For, What You Bring To Us, What You'll Need To Be Successful, Working Conditions, plus some intro paragraphs. Also mention "paid 12 week hands-on experience" (pay? It says paid but not amount; we should not create Pay section unless amount specified. So we can include mention of paid in About The Program paragraph. Benefits: mention full benefits, Employee Stock Ownership Plan, etc. So we can have Benefits section. Schedule: mention 12 week summer internship (duration). Could be schedule? Probably we can include Schedule section with "12-week summer internship". The posting says "paid 12 week hands-on experience". That's schedule info. So we can include Schedule section. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO duplicated lines; we should keep only one mention? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines. So we should remove the repeated EEO statements. Keep maybe one? But better to remove all EEO boilerplate. However we need to preserve substantive information; EEO is not substantive for job description? It's boilerplate; remove. We need to 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. We need to decide which sections to include based on content. Sections possible: - About The Program (could map to About the role? but heading should be About the role? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those exact headings if appropriate. But we can also use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings when applicable. However the posting has sections like "About The Program", "What You'll Gain", "What We Look For", "What You Bring To Us", "What You'll Need To Be Successful", "Working Conditions". We could map them to appropriate headings: About The Program -> About the role (or maybe About the role). What You'll Gain -> maybe Benefits? But Benefits is separate. Could treat What You'll Gain as Benefits? Not exactly. Could treat as "What You'll Gain" as a section heading but not in the list; but instruction says use those examples, not exclusive. Safer to use those headings where they match. For sections not matching, we could still use

  with the actual heading text from posting. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, just gives examples. So we can use the actual headings from posting. Thus we will output:

  About The Program

  ... (the paragraph about paid 12 week hands-on experience, exposure to areas)

  Then maybe a
  for the list of areas: Project Management, Engineering, BIM, Estimating & Preconstruction, Procurement & Supply Chain. Then

  What You'll Gain

  list of bullet points. Then

  What We Look For

  list of bullet points. Then

  What You Bring To Us

  ... (the paragraph about pursuing bachelor's degree, graduation date, fields, etc.) Possibly also list of fields? It's a paragraph with bullet-like list but we can keep as

  . Then

  What You'll Need To Be Successful

  list of bullet points. Then

  Working Conditions

  ... (the paragraph about work environment). Then maybe

  Benefits

  ... (competitive compensation, full benefits, Employee Stock Ownership Plan, etc.) Actually we have mention of competitive compensation, full benefits, ESOP. Could be Benefits section. Schedule: we could include

  Schedule

  with

  Paid 12‑week summer internship.

  Pay: not specified amount, so we should not create Pay section. We must not include filler like "commensurate with experience". Not present. We need to preserve all substantive information; do not invent or summarize away detail. We must remove duplicated lines: there are duplicate EEO statements; we will remove them. We must not include navigation, cookie, legal, etc. Not present. Now craft HTML. We need to ensure proper nesting: each

  followed by either

  or

  • . Use
    • for any list. Let's extract content. Intro paragraphs: "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." We could keep this as a leading

      before sections, or incorporate into About The Program. Probably better to have a leading

      summarizing the company and then sections. But instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it." So we can have an introductory

      . Now About The Program section: "Rosendin’s Summer Internship Program is a paid 12 week hands-on experience designed for students ready to take the next step in their professional journey. You'll gain exposure to the electrical construction industry by working on real projects alongside experienced professionals across areas such as: Project ManagementEngineeringBIM (Building Information Modeling)Estimating & PreconstructionProcurement & Supply Chain Apply classroom learning while exploring career paths and taking on meaningful responsibilities alongside industry leaders." Note there is missing spaces after commas; but we keep as is. We'll make a

      for the first sentence, then a

      for the list. List items: Project Management, Engineering, BIM (Building Information Modeling), Estimating & Preconstruction, Procurement & Supply Chain. Now What You'll Gain: bullet list: - Hands-on experience contributing to active projects - Opportunities to take ownership of meaningful work and make an impact - Mentorship and guidance from industry experts - Exposure to electrical construction systems, processes, and technologies - Development of technical, professional, and leadership skills - Networking opportunities across teams and business functions Now What We Look For: bullet list: - Coachability & Curiosity – Eager to learn, seek feedback, and take initiative - Accountability & Work Ethic – Takes ownership, follows through, and delivers high-quality work - Learning Agility & Adaptability – Thrives in fast-paced environments and quickly applies new knowledge - Collaboration & Communication – Works effectively with others and communicates clearly and professionally Now What You Bring To Us: paragraph: "You are currently pursuing a bachelor's degree with a graduation date of December 2027 or later in a field aligned with Rosendin's work including but not limited to: Rising junior or rising senior status preferredConstruction Management or Construction EngineeringEngineering disciplines (Architectural, Electrical, Civil, Mechanical, Construction, etc.)BIM (Building Information Modeling)Estimating & PreconstructionProcurement & Supply ChainPrevious construction internship experience is a plus" We need to keep the content; maybe break into

      and maybe a

      for the fields? The instruction says use
      • for any list of duties/requirements/benefits. This is a list of fields; could be considered a list. So we could make a
        for the fields. But the text includes "Rising junior or rising senior status preferred" as separate item. Might be better to keep as

        with the list separated by commas or semicolons. However to follow instruction, we could treat as list. Let's parse: "You are currently pursuing a bachelor's degree with a graduation date of December 2027 or later in a field aligned with Rosendin's work including but not limited to: Rising junior or rising senior status preferredConstruction Management or Construction EngineeringEngineering disciplines (Architectural, Electrical, Civil, Mechanical, Construction, etc.)BIM (Building Information Modeling)Estimating & PreconstructionProcurement & Supply ChainPrevious construction internship experience is a plus" There are missing spaces after colons and between items. We'll keep as is but maybe add spaces for readability? We must not invent detail; adding spaces is okay as formatting but not changing content. We'll keep the text as given but we can add spaces for readability; it's not altering substantive info. Safer to keep exactly as given? The instruction says preserve ALL substantive information; adding spaces is not changing substantive info. It's fine. We'll output as

        with the sentence then maybe a

        for the list after colon. Better:

        You are currently pursuing a bachelor's degree with a graduation date of December 2027 or later in a field aligned with Rosendin's work including but not limited to:

        • Rising junior or rising senior status preferred
        • Construction Management or Construction Engineering
        • Engineering disciplines (Architectural, Electrical, Civil, Mechanical, Construction, etc.)
        • BIM (Building Information Modeling)
        • Estimating & Preconstruction
        • Procurement & Supply Chain
        • Previous construction internship experience is a plus
        That seems reasonable. Now What You'll Need To Be Successful: bullet list: - Interest in applying technical knowledge to real-world projects and challenges - Strong organizational skills with attention to detail and accuracy - Ability to manage multiple tasks and adapt to changing priorities - Strong analytical and problem-solving skills - Professional verbal and written communication skills - Ability to collaborate effectively with diverse teams and stakeholders - Proficiency in, or willingness to learn, Microsoft Office applications (Outlook, Word, Excel) and other industry-related technologies - Positive attitude and commitment to continuous learning Now Working Conditions: paragraph: "General work environment: This position is performed primarily on active construction sites. Activities include sitting for extended periods, standing, walking, typing, carrying, pushing, and bending. Work is conducted primarily indoors with varying environmental conditions, such as fluorescent lighting and air conditioning.Noise level is typically low to medium.Occasional lifting of up to 30 lbs." We need to keep as is; maybe add spaces after periods. Now Benefits section: from intro: "We offer a wide range of job opportunities, competitive compensation, full benefits, an Employee Stock Ownership Plan and more." Also later: "Rosendin is one of the largest electrical contractors in the United States employing over 10,000 people. We are EMPLOYEE OWNED (ESOP) and have a wonderful reputation for building quality electrical and communications installations, building value for clients, and building people’s careers within the company." That's more about company but could be part of Benefits? Might be considered general info. We'll create Benefits section with bullet list: competitive compensation, full benefits, Employee Stock Ownership Plan (ESOP