Engineering Intern- Summer 2027

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarized away detail. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO etc. Also remove the video link? The video link is part of "Take a peek into what makes us different here: https://youtu.be/...". That's likely promotional content, but not required? It's not a core job description; it's more about company culture. Might be considered boilerplate? It's not required to preserve; but it's part of the description about culture. However it's a link to a video; we could keep as part of prose? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The video link is not those categories; it's part of "It's How We're Different". Might be considered promotional but not disallowed. However we need to preserve all substantive information. The video link is not essential to job duties; but it's part of company description. Might be okay to keep as a

with the link? But we might decide to drop it as it's not essential. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The video link is not substantive to the role; it's more marketing. Could be considered non-essential. Safer to keep it? The instruction about removing boilerplate includes EEO etc. Not video. I'd keep it as a paragraph maybe. We need sections: About the role (maybe from position summary?), Responsibilities (Essential Duties And Responsibilities), Requirements (maybe Qualifications?), Skills (Skills And Requirements), Benefits (Let's Talk Perks + Benefits), Pay (Pay Transparency), Schedule (maybe Internship Duration). Also Qualifications section separate? The instruction list includes Qualifications as a possible heading. We have Qualifications (Required) and Preferred. Could combine into Qualifications section. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First, company intro: "At Henderson, We're About More Than Just Buildings...". That's about company culture. Could be placed under About the role? Actually About the role likely refers to position summary. But we have a Position Summary paragraph: "The Engineering Intern supports engineering design, drafting, and project coordination activities while gaining practical experience in building systems engineering. Working under the guidance of experienced engineers and designers, the intern assists with engineering calculations, technical documentation, system layouts, and professional development activities. Internship Duration: May 24, 2027 – August 6, 2027". That's the position summary. So we can put that under About the role? Or we could have a section About the role containing that summary. The internship duration could go under Schedule section. But we also have schedule: Internship Duration: May 24, 2027 – August 6, 2027. That's schedule. Thus we can have:

About the role

The Engineering Intern supports engineering design, drafting, and project coordination activities while gaining practical experience in building systems engineering. Working under the guidance of experienced engineers and designers, the intern assists with engineering calculations, technical documentation, system layouts, and professional development activities.

Then schedule section:

Schedule

Internship Duration: May 24, 2027 – August 6, 2027

Now Responsibilities: list of duties under Essential Duties And Responsibilities, broken into subcategories: Engineering Design, Drafting and Documentation, Learning and Development. We need to output a

