Bridge Project Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate, EEO, legal, etc. Must preserve all substantive information. We need to parse the posting. Content: - Intro paragraph: "What We're Looking For At HNTB, you can invest in a career that is meaningful and rewarding to you while making a difference for Michigan communities that matter to all of us. As part of a nationwide firm, HNTB Michigan has been a part of delivering solutions for some of the largest and most innovative infrastructure projects across the state. With our historic growth and several office locations across the state, it is an exciting time to join our team of passionate professionals and employee owners working to build a better tomorrow." - Then description: "This opportunity entails being responsible for the production and modification of design calculations, technical reports, engineering plans and specifications for assigned projects. This position consults with the project manager to perform research, development, calculations, design and delivery. Applies engineering techniques, procedures and design criteria for projects ranging in size and complexity. Leverages technical knowledge and experience to address design related issues or concerns, working closely with the project manager through creative problem solving, interactions with clients and by completing tasks to meet the project schedule. Develops conceptual and detailed designs and calculations to support the project completion using current drawing and technical tools, programs and software. May mentor, train and review work of junior engineer staff and provide constructive feedback. As a member of the team, you will contribute to the successful project delivery for a diverse range of projects for HNTB’s clients" - Then "What You'll Do" list: bullet points: Responsible for the planning and distribution of discipline-specific work, and adherence to the schedule and budget on projects. Assists in marketing responsibilities, including proposal generation. Assists with the development of scope of work and level of effort for projects and/or assignments within discipline. Oversees completeness and accuracy of project team’s work within the technical discipline. Guides and mentors team to overall project objectives. Coordinates technical aspects of project with client counterpart and teaming partners at staff level for work within the discipline. Works closely with other disciplines on multi-discipline projects. Performs other duties as assigned. - Then "What You'll Need": Bachelor’s degree in Engineering and 6 years of relevant experience, or Master’s degree in Engineering and 5 years of relevant experience, or PhD in Engineering and 4 years of relevant experience - Then "What You'll Bring": Understands the impacts of decisions on technical design and work planning. Coordinates work planning and design effectively across multiple technical disciplines. Prepares high quality deliverables that are on time, and within budget and scope. - Then "What We Prefer": Master’s degree in Engineering 8 years relevant experience Professional Engineer (PE) certification Experience with CSi Bridge, LARSA 4D, STAAD, Midas Civil, LEAP Bridge Concrete, AASHTOWare BrR, PG Super, and OpenBridge Modeler Experience with MDOT bridge and structure design - Then "Additional Information": Click here for benefits information: HNTB Total Rewards Click here to learn more about Equal Opportunity Employer/Disability/Veteran Visa sponsorship is not available for this position. #AK #Bridges Locations: Detroit, MI, East Lansing, MI (Lansing), Grand Rapids, MI Notice To Third-party Agencies ... etc. Also Job Type: Regular Full/Part Time: Full time Job Category: Engineering Group ReqID: R-31548 etc. We need to remove boilerplate: EEO, legal, visa sponsorship note? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the "Click here for benefits information: HNTB Total Rewards" maybe? Actually benefits information is a link; but we are told to include Benefits section only if posting actually states them. The posting says "Click here for benefits information: HNTB Total Rewards". That's a statement about benefits but not details. It's vague; but it's still stating there is benefits info. However the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits info via a link, but not actual benefits. Might be considered stating them? It says "Click here for benefits information: HNTB Total Rewards". That is a statement that benefits info exists. I'd say we can include a Benefits section with that link? But we should not invent details. We could include a

with that sentence? However they said "Prefer a few substantive sections over many thin ones." Might be better to omit Benefits because it's just a link with no detail. But the rule says include section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state benefits info via a link, but it's not specific benefits. It's still a statement that benefits info exists. I'd lean to include a Benefits section with that link as a

