EUV Program Manager
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 parse the job posting.
Content:
- About NY Creates: description paragraph.
- Job Description Position Summary, EUV Program Manager: description.
- Key Responsibilities: list of bullet-like sentences separated by periods? Actually they are sentences separated by periods but each begins with a verb. We need to treat as list items.
- Requirements: Minimum Qualifications, EUV Program Manager: includes bullet-like statements.
- Preferred Qualifications, EUV Program Manager: list.
- Benefits: list of benefits.
- Location: address.
- Salary Range: $120,000 - $150,000.
- Additional Information: note about export control etc. Might be considered boilerplate? It's substantive but maybe we can include as a short paragraph under "Additional Information"? The instruction says include a section only when posting has real, specific content for it. It does have content: export control note. Could be a section "Additional Information". But they gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Additional Information but we could still include if content. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not exclusive. So we can add Additional Information if needed.
But we need to avoid filler. The export control note is substantive.
Also we have "Location: 257 Fuller Road, Albany, NY 12203". Could be a short paragraph.
We need to not repeat job title as heading. The job title is EUV Program Manager. Already appears in sections but not as heading.
We need to not put Job ID/requisition numbers as headings. There's a recblid at end; we drop it.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "Don't meet every requirement? ..." that's not boilerplate; it's encouraging to apply. Might be considered application encouragement but not instruction. Probably keep.
Also "This position is contingent on the satisfactory completion of a background check; this position may require annual background checks." That's part of requirements.
We need to preserve all substantive information.
Let's extract sections:
1. About NY Creates: paragraph.
2. Position Summary: maybe under "About the role"? Could be "About the role" heading with summary.
But they said "About the role" as example heading. We can use that for the position summary.
Alternatively we could have "About NY Creates" as separate section? Not in examples but could be "About the company". However they didn't list that. Might be better to combine under "About the role". But the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings where applicable. So we need sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly also Schedule if present (not). Also Skills maybe if present (not explicit). We'll include only those with content.
Thus:
- About the role
: combine the position summary and maybe the NY Creates description? The "About NY Creates" is about the organization, not the role. Could be placed under About the role? Might be okay. But we could also add a separate About NY Creates
but not in examples. Safer to follow examples: Use About the role for role summary; we can include NY Creates description as part of that or as a preceding paragraph before headings? The instruction says output only HTML fragment; we can include a
before first heading? Probably okay. But they didn't forbid extra paragraphs outside headings. We'll include a
for the NY Creates description, then headings.
Thus:
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 operates 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 more than $25 billion - placing it at the global epicenter of high-tech innovation and commercialization.
Then About the role
: position summary paragraph.
Then Responsibilities
: with each responsibility as - .
Then
Requirements
: maybe combine Minimum Qualifications and Preferred Qualifications? But they said Qualifications as a heading separate from Requirements. Actually they list Requirements and Qualifications as separate possible headings. So we can have:
- Requirements
: Minimum Qualifications (the must-haves).
- Qualifications
: Preferred Qualifications (the nice-to-haves).
Alternatively we could combine but better to follow examples.
Thus:
Requirements
: with each minimum qualification as - .
Qualifications
: with each preferred qualification as - .
Then
Benefits
: with benefits.
Then Pay
: with salary range.
Location maybe as
after Pay or before.
Schedule not present.
We also need to include Additional Information about export control. Could be a
Additional Information
with . Since not in examples but we have content. Might be okay.
But they said "Prefer a few substantive sections over many thin ones." Adding Additional Information may be thin but it's substantive. Could incorporate into Requirements or Qualifications? Not really. Could be a
after Benefits before Pay.
I'll include a
Additional Information
with the export control note.
Now let's extract exact text.
About NY Creates paragraph: "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 operates 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 more than $25 billion - placing it at the global epicenter of high-tech innovation and commercialization."
Position Summary: "Position Summary, EUV Program Manager This position requires leadership, organization, and coordination in support of NY Creates Extreme Ultraviolet Lithography (EUV) program - a next-generation semiconductor research and development center, supporting the research and development of the world's most complex and powerful semiconductors. The EUV program consists of NY Creates current EUV offerings as well as North America's first and only non-profit research and development center utilizing ASML's High NA EUV tool, developing the semiconductor industry's most advanced manufacturing technology."
We need to avoid repeating "Position Summary, EUV Program Manager" maybe as part of heading? We'll just keep the sentences.
Responsibilities list: The text after "Key Responsibilities" includes many sentences separated by periods. Let's split:
- Coordinating the executive staff and underlying personnel in the administrative system that guides day-to-day operations, supporting the development and maintenance of processes, procedures, and communications that enable EUV program to fulfill its mission and goals.
- Assisting the staff in assuring compliance against the terms, deliverables, and milestones outlined in EUV program plans and partnership contracts.
- Coordinating and supporting the external presence of EUV program via reports, newsletter content generation, conference coordination, and other outreach, as required.
- Acting as a liaison on behalf of the program with its internal and external stakeholders, including sponsors, and partners, as well as government officials, executives and staff members of NY Creates, and the public.
- Meeting planning and facilitation, presentation preparation, communications with program partners, potential partners, and representatives of government agencies, and review and editing of critical documents.
- Coordinating with internal departments to establish and execute support systems required by the EUV program and its partners.
- Supporting the efforts of EUV program leadership toward the establishment of the EUV program's project portfolio, from strategic alignment of programs and projects to portfolio categories and criteria, through proposal, evaluation, selection and prioritization, to contracting, execution, tracking and measuring the achieved results.
- Evaluating and maintaining program and project financial models, budgets, and forecasts.
- Providing regular financial analysis and fiscal-related reporting to leadership and other stakeholders as required
- Assist in managing the allocation of financial resources for assigned projects and initiatives.
- Facilitate the planning, coordination, and oversight of project scopes, budgets, deliverables, milestones, schedules, and dependencies across the programs and projects in the portfolio and resolve or escalate conflicts.
- Creating and maintaining program documentation and artifacts to track project proposals, plans, contracts, budgets, changes, deliverables, and the progress of each project
- Creating and analyzing key performance indicators to assist with driving improved results and provide detailed analysis, identifying risks and opportunities and addresses weaknesses or execution issues if required.
- Tracking project changes and implementing changes to the contract documents.
- Other reasonable duties as assigned
We need to ensure each - ends with proper punctuation? Not required.
Now Requirements (Minimum Qualifications):
Text: "Minimum Qualifications, EUV Program Manager This position requires a bachelor's degree in the area of hard sciences or engineering sciences, business, management, or a related field from a college or university accredited by the U.S. Department of Education or internationally recognized accrediting organization OR equivalent relevant professional experience.The incumbent must have a minimum of ten years of relevant professional experience and possess clear and well-reasoned verbal and written communications. The incumbent must have 7+ years professionally responsible experience in project management managing technical projects. The incumbent must have 5+ years' experience in navigating complex organizational structures and collaborating with technical and business teams.The incumbent must have a basic understanding of semiconductor industry, IC manufacturing process and process technologies. The Program Manager will possess clear and well-reasoned verbal and written communications. The incumbent must have experience in project management best practices and standards, working with stakeholders and collaborating in a cross-functional team environment. Additionally, the Program Manager must possess the ability to interface with customers and internal partners at various levels within an organization; work independently; prioritize demands in a fast-paced environment; have strong organization skills; and have experience with project management software."
We need to split into list items. Some sentences are repetitive (clear and well-reasoned verbal and written communications appears twice). We'll keep as separate items? Might be duplicate but we should preserve all substantive information; duplicates okay but we could deduplicate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines? Earlier they said "Remove cookie/navigation/legal/EEO/equal-opportunity/s
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 parse the job posting. Content: - About NY Creates: description paragraph. - Job Description Position Summary, EUV Program Manager: description. - Key Responsibilities: list of bullet-like sentences separated by periods? Actually they are sentences separated by periods but each begins with a verb. We need to treat as list items. - Requirements: Minimum Qualifications, EUV Program Manager: includes bullet-like statements. - Preferred Qualifications, EUV Program Manager: list. - Benefits: list of benefits. - Location: address. - Salary Range: $120,000 - $150,000. - Additional Information: note about export control etc. Might be considered boilerplate? It's substantive but maybe we can include as a short paragraph under "Additional Information"? The instruction says include a section only when posting has real, specific content for it. It does have content: export control note. Could be a section "Additional Information". But they gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Additional Information but we could still include if content. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not exclusive. So we can add Additional Information if needed.
But we need to avoid filler. The export control note is substantive.
Also we have "Location: 257 Fuller Road, Albany, NY 12203". Could be a short paragraph.
We need to not repeat job title as heading. The job title is EUV Program Manager. Already appears in sections but not as heading.
We need to not put Job ID/requisition numbers as headings. There's a recblid at end; we drop it.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "Don't meet every requirement? ..." that's not boilerplate; it's encouraging to apply. Might be considered application encouragement but not instruction. Probably keep.
Also "This position is contingent on the satisfactory completion of a background check; this position may require annual background checks." That's part of requirements.
We need to preserve all substantive information.
Let's extract sections:
1. About NY Creates: paragraph.
2. Position Summary: maybe under "About the role"? Could be "About the role" heading with summary.
But they said "About the role" as example heading. We can use that for the position summary.
Alternatively we could have "About NY Creates" as separate section? Not in examples but could be "About the company". However they didn't list that. Might be better to combine under "About the role". But the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings where applicable. So we need sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly also Schedule if present (not). Also Skills maybe if present (not explicit). We'll include only those with content.
Thus:
- About the role
: combine the position summary and maybe the NY Creates description? The "About NY Creates" is about the organization, not the role. Could be placed under About the role? Might be okay. But we could also add a separate About NY Creates
but not in examples. Safer to follow examples: Use About the role for role summary; we can include NY Creates description as part of that or as a preceding paragraph before headings? The instruction says output only HTML fragment; we can include a
About the role
: combine the position summary and maybe the NY Creates description? The "About NY Creates" is about the organization, not the role. Could be placed under About the role? Might be okay. But we could also add a separateAbout NY Creates
but not in examples. Safer to follow examples: Use About the role for role summary; we can include NY Creates description as part of that or as a preceding paragraph before headings? The instruction says output only HTML fragment; we can include abefore first heading? Probably okay. But they didn't forbid extra paragraphs outside headings. We'll include a
for the NY Creates description, then headings. Thus:
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 operates 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 more than $25 billion - placing it at the global epicenter of high-tech innovation and commercialization.
ThenAbout the role
: position summary paragraph. ThenResponsibilities
:- with each responsibility as
- .
Then
Requirements
: maybe combine Minimum Qualifications and Preferred Qualifications? But they said Qualifications as a heading separate from Requirements. Actually they list Requirements and Qualifications as separate possible headings. So we can have: -Requirements
: Minimum Qualifications (the must-haves). -Qualifications
: Preferred Qualifications (the nice-to-haves). Alternatively we could combine but better to follow examples. Thus:Requirements
:- with each minimum qualification as
- .
Qualifications
:- with each preferred qualification as
- .
Then
Benefits
:- with benefits.
Then
- ends with proper punctuation? Not required. Now Requirements (Minimum Qualifications): Text: "Minimum Qualifications, EUV Program Manager This position requires a bachelor's degree in the area of hard sciences or engineering sciences, business, management, or a related field from a college or university accredited by the U.S. Department of Education or internationally recognized accrediting organization OR equivalent relevant professional experience.The incumbent must have a minimum of ten years of relevant professional experience and possess clear and well-reasoned verbal and written communications. The incumbent must have 7+ years professionally responsible experience in project management managing technical projects. The incumbent must have 5+ years' experience in navigating complex organizational structures and collaborating with technical and business teams.The incumbent must have a basic understanding of semiconductor industry, IC manufacturing process and process technologies. The Program Manager will possess clear and well-reasoned verbal and written communications. The incumbent must have experience in project management best practices and standards, working with stakeholders and collaborating in a cross-functional team environment. Additionally, the Program Manager must possess the ability to interface with customers and internal partners at various levels within an organization; work independently; prioritize demands in a fast-paced environment; have strong organization skills; and have experience with project management software." We need to split into list items. Some sentences are repetitive (clear and well-reasoned verbal and written communications appears twice). We'll keep as separate items? Might be duplicate but we should preserve all substantive information; duplicates okay but we could deduplicate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines? Earlier they said "Remove cookie/navigation/legal/EEO/equal-opportunity/s
Pay
:with salary range. Location maybe as
after Pay or before. Schedule not present. We also need to include Additional Information about export control. Could be a
Additional Information
with. Since not in examples but we have content. Might be okay. But they said "Prefer a few substantive sections over many thin ones." Adding Additional Information may be thin but it's substantive. Could incorporate into Requirements or Qualifications? Not really. Could be a
after Benefits before Pay. I'll include a
Additional Information
with the export control note. Now let's extract exact text. About NY Creates paragraph: "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 operates 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 more than $25 billion - placing it at the global epicenter of high-tech innovation and commercialization." Position Summary: "Position Summary, EUV Program Manager This position requires leadership, organization, and coordination in support of NY Creates Extreme Ultraviolet Lithography (EUV) program - a next-generation semiconductor research and development center, supporting the research and development of the world's most complex and powerful semiconductors. The EUV program consists of NY Creates current EUV offerings as well as North America's first and only non-profit research and development center utilizing ASML's High NA EUV tool, developing the semiconductor industry's most advanced manufacturing technology." We need to avoid repeating "Position Summary, EUV Program Manager" maybe as part of heading? We'll just keep the sentences. Responsibilities list: The text after "Key Responsibilities" includes many sentences separated by periods. Let's split: - Coordinating the executive staff and underlying personnel in the administrative system that guides day-to-day operations, supporting the development and maintenance of processes, procedures, and communications that enable EUV program to fulfill its mission and goals. - Assisting the staff in assuring compliance against the terms, deliverables, and milestones outlined in EUV program plans and partnership contracts. - Coordinating and supporting the external presence of EUV program via reports, newsletter content generation, conference coordination, and other outreach, as required. - Acting as a liaison on behalf of the program with its internal and external stakeholders, including sponsors, and partners, as well as government officials, executives and staff members of NY Creates, and the public. - Meeting planning and facilitation, presentation preparation, communications with program partners, potential partners, and representatives of government agencies, and review and editing of critical documents. - Coordinating with internal departments to establish and execute support systems required by the EUV program and its partners. - Supporting the efforts of EUV program leadership toward the establishment of the EUV program's project portfolio, from strategic alignment of programs and projects to portfolio categories and criteria, through proposal, evaluation, selection and prioritization, to contracting, execution, tracking and measuring the achieved results. - Evaluating and maintaining program and project financial models, budgets, and forecasts. - Providing regular financial analysis and fiscal-related reporting to leadership and other stakeholders as required - Assist in managing the allocation of financial resources for assigned projects and initiatives. - Facilitate the planning, coordination, and oversight of project scopes, budgets, deliverables, milestones, schedules, and dependencies across the programs and projects in the portfolio and resolve or escalate conflicts. - Creating and maintaining program documentation and artifacts to track project proposals, plans, contracts, budgets, changes, deliverables, and the progress of each project - Creating and analyzing key performance indicators to assist with driving improved results and provide detailed analysis, identifying risks and opportunities and addresses weaknesses or execution issues if required. - Tracking project changes and implementing changes to the contract documents. - Other reasonable duties as assigned We need to ensure each
- .
Then
- .