Project Engineer

We need to output HTML fragment with sections: Overview? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real, specific content. We have Overview (intro), Location & Travel Details, Company Overview, Responsibilities, Qualifications, Knowledge, Skills, & Abilities (maybe Skills), Work Environment (maybe not a standard heading but could be part of Qualifications?), What's In It For You (Benefits, Pay). Also there is Compensation $60K and up, per year, commensurate with experience. That is Pay but includes "commensurate with experience" which is filler? The rule says: 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. The posting states compensation $60K and up, per year, commensurate with experience. That's a specific number with qualifier. It's not just "commensurate with experience" alone; it's "$60K and up, per year, commensurate with experience." That seems substantive enough to include Pay section. However we must avoid filler like "commensurate with experience" alone; but it's part of the sentence. I think we can include Pay section with that sentence. Benefits: there is a list: 401(k) with company match & ESPP, Flexible spending account, Medical/Dental/Vision insurance, Diabetes Management, Telehealth Coverage, Prescription Drug Plan, Pet Insurance, Paid Time Off, Paid Holidays, Bereavement Leave, Military Leave, Employee Assistance Program, Short and long-term disability, life insurance, accidental death & dismemberment, Voluntary life insurance, accident, critical illness, hospital indemnity coverage, Emergency Travel Assistance Program, Group legal plan. Also maybe other benefits like "Competitive pay with ongoing performance review and merit increase" (that's pay). So we can create Benefits section with ul list. Schedule: The posting mentions traveling position up to 90% of the time, some overnight travel. Also "Willingness and ability to travel to job sites 60% of the time" (contradiction?). There's location & travel details. This could be considered Schedule? Not exactly schedule but travel expectations. The instruction says include Schedule section only if posting actually states them. It does mention travel percentage; we could treat as Schedule? Might be better to include a "Location & Travel" section but not in allowed headings. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "Location". So we could incorporate location/travel details into Overview or maybe under Responsibilities? But better to put under Overview? The overview already has location & travel details paragraph. We could keep that as part of Overview paragraph (maybe under an

About the role? Actually About the role is a generic heading; we could use that for the overview description. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use About the role heading for the overview/intro. Then Responsibilities heading for responsibilities list. Qualifications heading for qualifications (degree). Skills heading for Knowledge, Skills, & Abilities list. Benefits heading for benefits list. Pay heading for compensation. Schedule heading maybe for travel expectations? The posting includes travel details; we could put that under Schedule. It says "Location & Travel Details: This is a traveling position, up to 90% of the time, encompassing work sites in the assigned project area, statewide, and will include some overnight travel." Also later "Willingness and ability to travel to job sites 60% of the time". That's schedule/travel expectation. So we can include Schedule section with that info. We must not repeat the job title as heading. So we will not include "Project Engineer" heading. We must not include Job ID/requisition numbers. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the EEO statement, disclaimer about scams, accessibility contact, etc. Also remove "Position may be subject to pre-employment screening..." maybe that's boilerplate? It's somewhat specific but could be considered boilerplate; but it's about hiring process. The instruction says remove application instructions. That line is about pre-employment screening, maybe considered part of application instructions. Safer to remove it. Also remove "Accessibility: If you need accommodation..." etc. Also remove "Due to the high volume of applications..." etc. Also remove EEO statement. Also remove disclaimer about scams. Also remove "MasTec Clean Energy & Infrastructure and our subsidiaries do not work with any third-party recruiters..." etc. We need to preserve all substantive information: overview, location/travel, company overview, responsibilities, qualifications, knowledge/skills/abilities, work environment (maybe we can incorporate into Qualifications or Skills?), benefits, pay, schedule. Work environment details: "When visiting jobsites, the work environment involves some exposure to hazards or physical risks, which require following basic safety precautions This work environment may involve moderate exposure to unusual elements, such as extreme temperatures, dirt, dust, fumes, smoke, unpleasant odors and/or loud noises Physical Demands: Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." This is substantive; we could include under a heading? Not in allowed list. Could be part of Qualifications or Skills? Maybe we can add a section "Work Environment" but not allowed. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those specific types. It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for those sections; but we could also use other headings if needed? Probably better to stick to those. We could incorporate work environment details into Qualifications or Skills as a bullet? But it's not a skill. Could be part of Overview. We'll add a paragraph under Overview after company overview. We need to ensure we don't create sections with filler. For Pay we have "$60K and up, per year, commensurate with experience." That's specific enough. For Benefits we have a list; we will output