. However the instruction also says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The benefits link might be considered navigation? Not sure. Pay and Schedule: Not mentioned. So we should not include Pay or Schedule sections. We need sections: About the role (intro), Responsibilities (What You'll Do), Requirements (What You'll Need), Qualifications (maybe What You'll Bring?), Skills (What We Prefer?), Benefits (maybe). But we need to map headings to content. We have: - About the role: could be the introductory paragraph(s) before "What You'll Do". That includes the first paragraph about HNTB and the opportunity description. Could combine. - Responsibilities: the bullet list under "What You'll Do". - Requirements: the "What You'll Need" (education/experience). - Qualifications: maybe "What You'll Bring" (impacts, coordination, deliverables). Could be considered qualifications. - Skills: "What We Prefer" (preferred qualifications, certifications, software experience, MDOT experience). That fits Skills. - Benefits: maybe the link. We should not include Pay or Schedule. We must not repeat job title as heading. No Job ID. We must preserve all substantive information. So we need to keep the locations? The posting includes locations: Detroit, MI, East Lansing, MI (Lansing), Grand Rapids, MI. That's substantive. Should we include that? Possibly under About the role or a separate section? There's no heading for Locations in the allowed list. Could we put it in a

under About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It doesn't say we cannot have other headings, but likely we should stick to those. However we need to preserve location info. Could embed in a paragraph under About the role. Also we have "Job Type: Regular Full/Part Time: Full time". That's schedule info? It's full time. Could be considered Schedule? But we should not create Schedule unless posting actually states them. It does state full time. So we could include a Schedule section with that info. However the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state full time. So we could include Schedule with that. But we need to see if we should include Pay? Not stated. So no Pay. But the instruction also says "Prefer a few substantive sections over many thin ones." So maybe we shouldn't create a Schedule section just for "Full time". Might be considered thin. Better to incorporate that info into About the role or Responsibilities? Could add a sentence. Similarly, benefits link is thin. Might be better to omit Benefits section. Thus we could have sections: About the role (intro + locations + job type), Responsibilities, Requirements, Qualifications, Skills. Let's craft. About the role: combine first paragraph and opportunity description plus locations and job type. First paragraph: "What We're Looking For At HNTB, you can invest in a career that is meaningful and rewarding to you while making a difference for Michigan communities that matter to all of us. As part of a nationwide firm, HNTB Michigan has been a part of delivering solutions for some of the largest and most innovative infrastructure projects across the state. With our historic growth and several office locations across the state, it is an exciting time to join our team of passionate professionals and employee owners working to build a better tomorrow." Opportunity description: "This opportunity entails being responsible for the production and modification of design calculations, technical reports, engineering plans and specifications for assigned projects. This position consults with the project manager to perform research, development, calculations, design and delivery. Applies engineering techniques, procedures and design criteria for projects ranging in size and complexity. Leverages technical knowledge and experience to address design related issues or concerns, working closely with the project manager through creative problem solving, interactions with clients and by completing tasks to meet the project schedule. Develops conceptual and detailed designs and calculations to support the project completion using current drawing and technical tools, programs and software. May mentor, train and review work of junior engineer staff and provide constructive feedback. As a member of the team, you will contribute to the successful project delivery for a diverse range of projects for HNTB’s clients" Locations: "Locations: Detroit, MI, East Lansing, MI (Lansing), Grand Rapids, MI" Job type: "Job Type: Regular Full/Part Time: Full time" We can combine into a few paragraphs. Responsibilities: list bullet points. Requirements: "Bachelor’s degree in Engineering and 6 years of relevant experience, or Master’s degree in Engineering and 5 years of relevant experience, or PhD in Engineering and 4 years of relevant experience" Qualifications: "Understands the impacts of decisions on technical design and work planning. Coordinates work planning and design effectively across multiple technical disciplines. Prepares high quality deliverables that are on time, and within budget and scope." Skills: "Master’s degree in Engineering, 8 years relevant experience, Professional Engineer (PE) certification, Experience with CSi Bridge, LARSA 4D, STAAD, Midas Civil, LEAP Bridge Concrete, AASHTOWare BrR, PG Super, and OpenBridge Modeler, Experience with MDOT bridge and structure design" We need to ensure we preserve all substantive information. Did we miss anything? The "Additional Information" includes "Click here for benefits information: HNTB Total Rewards" and "Click here to learn more about Equal Opportunity Employer/Disability/Veteran Visa sponsorship is not available for this position." We removed EEO etc. The visa sponsorship note is also boilerplate? It's about visa sponsorship not available. That's likely considered boilerplate/legal? Might be removed. The instruction says remove scam-warning boilerplate. Visa sponsorship not available is not scam warning but could be considered a note. I'd remove it. Also "#AK #Bridges" maybe tags; could be removed as boilerplate. Also "Notice To Third-party Agencies" etc is legal boilerplate; remove. Also "Job Type: Regular Full/Part Time: Full time Job Category: Engineering Group ReqID: R-31548" we kept job type but removed Job Category and ReqID as they are metadata. We should not include Job Category or ReqID. Thus final