Building Envelope Internship Opportunity
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. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them.
Thus we need to decide which sections to include: About the role (maybe from Company Description and Job Description?), Responsibilities (What You’ll Do), Requirements (Qualifications), Skills (maybe from Qualifications?), Benefits (What You’ll Gain?), Pay (none), Schedule (Work Environment mentions 2-3 days per week field, but that's schedule? It's about work environment; schedule maybe not explicit. The posting does not give explicit schedule like hours per week; but says "approximately 2–3 days per week in the field". That could be considered schedule. However the instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule (2-3 days per week in the field). So we could include a Schedule section with that detail. Benefits: "What You’ll Gain" is basically benefits. So we can include Benefits section.
We need to avoid duplication. Also need to remove EEO boilerplate lines: "All your information will be kept confidential according to EEO guidelines. SOCOTEC is an Equal Opportunity Employer. SOCOTEC is an Equal Opportunity Employer." Remove those.
Also remove "For more information, please visit www.socotec.us" maybe considered application instruction? It's not exactly instruction but could be considered extra; but it's not boilerplate? Might be okay to keep? The instruction says remove application instructions. That line is not an instruction to apply but a reference. Might keep? Safer to drop it as it's not substantive? It's minor metadata; we could fold into a short
or drop. Probably drop.
Also "Job Type: Full-Time" is substantive; we could include maybe in a short
or maybe as part of Schedule? Not exactly schedule. Could be its own section? Not among allowed headings list; but we could put it under a generic heading? 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 suggests those are typical. Probably we should stick to those headings only. So we need to map content to those headings.
Thus we need sections: About the role (company description + job description overview), Responsibilities (What You’ll Do), Requirements (Qualifications), Skills (maybe from Qualifications like communication, attention to detail, etc.), Benefits (What You’ll Gain), Pay (none -> omit), Schedule (Work Environment field days), maybe also include "Work Environment" as part of Schedule? Could combine.
We must not create Pay section if not stated. So omit Pay.
We must not create Schedule unless posting actually states them. It does state schedule: "approximately 2–3 days per week in the field". So we can include Schedule.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
SOCOTEC is a provider of niche consulting services within the architecture, engineering and construction industries focusing on high-performance buildings and specialty structures. Through an integrated, holistic approach, our professionals provide solutions for building envelope, energy efficiency, sustainability, code advisory and construction advisory projects. SOCOTEC's combination of expertise, experience and methods are increasingly recognized as best-in-class fueling significant growth. With a rapidly growing US footprint and over $360M in annual revenue, SOCOTEC is building the infrastructure to match its ambitions. We are proud to be certified as a Great Place to Work by the global authority on workplace culture. The Building Envelope team helps clients evaluate, design, construct, maintain, and improve the exterior components of buildings. The building envelope includes systems such as exterior walls, windows, doors, roofs, waterproofing, and other components that protect buildings from weather and the surrounding environment. Projects range from new construction to upgrades, repairs, maintenance, and repositioning of existing buildings. As a Building Envelope Intern, you will work alongside experienced engineers, inspectors, and Project Managers to gain exposure to both the technical and practical sides of building envelope consulting.
Responsibilities
- Participate in field visits and construction site inspections alongside experienced engineers and inspectors.
- Observe different phases of exterior wall and building envelope construction.
- Learn how building envelope projects progress from design and planning through construction.
- Assist with field reviews and documenting construction progress.
- Learn how to identify and document building envelope conditions and potential issues.
- Assist with reviewing architectural and construction drawings.
- Gain exposure to shop drawings, design development, and construction documents.
- Assist with building envelope research, inspections, and technical evaluations.
- Help prepare clear and detailed project reports, photographs, and other documentation.
- Gain exposure to building codes, construction standards, and industry best practices.
- Work alongside Project Managers and other team members to support project activities and deadlines.
- Learn how engineers and inspectors communicate technical information to clients, contractors, architects, and design teams.
- Attend team meetings, training sessions, and in-house seminars.
- Assist with other project-related assignments as needed.
- Develop your technical, communication, organization, and problem-solving skills.
Requirements
- Currently pursuing a Bachelor’s degree in Engineering, Architecture, Construction Management, or a related field.
- Architectural, Civil, or Mechanical Engineering is preferred.
- Interest in building envelope design, construction, inspection, and engineering.
- Basic understanding of building construction, architectural design, or structural concepts is a plus.
- Ability or willingness to learn how to read and interpret architectural and construction drawings.
- Strong written and verbal communication skills.
- Strong attention to detail and problem-solving skills.
- Ability to work collaboratively with engineers, inspectors, Project Managers, and other team members.
- Proficiency in Microsoft Office.
- Familiarity with AutoCAD, Revit, BIM, or other modeling/drafting software is a plus, but not required.
- Comfortable working both in an office and on active construction sites.
- Willingness to learn, ask questions, and take on new challenges.
Skills
Strong written and verbal communication skills, strong attention to detail, problem‑solving abilities, teamwork, proficiency with Microsoft Office, and a willingness to learn technical tools such as AutoCAD, Revit, or BIM.
But note: Skills section may duplicate content from Qualifications; but we can still include if we have specific skills. However instruction: Prefer a few substantive sections over many thin ones. Could combine Requirements and Skills? But they ask to use headings like Skills. We could keep Skills but ensure it's not thin. Could list specific skills.
But we already listed many qualifications; maybe we can merge Qualifications and Skills into one Requirements section? However they said use headings like Requirements, Qualifications, Skills. It's ambiguous. Probably we should have Requirements (or Qualifications) and Skills separate if we have distinct content. But we risk thin sections. Let's think: The posting's "Qualifications" section includes education, interest, understanding, ability to learn drawings, communication skills, attention to detail, problem-solving, teamwork, proficiency in MS Office, familiarity with AutoCAD etc., comfort working office/field, willingness to learn. That's basically both requirements and skills. So we could have a single "Qualifications" section with list. Then we could omit Skills section to avoid thin duplication. The instruction says use headings like those examples, but not mandatory to include all. So we can include only those sections that have substantive content. So we can have About the role, Responsibilities, Qualifications, Benefits, Schedule. That's five sections.
Now Benefits: "What You’ll Gain" list. We'll put as Benefits.
Schedule: from Work Environment: "This is a combination of field and office-based work. Building Envelope interns should expect to spend approximately 2–3 days per week on construction sites or at project locations. Field work may involve walking active construction sites, climbing stairs or ladders, and working in various weather conditions. Interns will be expected to follow all applicable site safety requirements and will receive guidance from their supervisor and project team." That's schedule and work environment. We'll put schedule details.
We must not include filler like "commensurate with experience". Not present.
Now we need to ensure we preserve all substantive information. Let's check we didn't miss any important details:
- Company description: included in About the role.
- Job Description overview: included.
- About SOCOTEC’s Summer Internship Program: we didn't include that explicitly. It's a paragraph describing internship program: "SOCOTEC’s summer internship program is designed for college students who are eager to gain hands-on industry experience and learn more about the work we do. Interns receive well-rounded exposure to their field, with opportunities to spend time both on job sites and in the office while working alongside experienced professionals. As a Building Envelope Intern, you can expect to spend approximately 2–3 days per week in the field, gaining firsthand experience with real-world building projects, construction activities, and site inspections. The remainder of your time will be spent in the office supporting project teams and learning how Building Envelope services are delivered."
We have some of that in Schedule and About the role maybe. But we should include that content somewhere. Could be part of About the role or Schedule. Since it's about the internship program, we could incorporate into About the role or maybe a separate section "About the internship". But we only have allowed headings; we could incorporate into About the role (makes sense). So we need to ensure we include that paragraph.
Thus About the role should include company description, job description, and internship program overview.
Let's craft About the role paragraph(s) maybe multiple but we can combine.
Now Responsibilities: we captured "What You’ll Do" list.
Qualifications: we captured the Qualifications list.
Benefits: we captured "What You’ll Gain" list.
Schedule: we captured Work Environment details (including field days, safety, etc.)
Potential Career Paths: we have that info: "This internship can provide a strong foundation for future opportunities in Building Envelope Engineering, Inspection, and Consulting, including entry-level roles such as: Building Envelope Engineer, Engineer Inspector, Building Envelope Consultant, Project Engineer". This is substantive; we need to preserve it. Where to put? Could be part of Benefits or maybe a separate section "Career Paths". Not among standard headings but we could add
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Thus we need to decide which sections to include: About the role (maybe from Company Description and Job Description?), Responsibilities (What You’ll Do), Requirements (Qualifications), Skills (maybe from Qualifications?), Benefits (What You’ll Gain?), Pay (none), Schedule (Work Environment mentions 2-3 days per week field, but that's schedule? It's about work environment; schedule maybe not explicit. The posting does not give explicit schedule like hours per week; but says "approximately 2–3 days per week in the field". That could be considered schedule. However the instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule (2-3 days per week in the field). So we could include a Schedule section with that detail. Benefits: "What You’ll Gain" is basically benefits. So we can include Benefits section. We need to avoid duplication. Also need to remove EEO boilerplate lines: "All your information will be kept confidential according to EEO guidelines. SOCOTEC is an Equal Opportunity Employer. SOCOTEC is an Equal Opportunity Employer." Remove those. Also remove "For more information, please visit www.socotec.us" maybe considered application instruction? It's not exactly instruction but could be considered extra; but it's not boilerplate? Might be okay to keep? The instruction says remove application instructions. That line is not an instruction to apply but a reference. Might keep? Safer to drop it as it's not substantive? It's minor metadata; we could fold into a short
or drop. Probably drop. Also "Job Type: Full-Time" is substantive; we could include maybe in a short
or maybe as part of Schedule? Not exactly schedule. Could be its own section? Not among allowed headings list; but we could put it under a generic heading? 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 suggests those are typical. Probably we should stick to those headings only. So we need to map content to those headings.
Thus we need sections: About the role (company description + job description overview), Responsibilities (What You’ll Do), Requirements (Qualifications), Skills (maybe from Qualifications like communication, attention to detail, etc.), Benefits (What You’ll Gain), Pay (none -> omit), Schedule (Work Environment field days), maybe also include "Work Environment" as part of Schedule? Could combine.
We must not create Pay section if not stated. So omit Pay.
We must not create Schedule unless posting actually states them. It does state schedule: "approximately 2–3 days per week in the field". So we can include Schedule.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
SOCOTEC is a provider of niche consulting services within the architecture, engineering and construction industries focusing on high-performance buildings and specialty structures. Through an integrated, holistic approach, our professionals provide solutions for building envelope, energy efficiency, sustainability, code advisory and construction advisory projects. SOCOTEC's combination of expertise, experience and methods are increasingly recognized as best-in-class fueling significant growth. With a rapidly growing US footprint and over $360M in annual revenue, SOCOTEC is building the infrastructure to match its ambitions. We are proud to be certified as a Great Place to Work by the global authority on workplace culture. The Building Envelope team helps clients evaluate, design, construct, maintain, and improve the exterior components of buildings. The building envelope includes systems such as exterior walls, windows, doors, roofs, waterproofing, and other components that protect buildings from weather and the surrounding environment. Projects range from new construction to upgrades, repairs, maintenance, and repositioning of existing buildings. As a Building Envelope Intern, you will work alongside experienced engineers, inspectors, and Project Managers to gain exposure to both the technical and practical sides of building envelope consulting.
Responsibilities
- Participate in field visits and construction site inspections alongside experienced engineers and inspectors.
- Observe different phases of exterior wall and building envelope construction.
- Learn how building envelope projects progress from design and planning through construction.
- Assist with field reviews and documenting construction progress.
- Learn how to identify and document building envelope conditions and potential issues.
- Assist with reviewing architectural and construction drawings.
- Gain exposure to shop drawings, design development, and construction documents.
- Assist with building envelope research, inspections, and technical evaluations.
- Help prepare clear and detailed project reports, photographs, and other documentation.
- Gain exposure to building codes, construction standards, and industry best practices.
- Work alongside Project Managers and other team members to support project activities and deadlines.
- Learn how engineers and inspectors communicate technical information to clients, contractors, architects, and design teams.
- Attend team meetings, training sessions, and in-house seminars.
- Assist with other project-related assignments as needed.
- Develop your technical, communication, organization, and problem-solving skills.
Requirements
- Currently pursuing a Bachelor’s degree in Engineering, Architecture, Construction Management, or a related field.
- Architectural, Civil, or Mechanical Engineering is preferred.
- Interest in building envelope design, construction, inspection, and engineering.
- Basic understanding of building construction, architectural design, or structural concepts is a plus.
- Ability or willingness to learn how to read and interpret architectural and construction drawings.
- Strong written and verbal communication skills.
- Strong attention to detail and problem-solving skills.
- Ability to work collaboratively with engineers, inspectors, Project Managers, and other team members.
- Proficiency in Microsoft Office.
- Familiarity with AutoCAD, Revit, BIM, or other modeling/drafting software is a plus, but not required.
- Comfortable working both in an office and on active construction sites.
- Willingness to learn, ask questions, and take on new challenges.
Skills
Strong written and verbal communication skills, strong attention to detail, problem‑solving abilities, teamwork, proficiency with Microsoft Office, and a willingness to learn technical tools such as AutoCAD, Revit, or BIM.
But note: Skills section may duplicate content from Qualifications; but we can still include if we have specific skills. However instruction: Prefer a few substantive sections over many thin ones. Could combine Requirements and Skills? But they ask to use headings like Skills. We could keep Skills but ensure it's not thin. Could list specific skills. But we already listed many qualifications; maybe we can merge Qualifications and Skills into one Requirements section? However they said use headings like Requirements, Qualifications, Skills. It's ambiguous. Probably we should have Requirements (or Qualifications) and Skills separate if we have distinct content. But we risk thin sections. Let's think: The posting's "Qualifications" section includes education, interest, understanding, ability to learn drawings, communication skills, attention to detail, problem-solving, teamwork, proficiency in MS Office, familiarity with AutoCAD etc., comfort working office/field, willingness to learn. That's basically both requirements and skills. So we could have a single "Qualifications" section with list. Then we could omit Skills section to avoid thin duplication. The instruction says use headings like those examples, but not mandatory to include all. So we can include only those sections that have substantive content. So we can have About the role, Responsibilities, Qualifications, Benefits, Schedule. That's five sections. Now Benefits: "What You’ll Gain" list. We'll put as Benefits. Schedule: from Work Environment: "This is a combination of field and office-based work. Building Envelope interns should expect to spend approximately 2–3 days per week on construction sites or at project locations. Field work may involve walking active construction sites, climbing stairs or ladders, and working in various weather conditions. Interns will be expected to follow all applicable site safety requirements and will receive guidance from their supervisor and project team." That's schedule and work environment. We'll put schedule details. We must not include filler like "commensurate with experience". Not present. Now we need to ensure we preserve all substantive information. Let's check we didn't miss any important details: - Company description: included in About the role. - Job Description overview: included. - About SOCOTEC’s Summer Internship Program: we didn't include that explicitly. It's a paragraph describing internship program: "SOCOTEC’s summer internship program is designed for college students who are eager to gain hands-on industry experience and learn more about the work we do. Interns receive well-rounded exposure to their field, with opportunities to spend time both on job sites and in the office while working alongside experienced professionals. As a Building Envelope Intern, you can expect to spend approximately 2–3 days per week in the field, gaining firsthand experience with real-world building projects, construction activities, and site inspections. The remainder of your time will be spent in the office supporting project teams and learning how Building Envelope services are delivered." We have some of that in Schedule and About the role maybe. But we should include that content somewhere. Could be part of About the role or Schedule. Since it's about the internship program, we could incorporate into About the role or maybe a separate section "About the internship". But we only have allowed headings; we could incorporate into About the role (makes sense). So we need to ensure we include that paragraph. Thus About the role should include company description, job description, and internship program overview. Let's craft About the role paragraph(s) maybe multiplebut we can combine. Now Responsibilities: we captured "What You’ll Do" list. Qualifications: we captured the Qualifications list. Benefits: we captured "What You’ll Gain" list. Schedule: we captured Work Environment details (including field days, safety, etc.) Potential Career Paths: we have that info: "This internship can provide a strong foundation for future opportunities in Building Envelope Engineering, Inspection, and Consulting, including entry-level roles such as: Building Envelope Engineer, Engineer Inspector, Building Envelope Consultant, Project Engineer". This is substantive; we need to preserve it. Where to put? Could be part of Benefits or maybe a separate section "Career Paths". Not among standard headings but we could add