Deputy Structural Design Manager

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse the posting. Content: - Intro: "What We're Looking For" then description about role. Could be "About the role". We'll treat that as About the role. - "What You'll Do" -> Responsibilities. - "What You'll Need" -> Requirements (maybe also Qualifications). It lists Bachelor’s degree in Engineering and 8 years of relevant experience, 2 years task management or Deputy PM experience. - "What You'll Bring" -> Skills? It lists abilities: delivering 4for4, identifying risk, leading technical team, using system tools, interfacing with client-level peer, providing technical guidance, demonstrated ability to learn, teach, implement new standards. - "What We Prefer" -> Qualifications (preferred). Master’s degree, 10 years experience, PE certification, Design-Build experience as structural technical lead, etc. - Pay: there are pay ranges for Colorado, Nevada, Connecticut. So we have Pay section with those ranges. - Benefits: there is a link "Click here for benefits information: HNTB Total Rewards". That's a benefit reference. We can include Benefits section with that note. - Schedule: not mentioned. No schedule info. So omit. - Locations: could be included maybe as part of About the role? Not a defined heading. Could be included in About the role paragraph. - Other metadata like Job ID, etc should be dropped. - Remove boilerplate: EEO, visa sponsorship, etc. We need to preserve all substantive information. So include the description paragraphs. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide what to list as lists. Responsibilities: many bullet-like sentences separated by periods. Could convert each sentence to