• items. For Schedule we have travel details. Now produce HTML fragment. Structure:

  About the role

  Overview text: Cash Construction is now hiring for Project Engineers for current and upcoming work in/near Pflugerville, TX! The Project Engineer will assist directly with the daily management, supervision, coordination, and successful completion of the project(s) to safely meet time and cost objectives with respect to contracting, scheduling, estimating, bidding, and contract administration functions. In this position, the Project Engineer will learn how to take skills he or she may have acquired in school and/or during internships or other related work and apply them in a professional construction setting.

  Maybe also include location & travel details? But we have Schedule section for that. We could also include Company Overview under About the role? Could add another paragraph. Better: About the role includes overview and company overview? Might be too long but okay. Alternatively we could have About the role for overview, then a separate section for Company Overview? Not in allowed headings. So we incorporate company overview into About the role. Thus About the role paragraph includes both overview and company overview. Then Responsibilities:

  Responsibilities

  • ... each responsibility as li. We need to extract responsibilities list from the posting. It's a long paragraph with many responsibilities separated by semicolons? Actually the responsibilities section is a long sentence with many items separated by semicolons. We need to split into list items. We'll parse each distinct responsibility. Responsibilities text: "Promote and comply with all Company safety policies and procedures Contract professional services; schedule and coordinate Develop Construction Documents Identify and coordinate the submittals of all documents Review construction documents and prepare bid list to ensure all work items are accounted for and manage the bid process Coordinate team for takeoff and bid assembly assignments Attend pre-construction and job meetings Review construction documents to ensure compliance with Owner’s contract Initiate, review and obtain Owner’s approval on construction documents Review the submittal and approval process of the monthly application with the Owner Establish and manage a construction and engineering schedule to include: construction documents; permits, submittals and approvals; construction activity Obtain shop drawings from all subs; complete review and approval Confer with Director of EH & S on any jobsite safety issues Manage and resolve or assist superintendents in resolving all conflicts such as failure of subcontractors to perform failure of materials to arrive contract disputes and trade conflicts Interface with field superintendents to maintain an open line of communication and reporting monitor job progress, schedules and subcontractor performance and coordinate the operation of the field through management of field personnel Review the project and determine acceptability of completed work on an on-going basis Inspect the work and establish the final punch list Maintain extra work authorization log, identifying items and their resolutions Review General Conditions cost on a monthly basis Review subcontractor’s application for payment based on percent complete and approve or adjust Implement and maintain benchmark and inspection documentation Obtain and track installed quantities and materials and compare budget Obtain and compile quality control documentation Manage and supervise your team’s Superintendents by giving ongoing performance feedback and conducting annual performance appraisals in a timely manner" We need to split each line as separate
  • . Some lines have semicolons inside but we keep as one. We'll output each as
  • . Qualifications:

    Qualifications

    Bachelor's degree (B. S.) from four-year college or university in Construction Management, Engineering, or equivalent combination of education and experience

    Skills:

    Skills

    • Take reasonable care of your own and others health and safety and of those who may be affected by the day-to-day delivery of this role by taking personal responsibility for working toward Cash’s Zero Injury principles
    • Proficient in Microsoft Office, Excel, Primavera, Timberline, and Construction Software
    • Ability to read, analyze and interpret blueprints, professional journals, technical procedures, contracts, or governmental regulations
    • Write reports, business correspondence and document project activities
    • Effectively present information and respond to questions from project managers, superintendents, clients, customers and the general public
    • Effectively present information to top management, public groups, and/or boards of directors
    • Calculate figures and amounts such as discounts, interest, proportions, percentages, area, circumference, and volume
    • Ability to apply concepts of basic algebra and geometry
    • Solve practical problems and deal with a variety of concrete variables in standardized situations
    • Interpret a variety of instructions furnished in written, oral, diagram or schedule form
    • Willingness and ability to travel to job sites 60% of the time
    But note: "Willingness and ability to travel to job sites 60% of the time" is also schedule/travel; maybe we should move that to Schedule section instead of Skills. However it's listed under Knowledge, Skills, & Abilities. We could keep it there but also have Schedule section with travel details. Might duplicate. Better to keep it in Skills as it's part of KS