Technical Program Manager
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. Not present. Remove duplicated lines. Remove application instructions (none). Remove Job ID etc (none). Remove "Professional Education And Experience Requirements For The Role Include" maybe part of Requirements.
We need to extract content.
Let's parse the posting:
Job Description: We have an exciting opportunity for a Technical Program Manager at UL Research Institutes, within our Digital Safety Research Institute (DSRI). This is a REMOTE opportunity The Technical Program Manager plans, executes, and brings projects to closure on behalf of Digital Safety. The Technical Program Manager oversees the entire technical project lifecycle, ensuring that projects are completed on time, within budget, and according to the specified scope and quality requirements. The Technical Program Manager manages resources, coordinates teams, and mitigates risks to deliver successful project outcomes.
Then description of ULRI and DSRI.
Then "What You’ll Learn And Achieve As the Technical Program Manager, you will play a key role in the rapid growth of UL as you:" followed by bullet-like sentences separated by commas and periods. This is responsibilities.
Then "What Makes You a Great Fit While no one candidate will embody every quality, the successful candidate will bring many of the following professional competencies and personal attributes:" list of competencies.
Then "Professional Education And Experience Requirements For The Role Include Bachelor's degree in computer science and 3 years or more of hands-on experience as a software engineer. PMP Certification (or equivalent) and four year or more in product and program management. PMP Certification or equivalent Agile certifications (e.g., Certified ScrumMaster), and Six Sigma certifications."
Then "About UL Research Institutes And UL Standards & Engagement ..." (organization description). Could be part of About the role? Might be separate but we can include as About the role? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need sections: About the role (maybe includes description of role and organization). Responsibilities (the "What You’ll Learn And Achieve" list). Requirements (education/experience). Qualifications (maybe certifications?). Skills (competencies). Pay (salary range). We'll include.
We must not repeat job title as heading. Good.
We need to preserve all substantive info. So we need to include the description of ULRI and DSRI maybe under About the role? Or maybe we could have a separate section "About UL Research Institutes" but not in allowed headings. The allowed headings list is just examples; we can use those headings but not required to use exactly those? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings for sections. Probably we should map content to those headings. So we will have:
About the role
... includes the initial description and maybe organization description.
Responsibilities
- ... each duty.
Requirements
... education/experience.
Qualifications
... certifications? Actually the requirements already include certifications. But we could split: Requirements = education/experience; Qualifications = certifications. However the posting lumps them together. We need to preserve all info; we can put them under Requirements or Qualifications. To avoid duplication, we could put education/experience under Requirements, and certifications under Qualifications. That seems reasonable.
Skills
- ... competencies.
Pay
Salary Range $108,418.43-$149,075.34 Pay Type Salary
We must not include Benefits or Schedule.
Now we need to extract the exact sentences.
Let's copy the relevant parts.
About the role: The first paragraph: "We have an exciting opportunity for a Technical Program Manager at UL Research Institutes, within our Digital Safety Research Institute (DSRI). This is a REMOTE opportunity The Technical Program Manager plans, executes, and brings projects to closure on behalf of Digital Safety. The Technical Program Manager oversees the entire technical project lifecycle, ensuring that projects are completed on time, within budget, and according to the specified scope and quality requirements. The Technical Program Manager manages resources, coordinates teams, and mitigates risks to deliver successful project outcomes."
Then after that there is description of ULRI and DSRI. Should we include that? It's about the organization, not the role. Could be part of About the role? Might be better to include as part of About the role? The instruction: "About the role" heading likely expects description of the role and maybe the team. The organization description could be considered part of About the role? It's about ULRI and DSRI. I'd include it in About the role as it's substantive info about the organization.
Thus About the role paragraph will include: the initial description plus the paragraphs about ULRI and DSRI.
Let's copy those paragraphs exactly as they appear (preserving punctuation). We'll need to ensure we don't include boilerplate like "To learn more, visit our websites UL.org and ULSE.org." That's part of the organization description; it's substantive? It's a link; maybe we keep it? It's not boilerplate; it's info about where to learn more. Might be okay to keep. But it's not essential; but we can keep.
The organization description: "UL Research Institutes At UL Research Institutes (ULRI), we expand the boundaries of safety science to create a more secure and sustainable world. For more than a century, we have studied the unintended consequences of innovation, designed solutions to mitigate risk and shared our findings with academia, scientists, manufacturers, and policymakers across industries. We identify critical safety and sustainability issues, asking tough questions because we believe a safer world begins with knowledge. Build a safer, more secure, and sustainable future with us. Join us and work with our Fire Safety teams who conduct the research required to produce that knowledge and put it into practice. Digital Safety Research Institute The Digital Safety Research Institute (DSRI) addresses unresolved safety risks and emerging dangers in the world’s digital ecosystem. We aim to help protect people from unwanted access to personal devices and privacy, algorithms, and disinformation threats by working to create a new digital safety ecosystem. DSRI is committed to sharing digital safety insights, collaborating with key stakeholders, and offering extensive outreach and education to help support safer digital environments for people everywhere. To learn more, visit our websites UL.org and ULSE.org."
We'll include that.
Now Responsibilities: The list after "What You’ll Learn And Achieve As the Technical Program Manager, you will play a key role in the rapid growth of UL as you:" then a series of clauses separated by commas and periods. Let's extract each duty as a bullet.
The text:
"Define project objectives, scope, deliverables, and success criteria and develop comprehensive project plans, including schedules, budgets, and resource allocation, Identifying project dependencies, risks, and mitigation strategies. Collaborate with engineering team leads, research leadership, and external partners (sponsors, researchers, engineers, and adopters) to gather requirements and establish clear communication channels. Coordinate and lead cross-functional project teams, assign tasks and responsibilities, and monitor project progress, ensuring adherence to timelines, budgets, and quality standards. Foster effective teamwork and collaboration among team members. Conduct regular project status meetings, providing updates to stakeholders and addressing any issues or concerns. Manage changes to project scope, schedule, and resources, following appropriate change control processes and proactively identify and resolve project issues and conflicts. Escalate critical risks and issues to appropriate stakeholders and senior management. Ensure compliance with organizational policies, sponsor requirements, research data-handling expectations, and our open-source release processes. Establish and maintain strong relationships with project stakeholders, ensuring effective communication and collaboration. and provide regular project status reports and updates to stakeholders, including progress, milestones, and key decisions. Manage resources to balance internal Digital Safety tasks with UL-wide organizational assignments. Manage stakeholder expectations and address concerns or feedback. Facilitate effective communication among project team members, ensuring alignment and clarity. Conduct project reviews and lessons learned sessions to identify areas for improvement. Document project outcomes, successes, and challenges for future reference. Perform other duties as assigned."
We need to split into sensible bullet items. Each sentence seems to be a duty. We'll create - for each sentence.
Let's list sentences:
1. Define project objectives, scope, deliverables, and success criteria and develop comprehensive project plans, including schedules, budgets, and resource allocation, Identifying project dependencies, risks, and mitigation strategies.
2. Collaborate with engineering team leads, research leadership, and external partners (sponsors, researchers, engineers, and adopters) to gather requirements and establish clear communication channels.
3. Coordinate and lead cross-functional project teams, assign tasks and responsibilities, and monitor project progress, ensuring adherence to timelines, budgets, and quality standards.
4. Foster effective teamwork and collaboration among team members.
5. Conduct regular project status meetings, providing updates to stakeholders and addressing any issues or concerns.
6. Manage changes to project scope, schedule, and resources, following appropriate change control processes and proactively identify and resolve project issues and conflicts.
7. Escalate critical risks and issues to appropriate stakeholders and senior management.
8. Ensure compliance with organizational policies, sponsor requirements, research data-handling expectations, and our open-source release processes.
9. Establish and maintain strong relationships with project stakeholders, ensuring effective communication and collaboration.
10. and provide regular project status reports and updates to stakeholders, including progress, milestones, and key decisions. (Note: starts with "and". We'll keep as is but maybe remove leading "and"? It's part of sentence; we can keep.)
11. Manage resources to balance internal Digital Safety tasks with UL-wide organizational assignments.
12. Manage stakeholder expectations and address concerns or feedback.
13. Facilitate effective communication among project team members, ensuring alignment and clarity.
14. Conduct project reviews and lessons learned sessions to identify areas for improvement.
15. Document project outcomes, successes, and challenges for future reference.
16. Perform other duties as assigned.
We'll keep as is.
Now Requirements: "Professional Education And Experience Requirements For The Role Include Bachelor's degree in computer science and 3 years or more of hands-on experience as a software engineer."
We'll put that in a
.
Now Qualifications: The certifications: "PMP Certification (or equivalent) and four year or more in product and program management. PMP Certification or equivalent Agile certifications (e.g., Certified ScrumMaster), and Six Sigma certifications."
We'll put that in a
.
Now Skills: list of competencies from "What Makes You a Great Fit While no one candidate will embody every quality, the successful candidate will bring many of the following professional competencies and personal attributes:" then list:
- Strong leadership skills to guide and motivate team members towards project goals.
- Demonstrated ability to manage multiple concurrent projects across competing priorities.
- Excellent written and verbal communication skills.
- Relevant technical knowledge.
- Highly organized and skilled in managing multiple tasks, priorities, and deadlines.
- Strong problem-solving skills to analyze complex situations.
- Skilled negotiator to manage stakeholder expectations, resolve conflicts.
- Solid understanding of budget
for prose. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. Not present. Remove duplicated lines. Remove application instructions (none). Remove Job ID etc (none). Remove "Professional Education And Experience Requirements For The Role Include" maybe part of Requirements. We need to extract content. Let's parse the posting: Job Description: We have an exciting opportunity for a Technical Program Manager at UL Research Institutes, within our Digital Safety Research Institute (DSRI). This is a REMOTE opportunity The Technical Program Manager plans, executes, and brings projects to closure on behalf of Digital Safety. The Technical Program Manager oversees the entire technical project lifecycle, ensuring that projects are completed on time, within budget, and according to the specified scope and quality requirements. The Technical Program Manager manages resources, coordinates teams, and mitigates risks to deliver successful project outcomes. Then description of ULRI and DSRI. Then "What You’ll Learn And Achieve As the Technical Program Manager, you will play a key role in the rapid growth of UL as you:" followed by bullet-like sentences separated by commas and periods. This is responsibilities. Then "What Makes You a Great Fit While no one candidate will embody every quality, the successful candidate will bring many of the following professional competencies and personal attributes:" list of competencies. Then "Professional Education And Experience Requirements For The Role Include Bachelor's degree in computer science and 3 years or more of hands-on experience as a software engineer. PMP Certification (or equivalent) and four year or more in product and program management. PMP Certification or equivalent Agile certifications (e.g., Certified ScrumMaster), and Six Sigma certifications." Then "About UL Research Institutes And UL Standards & Engagement ..." (organization description). Could be part of About the role? Might be separate but we can include as About the role? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need sections: About the role (maybe includes description of role and organization). Responsibilities (the "What You’ll Learn And Achieve" list). Requirements (education/experience). Qualifications (maybe certifications?). Skills (competencies). Pay (salary range). We'll include.
We must not repeat job title as heading. Good.
We need to preserve all substantive info. So we need to include the description of ULRI and DSRI maybe under About the role? Or maybe we could have a separate section "About UL Research Institutes" but not in allowed headings. The allowed headings list is just examples; we can use those headings but not required to use exactly those? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings for sections. Probably we should map content to those headings. So we will have:
About the role
About the role
... includes the initial description and maybe organization description.
Responsibilities
- ... each duty.
Requirements
... education/experience.
Qualifications
... certifications? Actually the requirements already include certifications. But we could split: Requirements = education/experience; Qualifications = certifications. However the posting lumps them together. We need to preserve all info; we can put them under Requirements or Qualifications. To avoid duplication, we could put education/experience under Requirements, and certifications under Qualifications. That seems reasonable.
Skills
- ... competencies.
Pay
Salary Range $108,418.43-$149,075.34 Pay Type Salary
We must not include Benefits or Schedule. Now we need to extract the exact sentences. Let's copy the relevant parts. About the role: The first paragraph: "We have an exciting opportunity for a Technical Program Manager at UL Research Institutes, within our Digital Safety Research Institute (DSRI). This is a REMOTE opportunity The Technical Program Manager plans, executes, and brings projects to closure on behalf of Digital Safety. The Technical Program Manager oversees the entire technical project lifecycle, ensuring that projects are completed on time, within budget, and according to the specified scope and quality requirements. The Technical Program Manager manages resources, coordinates teams, and mitigates risks to deliver successful project outcomes." Then after that there is description of ULRI and DSRI. Should we include that? It's about the organization, not the role. Could be part of About the role? Might be better to include as part of About the role? The instruction: "About the role" heading likely expects description of the role and maybe the team. The organization description could be considered part of About the role? It's about ULRI and DSRI. I'd include it in About the role as it's substantive info about the organization. Thus About the role paragraph will include: the initial description plus the paragraphs about ULRI and DSRI. Let's copy those paragraphs exactly as they appear (preserving punctuation). We'll need to ensure we don't include boilerplate like "To learn more, visit our websites UL.org and ULSE.org." That's part of the organization description; it's substantive? It's a link; maybe we keep it? It's not boilerplate; it's info about where to learn more. Might be okay to keep. But it's not essential; but we can keep. The organization description: "UL Research Institutes At UL Research Institutes (ULRI), we expand the boundaries of safety science to create a more secure and sustainable world. For more than a century, we have studied the unintended consequences of innovation, designed solutions to mitigate risk and shared our findings with academia, scientists, manufacturers, and policymakers across industries. We identify critical safety and sustainability issues, asking tough questions because we believe a safer world begins with knowledge. Build a safer, more secure, and sustainable future with us. Join us and work with our Fire Safety teams who conduct the research required to produce that knowledge and put it into practice. Digital Safety Research Institute The Digital Safety Research Institute (DSRI) addresses unresolved safety risks and emerging dangers in the world’s digital ecosystem. We aim to help protect people from unwanted access to personal devices and privacy, algorithms, and disinformation threats by working to create a new digital safety ecosystem. DSRI is committed to sharing digital safety insights, collaborating with key stakeholders, and offering extensive outreach and education to help support safer digital environments for people everywhere. To learn more, visit our websites UL.org and ULSE.org." We'll include that. Now Responsibilities: The list after "What You’ll Learn And Achieve As the Technical Program Manager, you will play a key role in the rapid growth of UL as you:" then a series of clauses separated by commas and periods. Let's extract each duty as a bullet. The text: "Define project objectives, scope, deliverables, and success criteria and develop comprehensive project plans, including schedules, budgets, and resource allocation, Identifying project dependencies, risks, and mitigation strategies. Collaborate with engineering team leads, research leadership, and external partners (sponsors, researchers, engineers, and adopters) to gather requirements and establish clear communication channels. Coordinate and lead cross-functional project teams, assign tasks and responsibilities, and monitor project progress, ensuring adherence to timelines, budgets, and quality standards. Foster effective teamwork and collaboration among team members. Conduct regular project status meetings, providing updates to stakeholders and addressing any issues or concerns. Manage changes to project scope, schedule, and resources, following appropriate change control processes and proactively identify and resolve project issues and conflicts. Escalate critical risks and issues to appropriate stakeholders and senior management. Ensure compliance with organizational policies, sponsor requirements, research data-handling expectations, and our open-source release processes. Establish and maintain strong relationships with project stakeholders, ensuring effective communication and collaboration. and provide regular project status reports and updates to stakeholders, including progress, milestones, and key decisions. Manage resources to balance internal Digital Safety tasks with UL-wide organizational assignments. Manage stakeholder expectations and address concerns or feedback. Facilitate effective communication among project team members, ensuring alignment and clarity. Conduct project reviews and lessons learned sessions to identify areas for improvement. Document project outcomes, successes, and challenges for future reference. Perform other duties as assigned." We need to split into sensible bullet items. Each sentence seems to be a duty. We'll create. Now Qualifications: The certifications: "PMP Certification (or equivalent) and four year or more in product and program management. PMP Certification or equivalent Agile certifications (e.g., Certified ScrumMaster), and Six Sigma certifications." We'll put that in a
. Now Skills: list of competencies from "What Makes You a Great Fit While no one candidate will embody every quality, the successful candidate will bring many of the following professional competencies and personal attributes:" then list: - Strong leadership skills to guide and motivate team members towards project goals. - Demonstrated ability to manage multiple concurrent projects across competing priorities. - Excellent written and verbal communication skills. - Relevant technical knowledge. - Highly organized and skilled in managing multiple tasks, priorities, and deadlines. - Strong problem-solving skills to analyze complex situations. - Skilled negotiator to manage stakeholder expectations, resolve conflicts. - Solid understanding of budget