Entry-Level Engineer, Building Technology
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. 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. IMPORTANT: 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. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Let's extract sections:
- Intro: "Do you want to help engineer what’s next? Simpson Gumpertz & Heger (SGH) is a national engineering firm ..." This is about the company. Could be "About the role"? Actually "About the role" is for role description. But we have a description of the firm and culture. Could be "About the role" or maybe we can combine into a single "About the role" section that includes company overview and what makes careers special. However we need to avoid thin sections.
- "What makes careers at SGH so special?" includes bullet points: Our Work, Our People, Our Commitment, Our Contribution. That's a list.
- "We Want Someone Passionate About Engineering And Problem-solving." Then description of Building Technology division, looking for upcoming 2027 graduates with certain degrees to join Chicago office.
- "What You’ll Do": description of Building Technology, duties: assist with new design, evaluation, investigation, design of repairs for existing buildings. Essential duties include climbing ladders and scaffolds, ability to work at great heights, ability to travel by car to multiple job sites. A strong technical education, professional demeanor, and desire to learn is essential.
- "What You’ll Need": list of qualifications: Bachelor of Architectural Engineering or Bachelor of Science in Civil or Structural Engineering. 0 to 5 years of experience, EIT preferred. Demonstrated interest in building construction and solving engineering problems. Commitment to lifelong learning and enthusiasm for the work. Experience in any of the following areas is a plus: building construction or an allied field, industrial rope access (rock climbing), mechanical repair, AutoCAD, Revit. Enthusiasm and passion - consistently maintains high levels of activity and productivity. Communication - conveys information to internal and external clients clearly with excellent writing and oral skills. Problem-solving – capability to solve minor or complex problems using data, logic, judgement and problem-solving tools. Accountability and responsibility - self-starter with willingness to interact as a team player and take independent initiative to ensure tasks are competed. Teamwork - work with others toward a shared goal, participating actively, sharing responsibility and rewards and contributing to the capability of the team. Teachable – passionate and willingness for continued learning of new ideas and concepts. Must be able to climb ladders and scaffolds, and work at great heights. Must have a valid driver’s license and an acceptable Motor Vehicle Report.
- "Benefits Overview": list of benefits.
- "Compensation": includes compensation range: Associate Principal $79,560—$85,280 USD. Also description of total compensation package.
- There's also "SGH is an Equal Opportunity Employer..." which is boilerplate EEO, should be removed.
- Also recruitment agency note, etc. Remove.
Thus we need sections: About the role (maybe combine company overview and culture), Responsibilities (What You’ll Do), Requirements/Qualifications (What You’ll Need), Skills (maybe we can extract skills list), Benefits, Pay.
We need to decide which headings to use. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose subset.
We have content for About the role (company overview and culture). Responsibilities (What You’ll Do). Requirements (What You’ll Need). Skills (maybe the list of soft skills and technical skills). Benefits (Benefits Overview). Pay (Compensation). No schedule info.
We must not create sections with filler. So we will include those sections only if we have substantive content.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from those sections.
We need to format lists with
- . For prose, use
.
We must not repeat the job title as heading. The job title is "Associate Project Consultant"? Actually the posting says "As an Associate Project Consultant, under the direction of a licensed engineer". So we should not repeat that as heading.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
First, maybe a short paragraph for metadata? The posting includes location: Chicago office. Also mentions upcoming 2027 graduates. That's substantive; we should include it somewhere, maybe in About the role or Responsibilities? Could be part of About the role: "We are looking for upcoming 2027 graduates with a Bachelor of Architectural Engineering or Bachelor of Science in Civil or Structural Engineering to join our team in the Chicago office." That's part of Requirements? Actually it's part of "What You’ll Need"? It mentions degree and location. We'll include in Requirements/Qualifications.
We need to preserve all details: e.g., "Building Technology is the application of engineering principles, physics, and materials science to the exterior envelope of buildings to make them durable, energy-efficient, and able to reliably resist water infiltration." That's part of Responsibilities.
Also "Essential duties include climbing ladders and scaffolds, the ability to work at great heights, and the ability to travel by car to multiple job sites."
Also "A strong technical education, professional demeanor, and desire to learn is essential to this position."
Now for Requirements: list of degree, 0-5 years experience, EIT preferred, demonstrated interest, commitment to lifelong learning, enthusiasm for work, experience plus list, enthusiasm and passion, communication, problem-solving, accountability, teamwork, teachable, must be able to climb ladders and scaffolds, work at great heights, valid driver's license, acceptable MVR.
We need to keep all those as list items.
Skills: maybe we can separate technical skills vs soft skills. But we could also put all under Requirements or Qualifications. The instruction allows us to use sections like Requirements, Qualifications, Skills. We need to decide which to use to avoid thin sections. We have a lot of content for Requirements/Qualifications; we could combine them into one section called "Requirements" (or "Qualifications") and include both hard and soft requirements. Then we could have a separate "Skills" section for the soft skills like communication, problem-solving, etc. But that might be thin. Better to have one "Requirements" section that includes all bullet points (including degree, experience, skills, etc.). Then we could have a separate "Benefits" and "Pay". And maybe "About the role" for company overview and culture.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay.
Check if we have content for each:
- About the role: company description, culture, what makes careers special, maybe also mention looking for upcoming 2027 graduates? Actually that is more about the role requirements. But we can include location and target candidate in About the role? Might be okay. However we need to preserve all substantive info; we can put the "We Want Someone Passionate..." paragraph in About the role or Responsibilities? It's more about who they want. Could be part of About the role (the role description). But we already have Responsibilities for duties. The "We Want Someone Passionate..." is more about desired candidate traits, which could be part of Requirements. Let's think.
Better: About the role: company overview and culture (first paragraphs). Responsibilities: What You’ll Do. Requirements: What You’ll Need (including degree, experience, skills, etc.). Benefits: Benefits Overview. Pay: Compensation.
Thus we need to extract About the role content: The first paragraph: "Do you want to help engineer what’s next? Simpson Gumpertz & Heger (SGH) is a national engineering firm committed to delivering holistic advice for our clients’ most complex challenges. We leverage our collective and diverse experience, technical expertise, and industry knowledge of structures and building enclosures, advanced analysis, performance & code consulting, and applied science & research to deliver unrivaled, comprehensive solutions that drive superior performance. With 800 employees in offices nationwide, SGH’s industry-leading teams constantly seek to advance the meaning of what’s possible."
Then "What makes careers at SGH so special? The only way to advance is to question and explore. Every member of the SGH team is both a learner and an educator, committed to advancing ourselves, our teams, and our industry. Together we are creating a community that never settles for what is but always seeks what could be."
Then "There Are Many Reasons To Love SGH Our Work: Our clients trust us to bring clarity and deliver outstanding solutions for their most complex projects.Our People: We are bold thinkers and compassionate teammates, committed to lifelong learning and professional growth.Our Commitment: We live with integrity and embrace an obligation to give back to our professions and communities.Our Contribution: We offer a comprehensive and rich compensation and benefits package with company-paid and voluntary programs to help build healthy lifestyles, strong relationships, and future prosperity."
We need to keep that as prose or list? The "There Are Many Reasons To Love SGH" includes bullet-like statements but not formatted as list. We could turn them into a list for clarity, but we must not invent structure; we can keep as prose. However we could also make a
- for each reason. The instruction: Use
- for any list of duties/requirements/benefits. This is a list of reasons, but not explicitly a list in source. It's okay to keep as prose. But we could also convert to list to improve readability, but that might be considered adding structure not present. Safer to keep as prose.
Thus About the role will be a few
paragraphs.
Now Responsibilities: content from "What You’ll Do". Let's extract:
"Building Technology is the application of engineering principles, physics, and materials science to the exterior envelope of buildings to make them durable, energy-efficient, and able to reliably resist water infiltration. As an Associate Project Consultant, under the direction of a licensed engineer, you will assist with new design, evaluation, investigation, and design of repairs for existing buildings. Essential duties include climbing ladders and scaffolds, the ability to work at great heights, and the ability to travel by car to multiple job sites. A strong technical education, professional demeanor, and desire to learn is essential to this position."
We need to keep all that. Could be a
for prose, and maybe a
- for the essential duties list? The essential duties are a list: climbing ladders and scaffolds, ability to work at great heights, ability to travel by car to multiple job sites. We can make a list.
Thus Responsibilities:
for the first sentences, then
- for duties.
Now Requirements: content from "What You’ll Need". Let's list:
- Bachelor of Architectural Engineering or Bachelor of Science in Civil or Structural Engineering.
- 0 to 5 years of experience, EIT preferred.
- Demonstrated interest in building construction and solving engineering problems.
- Commitment to lifelong learning and
for prose. Do NOT repeat the job title as a heading. 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. IMPORTANT: 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. Prefer a few substantive sections over many thin ones. We need to parse the posting. Let's extract sections: - Intro: "Do you want to help engineer what’s next? Simpson Gumpertz & Heger (SGH) is a national engineering firm ..." This is about the company. Could be "About the role"? Actually "About the role" is for role description. But we have a description of the firm and culture. Could be "About the role" or maybe we can combine into a single "About the role" section that includes company overview and what makes careers special. However we need to avoid thin sections. - "What makes careers at SGH so special?" includes bullet points: Our Work, Our People, Our Commitment, Our Contribution. That's a list. - "We Want Someone Passionate About Engineering And Problem-solving." Then description of Building Technology division, looking for upcoming 2027 graduates with certain degrees to join Chicago office. - "What You’ll Do": description of Building Technology, duties: assist with new design, evaluation, investigation, design of repairs for existing buildings. Essential duties include climbing ladders and scaffolds, ability to work at great heights, ability to travel by car to multiple job sites. A strong technical education, professional demeanor, and desire to learn is essential. - "What You’ll Need": list of qualifications: Bachelor of Architectural Engineering or Bachelor of Science in Civil or Structural Engineering. 0 to 5 years of experience, EIT preferred. Demonstrated interest in building construction and solving engineering problems. Commitment to lifelong learning and enthusiasm for the work. Experience in any of the following areas is a plus: building construction or an allied field, industrial rope access (rock climbing), mechanical repair, AutoCAD, Revit. Enthusiasm and passion - consistently maintains high levels of activity and productivity. Communication - conveys information to internal and external clients clearly with excellent writing and oral skills. Problem-solving – capability to solve minor or complex problems using data, logic, judgement and problem-solving tools. Accountability and responsibility - self-starter with willingness to interact as a team player and take independent initiative to ensure tasks are competed. Teamwork - work with others toward a shared goal, participating actively, sharing responsibility and rewards and contributing to the capability of the team. Teachable – passionate and willingness for continued learning of new ideas and concepts. Must be able to climb ladders and scaffolds, and work at great heights. Must have a valid driver’s license and an acceptable Motor Vehicle Report. - "Benefits Overview": list of benefits. - "Compensation": includes compensation range: Associate Principal $79,560—$85,280 USD. Also description of total compensation package. - There's also "SGH is an Equal Opportunity Employer..." which is boilerplate EEO, should be removed. - Also recruitment agency note, etc. Remove. Thus we need sections: About the role (maybe combine company overview and culture), Responsibilities (What You’ll Do), Requirements/Qualifications (What You’ll Need), Skills (maybe we can extract skills list), Benefits, Pay. We need to decide which headings to use. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose subset. We have content for About the role (company overview and culture). Responsibilities (What You’ll Do). Requirements (What You’ll Need). Skills (maybe the list of soft skills and technical skills). Benefits (Benefits Overview). Pay (Compensation). No schedule info. We must not create sections with filler. So we will include those sections only if we have substantive content. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from those sections. We need to format lists with
- . For prose, use
. We must not repeat the job title as heading. The job title is "Associate Project Consultant"? Actually the posting says "As an Associate Project Consultant, under the direction of a licensed engineer". So we should not repeat that as heading. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, maybe a short paragraph for metadata? The posting includes location: Chicago office. Also mentions upcoming 2027 graduates. That's substantive; we should include it somewhere, maybe in About the role or Responsibilities? Could be part of About the role: "We are looking for upcoming 2027 graduates with a Bachelor of Architectural Engineering or Bachelor of Science in Civil or Structural Engineering to join our team in the Chicago office." That's part of Requirements? Actually it's part of "What You’ll Need"? It mentions degree and location. We'll include in Requirements/Qualifications. We need to preserve all details: e.g., "Building Technology is the application of engineering principles, physics, and materials science to the exterior envelope of buildings to make them durable, energy-efficient, and able to reliably resist water infiltration." That's part of Responsibilities. Also "Essential duties include climbing ladders and scaffolds, the ability to work at great heights, and the ability to travel by car to multiple job sites." Also "A strong technical education, professional demeanor, and desire to learn is essential to this position." Now for Requirements: list of degree, 0-5 years experience, EIT preferred, demonstrated interest, commitment to lifelong learning, enthusiasm for work, experience plus list, enthusiasm and passion, communication, problem-solving, accountability, teamwork, teachable, must be able to climb ladders and scaffolds, work at great heights, valid driver's license, acceptable MVR. We need to keep all those as list items. Skills: maybe we can separate technical skills vs soft skills. But we could also put all under Requirements or Qualifications. The instruction allows us to use sections like Requirements, Qualifications, Skills. We need to decide which to use to avoid thin sections. We have a lot of content for Requirements/Qualifications; we could combine them into one section called "Requirements" (or "Qualifications") and include both hard and soft requirements. Then we could have a separate "Skills" section for the soft skills like communication, problem-solving, etc. But that might be thin. Better to have one "Requirements" section that includes all bullet points (including degree, experience, skills, etc.). Then we could have a separate "Benefits" and "Pay". And maybe "About the role" for company overview and culture. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. Check if we have content for each: - About the role: company description, culture, what makes careers special, maybe also mention looking for upcoming 2027 graduates? Actually that is more about the role requirements. But we can include location and target candidate in About the role? Might be okay. However we need to preserve all substantive info; we can put the "We Want Someone Passionate..." paragraph in About the role or Responsibilities? It's more about who they want. Could be part of About the role (the role description). But we already have Responsibilities for duties. The "We Want Someone Passionate..." is more about desired candidate traits, which could be part of Requirements. Let's think. Better: About the role: company overview and culture (first paragraphs). Responsibilities: What You’ll Do. Requirements: What You’ll Need (including degree, experience, skills, etc.). Benefits: Benefits Overview. Pay: Compensation. Thus we need to extract About the role content: The first paragraph: "Do you want to help engineer what’s next? Simpson Gumpertz & Heger (SGH) is a national engineering firm committed to delivering holistic advice for our clients’ most complex challenges. We leverage our collective and diverse experience, technical expertise, and industry knowledge of structures and building enclosures, advanced analysis, performance & code consulting, and applied science & research to deliver unrivaled, comprehensive solutions that drive superior performance. With 800 employees in offices nationwide, SGH’s industry-leading teams constantly seek to advance the meaning of what’s possible." Then "What makes careers at SGH so special? The only way to advance is to question and explore. Every member of the SGH team is both a learner and an educator, committed to advancing ourselves, our teams, and our industry. Together we are creating a community that never settles for what is but always seeks what could be." Then "There Are Many Reasons To Love SGH Our Work: Our clients trust us to bring clarity and deliver outstanding solutions for their most complex projects.Our People: We are bold thinkers and compassionate teammates, committed to lifelong learning and professional growth.Our Commitment: We live with integrity and embrace an obligation to give back to our professions and communities.Our Contribution: We offer a comprehensive and rich compensation and benefits package with company-paid and voluntary programs to help build healthy lifestyles, strong relationships, and future prosperity." We need to keep that as prose or list? The "There Are Many Reasons To Love SGH" includes bullet-like statements but not formatted as list. We could turn them into a list for clarity, but we must not invent structure; we can keep as prose. However we could also make a
- for each reason. The instruction: Use
- for any list of duties/requirements/benefits. This is a list of reasons, but not explicitly a list in source. It's okay to keep as prose. But we could also convert to list to improve readability, but that might be considered adding structure not present. Safer to keep as prose.
Thus About the role will be a few
paragraphs. Now Responsibilities: content from "What You’ll Do". Let's extract: "Building Technology is the application of engineering principles, physics, and materials science to the exterior envelope of buildings to make them durable, energy-efficient, and able to reliably resist water infiltration. As an Associate Project Consultant, under the direction of a licensed engineer, you will assist with new design, evaluation, investigation, and design of repairs for existing buildings. Essential duties include climbing ladders and scaffolds, the ability to work at great heights, and the ability to travel by car to multiple job sites. A strong technical education, professional demeanor, and desire to learn is essential to this position." We need to keep all that. Could be a
for prose, and maybe a
- for the essential duties list? The essential duties are a list: climbing ladders and scaffolds, ability to work at great heights, ability to travel by car to multiple job sites. We can make a list.
Thus Responsibilities:
for the first sentences, then
- for duties. Now Requirements: content from "What You’ll Need". Let's list: - Bachelor of Architectural Engineering or Bachelor of Science in Civil or Structural Engineering. - 0 to 5 years of experience, EIT preferred. - Demonstrated interest in building construction and solving engineering problems. - Commitment to lifelong learning and
- for the essential duties list? The essential duties are a list: climbing ladders and scaffolds, ability to work at great heights, ability to travel by car to multiple job sites. We can make a list.
Thus Responsibilities:
- for any list of duties/requirements/benefits. This is a list of reasons, but not explicitly a list in source. It's okay to keep as prose. But we could also convert to list to improve readability, but that might be considered adding structure not present. Safer to keep as prose.
Thus About the role will be a few
- for each reason. The instruction: Use