Director, Enterprise SaaS Delivery

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove application instructions, navigation, cookie, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About the role: The first paragraph(s) describing role: "The Director Enterprise SaaS Delivery leads technical delivery and demand-shaping activities for assigned enterprise SaaS applications. The role supervises a Technical Delivery Manager and a Technical Product Owner for SaaS solutions, ensuring vendor releases, integrations, technical dependencies, and operational readiness are managed with discipline. The Director also partners with Product Management, Enterprise Architecture, and Technical Business Management to define and analyze new requests before they enter the delivery pipeline, helping the business confirm the problem, high-level requirements, process impacts, and expected value needed for a sound business case." That's about the role. - Responsibilities: The "Essential Responsibilities" section with sub-bullets: Leadership and Delivery Governance, Business Analysis and Demand Shaping, SaaS Application and Vendor Oversight, Operational Excellence. Each has bullet points. We need to output a

• list for any list of duties/requirements/benefits. So we can combine all responsibilities into a list. - Requirements: The "Qualifications" section includes Required and Preferred. Could split into Requirements (maybe required) and Qualifications (maybe preferred). But the instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have Required qualifications: Bachelor's degree, 8+ years experience, etc. Also Preferred: experience with sales tech, CRM, etc., experience with ServiceNow, Jira, Azure DevOps, certifications. We also have "Role Boundaries" which is more about accountability; could be part of Responsibilities or maybe Qualifications? Probably part of Responsibilities (governance). But we can include as part of Responsibilities. We have Pay: "The base salary compensation range for this role is $140,000 to $190,000. Final compensation for this role will be determined by various factors such as a candidate’s relevant work experience, skills, certifications, and geographic location." We have Benefits: "Full time positions are eligible for benefits that include participation in a retirement plan, life and disability insurance, health, dental and vision plans, flexible spending accounts, 15 paid vacation days, 2 paid personal days, 9 paid holidays, 40 hours of paid sick leave, parental leave, and employee stock purchase plan." We have Schedule: Not explicitly mentioned; maybe "Full time positions" implies full-time schedule. But we should not create Schedule section unless posting actually states them. It does not give schedule details beyond full-time. Could we infer schedule? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Benefits and Pay. For Schedule, it does not state schedule specifics (like hours, shift). It says "Full time positions are eligible for benefits". That implies full-time schedule but not explicit schedule details. Safer to omit Schedule section because not explicitly stated. However we could include a short line "Full-time" but that might be considered filler? 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. Since schedule is not explicitly stated, we should not create a Schedule section. Skills: Could be derived from qualifications? There's no explicit Skills section. Might combine with Qualifications? But we need to include Skills heading only if there is real specific content. The posting does not have a separate Skills bullet list. However we could treat "Strong judgment, stakeholder management, written communication, facilitation, and executive-level reporting skills." as skills. That's under Qualifications Required. So we could put those under Skills heading. But we also have Required and Preferred qualifications. Might be better to split: Requirements (required qualifications), Qualifications (preferred), Skills (specific skills like communication, stakeholder management). However the instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one Qualifications section? But we have headings for both Requirements and Qualifications. We need to decide. We could make: - About the role (h3) - Responsibilities (h3) with ul list - Requirements (h3) with ul list of required qualifications - Qualifications (h3) with ul list of preferred qualifications/certifications - Skills (h3) maybe not needed if we covered skills in Requirements/Qualifications. But we have explicit skills statement; could put under Skills. - Benefits (h3) with ul list - Pay (h3) with p We must not include Schedule. We must not include boilerplate like EEO, About Sinclair, About the Team, visa sponsorship note, etc. We must preserve all substantive information: ensure we don't lose any details. Let's extract substantive content: About the role paragraph: as above. Responsibilities: list items: From Leadership and Delivery Governance: - Lead, coach, and evaluate the Technical Delivery Manager and Technical Owner; establish clear accountabilities, operating rhythms, priorities, and development plans. - Set the delivery governance for assigned SaaS applications, including release planning, dependency management, risk escalation, technical readiness, deployment coordination, and post-release review. - Review vendor roadmaps, release calendars, lifecycle notices, and implementation plans; align timing with product priorities, business operating periods, and change-management needs. - Provide leadership visibility into delivery performance, key technical risks, vendor commitments, operational trends, and decisions requiring escalation. - Ensure technical delivery work follows applicable SDLC, change-management, security, architecture, and production-readiness standards. Business Analysis and Demand Shaping: - Partner with Product Management, Architecture, and Technical Business Management to assess new project and enhancement requests before commitment to a delivery roadmap. - Lead or direct high-level business analysis, including current and future-state process modeling, stakeholder analysis, problem definition, process impacts, assumptions, constraints, and dependency identification. - Guide development of epics, use cases, and high-level business requirements that give the business a sufficiently clear basis for scope, estimates, options, and business-case decisions. - Challenge incomplete requests constructively and help sponsors resolve gaps in objectives, process ownership, value, feasibility, data needs, integration needs, security considerations, and change impacts. - Coordinate technical discovery across product teams and shared technology functions so estimates and business cases reflect credible technical scope and dependencies. SaaS Application and Vendor Oversight: - Provide senior oversight for third-party SaaS vendors, including delivery commitments, technical documentation, escalation management, release quality, support responsiveness, and roadmap alignment. - Ensure the Sales SaaS Technical Owner maintains a reliable technical operating model for the application, including integrations, environments, access, monitoring, release readiness, documentation, and vendor coordination. - Work with Product Management to ensure technical delivery activities support product roadmaps and business outcomes without duplicating product ownership of prioritization, functional requirements, or value realization. - Partner with infrastructure, network, security, identity, data and integration, and service desk functions to address cross-functional dependencies and recurring operational issues. Operational Excellence: - Review release outcomes, incidents, and operational trends; direct corrective actions that improve application reliability, supportability, and user experience. - Establish practical measures for delivery reliability, release success, dependency readiness, incident escalation, vendor performance, and documentation quality. - Ensure Tier 2 product teams retain ownership for application support coordination, including vendor support where applicable, while the director provides governance and escalated operational oversight. Also Role Boundaries could be included but maybe not needed as it's more about accountability; but it's substantive. Could add as a bullet under Responsibilities or separate? Might be considered part of Responsibilities. We'll include as bullet. Role Boundaries: - The Director is accountable for technical delivery leadership, upstream analysis, vendor and dependency governance, and operational oversight for the assigned SaaS portfolio. - Product Management remains accountable for product strategy, prioritization, functional requirements, and value realization. - Technical Business Management retains financial and portfolio-management responsibilities, including application budgets. - Product teams retain Tier 2 application support responsibilities. - Infrastructure, security, service desk, and engineering teams remain accountable for their specialized technical services. Now Requirements (required qualifications): - Bachelor's degree in information technology, business, computer science, or related field; equivalent experience may be considered. - Eight or more years of progressively responsible experience in enterprise application delivery, technical program management, SaaS delivery, systems integration, business analysis, or technology operations, including at least three years leading people or teams. - Experience working with third-party SaaS vendors and coordinating complex releases, integrations, and cross-functional technical dependencies. - Demonstrated ability to translate business needs into process models, epics, use cases, and high-level requirements that support decision making and business cases. - Strong judgment, stakeholder management, written communication, facilitation, and executive-level reporting skills. Preferred qualifications (could be Qualifications heading): - Experience supporting sales technology, CRM, revenue operations, advertising, media, or other commercially critical SaaS platforms. - Experience with ServiceNow, Jira, Azure DevOps, and enterprise architecture or process-modeling methods. - PMP, ITIL, Scrum, SAFe, CBAP, or comparable certification. Skills: maybe we could extract specific skills like "Strong judgment, stakeholder management, written communication, facilitation, and executive-level reporting skills." but that's already in Required. Could also include "experience working with third-party SaaS vendors", etc. But we might not need separate Skills if we already covered. However the instruction says we can include Skills heading if there is real specific content. We have that content; but it's duplicated. To avoid duplication, maybe we put skills under Skills heading and not repeat under Requirements. But then we would lose the required qualification statement about strong judgment etc. We could move that to Skills and keep other qualifications under Requirements. Let's decide. We could structure: - Requirements (h3): education, years experience, vendor experience, ability to translate business needs. - Skills (h3): strong judgment, stakeholder management, written communication, facilitation, executive-level reporting. - Qualifications (h3): preferred experience, certifications. That avoids duplication. Now Benefits (h3): list items. Pay (h3): p with salary range and note about final compensation. We must not include Schedule. Now produce HTML fragment: use

  for each section heading, then content:

  for prose,

  • for lists. We need to ensure we don't include any extra text outside HTML. Let's craft. First, About the role:

    About the role

    The Director Enterprise SaaS Delivery leads technical delivery and demand-shaping activities for assigned enterprise SaaS applications. The role supervises a Technical Delivery Manager and a Technical Product Owner for SaaS solutions, ensuring vendor releases, integrations, technical dependencies, and operational readiness are managed with discipline. The Director also partners with Product Management, Enterprise Architecture, and Technical Business Management to define and analyze new requests before they enter the delivery pipeline, helping the business confirm the problem, high-level requirements, process impacts, and expected value needed for a sound business case.

    Second, Responsibilities:

    Responsibilities

    then each bullet as
    • . Need to include all bullets from above plus Role Boundaries. Let's list them: - Lead, coach, and evaluate the Technical Delivery Manager and Technical Owner; establish clear accountabilities, operating rhythms, priorities, and development plans. - Set the delivery governance for assigned SaaS applications, including release planning, dependency management, risk escalation, technical readiness, deployment coordination, and post-release review. - Review vendor roadmaps, release calendars, lifecycle notices, and implementation plans;