Project Controls Department Head

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also must not create sections with filler like "commensurate with experience". Must include Pay and Schedule only if posting actually states them. The posting includes salary range and appointment type (full-time career appointment, exempt). Also work modality location. So we can have Pay section with salary range. Schedule? Not explicitly given; maybe work modality location but not schedule (hours). Could include "Work modality" maybe as Schedule? But schedule typically refers to work hours, shift, etc. Not present. So we should not create Schedule section unless there is explicit schedule info. There's "Work will be primarily performed at: Lawrence Berkeley National Lab, 1 Cyclotron Road, Berkeley, CA." That's location, not schedule. So we skip Schedule. Benefits: Not explicitly mentioned. There's mention of appointment type, exempt, monthly paid, background check, work authorization, visa sponsorship not available. No explicit benefits like health, retirement. So we should not create Benefits section unless there is real content. Could we consider "Appointment type: This is a full-time career appointment, exempt (monthly paid) from overtime pay." as Benefits? Not really. Better to omit Benefits. Skills: There's "Desired Skills/knowledge PMP certification and EVMS certification experience." Also many skills listed in Required Qualifications. Could combine under Skills section. But we also have Qualifications (education, experience). The instructions: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what to put where. We have "About the role": introductory paragraph describing mission, dual function, etc. That's suitable. Responsibilities: list of duties. Requirements: maybe required qualifications? But they also have Required Qualifications and Desired Skills/knowledge. Could treat Required Qualifications as Qualifications section. Desired Skills/knowledge as Skills. We must not repeat content. Let's extract. Intro: "Lawrence Berkeley National Laboratory is hiring a Project Controls Department Head within the Engineering division. The Department Head (DH) for Project Controls (PC) fulfills a dual function. In the DH function, the incumbent develops the overall department strategy and advises the Division Director on current and future capabilities and tools for LBNL-led projects and externally led partner projects and is responsible for the department budget. In the direct PC leadership function, the incumbent provides project planning and controls expertise and professional project management guidance to Project Directors (PDs), Project Managers (PMs), and Principal Investigators (PIs) in the Project & Infrastructure Modernization Division for large, complex projects involving moderate to high risk. We're here for the same mission, to bring science solutions to the world. Join our team and YOU will play a supporting role in our goal to address global challenges! Have a high level of impact and work for an organization associated with 17 Nobel Prizes!" That's About the role. Responsibilities: bullet list from "Key Responsibilities" onward. Need to capture all responsibilities without duplication. Let's list them: - Manage, lead, and supervise the Project Planning and Controls Department staff. - Responsible for talent selection, management, performance, career development, succession planning, and workload leveling of staff. - Provide PC support for Projects across the LBNL organization including construction projects. - Collaborates with the Deputy of Operations to develop and maintain tools for the EG division to manage and project EG technical staffing needs and deployments. - Responsible for the department budget Division and Department Strategy. (maybe duplicate) - Identify best practices, tools, and approaches across the DOE complex and from the Project Management Institute (PMI) to ensure efficient and effective application of PP&C expertise to LBNL scientific projects. - Provide strategic leadership to the Engineering Division and make recommendations regarding PC capabilities for LBNL. - Provide PC support for projects across the LBNL organization, including construction projects. (duplicate of earlier) - Formulate and apply extensive knowledge of project planning, budgeting, scheduling, and software applications to LBNL PP&C practice. - Determine LBNL tools and approaches for PP&C. - Lead or participate in project management/controls networks, working groups, and external reviews. - Maintain strong collaboration with LBNL PMO, Scientific Project Managers and stakeholders to achieve objectives of the current scientific project portfolio and anticipate future changes in demand, rigor, and consequence. - Appoint Earned Value Surveillance Officer(s), providing institutional strategic and tactical advice to the LBNL Project Management Office (PMO). - Partner with other institutional stakeholders, including the PMO and OCFO, to ensure certification eligibility and status. - In collaboration with the LBNL PMO, DOE, and Engineering Management, modify and develop LBNL policies, practices, standards, system descriptions, software applications, and protocols to achieve scientific project objectives and ensure DOE requirements are met. We need to deduplicate: Provide PC support for projects across LBNL organization including construction projects appears twice; we can keep one. Also "Responsible for the department budget Division and Department Strategy." maybe combine with earlier "develops overall department strategy and advises Division Director ... and is responsible for the department budget." We'll keep both but can combine. We'll produce a

