Director, Strategic Programs & Business Operations

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to extract content. Job description includes: Role Overview (maybe "About the role"?). The posting includes "Job Description Role Overview". We can treat that as "About the role". Then responsibilities: bullet points under "What You Get to Do in This Role" with subheadings like Strategic Program Ownership, Strategic Planning & Program Design, Governance & Leadership, Cross-Functional Orchestration, AI-Native Program Management, Process & Capability Building, Strategic Advisory. Those are responsibilities. Qualifications: "Qualifications Required Qualifications" includes experience, core competencies, etc. Also "Preferred Qualifications". We can combine into Requirements/Qualifications sections. The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. We have content for: About the role (role overview). Responsibilities (the bullet list). Qualifications (required qualifications, core competencies). Preferred qualifications maybe also part of Qualifications. Skills maybe not explicitly listed; we could omit Skills if no specific skill list. Benefits: mention health plans, 401(k) with match, ESPP, matching donations, flexible time away plan, family leave programs. Also variable/incentive compensation, equity. Pay: base pay range $221,200 - $387,100, plus equity, variable/incentive compensation. Schedule: not mentioned; we should not create Schedule section if no content. So omit Schedule. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: EEO, accommodations, export control, etc. Also remove "Additional Information Work Personas", "Equal Opportunity Employer", etc. Also remove "From Fortune..." etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as given, but we can format as lists. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. Thus:

  About the role

  Role Overview You will drive HRSD's most critical cross-functional priorities and strategic initiatives, operating at the intersection of strategy and execution and setting the standard for how high-impact programs are designed, governed, and run at scale. You identify, prioritize, and accelerate programs of the highest complexity with quantifiable impact on revenue, market position, and competitive advantage. You operate as an AI-native program manager and strategic operator who thinks deeply but loves getting into details. This is an individual contributor role with full strategic authority and accountability for outcomes.

  But we need to ensure we don't repeat sentences? It's okay. Then Responsibilities: Could be a single
  with each responsibility as
  • . However there are subheadings inside responsibilities. Could we keep subheadings as

    ? Not allowed; only

    for section headings. We could embed subheadings as bold text within

    maybe. But instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow. Probably better to keep responsibilities as a list without subheadings, but we need to preserve all substantive information; we can include the subheading text as part of the list item. Thus each responsibility area can be a list item containing the description. Let's extract each: Strategic Program Ownership: Drive large-scale, high-visibility cross-functional strategic initiatives for HRSD. Identify, prioritize, and accelerate programs of the highest complexity with quantifiable impact on revenue, market position, and competitive advantage. Translate business objectives into execution strategy both tactical and strategic and take full ownership of technical project planning and delivery from conception through transition to operations. Strategic Planning & Program Design: Organize complex, ambiguous problems into prioritized milestones, deliverables, dependencies, and success criteria. Design programs to deliver specific strategic outcomes and drive relentless accountability against them. Establish business rhythm and operating cadences (QBRs, monthly forums, weekly alignment) that connect strategy to execution. Set the standard for how high-impact programs are designed and governed at scale. Governance & Leadership: Establish governance frameworks and lead executive-level meetings and cross-functional events. Serve as the go-to source of leadership, transparency, and visibility, clearly communicating objectives, status, risks, and results while ensuring surgical execution and handoffs across workstreams. Ensure robust processes for managing risk, change, resources, and financials. Cross-Functional Orchestration: Develop trusted relationships with key stakeholders, technology leaders, and functional heads to drive focus on strategic program objectives and optimize program delivery. Facilitate strategic alignment across product, engineering, design, research, marketing, and GTM. Identify and resolve cross-functional dependencies before they become blockers. Hold resources accountable for their responsibilities within programs. AI-Native Program Management: Operate as an AI-native program manager. Use AI to synthesize intelligence across workstreams, surface risk signals early, ensure data informs decision-making, draft and tailor communications at speed, direct AI agents, and provide leadership with actionable, forward-looking intelligence. Develop software-based or AI-driven solutions to replace repeatable operational tasks. Foster an environment of autonomy, transparency, and continuous improvement. Process & Capability Building: Develop and implement scalable processes, templates, and training to ensure program delivery and process adoption. Oversee change management efforts, guiding teams through organizational transitions. Continuously assess organizational effectiveness and implement improvements that increase speed, clarity, and accountability. Strategic Advisory: Serve as a strategic thought partner to the GM and executive leadership. Prepare analysis and recommendations on key business questions. Help leadership think clearly about strategic choices and tradeoffs. Provide data-driven insights that surface blind spots and unlock opportunities. Now Qualifications: Required Qualifications: Experience 12+ years of work experience in Technical Program Management, Product Management, Strategy, Operations, or related roles. Proven track record managing large-scale, complex, cross-functional initiatives with quantifiable business impact in high-growth or enterprise technology environments. Demonstrated success translating business strategy into execution plans and delivering on metrics. Core Competencies: list bullet points: High energy and disciplined execution skills. Willingness to do whatever it takes to deliver results. Ability to see the big picture while being execution-oriented and detail-focused. Strategic thinking and business acumen, comfortable with P&L, metrics, and business strategy. Ability to conceptualize, develop, drive, coordinate, and manage large, complex, cross-functional programs from ambiguity through delivery. Effective communicator, written and verbal, who uses AI tools to draft, refine, and tailor communications. Able to convey complex ideas clearly across executive and working-level audiences at speed. Comfortable directing AI agents and iterating on outputs in ambiguous, high-stakes environments. Strong collaboration, relationship-building, and influence skills. Masterful at bringing people together across functions, levels, and geographies without direct authority. Work independently and be highly productive with minimal oversight. Sound judgment and discretion with confidential information. Experience leveraging or critically thinking about how to integrate AI into work processes, decision-making, and problem-solving—including AI-powered tools, workflow automation, AI-driven insights, and exploring AI's potential impact on program management and organizational effectiveness. Preferred Qualifications: Experience in a startup or rapidly growing company. Strong financial acumen and experience with budget management. Proficiency with data analysis and business intelligence tools. MBA or equivalent advanced degree. Experience designing and scaling operating models. Expertise in the enterprise software/SaaS industry. We could combine Required and Preferred into a Qualifications section, maybe separate sub-sections? But we only have headings for Qualifications (maybe also Requirements). The instruction includes both Requirements and Qualifications headings. We could put required experience under Requirements, and core competencies under Qualifications? Or we could put all under Qualifications. But we need to follow instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need both Requirements and Qualifications sections if we have content. We could treat Requirements as the experience and proven track record etc. Qualifications as core competencies and preferred qualifications. Or we could put required qualifications under Requirements, and preferred under Qualifications. Let's do that. Thus:

    Requirements

    Experience 12+ years of work experience in Technical Program Management, Product Management, Strategy, Operations, or related roles. Proven track record managing large-scale, complex, cross-functional initiatives with quantifiable business impact in high-growth or enterprise technology environments. Demonstrated success translating business strategy into execution plans and delivering on metrics.

    Qualifications

    • High energy and disciplined execution skills.
    • Willingness to do whatever it takes to deliver results.
    • Ability to see the big picture while being execution-oriented and detail-focused.
    • Strategic thinking and business acumen, comfortable with P&L, metrics, and business strategy.
    • Ability to conceptualize, develop, drive, coordinate, and manage large, complex, cross-functional programs from ambiguity through delivery.
    • Effective communicator, written and verbal, who uses AI tools to draft, refine, and tailor communications.
    • Able to convey complex ideas clearly across executive and working-level audiences at speed.
    • Comfortable directing AI agents and iterating on outputs in ambiguous, high-stakes environments.
    • Strong collaboration, relationship-building, and influence skills.
    • Masterful at bringing people together across functions, levels, and geographies without direct authority.
    • Work independently and be highly productive with minimal oversight.
    • Sound judgment and discretion with confidential information.
    • Experience leveraging or critically thinking about how to integrate AI into work processes, decision-making, and problem-solving—including AI-powered tools, workflow automation, AI-driven insights, and exploring AI's potential impact on program management and organizational effectiveness.

    But we also have Preferred Qualifications. Could we add another

    Preferred Qualifications? Not in allowed headings. Could we incorporate them into Qualifications as additional list items, maybe label them as "Preferred". But we must not invent headings. We could add a note inside list items: "Preferred: Experience in a startup..." but that changes content. Better to add a separate section maybe "Qualifications" includes both required and preferred; we can label them within list items. However the instruction says preserve ALL substantive information; we can include preferred qualifications as part of Qualifications section, maybe as a sub-list with a note. That's acceptable. Thus we can add list items for preferred qualifications, maybe prefixed with "(Preferred) ". That preserves info. Now Benefits: We have health plans, flexible spending accounts, 401(k) Plan with company match, ESPP, matching donations, flexible time away plan and family leave programs. Also variable/incentive compensation, equity (when applicable). Also maybe "We also offer health plans...". We'll create a Benefits section. Pay: base pay range $221,200 - $387,100, plus equity (when applicable), variable/incentive compensation. Also note that base pay shown is a guideline, individual total compensation will vary based on qualifications, skill level, competencies, and work location. Also mention that compensation is based on geographic location and subject to change. We'll include that. Schedule: no content, so omit. Skills: no explicit skill list; we could omit Skills section. Now we need to ensure we don't include boilerplate like EEO, accommodations, export control, etc. Also remove "Additional Information Work Personas", "Equal Opportunity Employer", etc. Also remove "From Fortune..." etc. Now produce HTML fragment. Let's craft:

    About the role

    Role Overview You will drive HRSD's most critical cross-functional priorities and strategic initiatives, operating at the intersection of strategy and execution and