Engineering Intern

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the posting. Content: - About Harmon: description of company and internship. Could be "About the role" or maybe "About Harmon". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" heading for the description about the internship. - Responsibilities: "What You'll Do" bullet list. - Requirements/Qualifications: "What We're Looking For" includes bullet list of desired attributes, then "Minimum Qualifications" bullet list. We could combine into Requirements and Qualifications sections? The instruction says we can have sections for Requirements, Qualifications, Skills. We need to decide. We have "What We're Looking For" (soft skills) and "Minimum Qualifications" (education, GPA, AutoCAD). Could treat "What We're Looking For" as Skills or Requirements. Minimum Qualifications as Qualifications. We also have "What You'll Gain" which could be Benefits? But there is also a separate "Our Benefits" section listing benefits. So we have two benefit-like sections: "What You'll Gain" (internship gains) and "Our Benefits" (employee benefits). The instruction says include Benefits section only if posting actually states them. The posting does state benefits under "Our Benefits". So we should include a Benefits section with that list. We should not include Pay or Schedule because not mentioned. We should not repeat job title as heading. We should remove boilerplate: EEO line at end: "Apogee and our brands are an Equal Opportunity Employer." Remove. Also remove navigation/cookie etc none. We need to preserve all substantive information. Let's extract: About the role: The paragraph after "About Harmon Harmon is seeking a motivated Engineering Intern..." Actually the text: "Harmon, Inc. Locations: Cincinnati, OH | Minneapolis, MN About Harmon Harmon is seeking a motivated Engineering Intern to join our team for the summer. This internship offers an exciting opportunity to gain hands-on experience in the design and engineering of exterior curtain wall systems while working alongside experienced engineers and industry professionals. As an Engineering Intern, you will learn the fundamentals of facade engineering, project design, and construction documentation while contributing to real-world projects. Through mentorship and practical experience, you will develop technical skills and gain exposure to the engineering processes that support some of the most innovative building projects across North America." We can put that under

About the role

as a

. Responsibilities: The list under "What You'll Do As an Engineering Intern, you will:" then bullet points each starting with a verb. We'll output

