Electrical Designer / Electrical Engineer - Level II & III (Multiple Openings)

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 where there is real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO etc. Also remove "Applications are accepted on an ongoing basis." etc? That might be considered application instructions? It says "Applications are accepted on an ongoing basis." That's maybe not an instruction but a note. Might be considered boilerplate? It's not exactly application instructions but could be considered meta. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So "Applications are accepted on an ongoing basis." is an application instruction? Possibly yes. We'll drop it. We need to parse the posting. Let's extract sections: - About the role / summary: The first paragraphs about Henderson, mission, etc. That's about company, not role. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have a "Summary Electrical Engineers and Electrical Designers are responsible for the design, coordination, documentation, and delivery of electrical building systems for various environments. Depending on experience level, individuals may perform engineering calculations, prepare and review design documents, coordinate with project teams, manage tasks or projects, provide technical leadership, mentor others, and support business development activities. All team members are expected to uphold a client-centric mindset, demonstrate quality and integrity, and contribute to a collaborative, inclusive, and continuously learning environment. Today’s buildings are rapidly evolving. Electrical system design is no longer as simple as lighting and power design overlaid onto an architectural background. Our engineers understand that the electrical system forms the foundation that makes the building come to life. It’s a responsibility that we take very seriously. We balance the rigorous requirements of life safety and code compliance with practicality and aesthetic considerations to deliver a design that supports life of the building and delivers on our client’s vision for the project." That's a description of role. Could go under "About the role" or "Responsibilities". Then we have "Key Responsibilities" list. Then "Core Competencies" list. Then "Qualifications" list. Then "Let's Talk Perks" which includes culture and benefits. Then "Benefits" list. Then "Pay Transparency" with salary ranges per city. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no explicit schedule info. So we should not include Schedule unless present. There's mention of "Flexible Work Hours" under culture, but that's not a schedule spec. Might be considered schedule? The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. "Flexible Work Hours" is specific content about schedule flexibility. Could be considered schedule. But the heading "Schedule" maybe appropriate. However we have also "Culture" section with flexible work hours etc. The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should limit to those headings. So we should map content to those headings. If we have culture info, maybe put under Benefits? Or maybe under About the role? But we have a Benefits heading for benefits. Culture could be part of Benefits? Not exactly. Could be part of About the role? Might be okay to include a "Culture" heading? But instruction says use those headings; maybe we can still use others but they gave examples. Safer to stick to those headings. We can put flexible work hours under Benefits? Or maybe under About the role? Let's think. We have "Let's Talk Perks" which includes culture and benefits. Then separate "Benefits" list. So we could combine culture and benefits under Benefits heading? But the Benefits heading is for benefits like 401K, ESOP, etc. Culture items like flexible work hours, casual dress, paid volunteer time, etc. Could be considered benefits as well. So we can put all under Benefits heading. Pay heading: we have salary ranges. Schedule heading: we have no explicit schedule like full-time, part-time, shift. Not present. So we omit Schedule. Requirements vs Qualifications: The posting has "Qualifications" section with bullet points. Also there is "Core Competencies" which could be Skills. So we can map: - About the role: the summary paragraph(s) describing role. - Responsibilities: the "Key Responsibilities" list. - Requirements: maybe the "Qualifications" section? But they also have "Qualifications" heading. The instruction includes both Requirements and Qualifications as separate headings. We need to decide what goes where. Typically Requirements are mandatory qualifications; Qualifications are desired. But we have only one qualifications list. Could split: Requirements: Bachelor’s degree and 3+ years of relevant experience, Intermediate proficiency in Revit, Bluebeam, and design principles, FE and PE completion preferred, Ability to lead small tasks or portions of projects, Completion of FE exam, LEED and/or WELL accreditation. Intermediate to advanced knowledge and proficiency in engineering design, A&E industry, codes, design guides and standards required. Knowledge applicable to a range of practices, project or program types. Skills: Core Competencies list. But we also have "Qualifications" heading; we could put the same list under Qualifications. However we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section? But we must use headings as per examples; we could still include both but if content is thin maybe better to combine. However we have enough content for both? Let's see. We could treat "Requirements" as the mandatory items: Bachelor’s degree and 3+ years of relevant experience, Intermediate proficiency in Revit, Bluebeam, and design principles, Ability to lead small tasks or portions of projects, Intermediate to advanced knowledge and proficiency in engineering design, A&E industry, codes, design guides and standards required. Knowledge applicable to a range of practices, project or program types. And "Qualifications" as preferred: FE and PE completion preferred, Completion of FE exam, LEED and/or WELL accreditation. But the text says "FE and PE completion preferred" and "Completion of FE exam, LEED and/or WELL accreditation." That's somewhat overlapping. We'll split. Skills: Core Competencies list. Now Benefits: combine culture and benefits list. Pay: salary ranges. Now we need to ensure we don't include boilerplate: EEO, Vet/Disabled, E-Verify, legal notices, recruitment fraud alert, etc. Remove those. Also remove duplicated lines: e.g., "Accepting applications on an ongoing basis" appears twice; we drop. Also remove "Let's Talk Perks" heading? We'll convert to Benefits heading. Now produce HTML fragment with

