Roadway Project Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No metadata like Job ID. Remove boilerplate etc. We need to parse the posting. Content: - Intro: "We are seeking a Project Engineer to join our Roadway Design team in St. Louis, MO. This is an excellent opportunity for an experienced roadway engineer who is looking to take on greater technical and project responsibilities while contributing to meaningful transportation projects as part of a 100% employee-owned company." - Then description about Lochmueller, values, etc. - "Why Engineers Choose Lochmueller" bullet list. - "In this position, you will:" list of duties. - "What We're Looking For:" list of requirements. - "What We Offer:" list of benefits. - Then "Build Your Career With Lochmueller" more prose. - Then EEO etc (remove). We need sections: About the role (maybe intro + description), Responsibilities (duties list), Requirements (maybe education/experience), Qualifications (maybe PE license etc), Skills (maybe Civil 3D etc), Benefits (What We Offer), Pay (if any), Schedule (if any). The posting does not mention specific pay or schedule details. It mentions flexible scheduling, hybrid/telecommuting opportunities under Work-Life Balance. That could be considered schedule info? It says "flexible scheduling, and hybrid/telecommuting opportunities". That is schedule-related. So we could include a Schedule section with that detail. Pay: not mentioned specific salary, only "competitive compensation". That's vague; we should not include Pay section if only vague like "competitive compensation" (not specific). The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits we have specific list: health & wellness, work-life balance, financial well-being, professional growth. So Benefits section is okay. For Schedule we have "flexible scheduling, and hybrid/telecommuting opportunities". That's specific enough? It's a statement about schedule flexibility. I'd include Schedule section with that. For Pay we have "competitive compensation" which is vague; better to omit Pay section. Now we need to decide what goes into each section. About the role: Could combine introductory paragraph and company description, values, why engineers choose Lochmueller, build your career etc. But we need to avoid duplication. We'll include a concise prose about the role and company. Responsibilities: list from "In this position, you will:" bullet points. Requirements: maybe education and experience: Bachelor's degree in Civil Engineering or related field, 5+ years roadway/highway design experience. Qualifications: PE license preferred, ability to obtain MO licensure via comity, experience with Civil 3D/OpenRoads Designer, experience preparing roadway plans, specs, estimates, technical reports. Skills: strong communication, organization, project coordination skills, commitment to quality, client service, technical excellence. Benefits: list from "What We Offer:" with subcategories. Schedule: flexible scheduling, hybrid/telecommuting opportunities. We must not repeat job title as heading. Use

