Jobs · Information Technology · Florida

Project Administrator - CEI

England-Thims & Miller, Inc. · DeLand, FL · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes description (Who we are looking for...), responsibilities, requirements, certifications, etc. Also includes "Who We Are…Trusted Advisors..." and "What We Offer…" which could be about benefits etc. There's no explicit Pay or Schedule details. So we should not create Pay or Schedule sections. Benefits: there is "What We Offer… We recognize and reward hard work, we offer a competitive salary, full benefits package, and a potential performance-based bonus." That's benefits info. So we can have a Benefits section with that content. Qualifications: The posting includes Requirements (license, diploma, experience, etc.) and also certifications (required and desired). Could treat Requirements as Qualifications? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which headings to use based on content. There's a "Description Who we are looking for..." which could be About the role. Then Responsibilities section. Then Requirements (or Qualifications). There's also a list of certifications which could be under Qualifications or Skills. There's also "Who We Are…" which is about company culture; maybe not needed as a section. "What We Offer…" is benefits. We must not repeat job title as heading. No Job ID etc. We must preserve all substantive information, not invent or summarize away detail. Must not create sections with filler like "commensurate with experience". So we need to include actual content. We need to use
  • for any list of duties/requirements/benefits. Use

    for prose. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement and "This job description is representative..." etc. Those are boilerplate; we should remove them. Also the "What To Do Next…" is application instructions; remove. Also the link to culture maybe not needed? It's part of Who We Are… but could be considered boilerplate? It's a URL; maybe keep as part of About the role? But it's not a duty. Might be considered part of company description; we could keep as prose under About the role. However the instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The URL is not those; it's part of company culture; we can keep. We need to preserve all substantive information: responsibilities list, requirements list, certifications list, benefits statement, who we are description. Let's extract: About the role (description): "We are seeking a Project Administrator (PA) responsible for Construction and Inspection (CEI) services on assigned projects while ensuring compliance with contract documents. The PA independently evaluates project challenges, develops solution-focused approaches aligned with client goals, and coordinates with the Senior Project Engineer (SPE) as needed. This role requires strong judgment, initiative, and the ability to interpret plans, specifications, and contract provisions while maintaining accurate project documentation and records. The PA will coordinate with clients, contractors, utility agencies, public officials, and the public." That's prose. Responsibilities: bullet list under "Responsibilities" heading. The text includes many items each starting with a bold label? Actually the text: "Client Serve as the Owner’s representative, prioritizing public safety, quality, schedule, financial responsibility, and client satisfaction. Exercise professional judgment and decision-making with concurrence from the SPE. Proactively resolve project issues and communicate significant activities, decisions, and project updates to clients. Manage assigned staff and ensure all project activities are properly documented. Oversee change orders, supplemental agreements, work orders, and contractor payments. Maintain technical understanding of plans, specifications, shop drawings, and material requirements to ensure contract compliance. Lead project meetings with clients, contractors, utilities, agencies, and the public. Review and/or prepare progress and final estimates throughout the project lifecycle. ETM Model and promote ETM standards and procedures. Manage assigned CEI projects and foster a collaborative, high-performing team environment. Support project teams with problem-solving and risk mitigation. Provide mentorship, performance feedback, and professional development opportunities. Support recruiting efforts and identify key talent opportunities. Ensure quality control standards are met across projects. Assist with proposals, presentations, marketing efforts, and client relationship development. Stay current on industry trends, regulations, and best practices. Promote technology integration and process improvements. Maintain 100% compliance with safety requirements and PPE standards." We can treat each sentence as a list item. Requirements: "Valid and Safe Driver License Highschool Diploma or equivalent Eight (8) years of CEI or roadway or bridge construction experience, two (2) of those years involved in relevant transportation projects. Or Two (2) years of engineering experience in relevant transportation projects. A master’s degree in engineering, Engineering Technology, or Construction Management may be substituted for one (1) year of engineering experience." That's prose but could be list. Required Certifications: list: "FDOT Advanced MOT CTQP Quality Control Manager (Attend and pass the examination) CTQP Final Estimates Level II" Desired Certifications: list many. We could combine certifications under Requirements or Qualifications. Since we have headings: Requirements, Qualifications, Skills. We could put license, diploma, experience under Requirements. Certifications under Qualifications. Skills maybe not explicitly listed; we could omit Skills section if no specific skills listed besides those implied. Better to omit Skills if no real content. Benefits: "We recognize and reward hard work, we offer a competitive salary, full benefits package, and a potential performance-based bonus." Also maybe "What We Offer…" includes that. We also have "Who We Are…Trusted Advisors, Creating Community Our firm has assembled a remarkable team encompassing a wide range of experiences and backgrounds. Through collaborative efforts in a supportive environment, we consistently deliver top-notch work of exceptional quality. We prioritize the growth and fulfillment of each team member, providing ample opportunities for professional and personal development. A key factor in this is our engagement with high-caliber, 'Class-A' projects and esteemed clients. We approach our work with unwavering passion, recognizing the positive impact we have on the communities we serve. https://www.etminc.com/culture/" That could be About the company; but we already have About the role. Could we add a section "About the Company"? Not in allowed headings list but we could use About the role for role description and maybe incorporate company info there? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. So we should not add other headings like About the Company. We could incorporate company info under About the role or maybe under Benefits? Better to put under About the role as additional prose. Thus About the role section will include both the role description and company description. Now we need to output HTML fragment only. Structure:

    About the role

    ... combined prose ...

    Responsibilities

    • ...
    • ...

    Requirements

    ... maybe list? Could also use

      for each requirement line.

      but they said use
      • for any list of duties/requirements/benefits. So we should use list for requirements. Thus:

        Requirements

        • Valid and Safe Driver License
        • Highschool Diploma or equivalent
        • Eight (8) years of CEI or roadway or bridge construction experience, two (2) of those years involved in relevant transportation projects. Or Two (2) years of engineering experience in relevant transportation projects.
        • A master’s degree in engineering, Engineering Technology, or Construction Management may be substituted for one (1) year of engineering experience.

        Qualifications

        We could split into Required Certifications and Desired Certifications as sublists? Could just list all certifications under Qualifications. Thus:

        Qualifications

        • Required Certifications:
          • FDOT Advanced MOT
          • CTQP Quality Control Manager (Attend and pass the examination)
          • CTQP Final Estimates Level II
        • Desired Certifications:
          • CTQP Level II (Asphalt / earthwork / concrete)
          • CTQP – Drilled Shaft & Pile Driving
          • ICS 100, 200, 700
          • ITS: (5) FDOT General Courses
          • Managed Field Ethernet Switch Module
          • Closed Circuit Television Camera Module
          • Microwave Vehicle Detection System Module
          • Road Weather Detection System Module
          • Dynamic Message Sign Module
          • Tc3 Diamond Grinding and Grooving (TC3MN009-15-T1)
          • Curing, Sawing and Joint Sealing (TC3CN032-16-T)
          • PCC Paving Inspection (TC3CN004-15-T1)
        But nested lists may be okay. However they said use
        • for any list of duties/requirements/benefits. Not forbidding nested lists. Could be okay. Alternatively we could flatten: each certification as separate
        • . But we need to differentiate required vs desired. Could keep as separate headings inside Qualifications? But we only allowed headings list; we could add another

          inside? Not allowed. Better to keep as plain list with labels. Simplify: Provide two separate

          sections: Required Certifications and Desired Certifications? But those are not in the example headings list but could be considered under Qualifications. However 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 "e.g." implying those are examples; we could add other headings if needed. Safer to stick to those. So we will have Qualifications heading and inside we can have paragraphs describing required and desired. Thus:

          Qualifications

          Required Certifications: FDOT Advanced MOT; CTQP Quality Control Manager (Attend and pass the examination); CTQP Final Estimates Level II.

          Desired Certifications: CTQP Level II (Asphalt / earthwork / concrete); CTQP – Drilled Shaft & Pile Driving; ICS 100, 200, 700; ITS: (5) FDOT General Courses; Managed Field Ethernet Switch Module; Closed Circuit Television Camera Module; Microwave Vehicle Detection System Module; Road Weather Detection System Module; Dynamic Message Sign Module; Tc3 Diamond Grinding and Grooving (TC3MN009-15-T1); Curing, Sawing and Joint Sealing (TC3CN032-16-T); PCC Paving Inspection (TC3CN004-15-T1).

          That's prose, not list. But they said use
          • for any list of duties/requirements/benefits. Certifications are a list

Similar jobs

Project Manager

The Waldinger CorporationColumbus, OH· 1 wk ago
Project Managementapply on waldinger-careers.ttcportals.com

Project Manager

Production Resource GroupAntioch, TN· 1 wk ago
Project Managementapply on careers-prg.icims.com

Project Manager

The Waldinger CorporationWisconsin, United States· 1 wk ago
Project Managementapply on waldinger-careers.ttcportals.com

Project Manager

TrinzicBeavercreek Township, OH· 1 wk ago
Information Technologyapply on careers.trinzic.com

Project Manager

ArvatoOntario, CA· 1 wk ago
Supply Chainapply on jobs.smartrecruiters.com

Project Manager

PCL ConstructionWest Palm Beach, FL· 1 wk ago
Information Technologyapply on careers.pcl.com