headings and

• for lists,

  for prose. We must not include or . Just the fragment. Let's craft. First, About the role: combine the initial paragraphs about Henderson? Actually the instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have About the role heading with description of role and maybe company overview? The initial paragraphs about Henderson are more about company. Could be considered About the role? Might be okay. But we could also include company overview under About the role as it's relevant to role context. We'll include the summary paragraphs that describe the role and the company mission. We'll take the paragraph starting "At Henderson, We're About More Than Just Buildings..." up to "It's What We Do". Actually that's a lot. But we need to preserve all substantive information; we cannot invent or summarize away detail. So we need to keep the content but we can format as prose under About the role. Let's extract the substantive content before the "Summary Electrical Engineers..." section. The text: "At Henderson, We're About More Than Just Buildings We're about the people, experiences, and potential found inside. We’re a company of problem-solvers and innovators known for our technical excellence and ability to come up with out-of-the-box solutions. We love the process of bringing buildings to life. And we're changing the industry by integrating the building design and construction process. As an ESOP, each of our employee-owners are an essential part of our mission to lead the industry in innovation, sustainability, and client experience. With a vision to build a better world, Team Henderson has a people-first culture and diverse portfolio of world-class facilities. It's What We Do We provide total building system design services across multiple high-growth markets for industry leaders. You'll get to use your talent to work on projects for some of the biggest names in mission-critical, higher education, sports, healthcare, grocery, restaurant, and retail within the sectors we serve in business, community, grocery, health, retail, & venue. It's How We're Different We're about more than just buildings. We're about you. You, and the hundreds of passionate employee-owners who make us who we are. We’ve always been committed to providing an inclusive workplace where people can bring their full self to work and helps people reach their full potential – both as professionals and individuals. Together, we dream up innovative solutions for industry-wide problems, design spaces that become landmarks, and toast the good life at our happy hours. Take a peek into what makes us different here: https://youtu.be/AIt17t_uJ-A?si=oSMy5zQeUcb_faE3" That's a lot of company marketing. It's substantive? It's about the company, not the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep it. However we might consider that as "About the role" content? It's not exactly role but it's about the company. Could be okay. After that, we have "Summary Electrical Engineers and Electrical Designers are responsible..." That's also role description. We could combine both under About the role. Now Responsibilities: the "Key Responsibilities" list. Now Requirements: we need to decide. Let's extract the Qualifications bullet list: "Qualifications Bachelor’s degree and 3+ years of relevant experienceIntermediate proficiency in Revit, Bluebeam, and design principles.FE and PE completion preferredAbility to lead small tasks or portions of projects.Completion of FE exam, LEED and/or WELL accreditation.Intermediate to advanced knowledge and proficiency in engineering design, A&E industry, codes, design guides and standards required. Knowledge applicable to a range of practices, project or program types." Note there is no punctuation between items; we need to parse. We'll split into items: - Bachelor’s degree and 3+ years of relevant experience - Intermediate proficiency in Revit, Bluebeam, and design principles - FE and PE completion preferred - Ability to lead small tasks or portions of projects - Completion of FE exam, LEED and/or WELL accreditation - Intermediate to advanced knowledge and proficiency in engineering design, A&E industry, codes, design guides and standards required - Knowledge applicable to a range of practices, project or program types Now we need to separate Requirements vs Qualifications vs Skills. Let's define: Requirements (mandatory): - Bachelor’s degree and 3+ years of relevant experience - Intermediate proficiency in Revit, Bluebeam, and design principles - Ability to lead small tasks or portions of projects - Intermediate to advanced knowledge and proficiency in engineering design, A&E industry