Jobs · Project Management · California

Project Lead

Oldcastle Infrastructure · Chowchilla, CA · 3 wk ago
Project ManagementOther
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat job title as 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. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the job posting. Key sections: - Job Summary (description) - Job Location (Chowchilla, CA) - Job Responsibilities (list) - Job Requirements (list) - Compensation (Target Salary $70k-$80k, Yearly bonus 10%, 401(k), short/long term disability, life insurance, health/dental/vision, PTO, paid holidays) - What CRH Offers You (list: highly competitive base pay, comprehensive medical/dental/disability benefits, group retirement savings, health and wellness programs, inclusive culture) - About CRH (description) - Possibly "Oldcastle Infrastructure - Built For Life from Oldcastle Infrastructure on Vimeo." (maybe ignore as media) - Job ID: 526018 Exempt Oldcastle, a CRH company... (metadata) - Also "Oldcastle Infrastructure - Built For Life from Oldcastle Infrastructure on Vimeo." maybe ignore. We need to decide which sections to output. We have content for: - About the role (maybe Job Summary) - Responsibilities (Job Responsibilities) - Requirements (Job Requirements) - Benefits (Compensation and What CRH Offers You) - Pay (Compensation includes salary range and bonus) - Schedule (not mentioned) - Qualifications (maybe same as Requirements) - Skills (maybe part of Requirements) We need to avoid thin sections. We can combine some. We need to output only sections with real content. We have location info: "Job Location: This position will be located at our plant in Chowchilla, CA." That's substantive. Could be part of About the role or separate? There's no explicit heading for location but we could include in a short

    maybe under About the role. We need to avoid duplication: The posting repeats some content: "Oldcastle Infrastructure - Built For Life from Oldcastle Infrastructure on Vimeo." maybe ignore. We need to remove boilerplate: EEO statements, application instructions, etc. Thus final HTML could have sections:

    About the role

    Job summary: The P.L is the “voice of the customer” in our OI facilities. The P.L. is responsible for the customer experience from the point of sale to on-site delivery. To achieve OI's goal to enhance “ease of doing business,” a role to represent the customer's voice in our facilities has been developed to ensure 100% customer satisfaction on ALL sales orders. Once an opportunity becomes a sales order, the P.L. drives all activities from the point of sale to on-site delivery including coordinating with engineering, approval of submittals, scheduling with production and on-site delivery with the customer and transportation. The P.L. acts as the main point of contact for customers and vendors on assigned sales orders and is directly responsible for monitoring the project costs and compliance with contract documents, attending job meetings and balancing the customer and OI interests throughout the entire process.

    Job location: This position will be located at our plant in Chowchilla, CA.

    Responsibilities

    • Primary responsibility is being the “voice of the customer” in OI facilities.
    • Responsible for managing multiple sales orders concurrently.
    • Upon sales order assignment by the C.O.M, share responsibility with the O.S.R and Est. to hold a Turnover/Kick Off meeting at the point of sale to ensure all needed information and paperwork are complete; that the scope of work is clear; review the estimate and confirm values for all items; and begins the process of scheduling the project with production to align with “Customer Ship Date” in AX.
    • From point of sales order assignment, the P.L. becomes the point of contact for the customer. They must ensure the customer is kept up-to-date from production schedule to on-site delivery.
    • Provide direction and oversight to all aspects of the project team: engineering, production planning, transportation, procurement and accounting.
    • Prepare any applicable change order proposals in a timely manner, whether owner/ client/ engineer request or by generation from OI.
    • Monitors the progress and status from the point of sales as it moves through the process, and acts to problem solve proactively, offers technical advice, and assists other staff to expedite assigned projects, removes obstacles which may cause a project to fall behind schedule.
    • Ensures a mentality of continuous improvement of processes and systems.
    • If needed, coordinate site visits and work with the customer to ensure that all issues that arise from the point of sale to completion of the project are resolved promptly, including but not limited to change orders, adjustments to schedule and collect information as appropriate to each assigned project.
    • Identify and requisition special purchase items as required.
    • Managing the required submittals/approvals with customer as required.
    • Communicate with the Transportation department on the initial delivery needs of the customer and follow up when required.
    • Working with other project managers and the plant manager to manage the long-term schedule to minimize conflicts with operational restrictions.

    Requirements

    • Bachelor's degree or equivalent work experience required.
    • Civil Engineering preferred.
    • 3+ years Project Management experience.
    • Demonstrated ability to manage several large to small, complex projects simultaneously.
    • Intermediate to advanced knowledge of MS Office (Word, Excel, PowerPoint and Outlook).
    • Ability to review and work from production schematics and engineering drawings.
    • Strong organizational and communication skills.
    • Experience within the construction or precast concrete industry.

    Pay

    • Target Salary: $70,000.00 to $80,000.00
    • Yearly bonus of 10%

    Benefits

    • 401(k) plan / group retirement savings program
    • Short-term and long-term disability benefits
    • Life insurance
    • Health, dental, and vision insurance
    • Paid time off
    • Paid holidays
    • Highly competitive base pay
    • Comprehensive medical, dental and disability benefits programs
    • Group retirement savings program
    • Health and wellness programs
    • An inclusive culture that values opportunity for growth, development, and internal promotion
    We might combine some benefits overlapping; but it's okay. We need to avoid duplication: "401(k) plan / group retirement savings program" appears both in Compensation and What CRH Offers You; we can keep one. We also have "Highly competitive base pay" appears in What CRH Offers You; we could keep. We need to ensure we don't create sections with filler like "Schedule" (none). So omit. We need to preserve all substantive information: we included job summary, location, responsibilities, requirements, pay, benefits. Also we might include "About CRH" description? That is substantive but maybe could be considered "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no heading for About the company. Could we include it under About the role? Might be okay to add a separate section like "About CRH" but not in allowed headings. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive list? 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 CRH. We could incorporate that info into About the role or Benefits? Probably better to add a short paragraph under About the role about the company? But the About CRH description is about the company, not the role. However we could treat it as "About the role" includes company context? Might be okay. But we need to preserve ALL substantive information. If we omit About CRH description, we lose info. However maybe it's considered boilerplate? It's not boilerplate; it's a description of CRH. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About CRH is not those. So we should keep it. We could add a section "About the company" but not in allowed headings. However the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we can use other headings as needed, but they gave examples. Safer to stick to those headings but we could incorporate About CRH into About the role or Benefits? Probably better to add a separate section "About CRH" using

    as well, as it's a heading. The instruction didn't forbid other headings; just gave examples. So we can add About CRH. Thus final HTML:

    About the role

    Job summary: The P.L is the “voice of the customer” in our OI facilities. The P.L. is responsible for the customer experience from the point of sale to on-site delivery. To achieve OI's goal to enhance “ease of doing business,” a role to represent the customer's voice in our facilities has been developed to ensure 100% customer satisfaction on ALL sales orders. Once an opportunity becomes a sales order, the P.L. drives all activities from the point of sale to on-site delivery including coordinating with engineering, approval of submittals, scheduling with production and on-site delivery with the customer and transportation. The P.L. acts as the main point of contact for customers and vendors on assigned sales orders and is directly responsible for monitoring the project costs and compliance with contract documents, attending job meetings and balancing the customer and OI interests throughout the entire process.

    Job location: This position will be located at our plant in Chowchilla, CA.

    Responsibilities

      ...

    Requirements

      ...

    Pay

      ...

    Benefits

      ...

    About CRH

    CRH has a long and proud heritage. We are a collection of hundreds of family businesses, regional companies and large enterprises that together form the CRH family. CRH operates in a decentralized, diversified structure that allows you to work in a small

Similar jobs

Project Lead

Oldcastle InfrastructureHancock, MN· 1 mo ago
Information Technologyapply on app.careerarc.com

Project Lead

Oldcastle InfrastructureMansfield, TX· 4 mo ago
Information Technologyapply on app.careerarc.com

Project Lead

Tufts MedicineLowell, MA· 1 mo ago
Project Management$17–$20.02/hrapply on careers.tuftsmedicine.org

Project Lead

CRHRomeoville, IL· 1 mo ago
Project Managementapply on jobs.crh.com

Project Lead

VONNE (Voluntary Organisations'​ Network North East)Newcastle, CA· 1 mo ago
Information Technologyapply on vonne.org.uk

Project Lead

JT4North Las Vegas, NV· 1 mo ago
Information Technologyapply on recruiting.adp.com