Service Delivery Manager

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Key info: - Job Title: Service Delivery Manager (we do NOT repeat as heading) - Department: Client Experience - Reporting to: Client Experience Director - Location: Baltimore, MD. Hybrid role with 3 days per week required in office. - Hours of work: Typical hours 8:30 AM to 5:30 PM Monday-Friday. Flexibility dependent on location. Additional hours may be necessary as needed. This position is exempt from overtime. - Compensation: $125,000 - $135,000 annually (commensurate with experience) plus up to 10% annual salary as bonus. - About InVita Healthcare Technologies (company description) – could be "About the role"? Actually "About the role" is a heading for overview of role. We have "Overview" section describing role. So we can put that under

About the role

maybe. Or we could use "Overview" but spec says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have sections: Responsibilities (Essential Functions/Key Responsibilities). Requirements (Previous Experiences/Qualifications). Qualifications maybe overlapping. Skills maybe from responsibilities? Benefits? Not explicit benefits besides maybe bonus? Could include Pay and maybe Benefits (bonus). Schedule: hours of work and hybrid requirement. We also have Compliance Requirements, Physical Demands, etc. Those could be omitted if not matching headings; but we must preserve ALL substantive information. However we cannot create new headings not in list. We could embed that info under appropriate existing headings like Requirements or maybe under a generic

without heading? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include other headings if we want, but better to stick to those. However we need to preserve all substantive info; we can include them as paragraphs under appropriate sections or as extra sections if they don't fit. But we could also add a

for "Compliance" etc if we want, but not in the list; maybe safer to keep only those headings and put other info under relevant sections like Requirements or Skills. We need to avoid repeating job title as heading. Also do not put Job ID/requisition numbers as headings (none). Remove boilerplate like EEO etc. We have an EEO statement at end; we should remove that. Also remove "Learn more at invitahealth.com." maybe not needed but it's substantive? It's company info; could be part of About the role? Might be considered boilerplate but it's about company. Might keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn more at invitahealth.com." is not exactly boilerplate but could be considered navigation? It's a link; maybe we can drop it as it's not essential to job description. However we need to preserve ALL substantive information; but that line is not substantive to the role. It's more marketing. I'd drop it. Also remove "This document does not create an employment contract..." etc legal boilerplate. Remove that. Now compile content. Sections: - About the role: overview paragraph(s) describing role: "The Service Delivery Manager is a senior, customer facing leadership role responsible for ensuring an excellent client experience from InVita..." plus maybe earlier overview. We have "Overview" paragraph: "The Service Delivery Manager is a senior, customer facing leadership roles responsible for ensuring an excellent client experience from InVita. The Service Delivery Manager requires strong executive presence, exceptional stakeholder management skills, commercial awareness, technical and product knowledge, and the ability to coordinate effectively across the organization to ensure the delivery of InVita services in line with contractual commitments. This role will operate in fast-paced, innovative customer environment that require a collaborative approach and a strong understanding of both the customer’s business and the solutions we provide." We can put that under About the role. - Responsibilities: list of essential functions/key responsibilities bullet points. We have categories: Relationship Management, Contractual Delivery, Service & Incident Management, Transition Management, Continuous Improvement, Account Management, Objectives. We need to extract bullet points. Let's list them: Relationship Management: - Owns the client relationship on behalf of InVita - Partner closely with customers as a trusted advisor who deeply understands their unique challenges and goals - Identify and build relationships with key influencers and decisionmakers within the executive teams of our customers Contractual Delivery: - Owns the client contact on behalf of InVita - Ensures services are delivered in line with contractual SLAs - Ensuring incidents and service requests are delivered in line with contractual SLAs. (duplicate? maybe combine) - Lead periodic Service Reviews with allocated clients following contract requirements Service & Incident Management: - Partner with the client to prioritize incidents and service requests. - Orchestrate across internal teams to ensure timely resolution of incidents and requests. - Manage key technical service activities, including quarterly security assessments and platform patching. - Agreeing annual product patching scope and schedules with the client and overseeing implementation as part of the Product Maintenance Lifecycle (typically 2–4 times per year). - Conduct annual disaster recovery testing. Transition Management: - Participate in defining and negotiating support frameworks for new customers. - Manage service transition into production for newly acquired customers. - Orchestrate internal tech teams to ensure smooth delivery of upgrades for clients. Continuous Improvement: - Proactively identify problem areas and ensure improvement plans are implemented and tracked. - Lead the review and improvement on existing KPIs/Metrics to ensure meaningful data is available to support the ongoing delivery of service. - Lead the review of existing processes, procedures and tooling to support best in class service delivery. Account Management: - Understand the client’s business roadmap and strategy - Conduct strategic customer reviews - Identifying commercial opportunities for additional or upgrades services and products to support sales growth. Objectives: - Maintain high level of client satisfaction. - Deliver per Service Level Agreement - Generate concrete upsell, cross sell opportunities for Commercial Teams to pursue - Improving Customer Support Services. - Define standard client service management framework. We can combine into a single