• each. We need to keep each bullet as is. List items: - Support the design and engineering of exterior curtain wall systems. - Learn to read and interpret architectural drawings, structural drawings, and project specifications. - Assist with coordinating engineering calculations and shop drawings. - Support project evaluations, material take-offs, and proposal development. - Gain knowledge of Harmon products, services, operations, and engineering processes. - Learn and apply thermal analysis and structural analysis methodologies and software. - Develop engineering calculations and technical deliverables for proposals and projects. - Assist with reviewing blueprints and construction drawings to produce engineering documentation. - Utilize computer-aided drafting (CAD) tools to support engineering and design activities. - Assist Designers in creating proposal and project drawings using AutoCAD and 3D AutoCAD. - Support the maintenance and enhancement of engineering software tools, databases, and drafting standards. - Participate in meetings with architects, general contractors, and project teams to discuss design solutions and project requirements. - Identify opportunities to simplify and improve design processes. - Apply Continuous Improvement principles to daily work and support operational excellence initiatives. Now Requirements/Qualifications/Skills. We have "What We're Looking For Successful Candidates Will Demonstrate" bullet list: - Strong interest in engineering, construction, and building systems. - Excellent analytical and problem-solving abilities. - Strong attention to detail and organizational skills. - Ability to read and interpret technical drawings and specifications. - Effective verbal and written communication skills. - Ability to collaborate within a team environment. - Curiosity and a desire to learn new technologies and engineering concepts. - Interest in design software, engineering calculations, and construction technologies. We could put this under

  Skills

  or Requirements. Since they are desired attributes, maybe Skills. Then "Minimum Qualifications" bullet list: - Pursuing a Bachelor's degree in: - Civil Engineering - Structural Engineering - Mechanical Engineering - Architectural Engineering - Construction Engineering - Or a related engineering field - Junior or Senior standing preferred. - Cumulative GPA of 3.0 or higher preferred. - AutoCAD experience is a plus. We need to preserve the structure. Could output as
  • with nested list for the degree fields. Now Benefits: "Our Benefits" paragraph then list: - Competitive Benefits Package for employees and their dependents (Medical, Dental, Vision, Life, Disability) - Incentive Plans - 401(k) with employer contribution and match - Employee Stock Purchase Plan with employer match - Paid Time Off (Vacation and Sick Time) - Paid Holidays - Tuition Reimbursement Program - Employee Assistance Program (EAP) - Wellness Program - Training and Career Progression We should output as

    Benefits

    ... We should not include Pay or Schedule. Now ensure we don't include any boilerplate like EEO line. Now output only HTML fragment. Let's craft:

    About the role

    ...

    Responsibilities

    ...

    Skills

    ...

    Qualifications

    ...

    Benefits

    ...
    Check if any content duplicated: The "What You'll Gain" section is not used; we could incorporate into Benefits? But we already have Benefits section for employee benefits. The "What You'll Gain" describes internship gains: hands-on experience, exposure, training, mentorship, opportunities to collaborate, professional development. That is substantive and not covered elsewhere. Should we include a section for that? Could be "What You'll Gain" but not in the predefined headings list. The 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 says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate. "What You'll Gain" could be considered Benefits? But Benefits already used for employee benefits. However, the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid adding a section like "What You'll Gain" if we want, but the examples given are those headings. Safer to stick to given headings. We could incorporate "What You'll Gain" into Benefits or maybe into About the role? But Benefits already used for employee benefits; mixing might be confusing but still substantive. However, the instruction says "Prefer a few substantive sections over many thin ones." So we could combine internship gains into Benefits section? But they are different: Benefits are employee benefits; gains are learning outcomes. Might be better to have a separate section like "What You'll Gain" but not in the list. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we could add a heading like "What You'll Gain". However, to be safe, maybe we can treat it as part of "About the role" or "Responsibilities"? But it's more about outcomes. Could add a section "What You'll Gain" as

    What You'll Gain

    . That seems reasonable. But the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. I'd include What You'll Gain. Thus sections: About the role, Responsibilities, Skills, Qualifications, Benefits, What You'll Gain. Check if any content duplicated: The "What You'll Gain" list includes: - Hands-on experience working on complex building facade and curtain wall projects. - Exposure to engineering design, analysis, and project execution processes. - Training in industry-leading engineering software and tools. - Mentorship from experienced engineering professionals. - Opportunities to collaborate with architects, contractors, designers, and project teams. - Professional development and career-building experience in the construction and building envelope industry. We'll output as

    . Now ensure we didn't miss any substantive info: The locations line "Harmon, Inc. Locations: Cincinnati, OH | Minneapolis, MN" - should we include? It's location info. Could be placed in About the role paragraph or as a separate

    maybe. The instruction says preserve ALL substantive information. So we should include location. Could add a short

    after About the role heading: "Locations: Cincinnati, OH | Minneapolis, MN". Or incorporate into About the role paragraph. We'll add a

    after the About the role paragraph: "

    Locations: Cincinnati, OH | Minneapolis, MN

    " but maybe better as part of same paragraph. We'll keep About the role paragraph containing the description and then a separate

    for locations. Now check for any other info: The company name "Harmon, Inc." appears. Already in About. Now ensure we removed boilerplate: The EEO line at end removed. Now produce HTML. Let's craft:

    About the role

    Harmon is seeking a motivated Engineering Intern to join our team for the summer. This internship offers an exciting opportunity to gain hands-on experience in the design and engineering of exterior curtain wall systems while working alongside experienced engineers and industry professionals. As an Engineering Intern, you will learn the fundamentals of facade engineering, project design, and construction documentation while contributing to real-world projects. Through mentorship and practical experience, you will develop technical skills and gain exposure to the engineering processes that support some of the most innovative building projects across North America.

    Locations: Cincinnati, OH | Minneapolis, MN

    Responsibilities

    • Support the design and engineering of exterior curtain wall systems.
    • Learn to read and interpret architectural drawings, structural drawings, and project specifications.
    • Assist with coordinating engineering calculations and shop drawings.
    • Support project evaluations, material take-offs, and proposal development.
    • Gain knowledge of Harmon products, services, operations, and engineering processes.
    • Learn and apply thermal analysis and structural analysis methodologies and software.
    • Develop engineering calculations and technical deliverables for proposals and projects.
    • Assist with reviewing blueprints and construction drawings to produce engineering documentation.
    • Utilize computer-aided drafting (CAD) tools to support engineering and design activities.
    • Assist Designers in creating proposal and project drawings using AutoCAD and 3D AutoCAD.
    • Support the maintenance and enhancement of engineering software tools, databases, and drafting standards.
    • Participate in meetings with architects, general contractors, and project teams to discuss design solutions and project requirements.
    • Identify opportunities to simplify and improve design processes.
    • Apply Continuous Improvement principles to daily work and support operational