Entry-Level Engineer, Building Technology
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content.
We need to preserve all substantive information.
Let's extract sections:
1. About the role / company overview: "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. 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. 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."
That's a lot of prose. Could be placed under "About the role" or maybe "About SGH". We'll use "About the role".
2. Responsibilities: "We Want Someone Passionate About Engineering And Problem-solving. Our Building Technology division is always looking for great talent, especially people who enjoy solving difficult problems. We are looking to speak with recent or upcoming graduates with a Bachelor of Architectural Engineering or Bachelor of Science in Civil or Structural Engineering to join our team in the Los Angeles, CA office. What You’ll Do Building Technology is applying engineering principles, physics, and materials science to the exterior envelope of buildings to make them durable, energy-efficient, and able to resist water infiltration reliably. 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."
Thus responsibilities: assist with new design, evaluation, investigation, design of repairs; climbing ladders/scaffolds; work at great heights; travel by car to multiple job sites.
Also maybe "We Want Someone Passionate About Engineering And Problem-solving." could be part of responsibilities or qualifications.
We'll list responsibilities as bullet list.
3. Requirements / Qualifications: "What You’ll Need 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 maintain 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, judgment, 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 completed. 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 willing to continue learning new ideas and concepts. Must be able to climb ladders and scaffolds, and work at great heights. A valid driver’s license and an acceptable Motor Vehicle Report are required for this role."
We need to separate Requirements (maybe education/experience) vs Qualifications (skills). But we can combine or separate as appropriate. The instruction says we can have sections: Requirements, Qualifications, Skills. We need to decide what goes where.
We could put:
- Requirements: Bachelor of Architectural Engineering or BS Civil/Structural Engineering; 0-5 years experience; EIT preferred; valid driver's license; acceptable MVR; ability to climb ladders/scaffolds; work at great heights.
- Qualifications: Demonstrated interest in building construction and solving engineering problems; commitment to lifelong learning; enthusiasm for work.
- Skills: Enthusiasm and passion; Communication; Problem-solving; Accountability and responsibility; Teamwork; Teachable; Experience in building construction or allied field, industrial rope access, mechanical repair, AutoCAD, Revit (as plus).
But we need to avoid duplication. Also "Must be able to climb ladders and scaffolds, and work at great heights." appears also in responsibilities; but we can keep.
We also have Benefits Overview: list of benefits.
Pay: compensation range: Bachelor’s Degree: $79,560 - $81,640; Master’s Degree: $83,200 - $85,280; Base salary part of total comp; also mention $5,000 sign-on bonus; also "Associate Project Consultant $84,760—$96,200 USD". There's some inconsistency: they gave ranges for degree then also a specific range for the position. We need to preserve all substantive info. We'll include both.
Schedule: Not mentioned explicitly. No schedule info (like full-time, hours). So we should not create a Schedule section because no real specific content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we can include Pay and Benefits, but not Schedule.
Now we need to output HTML fragment with headings and - for lists,
for prose.
We must not include markdown code fences.
We need to ensure we don't repeat job title as heading. The job title is Associate Project Consultant; we must not use that as heading.
We need to drop boilerplate: EEO, equal opportunity, recruitment agency notice, contact info, etc. Also remove "SGH is an Equal Opportunity Employer..." etc. Also remove "TO ALL RECRUITMENT AGENCIES:" etc. Also remove "If the application system is not accessible..." etc. Also remove "This compensation range is a good faith estimate pursuant to applicable equal pay and pay transparency laws." maybe keep as part of Pay? It's substantive about pay range but it's a legal disclaimer; we might keep it as part of Pay section? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The disclaimer is substantive? It's about pay range being estimate; we could keep it as a paragraph under Pay. However it's somewhat boilerplate but it's about pay transparency; maybe keep.
Also remove "Base salary is a part of SGH’s industry leading Total Compensation package. Our Total Compensation package includes base salary, pay for extra hours worked, an annual discretionary bonus program, generous paid time off, and health and wellness benefits with a special emphasis on substantial SGH contributions to medical insurance premiums and SGH’s Profit Sharing & 401(k) Plan." That's substantive about compensation; keep.
Also "This position is eligible for a $5,000 sign-on bonus." keep.
Now we need to decide headings.
Potential sections:
- About the role (company overview and culture)
- Responsibilities
- Requirements
- Qualifications
- Skills
- Benefits
- Pay
We should not include Schedule.
Now we need to ensure we don't create empty sections.
Let's craft content.
About the role: combine the introductory paragraphs about SGH, mission, culture, reasons to love SGH. We'll put as
maybe multiple paragraphs.
Responsibilities: bullet list.
Requirements: bullet list (education/experience, license, physical ability).
Qualifications: bullet list (interest, commitment, enthusiasm).
Skills: bullet list (communication, problem-solving, accountability, teamwork, teachable, plus experience areas).
Benefits: bullet list of benefits as given.
Pay: paragraphs about salary ranges, sign-on bonus, total comp description, plus disclaimer.
Now we need to ensure we don't include duplicated lines. For example, "Must be able to climb ladders and scaffolds, and work at great heights." appears both in responsibilities and requirements; we should include only once? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If it's duplicated in the source, we might need to keep both? Usually we would deduplicate to avoid repetition but the instruction says preserve ALL substantive information; does that mean we must keep duplicates? It says "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing away detail would be removing info; but removing duplicate info could be considered summarizing? It's ambiguous. Safer to keep both occurrences? But that would be redundant and maybe considered filler? However they said "never emit a heading followed by filler/placeholder text". Duplicate info is not filler but redundant. I'd lean to keep it once to avoid redundancy but still preserve the info. I'd include it under Requirements (since it's a requirement) and not repeat under Responsibilities (maybe mention it there as part of duties). Actually responsibilities already include climbing ladders etc. So we could keep it in responsibilities and not duplicate in requirements. But the requirement also mentions it; we could keep it there as well but it's duplicate. I'd choose to include it under Responsibilities (as duty) and also under Requirements (as requirement) but maybe it's okay. However to be safe, I'll include it only once under Responsibilities (since it's a duty) and also mention under Requirements as "Ability to climb ladders and scaffolds and work at great heights." but that is duplicate. I'd rather include it under Requirements as it's a requirement; responsibilities already mention it; but we can keep both but maybe it's okay.
Given the instruction to prefer a few substantive sections over many thin ones, we might combine some.
Let's think: Could we merge Requirements and Qualifications into one "Requirements" section? But they ask to use those headings if we have content. We'll keep them separate.
Now let's draft HTML.
We'll start with
About the role
then ...
.
We need to ensure we don't include any HTML tags besides those.
Let's write the About the role paragraph(s). Could be multiple tags.
We'll combine the intro: "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 next paragraph: "What makes careers at SGH so special? The only way to advance is to question and explore. Every member of
- for lists,
for prose. We must not include markdown code fences. We need to ensure we don't repeat job title as heading. The job title is Associate Project Consultant; we must not use that as heading. We need to drop boilerplate: EEO, equal opportunity, recruitment agency notice, contact info, etc. Also remove "SGH is an Equal Opportunity Employer..." etc. Also remove "TO ALL RECRUITMENT AGENCIES:" etc. Also remove "If the application system is not accessible..." etc. Also remove "This compensation range is a good faith estimate pursuant to applicable equal pay and pay transparency laws." maybe keep as part of Pay? It's substantive about pay range but it's a legal disclaimer; we might keep it as part of Pay section? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The disclaimer is substantive? It's about pay range being estimate; we could keep it as a paragraph under Pay. However it's somewhat boilerplate but it's about pay transparency; maybe keep. Also remove "Base salary is a part of SGH’s industry leading Total Compensation package. Our Total Compensation package includes base salary, pay for extra hours worked, an annual discretionary bonus program, generous paid time off, and health and wellness benefits with a special emphasis on substantial SGH contributions to medical insurance premiums and SGH’s Profit Sharing & 401(k) Plan." That's substantive about compensation; keep. Also "This position is eligible for a $5,000 sign-on bonus." keep. Now we need to decide headings. Potential sections: - About the role (company overview and culture) - Responsibilities - Requirements - Qualifications - Skills - Benefits - Pay We should not include Schedule. Now we need to ensure we don't create empty sections. Let's craft content. About the role: combine the introductory paragraphs about SGH, mission, culture, reasons to love SGH. We'll put as
maybe multiple paragraphs. Responsibilities: bullet list. Requirements: bullet list (education/experience, license, physical ability). Qualifications: bullet list (interest, commitment, enthusiasm). Skills: bullet list (communication, problem-solving, accountability, teamwork, teachable, plus experience areas). Benefits: bullet list of benefits as given. Pay: paragraphs about salary ranges, sign-on bonus, total comp description, plus disclaimer. Now we need to ensure we don't include duplicated lines. For example, "Must be able to climb ladders and scaffolds, and work at great heights." appears both in responsibilities and requirements; we should include only once? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If it's duplicated in the source, we might need to keep both? Usually we would deduplicate to avoid repetition but the instruction says preserve ALL substantive information; does that mean we must keep duplicates? It says "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing away detail would be removing info; but removing duplicate info could be considered summarizing? It's ambiguous. Safer to keep both occurrences? But that would be redundant and maybe considered filler? However they said "never emit a heading followed by filler/placeholder text". Duplicate info is not filler but redundant. I'd lean to keep it once to avoid redundancy but still preserve the info. I'd include it under Requirements (since it's a requirement) and not repeat under Responsibilities (maybe mention it there as part of duties). Actually responsibilities already include climbing ladders etc. So we could keep it in responsibilities and not duplicate in requirements. But the requirement also mentions it; we could keep it there as well but it's duplicate. I'd choose to include it under Responsibilities (as duty) and also under Requirements (as requirement) but maybe it's okay. However to be safe, I'll include it only once under Responsibilities (since it's a duty) and also mention under Requirements as "Ability to climb ladders and scaffolds and work at great heights." but that is duplicate. I'd rather include it under Requirements as it's a requirement; responsibilities already mention it; but we can keep both but maybe it's okay. Given the instruction to prefer a few substantive sections over many thin ones, we might combine some. Let's think: Could we merge Requirements and Qualifications into one "Requirements" section? But they ask to use those headings if we have content. We'll keep them separate. Now let's draft HTML. We'll start with
About the role
then...
. We need to ensure we don't include any HTML tags besides those. Let's write the About the role paragraph(s). Could be multipletags. We'll combine the intro: "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 next paragraph: "What makes careers at SGH so special? The only way to advance is to question and explore. Every member of