Highway Engineer III

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 if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive info. We need to parse the posting. Content: Intro: "We Make Everything Around Us Better At PRIME AE..." etc. That's about the company. Could be "About the role"? Actually "About the role" maybe not. The posting includes "Who We Are:" description of company. Could be "About the company" but not in allowed headings. Allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role" for description of role? The posting includes "The Opportunity:" and "What You'll Do:" etc. So we can map: - About the role: maybe summary of role (The Opportunity). Could include description of role and location. - Responsibilities: "Key Responsibilities:" list. - Requirements: maybe "What You'll Bring:" includes degree, experience, certifications, etc. Could be Requirements. - Qualifications: maybe overlapping with Requirements; but we need to avoid duplication. Could treat "What You'll Bring:" as Requirements, and maybe Qualifications for preferred items (PE license, mentoring). But we need to decide. - Skills: maybe software proficiency, standards knowledge. - Benefits: "Why PRIME AE:" includes career growth, culture, meaningful work, growth with purpose, national reach, local feel. Also "Our Commitment:" inclusive environment. Also "Hybrid" at end maybe indicates hybrid work arrangement. Could be Benefits. - Pay: not mentioned. - Schedule: not mentioned (no explicit schedule). So we omit Pay and Schedule. We must not create sections with placeholder text. So only include sections where we have real content. We need to use

for each section heading, then content:

for prose,

