Senior Roadway Engineer / Project Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role, Responsibilities, Requirements, Benefits, Schedule. Possibly also Skills? But we can combine qualifications into Requirements.
We must not repeat job title as heading. Do not put Job ID etc.
We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, scam warning, duplicated lines, application instructions. Also remove duplicated lines like "Discover more about our team, values, and projects by visiting www.ice-eng.com." appears twice; we should keep only once? The rule: remove duplicated lines. So we keep one instance.
Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove the EEO statement and contact info? That is EEO boilerplate; we should remove. Also remove the hashtags at end.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
Job posting text:
"Senior Roadway Engineer / Project Manager Ocala, Florida Infrastructure Consulting & Engineering, LLC (ICE) is seeking an experienced Senior Roadway Engineer / Project Manager to join our Tampa, Florida office. This position will play a key role in designing and delivering roadway and transportation projects for the Florida Department of Transportation (FDOT), local governments, and other public-sector clients throughout Florida. The successful candidate will have a strong roadway design background, demonstrated FDOT experience, and the ability to lead projects from concept development through final Plans, Specifications, and Estimates (PS&E). This individual will manage and coordinate roadway design assignments, oversee project schedules and budgets, provide technical leadership to design staff, maintain strong client relationships, and help support the continued growth of ICE's transportation practice in Florida."
That's About the role.
Then "Qualifications / Requirements Minimum required qualifications include: ..."
We need to list requirements as - .
We have Minimum required qualifications:
- Bachelor's degree in Civil Engineering from an accredited college or university.
- Licensed Professional Engineer (PE) in the State of Florida required.
- Must have a minimum of 10 years of progressive roadway/highway design experience, including preparation and delivery of PS&E packages.
- Demonstrated FDOT roadway design experience, including familiarity with FDOT design standards, procedures, criteria, specifications, and plans preparation requirements.
- Experience with roadway geometric design, horizontal and vertical alignments, intersections, signing and pavement markings, maintenance of traffic coordination, drainage coordination, utilities, and other disciplines associated with roadway design.
- Proficiency in AutoCAD Civil 3D and OpenRoads Designer, along with familiarity with current FDOT CADD standards and workflows.
- Experience reviewing engineering calculations, plans, specifications, quantities, estimates, and technical documents for accuracy, constructability, and compliance with applicable standards.
- Strong written and verbal communication skills and the ability to effectively lead and work within multidisciplinary project teams.
Preferred qualifications include:
- Experience managing FDOT roadway projects.
- Experience delivering projects for counties, municipalities, and other transportation agencies.
- Demonstrated project management experience involving scopes, fees, schedules, budgets, staffing, subconsultants, and client coordination.
- Experience with alternative delivery methods, including Design-Build, where applicable.
- Knowledge of FDOT project development, permitting, utility coordination, right-of-way, drainage, traffic, and related transportation disciplines.
- Established relationships with FDOT and/or local government transportation professionals.
- Experience preparing scopes of work, fee proposals, letters of interest, and other materials supporting transportation project pursuits.
We could combine both minimum and preferred into a single list? Might be better to separate? The instruction: Use
- for any list of duties/requirements/benefits. Could have separate sections for Requirements (minimum) and Preferred Qualifications? But we only have headings: Requirements, Qualifications, Skills. Could put all under Requirements. Or we could have Requirements (minimum) and then maybe a Skills section for preferred? But better to keep one Requirements section with both minimum and preferred, maybe differentiate with text. However we must preserve all substantive information; we can include both as list items, maybe with a note "Preferred:" inside li. That's okay.
Next: Key Responsibilities list.
Responsibilities:
- Serve as Project Manager and/or Roadway Design Lead for local agency transportation projects and FDOT.
- Manage and oversee roadway design projects from initial concept through final PS&E delivery.
- Lead the development of roadway plans, specifications, quantities, cost estimates, technical reports, and supporting design documentation.
- Manage concurrent projects and assignments while maintaining project schedule, budget, quality, and client expectations.
- Coordinate roadway design with drainage, structures, traffic, utilities, environmental, survey, geotechnical, right-of-way, and other project disciplines.
- Apply FDOT or local government design criteria, manuals, standards, specifications, and CADD requirements to project development and design.
- Review contract drawings, calculations, specifications, and estimates to confirm design accuracy, constructability, consistency, and compliance with ICE's Quality Management procedures.
- Develop project scopes, work plans, schedules, staffing plans, and fee estimates.
- Monitor project financial performance, budgets, schedules, invoicing, and progress toward established milestones.
- Coordinate and manage subconsultants as necessary to meet project requirements.
- Ensure projects are appropriately staffed and provide direction to other team engineers, designers, and technical staff.
- Mentor and support the professional development of junior engineers and roadway design staff.
- Maintain effective communication and strong working relationships with clients, agency staff, subconsultants, contractors, and project stakeholders.
- Participate in client meetings, project presentations, design reviews, and field visits as required.
- Assist with identification and pursuit of transportation opportunities, including preparation of scopes, fee proposals, technical approaches, and qualifications packages.
- Support ICE's continued growth with FDOT and local government clients throughout Florida.
Leadership Expectations: As a senior member of the Tampa transportation team, this position will be expected to:
- Provide technical leadership and guidance to roadway engineering and design staff.
- Promote consistent application of ICE and FDOT design and quality standards.
- Assist with workload planning and allocation of project resources.
- Identify staffing needs and participate in recruitment and development of roadway personnel.
- Foster a collaborative, professional, and team-oriented work environment.
- Support coordination and sharing of technical resources among ICE offices as appropriate.
These could be part of Responsibilities or separate section? Could include under Responsibilities as well. We'll include them in Responsibilities list.
Physical Demands: This position predominantly involves work at a computer workstation, with occasional standing and walking. The employee may occasionally lift lightweight office supplies and materials, typically not exceeding 20 pounds. Periodic field visits may be required. During field activities, the employee may encounter construction environments involving traffic, noise, dust, uneven terrain, changing temperatures, and other typical roadway and construction-site conditions.
Expected Hours of Work: ICE offices are generally open from 8:00 a.m. to 5:00 p.m., Monday through Friday, with an unpaid lunch hour. Work schedules may vary based on project requirements, client needs, and project deadlines. Occasional evening, nighttime, or weekend work may be required for field activities, meetings, or project delivery.
Compensation: Salary and overall compensation will be commensurate with the selected candidate's education, professional experience, technical expertise, project management background, certifications, and other qualifications. ICE strives to provide competitive compensation reflective of the candidate's experience and contributions to the organization. ICE will discuss specific compensation details during the interview and selection process.
About ICE: paragraph.
Then benefits list: "Here’s what you can expect at ICE: · Amongst the industry’s best pay and benefits. · Professional development and clear paths for career growth. · A collaborative, supportive team of skilled professionals. · Opportunities to work on impactful infrastructure/Aviation projects that shape and connect communities. · Ability to play a vital role in shaping the future of this organization."
We need to output Benefits section with those bullet points.
We should not include the duplicated line "Discover more about our team, values, and projects by visiting www.ice-eng.com." twice; keep once.
We should remove EEO boilerplate and hashtags.
Now construct HTML.
We'll start with
About the role
then with the paragraph(s). Could combine two paragraphs? The first paragraph is long; we can keep as one
.
Then
Responsibilities
then - ... each responsibility.
Then
Requirements
then - ... each requirement (including preferred). Could separate minimum and preferred with a note but still list.
Then
Benefits
then - ... each benefit.
Then
Schedule
then with schedule info.
We might also include a short
for About ICE? Could be part of About the role? But we have About ICE description separate; maybe we can include under About the role as additional paragraph. The instruction: About the role section heading; we can put both the initial description and About ICE description there. But we should not repeat job title. It's fine.
Let's craft.
About the role paragraph: combine the initial description and About ICE description? Might be too long but okay.
Better: About the role: first paragraph describing role. Then maybe a second paragraph about ICE. We'll just put both as separate
under same heading? The rule: Use
for prose. We can have multiple
under heading.
Thus:
About the role
Senior Roadway Engineer / Project Manager Ocala, Florida Infrastructure Consulting & Engineering, LLC (ICE) is seeking an experienced Senior Roadway Engineer / Project Manager to join our Tampa, Florida office. This position will play a key role in designing and delivering roadway and transportation projects for the Florida Department of Transportation (FDOT), local governments, and other
- for any list of duties/requirements/benefits. Could have separate sections for Requirements (minimum) and Preferred Qualifications? But we only have headings: Requirements, Qualifications, Skills. Could put all under Requirements. Or we could have Requirements (minimum) and then maybe a Skills section for preferred? But better to keep one Requirements section with both minimum and preferred, maybe differentiate with text. However we must preserve all substantive information; we can include both as list items, maybe with a note "Preferred:" inside li. That's okay.
Next: Key Responsibilities list.
Responsibilities:
- Serve as Project Manager and/or Roadway Design Lead for local agency transportation projects and FDOT.
- Manage and oversee roadway design projects from initial concept through final PS&E delivery.
- Lead the development of roadway plans, specifications, quantities, cost estimates, technical reports, and supporting design documentation.
- Manage concurrent projects and assignments while maintaining project schedule, budget, quality, and client expectations.
- Coordinate roadway design with drainage, structures, traffic, utilities, environmental, survey, geotechnical, right-of-way, and other project disciplines.
- Apply FDOT or local government design criteria, manuals, standards, specifications, and CADD requirements to project development and design.
- Review contract drawings, calculations, specifications, and estimates to confirm design accuracy, constructability, consistency, and compliance with ICE's Quality Management procedures.
- Develop project scopes, work plans, schedules, staffing plans, and fee estimates.
- Monitor project financial performance, budgets, schedules, invoicing, and progress toward established milestones.
- Coordinate and manage subconsultants as necessary to meet project requirements.
- Ensure projects are appropriately staffed and provide direction to other team engineers, designers, and technical staff.
- Mentor and support the professional development of junior engineers and roadway design staff.
- Maintain effective communication and strong working relationships with clients, agency staff, subconsultants, contractors, and project stakeholders.
- Participate in client meetings, project presentations, design reviews, and field visits as required.
- Assist with identification and pursuit of transportation opportunities, including preparation of scopes, fee proposals, technical approaches, and qualifications packages.
- Support ICE's continued growth with FDOT and local government clients throughout Florida.
Leadership Expectations: As a senior member of the Tampa transportation team, this position will be expected to:
- Provide technical leadership and guidance to roadway engineering and design staff.
- Promote consistent application of ICE and FDOT design and quality standards.
- Assist with workload planning and allocation of project resources.
- Identify staffing needs and participate in recruitment and development of roadway personnel.
- Foster a collaborative, professional, and team-oriented work environment.
- Support coordination and sharing of technical resources among ICE offices as appropriate.
These could be part of Responsibilities or separate section? Could include under Responsibilities as well. We'll include them in Responsibilities list.
Physical Demands: This position predominantly involves work at a computer workstation, with occasional standing and walking. The employee may occasionally lift lightweight office supplies and materials, typically not exceeding 20 pounds. Periodic field visits may be required. During field activities, the employee may encounter construction environments involving traffic, noise, dust, uneven terrain, changing temperatures, and other typical roadway and construction-site conditions.
Expected Hours of Work: ICE offices are generally open from 8:00 a.m. to 5:00 p.m., Monday through Friday, with an unpaid lunch hour. Work schedules may vary based on project requirements, client needs, and project deadlines. Occasional evening, nighttime, or weekend work may be required for field activities, meetings, or project delivery.
Compensation: Salary and overall compensation will be commensurate with the selected candidate's education, professional experience, technical expertise, project management background, certifications, and other qualifications. ICE strives to provide competitive compensation reflective of the candidate's experience and contributions to the organization. ICE will discuss specific compensation details during the interview and selection process.
About ICE: paragraph.
Then benefits list: "Here’s what you can expect at ICE: · Amongst the industry’s best pay and benefits. · Professional development and clear paths for career growth. · A collaborative, supportive team of skilled professionals. · Opportunities to work on impactful infrastructure/Aviation projects that shape and connect communities. · Ability to play a vital role in shaping the future of this organization."
We need to output Benefits section with those bullet points.
We should not include the duplicated line "Discover more about our team, values, and projects by visiting www.ice-eng.com." twice; keep once.
We should remove EEO boilerplate and hashtags.
Now construct HTML.
We'll start with
About the role
thenwith the paragraph(s). Could combine two paragraphs? The first paragraph is long; we can keep as one
. Then
Responsibilities
then- ... each responsibility.
Then
Requirements
then- ... each requirement (including preferred). Could separate minimum and preferred with a note but still list.
Then
Benefits
then- ... each benefit.
Then
Schedule
thenwith schedule info. We might also include a short
for About ICE? Could be part of About the role? But we have About ICE description separate; maybe we can include under About the role as additional paragraph. The instruction: About the role section heading; we can put both the initial description and About ICE description there. But we should not repeat job title. It's fine. Let's craft. About the role paragraph: combine the initial description and About ICE description? Might be too long but okay. Better: About the role: first paragraph describing role. Then maybe a second paragraph about ICE. We'll just put both as separate
under same heading? The rule: Use
for prose. We can have multiple
under heading. Thus:
About the role
Senior Roadway Engineer / Project Manager Ocala, Florida Infrastructure Consulting & Engineering, LLC (ICE) is seeking an experienced Senior Roadway Engineer / Project Manager to join our Tampa, Florida office. This position will play a key role in designing and delivering roadway and transportation projects for the Florida Department of Transportation (FDOT), local governments, and other
- ... each benefit.
Then
- ... each requirement (including preferred). Could separate minimum and preferred with a note but still list.
Then
- ... each responsibility.
Then