Project Manager

We need to output HTML fragment with sections: About the role? The posting includes a paragraph about company culture before job description. That could be "About the role" or maybe "About the company". 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 (the page already shows it) and 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: - Intro paragraph about company culture and values (maybe "About the role" or "About the company"). - Job Description: "Adolfson & Peterson Construction, one of the nation’s top contractors, is recruiting for an experienced Project Manager. This position will manage and control assigned projects, including safety, budgets, contracts, schedules, and trade contractors and supplier coordination while working in conjunction with the Superintendent to lead the project team. Project scopes are generally up to $15 million or for designated components on a large, complex project. Because safety is paramount to AP and embedded into everything we do, all team members are responsible for working safely within our Incident and Injury Free culture." That could be part of About the role. - Responsibilities: a long list of bullet-like sentences (some are sentences). We need to format as

  • for any list of duties/requirements/benefits. So we need to extract each responsibility as a list item. - Requirements: list of qualifications (education, experience, skills). Also list items. - Pay: "Estimated Pay $89,600.00 - $143,000.00". That's specific, so we need a Pay section. - Benefits: list of benefits (Medical, Dental, Vision and Life Insurance, Health Savings Account, 401(k), Flexible Spending Accounts (Dependent & Medical Reimbursement), Paid Time Off (PTO) and Holidays, Tuition Assistance Program, Employee Referral Bonus). So Benefits section. - Schedule: not mentioned. So we should not include Schedule. - Qualifications/Skills: The posting lumps requirements; we could combine Requirements and maybe Skills. But we have to follow instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to include Requirements (which includes education, experience, proficiency, etc.) and maybe Skills (but we might not need separate Skills if covered). However we should not create empty sections. So we need to see if there is distinct Skills content separate from Requirements. The posting includes "Proficiency with scheduling, spreadsheets, cost control, and project management software. Prolog, Microsoft Project, P6, Procore, Bluebeam, and other construction programs a plus." That's a skill. Also "Solid understanding of value engineering, life cycle costing, and project profit/cost processes." etc. Many are more like qualifications. Could combine into Requirements. Safer to have Requirements section covering all qualification/skill content. Not create Skills unless there is distinct list. The posting does not have a separate "Skills" heading; we can omit Skills. - About the role: we have introductory paragraph(s). Could be "About the role". We'll include that. We must not include boilerplate like EEO statement at end. Remove duplicated lines. Also remove the repeated sentence about reviewing shop drawings etc appears twice; we need to preserve all substantive information but not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't explicitly say to deduplicate duplicates, but later says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. The duplicate line: "Review shop drawings, RFI’s, and ASI’s (all change orders) for coordination and implementation of project requirements;" appears twice in responsibilities. We should keep only one instance. Also there is duplicate of "Review shop drawings, RFI’s, and ASI’s (all change orders) for coordination and implementation of project requirements; keep project logs (i.e. shop drawings, RFI, ASI, OCO, etc.) updated and current for every progress meeting." Actually there are two similar lines: first one: "Review shop drawings, RFI’s, and ASI’s (all change orders) for coordination and implementation of project requirements." Then later: "Review shop drawings, RFI’s, and ASI’s (all change orders) for coordination and implementation of project requirements; keep project logs (i.e. shop drawings, RFI, ASI, OCO, etc.) updated and current for every progress meeting." The second includes extra detail about logs. So they are not exact duplicates; we keep both but ensure we don't duplicate the first line alone. We'll keep the second as it includes logs; the first is redundant. So we will keep the second. Now we need to format responsibilities as
    • . Each responsibility sentence becomes a list item. We'll need to break them at appropriate points. Let's list responsibilities from the text, removing duplicates and boilerplate. Original responsibilities block: "Take personal responsibility for working safely within an Incident and Injury Free (IIF) culture. Provide leadership throughout a project to ensure timely and quality results. Review shop drawings, RFI’s, and ASI’s (all change orders) for coordination and implementation of project requirements. Work with the Superintendent to prepare and update the detailed construction schedule. Lead the project estimate review, start-up, monthly interim, and close out meetings. Initiate and review close-out procedures with the project superintendent, owner, and architect before trade contractor work starts; maintain a zero punch list. Prepare letters of intent with trade contractors. Manage the trade contract process and all clarification or change issues. Ensure a timely submittal process, review, and execution of project changes by the owner and trade contractors. Review shop drawings, RFI’s, and ASI’s (all change orders) for coordination and implementation of project requirements; keep project logs (i.e. shop drawings, RFI, ASI, OCO, etc.) updated and current for every progress meeting. Manage and monitor material procurement for the project, including submittal approval, fabrication status, and delivery status. Work with the Superintendent in adhering to the schedule for early project close-out and final acceptance by the owner. Set firm and realistic deadlines so that the procedure and schedule for submittal of O&M manuals, close-out documents, and project warranties are in place before the work is 50% complete. Ensure project quality based on AP’s quality management programs. Facilitate collaborative team processes among project participants including design team, owners, and subcontractors. Lead or attend the weekly site progress meetings held with the owner, design team, and key trade contractors, project estimate reviews, start-up, monthly interim, and close out meetings; generate minutes from the meetings. Incorporate project management principles into the proposal process. Communicate field/office policies, instructions, and procedures to all project team members, including trade contractor personnel. Review project plans for constructability and cost feasibility; complete project risk assessments and prepare scope of work matrices. Provide technical expertise on projects in the pre-construction phase. Prepare the scope of work matrix for all trade contractor and supplier contracts, construction schedule, and performance expectations including workforce utilization goals prior to the award of the contract. Expedite project trade contractor/supplier buy-out; assist in review of bids to ensure that all items are included, exclusions are understood, and the bid is complete and conforms to the specifications before award. Draft and/or edit owner and subcontractor contract language. Analyze and manage project progress, costs, budgets, and cash flows. Create all project cost codes, budgets, and cash flow reports. Manage, review, and control all project costs and maintain accurate project cost projections. Confirm that total cost budgets, with contingencies, tie to the project contract amount; ensure project budgets are maintained. Prepare all monthly pay applications to the owner and ensure timely collection; collect, in accordance with the contract, all invoiced project amounts due from the owner and manage the project’s cash flow. Review and approve all trade contractor/supplier payment applications; collect supplier and trade contractor lien waivers to ensure all payments are properly disbursed. Prepare final written analysis on project profitability, profit enhancers, profit busters, and project problems for discussion in the close-out meeting and the permanent project records. Provide explanations for all significant project cost variances, by cost code, on the Intranet. Review the project’s QC plan and ensure compliance; report findings to project team and management. Other responsibilities as assigned." We need to remove duplicate line: the earlier "Review shop drawings, RFI’s, and ASI’s (all change orders) for coordination and implementation of project requirements." (without logs). We'll keep the later one with logs. Also note there is a line: "Prepare letters of intent with trade contractors. Manage the trade contract process and all clarification or change issues." That's two sentences combined; we can keep as one list item. Now Requirements block: "History of progressively more responsible leadership experience and proven results including: Bachelor’s degree in construction management, architecture, engineering, or related field and 6+ years of experience running construction projects with contract values greater than $5 million. Or, completion of an associate’s degree in construction management and 8+ years of relevant project management experience. Proficiency with scheduling, spreadsheets, cost control, and project management software. Prolog, Microsoft Project, P6, Procore, Bluebeam, and other construction programs a plus. Solid understanding of value engineering, life cycle costing, and project profit/cost processes. Recognition and achievement of high-quality construction standards. Thorough experience with multiple contract types under the CMR and Design-Build delivery methods. Current or ability to become current with OSHA 30 and company safety requirements. Ability to travel. Willingness to work in various (sometimes extreme) climate conditions. Demonstrated integrity and ethical standards. Experience in a complex business as an active participant in driving growth and change; demonstrated effectiveness in driving operations and executing plans. Experience in driving accountability for financial and operational effectiveness, integrating and aligning efforts within team, monitoring results, and tackling problems directly. Experience cultivating an active network of relationships, driving collaboration and alignment, relating well to colleagues, and connecting with employees at all levels. Ability to drive to the core of complex issues and provide insightful and constructive feedback. Developed skills (written, oral, and listening) in order to effectively communicate with diverse audiences." We need to format as list items. The first line "History of progressively more responsible leadership experience and proven results including:" could be a heading? But we are using
      • for list. We could treat that as a preamble sentence before the list. But instruction: Use
        • for any list of duties/requirements/benefits. So we can keep that introductory sentence as a

          before the

          . Or we could incorporate it as a list item? Better to keep as a

          preceding the list. Now Benefits block: "Medical, Dental, Vision and Life Insurance Health Savings Account 401(k) Flexible Spending Accounts (Dependent & Medical Reimbursement) Paid Time Off (PTO) and Holidays Tu