• list. - Requirements: maybe "Previous Experiences/Qualifications" section. List: - Bachelor’s degree and or equivalent professional experience across service management. - Knowledge of ITIL framework, qualification highly desirable. - Experience working in a managed service or regulated industry is beneficial. - Strong stakeholder and relationship management skills. - Ability to work unsupervised, operating at a senior management level. - Ability to make recommendations to resolve conflicts by using judgment that is consistent with InVita’s culture, policies, and procedures. - Innovation, Flexibility, and Adaptability – undertake tasks with a positive attitude and respond well to management and customer requests. - Good time management skills and the ability to deal with ambiguity and manage multiple priorities effectively. - Effective communication and collaboration skills suitable for liaising with colleagues and customers. - Fluency in English (both verbal and written). We could split into Requirements and Qualifications and Skills. But we have both Requirements and Qualifications headings allowed. We could put education/experience under Requirements, and skills under Skills. Qualifications maybe similar to Requirements. Let's decide: - Requirements: Bachelor’s degree or equivalent experience, Knowledge of ITIL framework (desirable), Experience in managed service/regulated industry (beneficial). - Qualifications: maybe same as Requirements? Could combine. But we have also "Strong stakeholder and relationship management skills." etc which are skills. Thus:

  Requirements

  • Bachelor’s degree or equivalent professional experience across service management.
  • Knowledge of ITIL framework (highly desirable).
  • Experience working in a managed service or regulated industry (beneficial).

  Skills

  • Strong stakeholder and relationship management skills.
  • Ability to work unsupervised, operating at a senior management level.
  • Ability to make recommendations to resolve conflicts using judgment consistent with InVita’s culture, policies, and procedures.
  • Innovation, flexibility, and adaptability – undertake tasks with a positive attitude and respond well to management and customer requests.
  • Good time management skills and ability to deal with ambiguity and manage multiple priorities effectively.
  • Effective communication and collaboration skills suitable for liaising with colleagues and customers.
  • Fluency in English (both verbal and written).
  We could also include "Compliance Requirements" maybe under Skills? But it's more about compliance; could be under Requirements? Might be better to add a separate section "Compliance" but not in list. However we could incorporate into Skills as "Knowledge of data protection and information security policies and procedures" etc. But we have details: "The employee is required to comply with all applicable data protection and information security policies and procedures relevant to its role. This includes actively supporting the principles of privacy by design and confidentiality when handling personal and health-related information, as applicable to its role. The Employee Shall Ensure appropriate handling of personal and health information in line with confidentiality and integrity standards; Report suspected data breaches or security incidents promptly; Follow established access control, data classification, and secure communication protocols; Participate in mandatory training and audits related to information security and data protection; Apply the company's best practices and guidance to safeguard information assets and support the company's compliance; Practice responsibilities as defined in the Information Security Policy in accordance with the employee’s role." That's substantive; we should preserve it. Could put under a section "Compliance" but not in allowed headings. Maybe we can put under "Requirements" as a bullet: "Must comply with data protection and information security policies, including privacy by design, breach reporting, access control, training, etc." That preserves info. - Benefits: we have bonus up to 10% annual salary. Also maybe other benefits not listed. So we can create Benefits section with that. - Pay: we have salary range $125,000 - $135,000 annually (commensurate with experience) plus up to 10% bonus. Since we have Benefits for bonus, Pay could be base salary. - Schedule: hybrid role 3 days per week in Baltimore office, typical hours 8:30 AM to 5:30 PM Mon-Fri, flexibility, additional hours as needed, exempt from overtime. We need to avoid filler like "commensurate with experience" in Pay section? 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. So we can include Pay section with the actual range; we can include the phrase "commensurate with experience" as part of the description? That's considered filler? It says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", ...). That means if the only content under Pay heading is "commensurate with experience" it's not allowed. But we have actual numbers, so it's okay to include that phrase as additional detail. Similarly for Schedule we have specifics. Now we need to output only HTML fragment, no /, no markdown. We'll produce:

  About the role