Self-Perform Operations Project Manager - Concrete - copy

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. The posting includes: Position Description (lead, direct, coordinate...). That's about the role. Essential Duties & Key Responsibilities list. Qualifications list. Physical Demands and Work Environment maybe could be under Requirements? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. We have: - About the role: Position Description (Lead, direct, and coordinate management of Self-Perform Operations (SPO) projects, including overall project pursuit, staffing, proactive planning and implementation, budget, and risk management.) - Responsibilities: Essential Duties & Key Responsibilities (list of many duties). Should be a

  • . - Requirements: Could include Minimum Years Experience? The posting includes "Minimum Years Experience:" but no value? Actually it shows "Minimum Years Experience:" but blank? It shows "Minimum Years Experience:" then line break? The snippet: "Division: Memphis Main Project Location(s): Memphis, TN 38119 USA Minimum Years Experience: Travel Involved: Job Type: Regular Job Classification: Experienced Education: Job Family: Construction Compensation: Salaried Exempt". So Minimum Years Experience is blank? It shows "Minimum Years Experience:" then next label "Travel Involved:" maybe missing value. So we cannot include that as it's not specific. Travel Involved also blank? Probably not. So we may skip Requirements section unless we have something like qualifications. But Qualifications is separate. - Qualifications: list of qualifications (Bachelor’s Degree..., Supervisor or management experience..., Prior union management experience..., Thorough knowledge..., Read..., Professional..., Proficient..., Leadership..., etc). That's a list. - Skills: Could be derived from qualifications? But we have a Qualifications section already; maybe we can combine Qualifications and Skills? The instruction says we can have sections like Qualifications, Skills. We have qualifications content; we could treat that as Qualifications. Skills maybe not separately listed; we could omit Skills if no specific skill list beyond qualifications. However qualifications include skills like "Professional written and verbal communication skills", "Proficient with computer applications and Microsoft Office skills", "Leadership and interpersonal relationship building skills". Those could be considered skills. But we already have them in qualifications. To avoid duplication, we could put them under Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one Qualifications section. Or we could have Qualifications (education/experience) and Skills (specific skills). But we have limited content; better to have Qualifications covering both. - Benefits, Pay, Schedule: Not provided. So we omit those sections. Thus we will output:

    About the role

    Lead, direct, and coordinate management of Self-Perform Operations (SPO) projects, including overall project pursuit, staffing, proactive planning and implementation, budget, and risk management.

    Responsibilities

    • Lead development of high-performance teams through supervision, training, coaching, and mentoring.
    • Ensure regular feedback with staff including timely completion of performance appraisals.
    • Provide leadership to foster environment of diversity and inclusion for all staff.
    • Develop and improve assigned client relationships fostering trusted advisor status.
    • Understand and administer company contract and subcontract agreements.
    • Promote involvement in community to help build strategic relationships and embrace community in which we live and work.
    • Foster and enhance internal, architect, owner, vendor, and supplier relations.
    • Assist in development and update master schedule to incorporate Self-Perform Operations (SPO) schedule; distribute latest schedule to trade partners and suppliers to ensure contractual obligations.
    • Manage budget and financial reporting, interpret and analyze reports to ensure adherence to project budget.
    • Manage productivity tracking program.
    • Manage Quality Control (QC) program.
    • Provide leadership for risk evaluation, contract negotiations, fee and pricing decisions.
    • Understand, comply, and advise others on company business ethics, and compliance programs.
    • Manage and oversee field operation and engineering processes and procedures.
    • Understand and manage labor agreements, if in union environment.
    • Develop and ensure implementation of project safety protocols.
    • Ensure timely submission of pay applications.
    • Collaborate with accounting to ensure timely submission and payment of supplier invoices in accordance with terms of contract agreement.
    • Review subcontracts, Purchase Orders, and Change Orders for accuracy.
    • Inform management of project and budget progress via regularly scheduled Operation Review Meetings (ORM).
    • Support and drive utilization of various company initiatives; promote and utilize emerging technologies and innovations to support sustainable competitive advantages.
    • Other activities, duties, and responsibilities as assigned.

    Qualifications

    • Bachelor’s Degree from accredited degree program and 8 years of related experience or equivalent combination of education, training, and experience
    • Supervisor or management experience, preferred
    • Prior union management experience, desired
    • Thorough knowledge of construction cost, scheduling, estimating, purchasing and engineering principles and techniques, budgeting, and accounting principles
    • Read, understand, and interpret contract documents, drawings, specifications, scopes of work and project schedule
    • Professional written and verbal communication skills
    • Proficient with computer applications and Microsoft Office skills
    • Leadership and interpersonal relationship building skills
    We might also include Physical Demands and Work Environment as part of Requirements? But we have no Requirements section. Could we add a Requirements section for Physical Demands and Work Environment? The instruction says we can have Requirements heading. It might be appropriate to include those details under Requirements. However we must avoid filler. Those are substantive. So we could add a Requirements section with two sub-sections? But we only allow
    • for list. We could combine them into a list. However they are prose paragraphs. Could use

      for each. The instruction: Use

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

        for prose. So Physical Demands and Work Environment are prose; we could put them in

        under a Requirements heading. Thus we could have:

        Requirements

        The physical demands described here are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. Performance of the required duties will require physical ability to climb permanent and temporary stairs, passenger use of construction personnel hoists, ability to climb ladders and negotiate work areas under construction. Specific vision abilities required by this job include close vision, peripheral vision, depth perception, and the ability to adjust focus. Performing this job requires use of hands to finger, handle, or feel objects, tools or controls, sit, talk and hear, stand, climb, balance, stoop, kneel, crouch, or crawl.

        The work environment characteristics described here are representative of those an employee encounters while performing the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. While performing the duties of this job, the employee regularly works on-site at the construction work site where the employee is exposed to moving mechanical parts; high precarious places; fumes or airborne particles; outside weather conditions and risk of electrical shock. The noise in these work environments is usually moderate to very loud.

        But we must check if we are duplicating content already covered elsewhere. Not duplicated. It's specific. We also have EEO statement at end: "Turner is an Equal Opportunity Employer - race, color, religion, sex, sexual orientation, gender identity, national origin, disability, status as a protected veteran, or other characteristics protected by applicable law." This is boilerplate EEO; we should remove it per instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So drop that. Also we have "Compensation: Salaried Exempt" which is a bit of metadata about pay type but not actual pay amount. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It states "Compensation: Salaried Exempt". That is a statement about compensation type (salaried exempt). Is that enough to create a Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation: Salaried Exempt. That is a statement about compensation type. Should we include a Pay section? It says "Prefer a few substantive sections over many thin ones." The compensation statement is minimal but it's specific. Could we include a Pay section with a

        stating "Salaried Exempt"? That would be a thin section. Might be better to fold that minor metadata into a short

        or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." Compensation is minor metadata; we could fold into a short

        maybe under About the role or elsewhere. But they said "fold minor metadata into a short

        or drop it." So we could add a short paragraph after About the role: "

        Compensation: Salaried Exempt

        " but that's still a separate line. Might be considered minor metadata. However we already have About the role paragraph; we could append that sentence. But better to keep it separate small paragraph. But the instruction also says: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we create a Pay heading with just "Salaried Exempt", that might be considered thin but still specific. However they said prefer few substantive sections over many thin ones. So maybe we should not create a Pay section; instead incorporate the compensation detail into a short

        somewhere else, maybe after About the role. Similarly, there is no schedule info. Thus final HTML could have sections: About the role, Responsibilities, Requirements (physical demands & work environment), Qualifications. We could also add a short paragraph for compensation after About the role. Let's craft:

        About the role

        Lead, direct, and coordinate management of Self-Perform Operations (SPO) projects, including overall project pursuit, staffing, proactive planning and implementation, budget, and risk management.

        Compensation: Salaried Exempt

        Then Responsibilities, Requirements, Qualifications. Check for any duplicated lines: Ensure we didn't include any boilerplate like "Division: Memphis Main Project Location(s): Memphis, TN 38119 USA".