Structural Engineering Section Manager

Structural Engineering Section Manager

HDR · Montgomery, AL · 1 mo ago

On-siteConsultingFull-time

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 with real specific content. We need to parse the posting. First, there is introductory fluff about HDR culture etc. That could be "About the role" or maybe "About HDR". But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content belongs where. The posting includes: - Intro: "At HDR, our employee-owners are fully engaged..." etc. That's about company culture. Could be "About the role"? Actually "About the role" would describe the role. But we have a separate "Responsibilities". The intro could be considered "About the role" (overview). We'll include that as About the role. - Then: "HDR is looking for a Structural Engineering Section Manager to join our team. This position may be based in Atlanta, Birmingham, Mobile, or Montgomery." That's location info; could be part of About the role or maybe a short paragraph. - Then: "In this role, we'll count on you to:" followed by bullet list: - Build team technical expertise and design production capacity through recruitment, staff development, and training. - Lead and mentor staff. - Participate in leadership for technical service functions and support the development of HDR services in technical design. - Prepare structural proposals including scope development and estimating hours/fee. - Some regional/national travel will be expected. That's responsibilities. - Then "Preferred Qualifications" list: - MS or MSCE degree in Structural Engineering - PE license required, SE preferred - Minimum of 10 years of experience in structural design - Excellent communication, leadership, and planning skills, and the ability to thrive in a team environment - Ability to manage, lead and mentor other team members - Strong knowledge of modeling software such as STAAD, Enercalc, TEDDS, etc. - Previous experience with an architectural/engineering or engineering consulting firm - An attitude and commitment to being an active participant of our employee-owned culture - Local candidates are preferred - Then "Required Qualifications" list: - Bachelor's degree or equivalent experience - A minimum of 10 years experience - Professional registration, license or certification may be required based on role - Strong communication and listening skills - Ability to handle multiple assignments - Good leadership and organizational skills - An attitude and commitment to being an active participant of our employee-owned culture is a must - Then "What We Believe" etc. That's more about company culture; could be part of About the role or maybe separate but not in headings list. We could incorporate into About the role. - Then "Our Commitment" etc. Also culture. - Then metadata: Primary Location, Other Locations, Industry, Schedule: Full-time, Employee Status: Regular, BusinessClass, Job Posting date, etc. We need to include Schedule if present: "Schedule:Full-time". That's specific, so we should include a Schedule section with that content. Also maybe Pay? Not present. Benefits? Not present. So we should not create Benefits or Pay sections. - Also we have "Industry:Building Engineering". Could be part of About the role or maybe not needed. But we can include in About the role as a short paragraph. - Job Posting date: Sep 18, 2026. Could be minor metadata; we can fold into a short p or drop. Probably drop. - Also there is EEO statement at end; we need to remove boilerplate. Thus sections: About the role: include intro paragraph about HDR culture, role overview, location, maybe industry. Responsibilities: the bullet list after "In this role, we'll count on you to:". Requirements: maybe combine Required Qualifications? The headings list includes Requirements and Qualifications separate. We need to decide what goes where. Typically "Requirements" could be mandatory (Required Qualifications) and "Qualifications" could be preferred. But we have both Preferred Qualifications and Required Qualifications. So we can map: - Requirements: Required Qualifications (mandatory) - Qualifications: Preferred Qualifications (preferred) Skills: maybe we could extract skills from both lists, but we already have them in Requirements/Qualifications. The instruction says prefer a few substantive sections over many thin ones. We could combine skills into either Requirements or Qualifications, but we have headings for Skills. If we include Skills, we need specific content. We could pull out skills like communication, leadership, planning, software knowledge, etc. But that would duplicate content. Better to not create Skills section if we already covered in Requirements/Qualifications. However we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we can omit Skills if not needed. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. Check if any Benefits or Pay: none. Now we need to output HTML fragment: use