• . But we need to preserve all info; we can either keep as prose paragraphs or list. The instruction: Use
  • for any list of duties/requirements/benefits. If we have a series of duties, we can make a list. It's okay. Similarly for Requirements: list items. Skills: list. Preferred Qualifications: list. Benefits: maybe just a paragraph with link. Pay: we can list each state range as
  • . Let's extract details. About the role paragraph: combine the first block after "What We're Looking For" up to before "What You'll Do". Let's capture: "The Deputy Structural Design Manager will provide leadership and technical oversight for the delivery of large-scale design-build infrastructure projects, which could exceed $1 billion in construction value. Working in partnership with the Structural Design Manager, this role coordinates and integrates the efforts of structural engineering teams across multiple firms and office locations, ensuring consistency in design standards, quality, and project execution. The Deputy Structural Design Manager is responsible for reviewing critical design decisions, managing technical interfaces, resolving complex engineering challenges, and overseeing adherence to project requirements, codes, and client expectations. The role supports design schedule development, resource planning, risk management, and stakeholder coordination while fostering collaboration among internal teams. This position serves as a key technical authority to achieve successful project delivery on complex, high-profile transportation, bridge, and other major infrastructure programs. At HNTB, you can create a career that is meaningful to you while building communities that matter to all of us. For more than a century, we have been delivering solutions for some of the largest, most complex infrastructure projects across the country. With our historic growth, it is an exciting time to join our team of employee-owners." That's the About the role. Responsibilities: after "What You'll Do". Let's capture each sentence: - Responsible for development of the project scope and fee quotation and assists in the preparation of technical proposals and contracts in accordance with HNTB's Sophisticated Contracting Approach (SCA). - Serves as the primary client liaison and manages the project team to deliver the scope, schedule, and budgets to completion and to the client’s satisfaction. - Assists with client project scoping and contract negotiations. - Performs technical discipline tasks including analysis, reports, design, specification, and production for assigned projects. - Implements the firm’s project delivery plan using HNTB's Sophisticated Delivery Approach (SDA) on each project. - Leads the development and the execution of the project management plan. - Supervises and mentors team to overall project objectives. - Performs coordination with managers on project staffing, including, but not limited to; recruitment, development, retention, and succession of project staff; development of plan for project staff reporting; and support for performance and compensation reviews. - Partners with Client Service Leaders and pursuit champions to assist with business development, building client relationships, and pursuit efforts for strategic and mini-mega projects in accordance with HNTB's Sophisticated Sales Approach (SSA). - Works with the project team and marketing resources to prepare appropriate proposal and presentation materials. - Leads proposal development and interview presentations for strategic and mini-mega projects to the client as well as general presentations within the industry and community. - May be responsible for the recruitment, hiring, development, and retention of staff, including development of plan for staff reporting, performance and compensation reviews, and succession. - Performs other duties as assigned. We'll list each as
  • . Requirements: after "What You'll Need". It says: "Bachelor’s degree in Engineering and 8 years of relevant experience 2 years task management or Deputy PM experience" We can make two list items. Skills: after "What You'll Bring". Let's capture each bullet (they are separated by periods). Items: - Successfully delivering 4for4 (on-time, on-budget, quality, client satisfaction) on smaller projects. - Identifying and escalating risk and change management issues, with oversight from more experienced staff. - Leading a technical team for small to midsize projects or task order with a few subconsultants. - Using system tools to manage, monitor, and deliver smaller projects or task orders. - Interfacing with your client-level peer on other projects or task orders. - Providing strong technical guidance to team and task leads as well as performing portions of the technical work. - Demonstrated ability to learn, teach, and efficiently implement new standards. We'll list each. Preferred Qualifications: after "What We Prefer". Items: - Master’s degree in Engineering - 10 years relevant experience - Professional Engineer (PE) certification - Design-Build experience as structural technical lead, and/or within design team management, strongly preferred. We'll list. Benefits: "Click here for benefits information: HNTB Total Rewards". We'll make a

    with that link? The instruction: use

    for prose. Could embed anchor? Not specified but we can include plain text with URL? Probably just text. Pay: we have ranges for Colorado, Nevada, Connecticut. We'll list each as

  • with description. We should not include schedule. We must not repeat job title as heading. Not include Job ID etc. We need to output only HTML fragment. Let's craft:

    About the role

    ...paragraph...

    Responsibilities

    • ...
    ...

    Requirements

    • Bachelor’s degree in Engineering and 8 years of relevant experience
    • 2 years task management or Deputy PM experience

    Skills

    • Successfully delivering 4for4 (on-time, on-budget, quality, client satisfaction) on smaller projects.
    ...

    Preferred Qualifications

    • Master’s degree in Engineering
    • 10 years relevant experience
    • Professional Engineer (PE) certification
    • Design-Build experience as structural technical lead, and/or within design team management, strongly preferred.

    Benefits

    Click here for benefits information: HNTB Total Rewards

    Pay

    • Colorado: approximate pay range $139,645.93 - $218,420.56
    • Nevada: approximate pay range $133,298.38 - $208,492.35
    • Connecticut: approximate pay range $139,645.93 - $218,420.56
    We need to ensure we preserve all substantive information. Also note that the pay ranges have disclaimer text; we could include that as prose after list? The instruction: include Pay section only if posting actually states them. It does state them, plus disclaimer. We could include the disclaimer as a

    after the list. But we must not invent or summarize away detail. The disclaimer is substantive: "Please note that the pay range provided is a good faith estimate for the position based on all selected locations within the state at the time of posting. Actual compensation will be dependent on factors, including but not limited to, the individual’s qualifications, experience, knowledge, skills, and abilities as well as physical work location within the state." This appears for each state. We could include a single

    after the list that captures that disclaimer (it's same for each). Or we could include each disclaimer as part of each

  • . Better to include a

    after list with the disclaimer (maybe generic). But the disclaimer mentions "based on all selected locations within the state". It's repeated for each state; we can summarize but that would be summarizing. Safer to include the disclaimer as a

    after the list, but we need to ensure we don't lose the per-state nuance. The disclaimer is same for each state; we can include it once. Thus:

    Pay

    • Colorado: approximate pay range $139,645.93 - $218,420.56
    • Nevada: approximate pay range $133,298.38 - $208,492.35
    • Connecticut: approximate pay range $139,645.93 - $218,420.56

    Please note that the pay range provided is a good faith estimate for the position based on all selected locations within the state at the time of posting. Actual compensation will be dependent on factors, including but not limited to, the individual’s qualifications, experience, knowledge, skills, and abilities as well as physical work location within the state.

    We also have "The anticipated last day to apply is 01/03/2027." That's a date; could be considered metadata but not explicitly excluded. It's not a heading; we could include in About the role or a separate

    maybe under About the role. It's substantive info about application deadline. Should we preserve? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that. Where? Could add a

    after About the role or maybe a separate section like "Application timeline"? But we only have allowed headings list; we could add a

    under About the role. Since it's not a duty/requirement/benefit, we can just put in a paragraph. Also "Please note that the job may be unposted prior to this date if the job is filled or no longer a need." That's also substantive. Also "Click here for benefits information: HNTB Total Rewards" we already have. Also "Click here to learn more about Equal Opportunity Employer/Disability/Veteran" is boilerplate EEO