for each section. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep specifics like "Medical, dental, vision, disability, and basic life insurance, plus options for supplemental voluntary life insurance", "Paid vacation, holidays, sick leave, parental leave, flexible scheduling, and hybrid/telecommuting opportunities", "Employee Stock Ownership Plan (ESOP), competitive compensation, 401(k) with company match, and student loan repayment assistance", "Professional membership dues, continuing education, licensure support, training opportunities, and career development resources". Also mention "100% employee-owned company", "CARDIA values", etc. We need to avoid boilerplate like EEO, AI statement, etc. Now craft HTML. Structure:

  About the role

  We are seeking a Project Engineer to join our Roadway Design team in St. Louis, MO. This is an excellent opportunity for an experienced roadway engineer looking to take on greater technical and project responsibilities while contributing to meaningful transportation projects as part of a 100% employee-owned company. At Lochmueller Group, you will work alongside a talented team of transportation professionals on a variety of roadway and transportation projects serving local municipalities, counties, and state agencies. You'll apply your technical expertise, collaborate directly with clients and stakeholders, and play a key role in delivering transportation improvements that positively impact the communities we serve. Lochmueller has over 40 years of helping communities reinvent their future through thoughtful planning and design, guided by the CARDIA values: Creativity, Accountability, Respect, Dedication, Integrity, and Achievement. As a 100% employee-owned firm, our people are invested in each other's success and the long-term success of the company, fostering a collaborative environment that supports professional growth, innovation, and meaningful impact.

  That seems to capture intro, values, employee ownership. Now Responsibilities:

  Responsibilities

  • Lead and support the planning, design, and delivery of roadway and transportation projects
  • Prepare engineering analyses, design calculations, plans, specifications, and estimates
  • Apply roadway design standards, criteria, and engineering best practices
  • Develop and review roadway designs utilizing Civil 3D and/or OpenRoads Designer
  • Coordinate with multidisciplinary teams to deliver high-quality solutions that meet client objectives
  • Assist with project scopes, budgets, schedules, and proposal development
  • Prepare and review technical reports, specifications, and project documentation
  • Collaborate with clients, contractors, and regulatory agencies throughout project delivery
  • Provide technical guidance and support to early-career engineers and design staff
  Requirements:

  Requirements

  • Bachelor's degree in Civil Engineering or a related field
  • 5+ years of roadway and/or highway design experience
  Qualifications:

  Qualifications

  • Professional Engineer (PE) license preferred
  • Candidates able to obtain Missouri licensure through comity also considered
  • Experience with Civil 3D and/or OpenRoads Designer
  • Experience preparing roadway plans, specifications, estimates, and technical reports
  Skills:

  Skills

  • Strong communication, organization, and project coordination skills
  • Commitment to quality, client service, and technical excellence
  Benefits:

  Benefits

  • Health & Wellness: Medical, dental, vision, disability, and basic life insurance, plus options for supplemental voluntary life insurance
  • Work-Life Balance: Paid vacation, holidays, sick leave, parental leave, flexible scheduling, and hybrid/telecommuting opportunities
  • Financial Well-Being: Employee Stock Ownership Plan (ESOP), competitive compensation, 401(k) with company match, and student loan repayment assistance
  • Professional Growth: Professional membership dues, continuing education, licensure support, training opportunities, and career development resources
  Schedule: We have flexible scheduling and hybrid/telecommuting opportunities already mentioned under Benefits Work-Life Balance. But we could still have a Schedule section highlighting those. However to avoid duplication, maybe we should not duplicate. The rule: do not repeat content? It didn't explicitly forbid duplication but we should preserve all substantive information; duplication is okay but maybe better to avoid. However the Schedule section could be separate to highlight schedule specifics. But the info is already in Benefits. If we create Schedule section we would be repeating. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we should not create a separate Schedule section if the info is already covered under Benefits. However the rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not forbid creating a Schedule section if the posting states schedule info. It does state flexible scheduling and hybrid/telecommuting opportunities. So we could create a Schedule section with that info, but then we would have duplicate info if also in Benefits. To avoid duplication, we could move the schedule info to Schedule section and remove from Benefits Work-Life Balance item. But then we would lose some info from Benefits (paid vacation etc). We could keep Benefits without schedule items, and Schedule section with flexible scheduling and hybrid/telecommuting. That seems reasonable and avoids duplication. Thus adjust Benefits: remove flexible scheduling and hybrid/telecommuting from Work-Life Balance item. Benefits:
  • Health & Wellness: Medical, dental, vision, disability, and basic life insurance, plus options for supplemental voluntary life insurance
  • Work-Life Balance: Paid vacation, holidays, sick leave, parental leave
  • Financial Well-Being: Employee Stock Ownership Plan (ESOP), competitive compensation, 401(k) with company match, and student loan repayment assistance
  • Professional Growth: Professional membership dues, continuing education, licensure support, training opportunities, and career development resources
  Schedule:

  Schedule

  • Flexible scheduling
  • Hybrid/telecommuting opportunities
  Now ensure we didn't miss any substantive info: The "Why Engineers Choose Lochmueller" bullet list: meaningful transportation projects, exposure to variety, expand technical expertise, collaborate with experienced professionals, shape career path, continue building skills, share in success through ESOP, be part of collaborative culture built on CARDIA values. Some of that is covered in About the role and Benefits (ESOP). Could incorporate some of those points in About the role to preserve. The "Why Engineers Choose..." list is substantive; we should not lose it. We could incorporate those points into About the role paragraph or as a separate section like "Why Join Lochmueller". But we only have allowed headings list; we could add a section like "Why Join Lochmueller" but not in allowed headings list? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could also use other headings if needed, but better to stick to those. However we could incorporate the "Why Engineers Choose..." content into About the role or Benefits. Let's see: The points: meaningful transportation projects (already in About), exposure to variety (maybe in About), expand technical expertise (maybe in About or Skills), collaborate with experienced professionals (maybe in About), shape career path (maybe in About), continue building skills (maybe in About), share in success through ESOP (Benefits), be part of collaborative culture built on CARDIA values (About). So we can absorb them. Thus About the role paragraph can be expanded to include those points. Let's craft About the role paragraph to include: meaningful transportation projects, exposure to variety of roadway and transportation projects, expand technical expertise, collaborate with experienced professionals invested in your success, shape career path aligned with interests (project delivery, technical leadership, or both), continue building skills and experience needed to advance career, share in success through employee ownership (ESOP), be part of collaborative culture built on creativity, accountability, respect, dedication, integrity, and achievement. We'll incorporate. Now final HTML. Check for