• for lists. We must not repeat job title as heading. No Job ID. We must preserve all substantive info; do not invent or summarize away detail. So we need to keep details like locations (Indianapolis or New Albany office), mention of projects types, etc. We need to be careful not to lose any info. Let's extract sections. **About the role** (maybe from "The Opportunity:" and location). Content: "We are currently seeking a Highway Engineer III to join our Transportation team in our Indianapolis or New Albany office. In this role, you will take an active role in the design and delivery of roadway and transportation infrastructure projects for state and local agency clients. You will work on projects involving roadway improvements, intersections, interchanges, ADA improvements, pedestrian facilities, maintenance of traffic, and transportation safety. This position is ideal for an experienced highway engineer ready to take greater ownership of technical design, project coordination, and delivery while collaborating with project managers, clients, and multidisciplinary teams. The current Engineer I description already identifies these types of transportation projects as the core focus of the position." We could also include earlier intro about PRIME AE? That's more about company, not role. But we could include in About the role? Might be okay but maybe better to include in a separate section? Not allowed headings besides those. Could we put company description under About the role? It might be okay but could be considered filler? It's substantive. However the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we can put any relevant content under them. So we could put company overview under About the role as well, but maybe better to put under About the role the role description; company overview could be placed under Benefits? Not exactly. But we could also put under About the role a brief about PRIME AE as part of role context. It's not prohibited. But we must not invent or summarize away detail. So we need to keep all details. Let's list all substantive info: - Company description: PRIME AE Group, Inc. (www.primeeng.com) is a nationally ranked, full-service architecture and engineering firm driven by collaboration, innovation, and commitment to strengthening communities. Offices across country, diverse team >550 professionals. Partner with public/private sector clients to deliver solutions across transportation, education, healthcare, municipal, federal, commercial, recreational markets. Culture blends entrepreneurial energy with resources of scaled multidisciplinary platform—giving people opportunity to shape meaningful projects while influencing future direction of firm. As PRIME AE expands capabilities, geographic reach, leadership bench, exciting time to join team building momentum, investing in growth, empowering leaders to make lasting impact. - The Opportunity: seeking Highway Engineer III to join Transportation team in Indianapolis or New Albany office. Role: active role in design and delivery of roadway and transportation infrastructure projects for state and local agency clients. Projects: roadway improvements, intersections, interchanges, ADA improvements, pedestrian facilities, maintenance of traffic, transportation safety. Ideal for experienced highway engineer ready to take greater ownership of technical design, project coordination, delivery while collaborating with PMs, clients, multidisciplinary teams. The current Engineer I description already identifies these types of transportation projects as core focus. - What You'll Do: perform and coordinate highway and roadway design activities from concept through final design and construction documentation. Independently complete engineering assignments, develop design solutions, coordinate with project teams and agencies, support project schedules, budgets, quality requirements. Provide technical guidance to junior engineers and designers while continuing to develop project management and client-facing responsibilities. - Key Responsibilities (list): - Perform and coordinate the design of roadway, highway, interchange, intersection, ADA, and other transportation improvement projects. - Develop roadway alignments, geometric layouts, maintenance of traffic plans, grading, drainage considerations, and transportation safety improvements. - Prepare and review construction plans, specifications, cost estimates, engineering calculations, technical reports, and supporting project documentation. - Utilize OpenRoads Designer (ORD), MicroStation, Civil 3D, and other engineering software to develop and review design models and construction documents. - Analyze engineering alternatives and independently develop practical design recommendations consistent with applicable standards and project requirements. - Coordinate with project managers, clients, agencies, engineers, and multidisciplinary teams throughout project development. - Support project schedules, budgets, quality control, and technical delivery while identifying and communicating potential project issues. - Participate in field investigations, site visits, agency meetings, and client coordination activities. - Provide technical guidance and support to junior engineers and designers and assist with reviewing their work. - Support project managers with scopes of work, level-of-effort estimates, proposals, and other project-delivery activities as needed. - What You'll Bring (requirements): - Bachelor’s degree in Civil Engineering from an ABET-accredited engineering program. - Minimum 6 years of experience in highway, roadway, or transportation engineering. - Engineer-in-Training (EIT) certification required; Professional Engineer (P.E.) license preferred or ability to obtain. - Demonstrated experience designing roadway and transportation infrastructure projects for state and/or local transportation agencies. - Proficiency with OpenRoads Designer (ORD), MicroStation, Civil 3D, or similar roadway design software. - Working knowledge of AASHTO, INDOT, MUTCD, ADA, and other applicable transportation design standards and guidelines. - Strong engineering judgment with the ability to independently analyze alternatives and develop practical design solutions. - Strong communication, organization, and technical writing skills with the ability to coordinate across multidisciplinary project teams. - Ability to manage multiple assignments, priorities, and deadlines while maintaining quality and attention to detail. - Experience providing technical guidance or mentoring junior engineers and designers preferred. - Why PRIME AE (benefits/culture): - We don’t just fill positions; we invest in people. - At PRIME AE, you’ll find a supportive, flexible environment where careers are built intentionally, not accidentally. - You’ll work on projects that improve everyday life, alongside colleagues who challenge and respect one another. - What sets us apart: - Career Growth: Flexible career paths across disciplines, from technical expertise to project and people leadership. - People-First Culture: We value trust, integrity, and collaboration, and we mean it. - Meaningful Work: Projects that strengthen communities, infrastructure, and public spaces. - Growth with Purpose: Strategic expansion backed by strong leadership and investment. - National Reach, Local Feel: Big-firm resources with the agility and relationships of local offices. - Our Commitment: PRIME AE Group is committed to creating an inclusive environment where differences are respected, voices are heard, and everyone has the opportunity to succeed. - Hybrid (maybe indicates hybrid work arrangement). We need to output HTML fragment. We must not include any boilerplate like cookie/navigation/legal/EEO etc. There's none. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must not create Pay or Schedule sections because not present. We must not create sections with filler like "commensurate with experience". Not present. We need to decide which headings to use. Potential sections: - About the role: could include company overview + opportunity description? Might be too much but okay. - Responsibilities: list of key responsibilities. - Requirements: What You'll Bring (mandatory). Could also include degree, experience, EIT, etc. - Qualifications: maybe include preferred items (PE license, mentoring experience). But we could also put those under Requirements as they are part of What You'll Bring (some required, some preferred). The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one section? But we have allowed headings; we could use Requirements for mandatory and Qualifications for preferred. However that creates two thin sections. Might be okay if they have substantive content. But we could also treat "What You'll Bring:" as Requirements, and then have a separate Qualifications for "Professional Engineer (P.E.) license preferred or ability to obtain" and "Experience providing technical guidance or mentoring junior engineers and designers preferred." However those are already in What You'll Bring list; splitting might duplicate. Better to have: - About the role (company + opportunity) - Responsibilities (list) - Requirements (education, experience, certifications, software, standards, skills) - Benefits (Why PRIME AE, culture, hybrid) We could omit Qualifications and Skills separate headings to avoid thin sections. But we have allowed Skills heading; we could put software and standards under Skills. However that would split responsibilities vs skills. Let's think: The posting includes many skill-like items: proficiency with software, working knowledge of standards, strong engineering judgment, communication, organization, technical writing, ability to manage multiple assignments, experience providing technical guidance. Those could go under Skills. Requirements could be education, years experience, EIT certification, demonstrated experience designing for state/local agencies. Qualifications could be PE license preferred, mentoring experience preferred. But we have to avoid too many thin sections. However each of these would have decent content. Given the instruction: "Prefer a few substantive sections over many thin ones." So maybe we should combine into three sections: About the role, Responsibilities, Requirements (including qualifications and skills). Benefits as fourth. Thus we have four sections: About the role, Responsibilities, Requirements, Benefits. We need to ensure we don't omit any substantive info. Let's craft each. **About the role**: Should include company description and the opportunity details (location, role summary). We'll keep it as prose (

  ) maybe with a

  for bullet points? The opportunity description includes bullet-like sentences but we can keep as

  sentences. We need to preserve all details: mention of PRIME AE Group, Inc., website, nationally ranked, full-service A/E firm, collaboration, innovation, commitment to strengthening communities, offices across country, >550 professionals, partner with public/private sector clients, deliver solutions across transportation, education, healthcare, municipal, federal, commercial, recreational markets, culture blends entrepreneurial energy with resources