ICT Security Designer

We need to output HTML fragment with sections for headings where there is real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, etc. Also remove duplicated lines, navigation, cookie, legal, application instructions. We need to preserve all substantive information. Let's parse the posting. Content: Intro paragraph about HDR culture, mission, etc. That's about the role? Could be "About the role" or maybe "About HDR". The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - Intro about HDR, employee-owners, mission, etc. Could be "About the role" or maybe "About HDR". Since they said "About the role" as example, we can use that for introductory descriptive paragraph about the role and company. - Then description of role: "As part of HDR’s Building Engineering Services Group, you’ll help design the critical infrastructure..." That's also about role. - Then "In the role of Security Designer I, we'll count on you to:" followed by list of duties (bulleted). Those are responsibilities. - Then "Preferred Qualifications:" list. - Then "Required Qualifications" list. - Then "What We Believe" etc. That's more about company culture; could be part of About the role or maybe separate but we don't have a heading for culture; we could put under About the role. - Then "Our Commitment" etc. Also culture. - Then "Primary Location: United States-Nebraska-Omaha Industry: Building Engineering Schedule: Full-time Employee Status: Regular Business Class: Information Communication Technology (ICT)/Security Job Posting: Sep 15, 2026". This includes Schedule (Full-time) and maybe location etc. We have a Schedule heading; we can include schedule info there. Also location maybe not needed as heading; could be placed in a paragraph under About the role or maybe omitted? The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So location etc can be minor metadata; we can include in a short p. - Also "At HDR, we are committed to the principles of employment equity..." that's EEO boilerplate; remove. We must not create Pay/Benefits sections unless posting actually states them. No pay or benefits mentioned. So omit those sections. We must not create heading with filler text. So only include sections where we have real content. Thus sections: - About the role (intro + description + maybe culture bits) - Responsibilities (list of duties) - Requirements (maybe combine Required Qualifications? Actually we have both Preferred Qualifications and Required Qualifications. Could combine under Requirements or Qualifications. The headings list includes Requirements, Qualifications, Skills. We need to decide. We have Required Qualifications: Bachelor's degree in Electrical Engineering or combination of education and relevant experience; attitude and commitment to being an active participant of our employee-owned culture is a must. Preferred Qualifications: Associate or technical school degree, or combination of education and relevant experience; Entry level to five years of related work experience; 2-10 years of related work experience (duplicate? weird); Problem-solving and growth mind-set; Ability to meet deadlines, handle multiple tasks independently, on schedule and under budget; Strong interpersonal and communication skills (oral and written); Ability to work in a high-velocity environment managing multiple tasks while maintaining attention to detail and workmanship quality; Strong computer skills and proficiency/ability to work in Bluebeam and Microsoft Office Suite; Ability to work in Revit, AutoCAD is a bonus; Must be able to learn new applications quickly; Knowledge of engineering drawings and design standards and practices; Strong desire for continuous learning and professional education; Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information; Preference given to local candidates. We also have some duplicated lines: "Associate or technical school degree, or combination of education and relevant experience" appears twice. Also "Entry level to five years of related work experience" and "2-10 years of related work experience" maybe overlapping but we keep both as they are in text. We need to preserve all substantive information; do not invent or summarize away detail. So we must keep both lines even if they seem overlapping. We also have "Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information." That's a requirement. We also have "Preference given to local candidates." We also have "Required Qualifications Bachelor's degree in Electrical Engineering or combination of education and relevant experience An attitude and commitment to being an active participant of our employee-owned culture is a must" Thus we can have a section "Requirements" for required qualifications, and maybe "Preferred Qualifications" under "Qualifications" or "Skills". The headings list includes Qualifications and Skills. We could put Preferred Qualifications under Qualifications, and maybe skills under Skills (like strong computer skills, etc). But we could also combine all under Qualifications. However we must not create thin sections; better to have a few substantive sections. We could do: - About the role (intro + role description + culture bits) - Responsibilities (list) - Requirements (required qualifications) - Qualifications (preferred qualifications + maybe skills) But we also have Skills heading; we could extract skills like strong computer skills, proficiency in Bluebeam/MS Office, Revit/AutoCAD bonus, ability to learn new apps, knowledge of engineering drawings, strong interpersonal communication, problem-solving, etc. But that would be splitting preferred qualifications into skills and qualifications. Might be okay but risk of thin sections. Given instruction: Prefer a few substantive sections over many thin ones. So maybe combine Preferred Qualifications and Skills into one "Qualifications" section. Thus sections: About the role, Responsibilities, Requirements, Qualifications. We also have Schedule info (Full-time). Could add a Schedule section. Since we have schedule info, we should include a Schedule section per heading list. It's substantive: "Schedule: Full-time". So we add Schedule section. We also have location etc; we could fold into About the role paragraph as minor metadata. We must not include Pay/Benefits. Thus final HTML:

