Senior Program Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must not include boilerplate like EEO, legal, scam warnings, application instructions. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About Crunchyroll (company description) - maybe not needed as a section? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections only if posting has real specific content for them. The posting includes "About The Role" (description). That's similar to "About the role". So we can have

About the role

with paragraph(s) describing role. - Core Areas of Responsibility: list of duties. That's responsibilities. - About You: list of qualifications/experience/skills. Could be split into Requirements, Qualifications, Skills. We need to decide. The posting includes: "About You We get excited about candidates like you because you have:" then a long list of requirements: 8+ years experience, BS degree, etc. Also includes "Nice to haves". So we can put Requirements (mandatory) and maybe Skills (tools). Qualifications maybe education. But we must not invent sections with placeholder. We need to include sections only when there is real specific content. We have Benefits: "Why you will love working at Crunchyroll" includes list of benefits. So we can have Benefits section. Pay: The posting does not mention specific salary or pay. It says "Receive a great compensation package including salary plus performance bonus earning potential, paid annually." That's somewhat vague but mentions compensation package. It's not a specific number, but it's still content about pay. The instruction: 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. The posting states "Receive a great compensation package including salary plus performance bonus earning potential, paid annually." That's not a specific number but it's stating compensation package. Is that considered filler? It's vague but still mentions compensation. The instruction says avoid placeholder like "commensurate with experience". This is similar but not exactly that phrase. It says "great compensation package including salary plus performance bonus earning potential". That's still vague but maybe acceptable as content. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation package, so we can include Pay section with that sentence. Schedule: The posting mentions "This is a full-time, on-site position based in Dallas, TXStandard business hours with occasional travel for vendor meetings or project support as needed." That's schedule info: full-time, on-site, standard business hours, occasional travel. So we can include Schedule section. Now we need to format. We must not include repeated job title. No markdown. We need to output only HTML fragment. Let's craft:

About the role

We are seeking an experienced, detail-oriented Senior Program Manager with a passion for leading teams, coordinating information, and solving problems across the IT organization. This role will be based on-site at least 3 days per week in our Dallas office and will play a critical role in managing Governance, Risk, and Compliance (GRC) initiatives. Candidates must be able to work onsite at our Dallas, TX location. The ideal candidate brings a strong program management background, has demonstrated the ability to deliver against company strategic goals, and drives value through efficient process and data-driven insights. This position will report into the Senior Director of Program Management for the Technology Solutions group and will work closely with various teams across the business to support pivotal initiatives.

Responsibilities

• Organize, plan and track ongoing projects and strategic initiatives for the Technology Solutions teams
• Oversee the day-to-day progress of projects and initiatives with regard to schedule, scope, and process - and organizes information so it’s digestible for a globally distributed team
• Effectively lead meetings, track next actions, and proactively follow up on action items
• Build and leverage effective partnerships across technical and business communities
• Serve as a key liaison with relevant business groups to facilitate planning and collaboration between teams, align on goals, identify dependencies, mitigate risks, and effectively communicate regular updates to all stakeholders
• Demonstrate an understanding of the business and its structure, processes, and tools, and how initiatives positively impact the overall business
• Establish and maintain best practices and repeatable processes to increase efficiency for teams in conjunction with the larger Technology Solutions group

Requirements

• 8+ years experience as project or program manager
• BS degree or equivalent experience required, MS degree preferred
• Experience working with globally distributed teams
• Working knowledge and understanding of key concepts and best practices for program management
• Excellent written and verbal communication skills at all levels, including Senior and C-level stakeholders
• Governance & Risk Management execution experience including Risk Assessment Methodologies, Risk Register Management, Risk Treatment Planning, and Control Design & Evaluation
• Experience with Risk and Regulatory compliance frameworks such as NIST CSF 2.0, NIST SP 800-53, ISO 27001/27002, SOC 2, PCI DSS, SOX ITGC, CCPA/CPRA, GDPR, EU Cyber Resilience Act (CRA), HIPAA, AI Governance, and Privacy by Design
• Security Program Management including Security Governance and Maturation, Policy & Standards Management, Control Framework Development, Security Metrics & KPIs, Security Roadmaps, Program Maturity Assessments, Security by Design, Privacy by Design
• Audit & Assurance experience including Internal Audit Coordination, External Audit Management, Evidence Collection, Control Testing, Remediation Tracking, Audit Readiness, and Continuous Monitoring
• Vendor & Third-Party Security including Vendor Risk Assessments, Security Questionnaires, Contract Security Requirements, DPAs, Security Riders, Vendor Scorecards, and Continuous Vendor Monitoring
• Must be self-motivating, self-sufficient and have the strong ability to work effectively as an individual or as part of a team
• Accuracy, acute attention to detail, and ability to work with minimal direct supervision
• Ideal candidate is inquisitive, organized, meticulous and has a desire for continued self-improvement and development of new skills
• Ability to demonstrate a calm and cool demeanor when managing multiple projects and deliverables
• Outstanding time management skills to balance multiple, changing priorities
• Experience with both agile and waterfall methodologies, and knowing when to apply each, preferred
• Experience with tools such as JIRA, Confluence, Smartsheet and Google Suite, a plus