• list. Requirements: maybe "Required Qualifications" section. Let's list: - Bachelor's/advanced degree in a related field and at least 12 years education and/or applied experience in the planning and control of moderate to large projects subject to DOE project management order(s). - Supervisory experience required. - Demonstrated experience in representing project status, reporting, controls, and execution status to independent evaluation or review boards. - Recognized as a subject matter expert in project planning and controls management within LBNL and across the DOE Complex. - Knowledge of DOE and LBNL project management requirements, including DOE Order 413.3c and EVMS techniques. - Excellent written and oral communication skills; ability to interact effectively at the management level within the organization and with other research institutions and external agencies; proven ability to interact effectively with personnel at all levels throughout the organization; effective consensus-building and negotiation skills. - Exceptional planning and organizing skills and ability to develop solutions to complex problems; sound judgment and ability to take decisive action without all desired information. - Demonstrated professional expertise to prepare for and respond to detailed and complex examinations from high-level internal and external reviews. - Excellent strategic planning and implementation skills; proven ability to work on multiple projects with varying priorities and deadlines. Qualifications: maybe we treat Required Qualifications as Qualifications. But we already used that. Actually the heading list includes both Requirements and Qualifications. Could split: Requirements = mandatory experience/education; Qualifications = maybe desired? But we have Desired Skills/knowledge separate. Let's assign: - Requirements: the mandatory items (degree, years, supervisory experience, etc.) - Qualifications: maybe the recognized SME, knowledge of DOE order, etc. But ambiguous. Better to follow typical job posting: Required Qualifications = qualifications. Desired Skills/knowledge = skills. So we can have Qualifications section for Required Qualifications, and Skills section for Desired Skills/knowledge. Thus: Qualifications: list the Required Qualifications items. Skills: list Desired Skills/knowledge: PMP certification and EVMS certification experience. Also there are many skill-like items in Required Qualifications (communication, planning, etc.) but those are qualifications. We'll keep them in Qualifications. Pay: Salary range: $187,956.00 - $260,000.00, which fits into the full salary of $167,904.00 - $281,916.00 depending upon candidate’s skills, knowledge, and abilities. This includes education, certifications, and years of experience. We should include that. Schedule: Not present, omit. Benefits: Not present, omit. Now we need to strip boilerplate: Remove EEO, misconduct disclosure, etc. Also remove "Application date: Priority consideration will be given to candidates who apply by October 13, 2026. Applications will be accepted until the job posting is removed." That's application instruction; remove. Also "Appointment type: This is a full-time career appointment, exempt (monthly paid) from overtime pay." That's not benefits but maybe we could include in Pay? It's about appointment type. Could be part of Pay or maybe we could add a section "Appointment" but not in list. Could incorporate into Pay section as note. But instructions: only use given headings. Could we put appointment type under Pay? Not ideal but we could include in Pay paragraph. Or we could create a separate section "Appointment" but not allowed. Could we treat it as part of Pay? Probably okay to include in Pay section as additional info. Work modality location: Could be included in About the role or maybe as a note. Not required heading. Could add a paragraph under About the role. We must not include navigation, cookie, legal, EEO, etc. Now produce HTML fragment:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Qualifications

  • ...
  ...

  Skills

  • PMP certification
  • EVMS certification experience

  Pay

  The expected salary for this position is $187,956.00 - $260,000.00, which fits into the full salary range of $167,904.00 - $281,916.00 depending upon the candidate’s skills, knowledge, and abilities (including education, certifications, and years of experience). This is a full-time career appointment, exempt (monthly paid) from overtime pay.

  We need to ensure we didn't miss any substantive info: Also mention "Work will be primarily performed at: Lawrence Berkeley National Lab, 1 Cyclotron Road, Berkeley, CA. A REAL ID or other acceptable form of identification is required to access Berkeley Lab sites". This is substantive location info. Could add to About the role paragraph. Also mention "Work authorization: Candidates must be eligible to work in the U.S. at the time of hire. Visa sponsorship is not available for this position." That's also substantive. Could add to About the role or maybe a separate section but not in headings. Could add to About the role as well. We must not include boilerplate like "Having a conviction history will not automatically disqualify an applicant". That's substantive? It's about background check. Could include in About the role or maybe a separate note. It's about background check. It's substantive. We'll include a sentence. Also "Background check: This position is subject to a background check. Any convictions will be evaluated to determine if they directly relate to the responsibilities and requirements of the position." That's substantive. We'll incorporate those into About the role or maybe a separate "Additional Information" but not allowed headings. We'll add to About the role. Now ensure we didn't duplicate content. Let's craft About the role paragraph: Lawrence Berkeley National Laboratory is hiring a Project Controls Department Head within the Engineering division. The Department Head (DH) for Project Controls (PC) fulfills a dual function. In the DH function, the incumbent develops the overall department strategy and advises the Division Director on current and future capabilities and tools for LBNL-led projects and externally led partner projects and is responsible for the department budget. In the direct PC leadership function, the incumbent provides project planning and controls expertise and professional project management guidance to Project Directors (PDs), Project Managers (PMs), and Principal Investigators (PIs) in the Project & Infrastructure Modernization Division for large, complex projects