About the role

At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? Watch Our Story: https://www.hdrinc.com/our-story Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world. We believe building engineering is more than systems and structures, it’s about powering progress and enabling innovation. As part of HDR’s Building Engineering Services Group, you’ll help design the critical infrastructure that supports the digital age and shapes the spaces where people work, connect, and thrive. From high-performance data centers driving the future of AI to dynamic commercial environments, your work will directly support technological advancement, sustainability, and human experience. We bring together mechanical, electrical, structural, and civil engineering experts to solve complex design challenges with precision, creativity, and collaboration. Whether you're optimizing energy efficiency, integrating resilient systems, or engineering the backbone of next-generation facilities, your contributions will help define the future of the built environment. This isn’t just a job, it’s a chance to lead innovation, engineer impact, and build a legacy of excellence. In the role of Security Designer I, we'll count on you to: ...

But we need to separate responsibilities list. So About the role should stop before the list of duties. So we put the intro up to "In the role of Security Designer I, we'll count on you to:" maybe not include the colon? Actually the colon introduces responsibilities. Better to put About the role up to before that sentence. Let's parse: Paragraphs: - Intro about HDR culture etc. - "As we foster a culture..." etc. - "Each and every role..." etc. - "We believe building engineering is more than systems and structures..." etc. - "As part of HDR’s Building Engineering Services Group, you’ll help design the critical infrastructure..." etc. - "From high-performance data centers..." etc. - "We bring together mechanical, electrical, structural, and civil engineering experts..." etc. - "Whether you're optimizing energy efficiency..." etc. - "This isn’t just a job, it’s a chance to lead innovation, engineer impact, and build a legacy of excellence." - Then "In the role of Security Designer I, we'll count on you to:" followed by list. Thus About the role can include all paragraphs up to the legacy sentence. Then Responsibilities heading with the list. Thus we need to extract that text. Let's copy the About the role content: "At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? Watch Our Story: https://www.hdrinc.com/our-story Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world. We believe building engineering is more than systems and structures, it’s about powering progress and enabling innovation. As part of HDR’s Building Engineering Services Group, you’ll help design the critical infrastructure that supports the digital age and shapes the spaces where people work, connect, and thrive. From high-performance data centers driving the future of AI to dynamic commercial environments, your work will directly support technological advancement, sustainability, and human experience. We bring together mechanical, electrical, structural, and civil engineering experts to solve complex design challenges with precision, creativity, and collaboration. Whether you're optimizing energy efficiency, integrating resilient systems, or engineering the backbone of next-generation facilities, your contributions will help define the future of the built environment. This isn’t just a job, it’s a chance to lead innovation, engineer impact, and build a legacy of excellence." Now Responsibilities: list after colon. List items: - General engineering knowledge of either the telecommunication (Horizontal/Backbone cabling) or electronic security systems (access control, video surveillance, intrusion detection etc.) and operational coordination with commercial hardware. - Show ability to design cabling pathways such as conduits or cable tray systems as well as proper bonding systems. - Meet with project clients to evaluate, define and review customer needs/objectives and ensure those requirements are met within the project design. - Define and develop complete project related construction documents to include all design documents (SD, DD, CD) to show design intent, project specifications and assist with system related activities within all construction administration (CA) activities. - Coordinate with integrated, multidisciplinary project teams to develop functional requirements, system designs and other project related requirements. - Edit telecommunication or security specifications for specific projects. - Maintain knowledge of current industry product offerings and research new emerging technologies. - Assist in problem resolution and technical troubleshooting when field support is needed. - Perform other duties as needed We need to put each as

inside

. Now Requirements (required qualifications): - Bachelor's degree in Electrical Engineering or combination of education and relevant experience - An attitude and commitment to being an active participant of our employee-owned culture is a must Also maybe "Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information." That is also a requirement (though appears under Preferred Qualifications list but it's a requirement). Actually it's in Preferred Qualifications list but it's a condition.