• for any list of duties/requirements/benefits. So we can combine all duties into a list. Or we could keep subheadings? The instruction only says use

  for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings like

  but we should stick to those. We could keep subheadings as

  maybe bold? But better to just list all duties in a

  . However we might lose the categorization. But we can still include the subcategory names as part of list items. Eg: "Engineering Design: Assist with basic engineering calculations and system design under supervision; Prepare system layouts, drawings, schematics, and project documentation; Support equipment and component selection; Organize project materials and maintain technical documentation; Coordinate project information with other disciplines; Seek guidance and ask questions when completing unfamiliar tasks." etc. We need to preserve all substantive information; we can combine. Let's extract each bullet: Engineering Design: - Assist with basic engineering calculations and system design under supervision. - Prepare system layouts, drawings, schematics, and project documentation. - Support equipment and component selection. - Organize project materials and maintain technical documentation. - Coordinate project information with other disciplines. - Seek guidance and ask questions when completing unfamiliar tasks. Drafting and Documentation: - Assist in the production of construction documents and project deliverables. - Support drafting and modeling efforts using AutoCAD, Revit, and Bluebeam Revu. - Develop proficiency in design and documentation software. Learning and Development: - Participate in internship meetings, training programs, and company-sponsored activities. - Research and apply company standards, guidelines, and procedures. - Continuously develop engineering knowledge and technical skills. - Provide project and administrative support as needed. Now Requirements: The posting has "Qualifications" section with Required and Preferred. Also "Skills And Requirements". The instruction list includes Requirements and Qualifications as separate possible headings. We need to decide what goes where. Usually Requirements could be the Skills And Requirements (soft skills). Qualifications could be education/experience. Let's follow that. Thus:

  Qualifications

  Required: High School Diploma or GED. Currently pursuing a Bachelor's degree in Architectural Engineering, Electrical Engineering, Mechanical Engineering, or a related field from an ABET-accredited university.

  Preferred: Coursework or experience with AutoCAD, Revit, Navisworks, or other CAD software. Drafting certification. Previous internship experience. Exposure to building systems engineering. Knowledge of industry codes and standards.

  But we need to use
  • for any list of duties/requirements/benefits. For qualifications, it's a list; we should use
    • . So we can list required and preferred as separate lists or combine. Better to have two
      maybe under same heading? But we can just make one list with items; we can differentiate via text. However the instruction: Use
      • for any list of duties/requirements/benefits. So we should use list for qualifications items. Thus:

        Qualifications

        • High School Diploma or GED.
        • Currently pursuing a Bachelor's degree in Architectural Engineering, Electrical Engineering, Mechanical Engineering, or a related field from an ABET-accredited university.
        • Preferred: Coursework or experience with AutoCAD, Revit, Navisworks, or other CAD software.
        • Preferred: Drafting certification.
        • Preferred: Previous internship experience.
        • Preferred: Exposure to building systems engineering.
        • Preferred: Knowledge of industry codes and standards.
        But mixing required and preferred in same list may be okay. Could separate headings but not allowed. We'll keep as is. Now Skills And Requirements: list of skills. Extract: - Strong written and verbal communication skills. - Effective analytical and problem-solving abilities. - Ability to manage multiple priorities in a fast-paced environment. - Self-motivated, adaptable, and receptive to feedback. - Ability to perform the essential functions of the position with or without reasonable accommodation. - Occasional travel may be required. - Ability to work at a computer and use standard office equipment for extended periods. We'll put under

        Skills

        with
        . Now Benefits: We have "Let's Talk Perks" and "Benefits". Both are lists of perks and benefits. We'll combine into Benefits section. Let's extract perks: Culture: - Flexible Work Hours (Because we all need to balance work and life.) - Casual Dress Code (Be yourself, please.) - Paid Volunteer Time (We literally pay you to volunteer.) - Paid Parental Leave (Because we know both parents deserve to be there for a new child.) - Health and Wellness Initiatives (Get Fit and Stay Fit.) - Receptive and Forward-Thinking Leadership (Our doors are always open.) - Clear Career Path Options (We want you to excel.) Benefits: - Industry-leading 401K match and profit sharing (When the company succeeds, we all share in that success.) - Employee Stock Ownership Plan (Yes, our employees are the owners.) - Paid Training for Professional Development (We’ll pay for the time you take getting better at what you do.) - Performance Bonuses (When you do well, we reward you for your work.) - Comprehensive and Extensive Insurance (We’ve got you covered.) - Paid Term Life and Disability (We’ve got your family covered, too.) - Health Savings Account & Flexible Spending Accounts (We'll help you take advantage of tax savings.) - Paid Time Off and Sick Time off (Take a break. You deserve it!) - Financial Wellness & Coaching Program (Financial security makes you a happier team member.) We'll combine all into a
        under Benefits. Now Pay: Pay Transparency list with city ranges. Extract: - Denver- $26.40-$28.60 - Las Vegas- $25.20-$27.30 - New York- $29.28-$31.72 - Los Angeles- $27.84-$30.16 - Washington D.C- $27.84-$30.16 We'll put under

        Pay

        with
        . Now Schedule we already have. Now About the role: we have position summary paragraph. Also there is introductory company description at top. Should we include that? It's about company, not role. Might be considered "About the role"? Could be considered company overview. The instruction: Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So About the role likely expects a description of the role. The position summary is appropriate. The introductory paragraph about Henderson is more about company; could be omitted as not directly about role? But it's substantive info about the company; but the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit that introductory paragraph, we are losing substantive info about the company. However the section headings list does not include a "Company Overview" heading. We could still include a paragraph before the first heading? The instruction says output ONLY the HTML fragment; we can include

        elements not under a heading? It didn't forbid that. It said use

        for section headings (list). It didn't say we cannot have other headings or paragraphs outside those sections. But we should prefer a few substantive sections over many thin ones. We could include a

        for the company overview before the first heading. That would preserve info. However the instruction: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections;