Graduate Engineer | Engineer-in-Training | Professional Engineer

We need to output HTML fragment with sections: Pay, Schedule, Benefits, About the role? Actually we need headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for section headings. Only include sections where posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to extract relevant info: Pay Range (given). Workdays & Hours (Schedule). Benefits list. About the role: description of role, department, etc. Responsibilities: list of duties. Requirements/Qualifications: Minimum Qualifications and Preferred Qualifications. Skills: maybe from preferred qualifications? Could combine. But we need to follow instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content. Likely we have content for About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (maybe preferred?), Skills (maybe from preferred qualifications like communication, AutoCAD, etc.), Benefits, Pay, Schedule. We must not create sections with filler like "commensurate with experience". We have actual content. We need to ensure we don't duplicate. For Requirements and Qualifications maybe we separate: Requirements = Minimum Qualifications; Qualifications = Preferred Qualifications. Skills could be extracted from preferred qualifications (communication, AutoCAD, etc.) but that overlaps with Qualifications. Might be okay to have Skills separate listing specific skills. We must not invent. So we need to extract exactly what's there. Let's parse posting: Pay Range: Graduate Engineer: $59,984 – $77,979 | Engineer-in-Training: $65,563 – $85,232 | Professional Engineer: $78,326 – $ 101,824 annual compensation Job Posting Closing on: Friday, October 9, 2026 📅 Workdays & Hours: Monday – Friday 8am – 5pm; Some evening/weekend work required. After just six months, enjoy the freedom of 2 days remote work each week or hybrid schedule! Subject to business needs (with department approval) Benefits for this position include: 11 Paid Holidays, Medical, Dental, Vision, Paid Time Off, Pension Plan, Professional Development Opportunities. Find Out More! The City of Fort Worth is one of the fastest growing large cities in the U.S. Our employees serve the needs of over 1,000,000 residents, promoting our values of exceptional customer experience, mutual respect, embracing our diversity, continuous improvement, ethical behavior, and accountability. 🌆 The City of Fort Worth’s Development Services Department is seeking a Graduate Engineer, Engineer‑in‑Training, or Professional Engineer for an open position within the Small‑Scale Infrastructure Program (SSIP), offering practical exposure to how real‑world infrastructure is planned, evaluated, and constructed. This role provides hands‑on experience with civil infrastructure projects including reviewing plans, designs, and technical documents, coordinating project intake, developing cost estimates, and supporting the engineering work behind the City’s Small‑Scale Infrastructure and infill development initiative. Minimum Qualifications Graduate Engineer Bachelor’s degree in civil engineering or other engineering discipline from an accredited college or universityNo experienceValid driver's license Engineer In Training Bachelor’s degree in civil engineering or other engineering discipline from an accredited college or universityNo experienceThe possession of registration as an Engineering-In-Training in the State of Texas; or, if licensed in another state, continued employment will be contingent upon obtaining registration as an Engineering-In-Training within the State of Texas within six (6) months of employmentValid driver's license Professional Engineer Bachelor’s degree in engineering from an accredited college or university with major course work in mathematical, physical, or engineering scienceFour (4) years of increasingly responsible civil engineering experience, including two (2) years in the assigned area of responsibilityPossession of registration as a Professional Engineer in the State of Texas. If licensed in another state, continued employment will be contingent upon obtaining registration as a Professional Engineer within the State of Texas within six (6) months of employmentValid driver's license Preferred Qualifications Ability to communicate clearly and effectively, both orally and in writingDesign experience with AutoCAD or willingness to learnExperience with principles and practices of civil engineering in streets, lighting, water, wastewater and utility systemsProject Management experienceCost estimating experienceExperience with Accela or other similar project management softwareMunicipal Government experience Job Responsibilities Include Review application materials for public infrastructure projects to ensure the requested infrastructure is within program limitations, examine as‑builts, GIS, City design criteria, and conduct field visits to identify potential design constraints or challenges Communicate clearly and respectfully with applicants by email or phone throughout the process, and, when available, meet with prospective applicants or respond to general inquiries Collaborate with consultants and contractors to develop accurate design and construction fees, prepare cost estimates based on project needs and challenges, and present proposed fees to applicants Oversee and coordinate the full project lifecycle for public infrastructure within private developments, managing cross-functional resources and timelines from initial design through final construction Support construction from start to finish by coordinating preconstruction meetings, reviewing submittals, scheduling and monitoring inspections, resolving field issues, managing schedules and change orders, overseeing closeout tasks, and handling administrative duties like invoice approvals and general inquiries Working Conditions and Physical Demands Depending on assignment, positions in this class typically require touching, talking, hearing, seeing, grasping, standing, stooping, kneeling, crouching, reaching, walking, repetitive motions, climbing and balancing. Light Work – Depending on assignment, positions in this class typically exert up to 20 pounds of force occasionally, up to 10 pounds of force frequently, and/or a negligible amount of force constantly having to move objects. If the use of arm and/or leg controls requires exertion of forces greater than that for the Sedentary Work category and the worker sits most of the time, the job is rated Light Work. Apply Now! Come be part of something special in Fort Worth. 🌟 Conditions of Employment ... (EEO boilerplate etc.) We need to remove EEO boilerplate, legal, etc. Also remove "Apply Now!" etc. Also remove "Conditions of Employment" etc. Also remove "Working Conditions and Physical Demands"? That might be considered substantive? It's about physical demands; maybe we could include under Responsibilities? But not required headings. The instruction says include sections only when posting has real specific content for it. We could include a section "Working Conditions" but not in the list of allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add extra headings like Working Conditions. We could incorporate that info into Responsibilities or About the role? Probably better to omit it because it's not requested heading. However we must preserve ALL substantive information; we cannot discard substantive info. But we can embed it within existing sections if appropriate. The physical demands info is substantive; we could put it under Responsibilities? Not exactly. Could put under About the role as additional detail. Or we could create a section "Working Conditions" but that's not in allowed headings; instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could still use other headings if needed, but better to stick to those. However we need to preserve all substantive info; we could embed physical demands in About the role or Responsibilities. Probably About the role can include description of role and working conditions. Thus we will produce sections:

About the role

with paragraph(s) containing description: The City of Fort Worth..., role provides hands-on experience..., also mention Working Conditions and Physical Demands (maybe as a sentence). Ensure we keep all details.

Responsibilities

with

• list of responsibilities.

  Requirements

  with Minimum Qualifications. Could be a
  • for each qualification category? Might need to list each: Graduate Engineer, Engineer In Training, Professional Engineer. Could present as list.

    Qualifications

    with Preferred Qualifications list.

    Skills

    maybe list specific skills from preferred qualifications: Ability to communicate clearly and effectively, both orally and in writing; Design experience with AutoCAD or willingness to learn; Experience with principles and practices of civil engineering in streets, lighting, water, wastewater and utility systems; Project Management experience; Cost estimating experience; Experience with Accela or other similar project management software; Municipal Government experience. That's essentially same as Qualifications; but we could treat Qualifications as preferred qualifications and Skills as specific abilities. Might be redundant but okay. Alternatively we could combine Qualifications and Skills; but instruction says prefer few substantive sections over many thin ones. So maybe we should not have both Qualifications and Skills if they overlap. Better to have Qualifications (preferred) and maybe Skills not needed. But we need to include Skills section only if posting has real specific content for it. The posting does list specific skills/experience; we could treat those as Skills. Then Qualifications could be the minimum qualifications? Actually we already have Requirements for minimum qualifications. So we could have Qualifications for preferred qualifications, and Skills maybe not needed. But we could still include Skills as subset of preferred qualifications; but that would be thin. Better to omit Skills section and just have Requirements (minimum) and Qualifications (preferred). However the instruction list includes Skills as possible heading; we can omit if not needed. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check if we have content for each: - About the role: yes. - Responsibilities: yes. - Requirements: yes (minimum qualifications). - Qualifications: yes (preferred qualifications). - Benefits: yes. - Pay: yes. - Schedule: yes (Workdays & Hours). We must not include fluff like "Find Out More!" etc. Now craft HTML. We need to use

    for each section heading. Use

    for prose. Use

    • for lists. We need to preserve all substantive info: ensure we include all details from each section. Let's extract About the role content: "The City of Fort Worth is one of the fastest growing large cities in the U.S. Our employees serve the needs of over 1,000,000 residents, promoting our values of exceptional customer experience, mutual respect, embracing our diversity, continuous improvement, ethical behavior, and accountability. 🌆 The City of Fort Worth’s Development Services Department is seeking a Graduate Engineer, Engineer‑in‑Training, or Professional Engineer for an open position within the Small‑Scale Infrastructure Program (SSIP), offering practical exposure to how real‑world infrastructure is planned, evaluated, and constructed. This role provides hands‑on experience with civil infrastructure projects including reviewing plans, designs, and technical documents, coordinating project intake, developing cost estimates, and supporting the engineering work behind the City’s Small‑Scale Infrastructure and infill development initiative." Also we could add Working Conditions and Physical Demands: "Depending on assignment, positions in this class typically require touching, talking, hearing, seeing, grasping, standing, stooping, kneeling, crouching, reaching, walking, repetitive motions, climbing and balancing. Light Work – Depending on assignment, positions in this class typically exert up to 20 pounds of force occasionally, up to 10 pounds of force frequently, and/or a negligible amount of force constantly having to move objects. If the use of arm and/or leg controls requires exertion of forces greater than that for the Sedentary Work category and the worker sits most of the time