Project Manager for Facilities and Infrastructure

We need to output HTML fragment with sections for headings: 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. No Job ID etc. Remove boilerplate. We need to parse the posting. First, we have Category, Subscribe etc - ignore. Department: Project Management, Locations: Albany, NY, Posted: Sep 17, 2026, Closes: Open Until Filled, Type: Full-Time, Salary Type: Annually, Salary Range: $145,000.00 - $160,000.00, Position ID: 204908. We need to include Pay section if salary range is given. Yes, we have salary range. So Pay section with that. Schedule? Not given explicitly besides Full-Time. Could we infer schedule? The posting says Type: Full-Time. That's schedule info. Should we include Schedule section? The rule: include a section ONLY when posting has real, specific content for it. "Full-Time" is specific content about schedule. So we can include Schedule with "Full-Time". However we need to avoid filler like "not specified". It's specified. So include. Benefits: there is a Benefits list: Medical, Vision, and Dental, Competitive Pay and PTO, Flexible Heath Spending and Dependent Care Accounts, Basic / Optional Life Insurance, Post-Retirement Health Insurance, Employer contribution of 7% of earnings to a Basic Retirement plan after meeting one year of service. Optional employee contributed retirement account. We need to include Benefits section with those items as list. About the role: The "About NY Creates" paragraph describes the organization. That could be About the role? Usually About the role is about the position. But we have "Job Description: Position Summary, Project Manager For Facilities And Infrastructure". That is a summary. We can treat that as About the role. Also there is "About NY Creates" which is about the organization. Could be considered About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have: - About the role: Could include the Position Summary paragraph: "The Project Manager for Facilities and Infrastructure lead planning and execution of construction, infrastructure upgrades, and new facility development, ensuring projects are delivered on time, within budget, and without disrupting operations. Manages design/construction partners, budgets, schedules, and compliance while aligning projects with long-term site plans. Collaborates across teams and drives performance of staff and suppliers to deliver high-quality, cost-effective solutions." That's substantive. - Responsibilities: The "Key Responsibilities" list is long. We'll output as

