Public Engagement & Strategic Communications Manager
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes a lot of prose about company culture, role description, responsibilities, qualifications (preferred and required), etc. No explicit Pay, Benefits, Schedule (though schedule is mentioned: Full-time). Actually there is "Schedule:Full-time". So we can include Schedule section with that content. Benefits not mentioned. Pay not mentioned. So we should not include Pay or Benefits sections.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat the job title as heading. Do not put Job ID/requisition numbers as headings. Remove boilerplate like EEO, etc. Also remove duplicated lines, navigation, cookie, legal, etc. Also remove application instructions (none present). Also remove the "Watch Our Story:" link? That's maybe boilerplate but it's part of description; but it's a link. Might be considered part of the description; but it's not essential? It says "Watch Our Story:' https://www.hdrinc.com/our-story'". That's promotional; could be considered boilerplate? It's not EEO but it's a marketing link. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This link is not those categories, but it's maybe not essential substantive info. However it's part of the "About the role" description. Might keep as part of prose? It's a link; but we can keep as plain text? Probably better to keep as part of prose but we can strip the URL? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The link is not substantive? It's a reference to story; maybe not essential. But it's part of the intro. I'd keep it as plain text without the URL? Might be considered navigation? It's a link to our-story; could be considered navigation. Safer to omit it.
We need to parse the posting and extract sections.
Let's identify content:
Intro paragraph about HDR culture, employee-ownership, etc. That's "About the role" or maybe "About HDR". We'll put under
About the role
with prose.
Then description of Strategic Communications Project Manager role: "The Strategic Communications Project Manager will develop, execute, and manage communication and public outreach activities on a variety of infrastructure projects. This is a person who is passionate about community engagement, loves to collaborate, and has a habit of thinking outside the box as a member of a high-performing team."
That's also part of About the role.
Then "Who You Are:" bullet list of attributes. That's qualifications/requirements. Could be under Requirements or Qualifications. We have both Preferred Qualifications and Required Qualifications sections later. So we can treat "Who You Are:" as part of Requirements (maybe as a list). Then we have Responsibilities section explicitly labeled. Then Preferred Qualifications, then Required Qualifications. Then "What We Believe", "Our Commitment", etc. Those are more about company culture; could be under About the role or maybe separate but we can combine.
We also have "Primary Location:United States-North Carolina-Raleigh Other Locations:..." and "Industry:Strategic Communications Schedule:Full-time Employee Status:Regular BusinessClass:Strategic Communications Job Posting:Sep 1, 2026". That's metadata; we can fold minor metadata into a short or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph with location, schedule, etc.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. Schedule is stated: Full-time. So we can include Schedule section with that content. However we also have location etc. Could put location under About the role or a separate "Details" but not required. Since we have Schedule section, we can include that.
We must not create Benefits or Pay sections.
Thus sections: About the role, Responsibilities, Requirements (maybe combine Who You Are + Required Qualifications?), Preferred Qualifications, Schedule.
But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use any of those that have content. We have About the role, Responsibilities, Requirements (maybe combine Who You Are and Required Qualifications), Qualifications (maybe Preferred Qualifications), Skills (maybe not separate), Schedule.
We could also have a Skills section if we extract skills from qualifications. But we can keep Qualifications for both preferred and required? Might be better to split: Requirements (required qualifications) and Qualifications (preferred). But the instruction says use headings as given; we can decide.
Let's extract content:
About the role: The introductory paragraphs about HDR culture, employee-ownership, service lines, etc., plus the role description.
Responsibilities: The list under "Responsibilities:" (multiple lines). We'll make
- each.
Requirements: The "Required Qualifications" list.
Qualifications: The "Preferred Qualifications" list.
Schedule: "Schedule:Full-time". Could also include location etc. But we can put location in About the role or a separate short p.
We must not repeat job title as heading.
We must not include boilerplate like EEO, etc. Remove the EEO statement at end.
Also remove duplicated lines: there may be duplicate sentences? Not obvious.
Now produce HTML.
We need to ensure we only output HTML fragment, no or , no markdown fences.
Let's craft.
First, About the role: combine paragraphs.
Paragraph 1: "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? 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. At HDR, our employee‑ownership model shapes everything we do, including how we support and care for our people. Our diverse service lines, including Water, Architecture, Building Engineering Services, Field Services, Power, Waste, Industrial, and Transportation reflect our commitment to shaping resilient, sustainable, and forward‑thinking communities around the world. Across these disciplines, our teams design and deliver solutions that safeguard public health, enhance quality of life, power innovation, and drive responsible growth. Whether advancing clean water, creating healing and learning environments, engineering next‑generation facilities, or building the infrastructure that moves people and energy, our work is rooted in technical excellence and a shared sense of purpose. Our employee‑owners collaborate across specialties, combining creativity, precision, and deep expertise to solve the most complex challenges facing our clients and communities."
Paragraph 2: Role description: "The Strategic Communications Project Manager will develop, execute, and manage communication and public outreach activities on a variety of infrastructure projects. This is a person who is passionate about community engagement, loves to collaborate, and has a habit of thinking outside the box as a member of a high-performing team."
We could also include "Who You Are:" as part of About the role? But it's more qualifications. We'll treat it under Requirements maybe.
But we already have Required Qualifications separate. The "Who You Are:" list includes many attributes that overlap with required qualifications. To avoid duplication, we could merge them. However we must preserve ALL substantive information; we can't discard. So we need to include that content somewhere. If we put it under Requirements, we need to ensure we don't duplicate with Required Qualifications. But we can combine them into a single list under Requirements, merging both sets. That would preserve all info without duplication. However the instruction says use headings; we can have a single Requirements section that includes both the Who You Are list and the Required Qualifications list. That's okay.
Similarly, Preferred Qualifications separate.
Thus:
About the role
... (combined intro paragraphs)
Responsibilities
- Lead the development of scope, schedule and budget for tasks and standalone projects.
- Interface with client and/or client-facing teams to coordinate delivery of a successful project.
- Lead communications strategy development for planning, design and construction projects.
- Lead campaign development activities including target audience analysis, branding, messaging, and market research
- Direct customer-facing communication in a variety of mediums including social, print, video and web.
- Lead concept development, writing and editing of collateral materials such as surveys, newsletters, websites, handouts, videos, advertisements, press releases and public notices.
- Coordinate with creative disciplines including graphic design, web development and social media to maintain consistency of brand, saturation of messaging, and user experience.
Requirements
- You are a forward-thinking person who is comfortable working on multi-disciplinary teams and collaborating effectively with colleagues in both content and technical development.
- You have a deep understanding of NEPA and how infrastructure projects are developed under these guidelines.
- You are not afraid of leading and facilitating contentious public meetings, public hearings, open houses and other meetings with the public, clients and other project stakeholders.
- You are a great writer, skilled at defining and articulating messages.
- You describe yourself as a storyteller.
- You are exceptionally organized, with an almost obsessive attention to detail, and highly driven with the ability to manage several projects and meet deadlines.
- You have a record of accomplishment of creating and implementing communications plans that included target audience strategies, marketing and advertising plans, event planning, and collateral material development and implementation.
- You have demonstrated a track record of successfully managing projects, including preparing and monitoring scope and budget, preparing and implementing schedule, and coordinating with team members to deliver successful projects.
- You are a highly creative person who understands the importance of clear communication across multiple channels and mediums.
- You are a lifelong learner who is constantly researching new technologies and trends, pushing clients and the team to innovate.
- You embrace the new.
- You’re a self-starter who thrives and adapts in fast-paced environments.
- A minimum of 7 years relevant industry experience, including management experience
- Excellent written and verbal communication skills
- Self-motivated and ability to work independent with multiple teams as well as team oriented
- Demonstrated leadership and organizational skills
- Great interpersonal and communication skills - positive outlook and attitude
- High aptitude for managing and solving tactical issues
- An attitude and commitment to being an active participant of our employee-owned culture is a must
- Comfortable and competent while working with senior leaders and managing cross-functional efforts
- Demonstrated ability to operate both strategically and tactically in a high-energy, fast-paced environment
- Committed to quality, continuous improvement, and HDR values
- Proficient in Adobe Creative Suite - InDesign
- Proficient in Microsoft Office Suite
Qualifications
- Master’s Degree preferred
- Previous work experience in the infrastructure industry
- Deep knowledge of communications plans and campaigns for public involvement, stakeholder engagement and public relations.
- Proven ability to develop compelling stories
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat the job title as heading. Do not put Job ID/requisition numbers as headings. Remove boilerplate like EEO, etc. Also remove duplicated lines, navigation, cookie, legal, etc. Also remove application instructions (none present). Also remove the "Watch Our Story:" link? That's maybe boilerplate but it's part of description; but it's a link. Might be considered part of the description; but it's not essential? It says "Watch Our Story:' https://www.hdrinc.com/our-story'". That's promotional; could be considered boilerplate? It's not EEO but it's a marketing link. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This link is not those categories, but it's maybe not essential substantive info. However it's part of the "About the role" description. Might keep as part of prose? It's a link; but we can keep as plain text? Probably better to keep as part of prose but we can strip the URL? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The link is not substantive? It's a reference to story; maybe not essential. But it's part of the intro. I'd keep it as plain text without the URL? Might be considered navigation? It's a link to our-story; could be considered navigation. Safer to omit it. We need to parse the posting and extract sections. Let's identify content: Intro paragraph about HDR culture, employee-ownership, etc. That's "About the role" or maybe "About HDR". We'll put under
About the role
with prose. Then description of Strategic Communications Project Manager role: "The Strategic Communications Project Manager will develop, execute, and manage communication and public outreach activities on a variety of infrastructure projects. This is a person who is passionate about community engagement, loves to collaborate, and has a habit of thinking outside the box as a member of a high-performing team." That's also part of About the role. Then "Who You Are:" bullet list of attributes. That's qualifications/requirements. Could be under Requirements or Qualifications. We have both Preferred Qualifications and Required Qualifications sections later. So we can treat "Who You Are:" as part of Requirements (maybe as a list). Then we have Responsibilities section explicitly labeled. Then Preferred Qualifications, then Required Qualifications. Then "What We Believe", "Our Commitment", etc. Those are more about company culture; could be under About the role or maybe separate but we can combine. We also have "Primary Location:United States-North Carolina-Raleigh Other Locations:..." and "Industry:Strategic Communications Schedule:Full-time Employee Status:Regular BusinessClass:Strategic Communications Job Posting:Sep 1, 2026". That's metadata; we can fold minor metadata into a shortor drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph with location, schedule, etc. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Schedule is stated: Full-time. So we can include Schedule section with that content. However we also have location etc. Could put location under About the role or a separate "Details" but not required. Since we have Schedule section, we can include that. We must not create Benefits or Pay sections. Thus sections: About the role, Responsibilities, Requirements (maybe combine Who You Are + Required Qualifications?), Preferred Qualifications, Schedule. But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use any of those that have content. We have About the role, Responsibilities, Requirements (maybe combine Who You Are and Required Qualifications), Qualifications (maybe Preferred Qualifications), Skills (maybe not separate), Schedule. We could also have a Skills section if we extract skills from qualifications. But we can keep Qualifications for both preferred and required? Might be better to split: Requirements (required qualifications) and Qualifications (preferred). But the instruction says use headings as given; we can decide. Let's extract content: About the role: The introductory paragraphs about HDR culture, employee-ownership, service lines, etc., plus the role description. Responsibilities: The list under "Responsibilities:" (multiple lines). We'll make
- each.
Requirements: The "Required Qualifications" list.
Qualifications: The "Preferred Qualifications" list.
Schedule: "Schedule:Full-time". Could also include location etc. But we can put location in About the role or a separate short p.
We must not repeat job title as heading.
We must not include boilerplate like EEO, etc. Remove the EEO statement at end.
Also remove duplicated lines: there may be duplicate sentences? Not obvious.
Now produce HTML.
We need to ensure we only output HTML fragment, no or , no markdown fences.
Let's craft.
First, About the role: combine paragraphs.
Paragraph 1: "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? 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. At HDR, our employee‑ownership model shapes everything we do, including how we support and care for our people. Our diverse service lines, including Water, Architecture, Building Engineering Services, Field Services, Power, Waste, Industrial, and Transportation reflect our commitment to shaping resilient, sustainable, and forward‑thinking communities around the world. Across these disciplines, our teams design and deliver solutions that safeguard public health, enhance quality of life, power innovation, and drive responsible growth. Whether advancing clean water, creating healing and learning environments, engineering next‑generation facilities, or building the infrastructure that moves people and energy, our work is rooted in technical excellence and a shared sense of purpose. Our employee‑owners collaborate across specialties, combining creativity, precision, and deep expertise to solve the most complex challenges facing our clients and communities."
Paragraph 2: Role description: "The Strategic Communications Project Manager will develop, execute, and manage communication and public outreach activities on a variety of infrastructure projects. This is a person who is passionate about community engagement, loves to collaborate, and has a habit of thinking outside the box as a member of a high-performing team."
We could also include "Who You Are:" as part of About the role? But it's more qualifications. We'll treat it under Requirements maybe.
But we already have Required Qualifications separate. The "Who You Are:" list includes many attributes that overlap with required qualifications. To avoid duplication, we could merge them. However we must preserve ALL substantive information; we can't discard. So we need to include that content somewhere. If we put it under Requirements, we need to ensure we don't duplicate with Required Qualifications. But we can combine them into a single list under Requirements, merging both sets. That would preserve all info without duplication. However the instruction says use headings; we can have a single Requirements section that includes both the Who You Are list and the Required Qualifications list. That's okay.
Similarly, Preferred Qualifications separate.
Thus:
About the role
... (combined intro paragraphs)
Responsibilities
- Lead the development of scope, schedule and budget for tasks and standalone projects.
- Interface with client and/or client-facing teams to coordinate delivery of a successful project.
- Lead communications strategy development for planning, design and construction projects.
- Lead campaign development activities including target audience analysis, branding, messaging, and market research
- Direct customer-facing communication in a variety of mediums including social, print, video and web.
- Lead concept development, writing and editing of collateral materials such as surveys, newsletters, websites, handouts, videos, advertisements, press releases and public notices.
- Coordinate with creative disciplines including graphic design, web development and social media to maintain consistency of brand, saturation of messaging, and user experience.
Requirements
- You are a forward-thinking person who is comfortable working on multi-disciplinary teams and collaborating effectively with colleagues in both content and technical development.
- You have a deep understanding of NEPA and how infrastructure projects are developed under these guidelines.
- You are not afraid of leading and facilitating contentious public meetings, public hearings, open houses and other meetings with the public, clients and other project stakeholders.
- You are a great writer, skilled at defining and articulating messages.
- You describe yourself as a storyteller.
- You are exceptionally organized, with an almost obsessive attention to detail, and highly driven with the ability to manage several projects and meet deadlines.
- You have a record of accomplishment of creating and implementing communications plans that included target audience strategies, marketing and advertising plans, event planning, and collateral material development and implementation.
- You have demonstrated a track record of successfully managing projects, including preparing and monitoring scope and budget, preparing and implementing schedule, and coordinating with team members to deliver successful projects.
- You are a highly creative person who understands the importance of clear communication across multiple channels and mediums.
- You are a lifelong learner who is constantly researching new technologies and trends, pushing clients and the team to innovate.
- You embrace the new.
- You’re a self-starter who thrives and adapts in fast-paced environments.
- A minimum of 7 years relevant industry experience, including management experience
- Excellent written and verbal communication skills
- Self-motivated and ability to work independent with multiple teams as well as team oriented
- Demonstrated leadership and organizational skills
- Great interpersonal and communication skills - positive outlook and attitude
- High aptitude for managing and solving tactical issues
- An attitude and commitment to being an active participant of our employee-owned culture is a must
- Comfortable and competent while working with senior leaders and managing cross-functional efforts
- Demonstrated ability to operate both strategically and tactically in a high-energy, fast-paced environment
- Committed to quality, continuous improvement, and HDR values
- Proficient in Adobe Creative Suite - InDesign
- Proficient in Microsoft Office Suite
Qualifications
- Master’s Degree preferred
- Previous work experience in the infrastructure industry
- Deep knowledge of communications plans and campaigns for public involvement, stakeholder engagement and public relations.
- Proven ability to develop compelling stories
- each.
Requirements: The "Required Qualifications" list.
Qualifications: The "Preferred Qualifications" list.
Schedule: "Schedule:Full-time". Could also include location etc. But we can put location in About the role or a separate short p.
We must not repeat job title as heading.
We must not include boilerplate like EEO, etc. Remove the EEO statement at end.
Also remove duplicated lines: there may be duplicate sentences? Not obvious.
Now produce HTML.
We need to ensure we only output HTML fragment, no or , no markdown fences.
Let's craft.
First, About the role: combine paragraphs.
Paragraph 1: "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? 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. At HDR, our employee‑ownership model shapes everything we do, including how we support and care for our people. Our diverse service lines, including Water, Architecture, Building Engineering Services, Field Services, Power, Waste, Industrial, and Transportation reflect our commitment to shaping resilient, sustainable, and forward‑thinking communities around the world. Across these disciplines, our teams design and deliver solutions that safeguard public health, enhance quality of life, power innovation, and drive responsible growth. Whether advancing clean water, creating healing and learning environments, engineering next‑generation facilities, or building the infrastructure that moves people and energy, our work is rooted in technical excellence and a shared sense of purpose. Our employee‑owners collaborate across specialties, combining creativity, precision, and deep expertise to solve the most complex challenges facing our clients and communities."
Paragraph 2: Role description: "The Strategic Communications Project Manager will develop, execute, and manage communication and public outreach activities on a variety of infrastructure projects. This is a person who is passionate about community engagement, loves to collaborate, and has a habit of thinking outside the box as a member of a high-performing team."
We could also include "Who You Are:" as part of About the role? But it's more qualifications. We'll treat it under Requirements maybe.
But we already have Required Qualifications separate. The "Who You Are:" list includes many attributes that overlap with required qualifications. To avoid duplication, we could merge them. However we must preserve ALL substantive information; we can't discard. So we need to include that content somewhere. If we put it under Requirements, we need to ensure we don't duplicate with Required Qualifications. But we can combine them into a single list under Requirements, merging both sets. That would preserve all info without duplication. However the instruction says use headings; we can have a single Requirements section that includes both the Who You Are list and the Required Qualifications list. That's okay.
Similarly, Preferred Qualifications separate.
Thus: