Senior Project Manager / Program Manager (Architecture)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title heading. Must not include Job ID etc. Must remove boilerplate: EEO, legal, etc. Must preserve all substantive info. We need to 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

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: - About the role: description of role, what they'll do, impact, etc. The paragraph: "As part of our Architecture practice at HDR, you’ll contribute to the design and delivery of spaces and experiences that advance community well-being around the world..." plus earlier intro about HDR. Likely belongs to About the role. - Responsibilities: list of duties under "In the role of Senior Project Manager / Program Manager, we'll count on you to:" then bullet list (though not bullet but sentences). We need to convert to

• . Items: Direct and coordinate work of single or multidiscipline teams throughout the project's lifecycle (from development & initiation to close-out); Assume leadership responsibilities for managing multidisciplinary science focused projects with a high degree of technical complexity and non-technical intricacies; Produce and coordinate several projects concurrently; Establish and maintain client relations, and be involved with marketing, contractual, design and production meetings; Conduct work sessions for deliverable development in conjunction with other staff and stakeholders; Coordinate staffing and workload through entire project life cycle, and ensure completion of deliverables on schedule; Track financial aspects of projects, and coordinate and adjust work effort with team to ensure that work is completed within parameters of agreed-to budget and schedule; Monitor the program's financial performance against pre-established financial metrics and make adjustments as necessary to meet earnings and profitability targets and control losses; Work with the Accounting, Operational and Business leadership for periodic project reviews; Implement QA/QC procedures; Supervise large project staffs and act as mentor for less-experienced Project Managers; Perform other duties as needed. - Preferred Qualifications: list: Experience and/or interest in sustainable design/LEED; PMP certification; Preference given to candidates currently residing in the Arlington, VA area; Preference given to candidates with laboratory experience; Due to client contract requirements US-born citizenship and a governmental background check are required. - Required Qualifications: list: Bachelor's degree in Architecture; 10 years related experience; A minimum 5 years project management experience; Registered Architect; Must be able to lead a team on projects; Experience with Microsoft Office (Word, Excel, Project); Knowledge and experience within the local and regional market; Good planning and mentoring skills; An attitude and commitment to being an active participant of our employee-owned culture is a must. - Skills: maybe combine some of the above? The posting includes "Good planning and mentoring skills" etc. Could be under Skills. But we already have Required Qualifications and Preferred Qualifications. The instruction includes Skills as possible section. We could put skills like Microsoft Office, planning, mentoring, etc. But we might avoid duplication. However we need to preserve all substantive info; we can put skills under Skills section, and qualifications under Required/Preferred. But we must not invent sections with filler. If we put Skills, we need actual content. We have content: "Experience with Microsoft Office (Word, Excel, Project)" is a skill. "Good planning and mentoring skills" is skill. "Knowledge and experience within the local and regional market" maybe skill. Also "Ability to lead a team" maybe skill. Could put those under Skills. But we also have Required Qualifications includes those items; we could keep them under Required Qualifications and not duplicate. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Required and Preferred into Qualifications? But they listed both as separate headings in the posting. The instruction allows Qualifications as a heading. Could we have a single Qualifications section containing both required and preferred? Might be okay but we need to preserve all info; we can separate required vs preferred within the section using

  or

  with notes. However the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists Requirements and Qualifications as separate possible headings. So we could have both Requirements and Qualifications sections. But we need to decide what goes where. Typically, Requirements = mandatory (required). Qualifications = preferred or additional. The posting has "Required Qualifications" and "Preferred Qualifications". So we could map Required Qualifications to Requirements section, and Preferred Qualifications to Qualifications section. That seems logical. Thus: - Requirements: Bachelor's degree in Architecture; 10 years related experience; Minimum 5 years project management experience; Registered Architect; Must be able to lead a team on projects; Experience with Microsoft Office (Word, Excel, Project); Knowledge and experience within the local and regional market; Good planning and mentoring skills; An attitude and commitment to being an active participant of our employee-owned culture is a must. - Qualifications (Preferred): Experience and/or interest in sustainable design/LEED; PMP certification; Preference given to candidates currently residing in the Arlington, VA area; Preference given to candidates with laboratory experience; Due to client contract requirements US-born citizenship and a governmental background check are required. Note: The citizenship and background check is a requirement (due to client contract). It's listed under Preferred Qualifications but actually it's a requirement. However we follow posting: it's under Preferred Qualifications. We'll keep it there. Now Skills: Could we extract any remaining skill not covered? The Required Qualifications already includes Microsoft Office, planning/mentoring, local market knowledge. Those could be considered skills but they are already in Requirements. To avoid duplication, maybe we don't need a separate Skills section. The instruction says prefer few substantive sections over many thin ones. So we could omit Skills if its content is already covered elsewhere. However we must preserve all substantive information; if we omit Skills section, we still have the info in Requirements (or Qualifications). That's fine. Benefits: The posting includes: "We provide a comprehensive benefits package that promotes employee ownership, employee health, performance, and success, which includes medical, dental, vision, short and long-term disability, life insurance, an employee assistance program, paid time away, parental leave, paid holidays, a retirement savings plan with employer match, employee referral bonus and tuition reimbursement." Also note: "(Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits.)" So we have Benefits content. Pay: The posting includes: "The expected compensation range for this position depends upon skills, experience, education and geographical location. (Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits.) Arlington, VA: $144,144 - $205,920." So we have Pay info: range for Arlington, VA. Schedule: The posting includes: "Schedule:Full-time Employee Status:Regular". So we have Schedule: Full-time. Thus we will include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include sections with filler like "commensurate with experience". Not needed. Now we need to format. We need to output only HTML fragment, no /, no markdown. We'll produce:

  About the role

  ... (combined intro paragraphs)

  But we need to ensure we don't repeat job title as heading. The job title is Senior Project Manager / Program Manager. We'll not put that as heading. Now we need to extract the About the role content. From posting: "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' We believe architecture is more than designing buildings, it’s about providing solutions to societal challenges and creating stronger, more vibrant communities. As part of our Architecture practice at HDR, you’ll contribute to the design and delivery of spaces and experiences that advance community well-being around the world. From healing environments and learning spaces to research labs and civic landmarks and infrastructure, your work will directly influence how individuals experience the world around them. We bring together architects, planners, designers, and technical experts to solve complex design challenges with creativity, curiosity, and collaboration. From championing design excellence with an emphasis on resilience and sustainability to pioneering innovative building technologies, your contributions will leave a lasting impact on the built environment. This isn’t just a job, it’s a chance to drive meaningful change and help define the future of our communities. 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 need to preserve all substantive info, but we can remove the URL? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The URL is not boilerplate; it's a link to Our Story. Should we keep it? It's part of the content. Probably keep as plain text (maybe as a link?). The instruction says output only HTML fragment; we could include an tag. But not required. We'll keep as plain text with the URL. We also need to remove duplicated lines. There's a duplicated line: "At HDR, our employee-owners are fully engaged..." appears again later? At the end there is "At HDR, we are committed to the principles of employment equity..." that's EEO boilerplate, should be removed. Also earlier there is "At HDR, our employee-owners are fully engaged..." appears only once at start. At the very end there is "At HDR, we are committed to the principles of employment equity..." which we will remove. Also there is "Read further to learn how you could help make great things possible not only in your community, but around the world." That's part of About the role. Now we need to format responsibilities as
  • each item. We need to split the responsibilities list into items. The original list is a paragraph with semicolons separating items. We'll split by semicolons and maybe "and". Better to split each bullet as separate sentence. We'll produce list items: - Direct and coordinate work of single or multidiscipline teams throughout the project's lifecycle (from development & initiation to close-out) - Assume leadership responsibilities for managing multidisciplinary science focused projects with a high degree of technical complexity and non-technical intricacies - Produce and coordinate several projects concurrently - Establish and maintain client relations, and be involved with marketing, contractual, design and production meetings - Conduct work sessions for deliverable development in conjunction with other staff and stakeholders - Coordinate staffing and workload through entire project life cycle, and ensure completion of deliverables on schedule - Track financial aspects of projects, and coordinate and adjust work effort with team to ensure that work is completed within parameters of agreed-to budget and schedule - Monitor the program's financial performance against pre-established financial metrics and make adjustments as necessary to meet earnings and profitability targets and control losses - Work with the Accounting, Operational and Business leadership for periodic project reviews - Implement QA/QC procedures - Supervise large project staffs and act as mentor for less-experienced Project Managers - Perform other duties as needed Now Requirements: list items. - Bachelor's degree in Architecture - 10 years related experience - A minimum 5 years project management experience - Registered Architect - Must be able to lead a team on projects - Experience with Microsoft Office (