Security Designer II

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. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, navigation, etc. Must not include placeholder sections. We need to parse the posting. Content: Intro paragraph about HDR culture etc. Could be "About the role" or maybe "About HDR". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide appropriate headings. We have sections: - Intro description: "At HDR, our employee-owners are fully engaged..." This is about company culture. Could be "About HDR" but not in list; but we can use "About the role" maybe includes description of role? Actually "About the role" could be a summary of the role. The posting includes description of role: "As part of HDR’s Building Engineering Services Group, you’ll help design the critical infrastructure..." That's role description. So we can put that under

About the role

. - Responsibilities: bullet list after "In the role of Security Designer II, we'll count on you to:" then list items. Those are responsibilities. So

Responsibilities

with

• each. - Preferred Qualifications: "CPP certification Preference given to candidates currently residing in the Mid-Atlantic (VA/MD/DC) Area". That's a preferred qualification. Could go under

  Preferred Qualifications

  but not in list; we have Qualifications heading maybe includes both required and preferred? The instruction list includes Qualifications as a possible heading. We could have

  Qualifications

  and inside include both required and preferred? But they said prefer few substantive sections over many thin ones. Could combine Required Qualifications and Preferred Qualifications under Qualifications. However they also have separate headings Requirements and Qualifications in list. Might be better to have Requirements (maybe required) and Qualifications (maybe preferred). But we need to decide. We have Required Qualifications: Bachelor's degree..., minimum 5 years experience..., familiarity with Autodesk, RCDD..., Electrical Engineering degree helpful, attitude commitment. Preferred Qualifications: CPP certification, preference for Mid-Atlantic residency. We could have

  Requirements

  for required qualifications, and

  Preferred Qualifications

  for preferred. But Preferred Qualifications not in the given list but we can still use it? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can add other headings if needed, but better to stick to those. Could put both under Qualifications. But we also have Skills maybe not explicitly listed. Could infer from responsibilities: design integrated electronic security systems, calculate electrical power loads, determine UPS requirements, design single line diagrams, write specifications, QA/QC, etc. Could list as Skills but we already have responsibilities covering them. Might be redundant. We have Benefits: paragraph about comprehensive benefits package. So

  Benefits

  with
  • items. We have Pay: compensation ranges for locations. So

    Pay

    with maybe a

    listing ranges. We have Schedule: "Full-time" and "Employee Status: Regular". So we can have

    Schedule

    with

    Full-time, Regular. We also have Location info: Primary Location etc. Could be included under About the role or maybe a separate section but not required. Could include in About the role paragraph. We must not include boilerplate like EEO, navigation, legal, etc. Also remove duplicated lines. We must preserve all substantive information. So we need to include all the details: responsibilities list, required qualifications, preferred qualifications, benefits list, pay ranges, schedule, location, maybe industry, job posting date? The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Job posting date maybe minor metadata; could be included in a short

    at end or dropped. Probably we can include a short

    with "Posted: Sep 25, 2026". But they said fold minor metadata into a short

    or drop it. So we can include a short paragraph. We must not include the "Watch Our Story:" link? That's maybe navigation? It's a link to story; could be considered boilerplate? It's part of intro but maybe keep as part of About the role? It's a link; we could keep as plain text? Probably better to drop it as it's not substantive about role. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to our story might be considered navigation? It's a link to company story; could be considered navigation. Safer to drop. Also remove "Read further to learn how you could help make great things possible not only in your community, but around the world." That's fluff; maybe keep as part of About the role? It's generic; could be dropped. But we need to preserve ALL substantive information; that line is not substantive specifics. So we can drop. Now craft HTML. Structure:

    About the role

    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. Primary Location: Glen Allen, VA; other locations: Arlington, VA; Vienna, VA; Fulton, MD.

    Maybe include location as separate? But okay.

    Responsibilities

    • Design integrated electronic security systems
    • Calculate electrical power loads, determine UPS requirements and design of system-related single line diagrams
    • Take responsibility for complete set of construction documents
    • Understand that assignments have objectives that require investigation of many variables
    • Independently perform security system/electrical engineering assignments with broad general instruction from Project Manager as to the results expected
    • Write specifications covering all security system matters; perform reviews and work directly with owners as a part of project team
    • Assist other Designers, Project Coordinators or Technicians as needed, and be responsible for work in all phases of security design process
    • Conduct QA/QC on the work of other Project Coordinators or Technicians as needed
    • Perform other duties as needed

    Requirements

    • Bachelor's degree in Electrical Engineering or combination of education and relevant experience
    • A minimum of 5 years of experience in security design
    • Familiarity with Autodesk
    • RCDD (Registered Communication Distribution Designer) certification helpful
    • Electrical Engineering degree helpful
    • Attitude and commitment to being an active participant of our employee-owned culture is a must

    Preferred Qualifications

    • CPP certification
    • Preference given to candidates currently residing in the Mid-Atlantic (VA/MD/DC) Area

    Benefits

    • Medical
    • Dental
    • Vision
    • Short and long-term disability
    • Life insurance
    • Employee assistance program
    • Paid time away
    • Parental leave
    • Paid holidays
    • Retirement savings plan with employer match
    • Employee referral bonus
    • Tuition reimbursement

    Pay

    Fulton, MD: $103,334 - $147,620; Arlington, VA: $112,728 - $161,040; Glen Allen, VA: $93,940 - $134,200; Vienna, VA: $112,728 - $161,040.

    Schedule

    Full-time, Regular employee status.

    Maybe add a short paragraph for posting date:

    Posted: Sep 25, 2026

    Check for any duplicated lines: we haven't repeated. Check for any boilerplate left: we removed EEO, navigation, etc. Check for any placeholder like "commensurate with experience" - none. Check for any missing substantive info: we included responsibilities, required qualifications, preferred qualifications, benefits, pay, schedule, location, role description. We omitted "Industry: Building Engineering" and "BusinessClass: Information Communication Technology (ICT)/Security". Those are substantive but maybe minor metadata; could be included in About the role or a short paragraph. Let's add a short paragraph after About the role: "Industry: Building Engineering; Business Class: Information Communication Technology (ICT)/Security." Or incorporate. We also omitted "Employee-owners" culture description earlier; we included some. We omitted "We believe building engineering is more than systems and structures..." we included in role description. We omitted "Each and every role throughout our organization makes a difference..." maybe fluff. We omitted "Watch Our Story:" link. We omitted "At HDR, we are committed to the principles of employment equity..." that's EEO boilerplate; removed. We omitted "We consider all qualified applicants, regardless of criminal histories..." also EEO; removed. We omitted "As we foster a culture of inclusion..." we included some culture in About the role? We included employee-owners culture but not the inclusion specifics. Could add a sentence about inclusion but maybe it's boilerplate? It's part of company culture; could be considered substantive? It's about inclusion and employee network groups. That is substantive: they list eight Employee Network Groups etc. That is specific info about benefits/culture. Should we include? It's under "Our Commitment" section. That is substantive about employee network groups and benefits. Could be included under Benefits or a separate section like "Culture". But we don't have a heading for Culture; we could add under Benefits? Not exactly. Could add a section "Employee Network Groups" but not in list. However we could include under Benefits as part of benefits package? It's not a benefit but a program. Might be okay to include under Benefits as a bullet list? But the instruction says prefer few substantive sections over many thin ones. Could add a paragraph under About the role describing culture and employee network groups. Let's incorporate: After role description, add a sentence: "HDR fosters a culture of inclusion through eight Employee Network Groups (Asian Pacific, Black, Hispanic/Latino(a), LGBTQ+, People with Disabilities, Veterans, Women, Young Professionals), each with an executive sponsor and open to all employees." That preserves that info. Also we omitted "Our Commitment As employee owners, we all have a role in creating an inclusive environment..." similar. We can combine. Now check for any other substantive info: "We provide a comprehensive benefits package that promotes employee ownership,