for each section heading, then content:
for prose,
for lists. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. We need to ensure we include all details from the posting that are substantive. Let's extract all substantive info: Intro paragraph(s): - "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 work to weave diversity, equity, and inclusion into our work and foster a sense of belonging throughout the 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 need to keep the URL? The instruction says preserve ALL substantive information; do not invent or summarize away detail. The URL is part of the posting. Should we keep it? It's a link. We can keep as plain text or as ? The instruction didn't forbid links. We can keep as plain text. But note: The URL appears with a stray quote at end: "https://www.hdrinc.com/our-story'". We'll keep as is. Then: "HDR is looking for a Structural Engineering Section Manager to join our team. This position may be based in Atlanta, Birmingham, Mobile, or Montgomery." Then responsibilities list. Then Preferred Qualifications list. Then Required Qualifications list. Then "What We Believe" paragraph: "HDR is our company. Together, we build on each other's life experiences and perspectives to make great things possible every day. This shapes our collaborative culture, encourages organizational trust and connects us closer to the clients and communities we serve." Then "Our Commitment" paragraph: "As employee owners, we all have a role in creating an inclusive environment where each of us is welcomed, valued, respected and empowered to bring our authentic selves to work every day. Our eight Employee Network Groups (Asian Pacific, Black, Hispanic/Latino(a), LGBTQ+, People with Disabilities, Veterans, Women, Young Professionals) help create a sense of belonging and foster a supportive environment where everyone is empowered to engage and contribute. Each group has an executive sponsor and is open to all employees." Then metadata: "Primary Location:United States-Georgia-Atlanta Other Locations:United States-Alabama-Mobile, United States-Alabama-Birmingham, United States-Alabama-Montgomery Industry:Building Engineering Schedule:Full-time Employee Status:Regular BusinessClass:Building Structural Job Posting:Sep 18, 2026" We need to preserve location info etc. Could be included in About the role or maybe a separate short paragraph. We should not include "Employee Status:Regular", "BusinessClass:Building Structural", "Job Posting:Sep 18, 2026" maybe minor metadata but we can fold into a short p or drop. 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 p for metadata like location, schedule, etc. But we already have Schedule section. So we can include location and industry in About the role. Thus About the role will contain: - Intro paragraph about HDR culture and impact. - Sentence about the role: "HDR is looking for a Structural Engineering Section Manager to join our team. This position may be based in Atlanta, Birmingham, Mobile, or Montgomery." - Maybe also industry: "Industry: Building Engineering." - Also maybe the What We Believe and Our Commitment paragraphs could be part of About the role (company culture). But we already have intro about culture; we could add those as additional paragraphs. We need to preserve all substantive info, so we should include the What We Believe and Our Commitment paragraphs somewhere. If we put them in About the role, that's fine. Thus About the role will be a series of
elements. Now Responsibilities:
each bullet. Now Requirements: Required Qualifications list. Now Qualifications: Preferred Qualifications list. Now Schedule:
Full-time
(or maybe just text). Since schedule is just "Full-time". We'll put
Full-time
. We must not create Benefits or Pay sections. Now ensure we don't repeat any content inadvertently. Let's draft. 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 work to weave diversity, equity, and inclusion into our work and foster a sense of belonging throughout the 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.

HDR is looking for a Structural Engineering Section Manager to join our team. This position may be based in Atlanta, Birmingham, Mobile, or Montgomery.

Industry: Building Engineering.

HDR is our company. Together, we build on each other's life experiences and perspectives to make great things possible every day. This shapes our collaborative culture, encourages organizational trust and connects us closer to the clients and communities we serve.

As employee owners, we all have a role in creating an inclusive environment where each of us is welcomed, valued, respected and empowered to bring our authentic selves to work every day. Our eight Employee Network Groups (Asian Pacific, Black, Hispanic/Latino(a), LGBTQ+, People with Disabilities, Veterans, Women, Young Professionals) help create a sense of belonging and foster a supportive environment where everyone is empowered to engage and contribute. Each group has an executive sponsor and is open to all employees.

Responsibilities

Build team technical expertise and design production capacity through recruitment, staff development, and training.

Lead and mentor staff.

Participate in leadership for technical service functions and support the development of HDR services in technical design.

Prepare structural proposals including scope development and estimating hours/fee.

Some regional/national travel will be expected.

Requirements

Bachelor's degree or equivalent experience

A minimum of 10 years experience

Professional registration,