• items. - Requirements: There's "Minimum Qualifications" and "Preferred Qualifications". The instruction: Use Requirements section for minimum qualifications? Possibly combine both? There's also Qualifications and Skills sections. We need to decide. We have Minimum Qualifications (education + experience). Preferred Qualifications (additional). Also there are skills mentioned within preferences (clean room protocol, etc). Could allocate: - Requirements: Minimum Qualifications (maybe also include "This position is contingent on the satisfactory completion of a background check.") That's a requirement. - Qualifications: Preferred Qualifications. - Skills: Could extract specific skills from preferences: clean room protocol development, chemical safety training, chairing meetings, understanding of HVAC etc, knowledge of cleanroom air management systems, experience with 3 level fabs, knowledge of methods to renovate building into fab, knowledge of formal Project Management, experience matrix managing, experience working with code officials, understanding construction safety, experience investigating root causes, working knowledge of design consultants, experience creating SOWs, bid lists, evaluating proposals, awarding contracts, registered architect or professional engineering license. But many of those are also qualifications. However we need to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all info. We can split into sections but ensure not to duplicate same sentence across sections. We could put Minimum Qualifications in Requirements, Preferred Qualifications in Qualifications, and specific technical skills in Skills. However some of the Preferred Qualifications are also skills; we could keep them in Qualifications and not duplicate in Skills. But we need to decide. Better approach: Use sections as follows: - About the role: Position Summary paragraph. - Responsibilities: Key Responsibilities list. - Requirements: Minimum Qualifications (education + experience) plus background check contingency. - Qualifications: Preferred Qualifications list (including all the bullet-like items). Could also include "PMP certification a plus" maybe as part of Requirements? It's mentioned under Minimum Qualifications: "PMP certification a plus for administering the various responsibilities listed above." That's a qualification but optional. Could place in Qualifications. - Skills: Could be empty? But we need to include only if there is real specific content. We could treat the list of specific technical skills (cleanroom protocol, HVAC, etc.) as Skills. However they are already in Preferred Qualifications. To avoid duplication, we could move those to Skills and keep Qualifications for more general preferences like PMP certification, registered architect/PE license, etc. But the instruction says preserve ALL substantive information; not duplicate but we can split. Let's parse the Preferred Qualifications paragraph: "Preferred Qualifications, Project Manager For Facilities And Infrastructure Skilled in clean room protocol development, management with experience controlling airborne molecular contamination. Experience with chemical safety training, chairing & conducting customer and construction meetings for project compliance, coordination, and reporting within semiconductor facilities organizations. Solid understanding of all Facilities site and building systems including HVAC, exhaust, abatement systems, chillers, boilers, waste treatment, process gases, chemical distribution, compressed air, process cooling water and DI water. Knowledge of cleanroom air management systems including VLF and turbulent flow rooms. Experience with 3 level fabs with both open and closed waffle slabs desired. Knowledge of methods and materials required to renovate an existing building into a fab/cleanroom or build a new Greenfield fab/cleanroom desired. Knowledgeable in the discipline of formal Project Management. Experience in following all steps from base line creation to changing order process, to acceptance & turnover. Proven ability to matrix manage and lead cross-functional teams responsible for the design and construction of major Facilities Programs. Experience working with code officials on building permits and inspections. Understanding of all aspects of construction safety. Experience investigating root causes of accidents and developing action plans to prevent occurrence. Working knowledge of design consultants and construction managers with the skill and proven experience to successfully handle cleanroom/new building construction. Experience in creating SOW's, bid lists, evaluating proposals, and awarding contracts. Registered architect or professional engineering license." Thus many items are skills/experience. We could treat the entire paragraph as Qualifications (preferred). And maybe we don't need a separate Skills section. The instruction says we can have Skills section but only if posting has real specific content for it. We could decide not to include Skills if we think Qualifications covers it. However we might still include Skills to break out technical skills. But risk of duplication. Given the instruction to prefer a few substantive sections over many thin ones, we should avoid creating many thin sections. So better to have: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 7 sections. That's fine. We'll put: - About the role: Position Summary paragraph (maybe also include About NY Creates? The "About NY Creates" is about the organization, not the role. Could be considered About the role? But we already have Position Summary. The About NY Creates is descriptive of the employer; could be considered About the role? Not exactly. Might be considered "About the role" or maybe we could omit it as it's not directly about the role but about the organization. However the instruction says use headings e.g. About the role. It didn't say we must include About NY Creates. We could include it as part of About the role? Might be okay. But to preserve ALL substantive information, we should include the About NY Creates paragraph somewhere. Where? Could be in About the role section as an introductory paragraph about the organization. That seems reasonable. Thus About the role will contain two paragraphs: the About NY Creates description and the Position Summary. Now Responsibilities: list of key responsibilities. Requirements: Minimum Qualifications (education + experience) plus background check contingency plus maybe note about PMP certification a plus? Actually PMP certification a plus is mentioned under Minimum Qualifications paragraph: "PMP certification a plus for administering the various responsibilities listed above." That's a qualification but optional; could go in Qualifications. We'll put Requirements: Minimum Qualifications (education + experience) and background check contingency. Qualifications: Preferred Qualifications paragraph (including PMP certification a plus, registered architect/PE license, etc.) Benefits: list. Pay: Salary Range. Schedule: Full-Time. Now we need to format as HTML fragment: use

  for each section heading, then content:

  for prose,

  • for lists. We must not include any extra markup like or . Just the fragment. Let's craft. First, About the role:

    NY Creates serves as a bridge for advanced electronics, leads projects that advance R&D in emerging technologies, and generates the jobs of tomorrow. NY Creates also runs some of the most advanced facilities in the world, boasts more than 3,000 industry experts and faculty, and manages public and private investments of approximately $25 billion – placing it at the global epicenter of high‑tech innovation and commercialization.

    The Project Manager for Facilities and Infrastructure lead planning and execution of construction, infrastructure upgrades, and new facility development, ensuring projects are delivered on time, within budget, and without disrupting operations. Manages design/construction partners, budgets, schedules, and compliance while aligning projects with long‑term site plans. Collaborates across teams and drives performance of staff and suppliers to deliver high‑quality, cost‑effective solutions.

    Note: The original text had "lead" maybe should be "leads". We'll preserve as is? It says "lead planning". We'll keep exact wording? We should preserve ALL substantive information; not change wording. So we keep "lead planning". It's okay. Now Responsibilities: we need to convert the long list into
    • . The list items are sentences starting with verbs. We'll split at each sentence that starts with a verb after a line break. The original "Key Responsibilities" paragraph includes many sentences separated by periods. We'll create list items for each sentence. Let's extract: - Provide technical leadership to the NY Creates team responsible for all site construction including rearrangements and infrastructure upgrades of the existing facility as well as the construction of new buildings, cleanrooms, labs, and infrastructure. - Employ accepted Project Management practices including the development and sign- off of baseline project documents, implementation of a work order and change order process, and proper project close-out. - Manage all design and construction contracts with architects and construction managers. - Drive staff and suppliers to provide cost-competitive, reliable, timely and effective engineering solutions on all design and construction projects. - Independently develop concepts, cost estimates, and presentations to sell programs and report status to the NY Creates executive team. - Ensure construction projects do not impact ongoing operations. - Maintain work with consultants to develop site master plan and ensure construction is consistent with future plans. - Work closely with facilities team and suppliers to ensure that projects remain on budget and on schedule. - Develop detailed budgets and schedules, identify all dependencies and ensure stakeholders understand status and gating needs. - Present budget and schedule status to NY Creates executives. - Use or drive construction manager to use, industry standard project schedule software tools. - Support tool installations as required and ensure site utilities, infrastructure, and cleanroom fit up is adequate to install and connect tooling. - Drive consultants to provide on time, on budget, high quality work for all tool hook-up design/build efforts. - Ensure that all proper NY Creates staff are involved in all new