We could also separate Qualifications (education) and Skills (tools). But we have many items; maybe we can split: Qualifications: education + experience; Skills: tools and methodologies. However the instruction: Prefer a few substantive sections over many thin ones. So maybe keep Requirements as above and not split further. But we also have "Nice to haves: Prior experience in or managing projects related to technology or streaming, a plus Professional certification such as PMP, CSM". Could be included in Requirements or maybe Skills. Since it's nice to have, we could still include under Requirements as optional? Might be okay. Now Benefits:

Benefits

• Receive a great compensation package including salary plus performance bonus earning potential, paid annually.
• Flexible time off policies allowing you to take the time you need to be your whole self.
• Generous medical, dental, vision, STD, LTD, and life insurance
• Health Saving Account HSA program
• Health care and dependent care FSA
• 401(k) plan, with employer match
• Employer paid commuter benefit
• Support program for new parents
• Pet insurance and some of our offices are pet friendly!

Pay: Actually we already included compensation package in Benefits. But the instruction says Pay section separate if posting states them. The posting states compensation package; we could either put that under Pay or Benefits. Since we already have Benefits, we could move compensation to Pay and keep other benefits under Benefits. But the instruction: Prefer a few substantive sections over many thin ones. Having both Pay and Benefits may be thin. However we have substantive content for both: Pay (compensation package) and Benefits (list). Could be okay. But we need to avoid duplication. The compensation package line appears in the "Why you will love working at Crunchyroll" bullet list. It's first bullet. If we separate Pay, we would have that line only. Benefits would be the rest. Let's do:

Pay

Receive a great compensation package including salary plus performance bonus earning potential, paid annually.

Benefits

• Flexible time off policies allowing you to take the time you need to be your whole self.
• Generous medical, dental, vision, STD, LTD, and life insurance
• Health Saving Account HSA program
• Health care and dependent care FSA
• 401(k) plan, with employer match
• Employer paid commuter benefit
• Support program for new parents
• Pet insurance and some of our offices are pet friendly!

Schedule:

Schedule

This is a full-time, on-site position based in Dallas, TX. Standard business hours with occasional travel for vendor meetings or project support as needed.

We also have "About The Team" description. Could be included as a section? Not in the list of allowed headings. The instruction only mentions those specific headings; we should not add other headings. So we should omit About The Team, About Our Values, etc. as they are not requested headings. However we must preserve ALL substantive information; but we cannot add headings not in list. The instruction says: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should only use those headings. It does not forbid other headings, but says "use

for section headings (e.g. ...)". It might be okay to add other headings but they'd deviate from the examples. Safer to stick to those headings only. So we omit About The Team etc. Thus final HTML includes sections: About the role, Responsibilities, Requirements, Pay, Benefits, Schedule. Possibly also Qualifications and Skills if we split. But we have many items in Requirements; we could split into Requirements (experience) and Qualifications (education) and Skills (tools). However that would be many sections. The instruction: Prefer a few substantive sections over many thin ones. So better to keep one Requirements section that includes education, experience, skills, etc. Thus final output: sections About the role, Responsibilities, Requirements, Pay, Benefits, Schedule. Check that we didn't include any boilerplate: we omitted About Crunchyroll, About The Team, About Our Values, EEO, legal, scam warnings, application instructions, etc. We kept all substantive info: role description, responsibilities, requirements (including all listed), pay, benefits