Service Delivery Manager
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for any list of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
The posting has:
- Company Overview (Zones description)
- Position Overview (Service Delivery Manager role description)
- "What You Will Do As The Service Delivery Manager" - this is responsibilities/duties
- "What You Will Bring To The Team" - this is requirements/qualifications
- Salary range: "Qualified candidates can expect a salary range up to $170,000"
- Benefits section: "Zones Offers a Comprehensive Benefits Package" with details
- EEO/legal boilerplate at the end (should be removed)
I need to structure this into appropriate sections. The job title is "Service Delivery Manager" but I shouldn't repeat it as a heading.
Possible sections:
- About the role (or Position Overview) - for the position overview paragraph
- Responsibilities - for "What You Will Do"
- Requirements (or Qualifications) - for "What You Will Bring To The Team"
- Pay - for salary range
- Benefits - for benefits package
I should not include EEO/legal boilerplate.
Let me create the HTML:
First, a brief company overview paragraph? The company overview is quite long. I could include it as a short paragraph under an "About the company" section, but the instructions say to use specific headings like "About the role". The company overview is more about the company than the role. I could fold it into a short paragraph at the beginning or under "About the role". But the instructions say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention "About the company". However, the company overview is substantive information. I could include it as a
before the first heading, or under a heading like "About the company". But the example headings don't include that. The instructions say "include a section ONLY when the posting has real, specific content for it". The company overview is real content. I think I'll include it as a short paragraph at the top, maybe under a heading "Company Overview" but that's not in the example list. The example list is not exhaustive; it says "e.g." So I can use other headings. But to be safe, I'll include company overview as a paragraph before the first heading, or under "About the role"? Actually, the position overview is separate. I'll create a "Company Overview" heading (h3) and put the company description there. That seems appropriate.
But the instructions: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. I'll use "Company Overview" as an h3.
Now, the position overview: that's "About the role". I'll use "About the role" heading.
Responsibilities: "What You Will Do" - list of bullet points.
Requirements: "What You Will Bring To The Team" - list of bullet points.
Pay: salary range up to $170,000.
Benefits: benefits package details.
I need to convert the bullet points into - . The responsibilities are listed as sentences separated by periods. Actually, they are separated by line breaks in the text. In the input, they are separated by periods and line breaks? Let's look: "Lead large, complex, enterprise-wide projects & managed services engagements through all project lifecycle phases.Responsible for building and maintaining strong client relationships at all levels, including C-level, with the objective of being a trusted business partner.Accountable for meeting revenue, profit, and growth objectives and for improving overall customer satisfaction targets.Establish and maintain relationships and communications at all levels of the organization.Optimization of resource allocation, scheduling, and utilization.Support senior executives across business lines in strategic analysis, project scoping and approach definition.Prepare reports for upper management regarding project performance and financial status.Plan and facilitate internal and client facing team meetings, working sessions and communicate output of such.Identification of risks, and development/facilitation of risk mitigation actions.Development and facilitation of change management plans/actions.Be the liaison between Zones and our customers for business, technical, and other project team meetings.Serve as escalation point for issues beyond project team authority; resolves conflicts involving scheduling, resources, or technical issues.Communicate with clients to assess satisfaction levels with products and services.Participates in customer meetings as sales support to develop new and grow existing business opportunities.Responsible for overall project management, including all phases of PMI project management concepts: Project Integration, Scope, Time Cost, Quality, Resources, Communications, Risk and Procurement. Set and continually manage project expectations with team members and other stakeholders.Develop and implement systems and processes to support meeting client SLAs.Train, mentor and coach subordinates and peers to deliver services and projects based on industry methodology and accepted best practices.Manage IT Service Levels and Operational Requests from the Customer.Travel to customer sites as required."
These are separate bullet points. I'll split them into individual list items. They are separated by periods but also each seems to be a separate duty. I'll treat each sentence as a separate bullet? Actually, they are separated by line breaks in the original? In the text provided, they are concatenated with periods. But looking at the raw text, each duty is on a new line? The user pasted as a block. I'll assume each distinct duty is separated by a period and capital letter. But better to split by the periods that start a new duty. However, some duties have multiple sentences. For example: "Responsible for overall project management, including all phases of PMI project management concepts: Project Integration, Scope, Time Cost, Quality, Resources, Communications, Risk and Procurement. Set and continually manage project expectations with team members and other stakeholders." That's two sentences but likely one bullet. Actually, the original formatting might have bullet points. I'll split by the line breaks as they appear in the user message. In the user message, the responsibilities are written as a paragraph with each duty separated by a period and no line breaks. But the requirements are similarly formatted. I need to parse them into individual items. I'll split by the pattern of a period followed by a capital letter (but careful with abbreviations like PMI, ITIL). This is tricky. Since the instruction says "Preserve ALL substantive information", I should keep the exact text but format as list items. I'll split the responsibilities into separate list items based on the original bullet points (if they were bullet points). In the text, they are not bullet points but a paragraph. However, the heading "What You Will Do As The Service Delivery Manager" suggests a list. I'll split each distinct responsibility as a separate list item. I'll use the sentences as they are, but combine sentences that belong together. Let me manually separate:
1. Lead large, complex, enterprise-wide projects & managed services engagements through all project lifecycle phases.
2. Responsible for building and maintaining strong client relationships at all levels, including C-level, with the objective of being a trusted business partner.
3. Accountable for meeting revenue, profit, and growth objectives and for improving overall customer satisfaction targets.
4. Establish and maintain relationships and communications at all levels of the organization.
5. Optimization of resource allocation, scheduling, and utilization.
6. Support senior executives across business lines in strategic analysis, project scoping and approach definition.
7. Prepare reports for upper management regarding project performance and financial status.
8. Plan and facilitate internal and client facing team meetings, working sessions and communicate output of such.
9. Identification of risks, and development/facilitation of risk mitigation actions.
10. Development and facilitation of change management plans/actions.
11. Be the liaison between Zones and our customers for business, technical, and other project team meetings.
12. Serve as escalation point for issues beyond project team authority; resolves conflicts involving scheduling, resources, or technical issues.
13. Communicate with clients to assess satisfaction levels with products and services.
14. Participates in customer meetings as sales support to develop new and grow existing business opportunities.
15. Responsible for overall project management, including all phases of PMI project management concepts: Project Integration, Scope, Time Cost, Quality, Resources, Communications, Risk and Procurement.
16. Set and continually manage project expectations with team members and other stakeholders.
17. Develop and implement systems and processes to support meeting client SLAs.
18. Train, mentor and coach subordinates and peers to deliver services and projects based on industry methodology and accepted best practices.
19. Manage IT Service Levels and Operational Requests from the Customer.
20. Travel to customer sites as required.
That seems reasonable.
Similarly for requirements:
"Bachelor’s Degree and a minimum of 10 years’ experience with Service Delivery, Project Management or business consulting, MBA preferred, or equivalent education, training or experience preferred.Exceptional communication skills and experience working with executives and C-level stakeholders.Demonstrated knowledge of PMBOK, including risk management, change order management, performance measurements, financial and qualitative analysis, and project/people management.Extensive experience in managing large long-term Managed Services engagements, managing profitability, and successfully meeting the client's expectations and goals. ITIL V3 or 4 certifications preferredAbility to manage multiple priorities while staying aligned to the project objectives.Leadership skills that would be applied across the client enterprise and across multiple project environments, to influence client's expectations and goals.Experience with business transformation and change management. Experience and success in managing service level agreements with penalties.Experience successfully collaborating in a pre-sales environment with technical resources.Demonstrated ability to translate technical requirements into a detailed quote or Statement of Work.Ability to effectively prioritize and execute tasks in a high-pressure environment.Ability to implement effective personnel/project risk management and safety strategies.Ability to work and adapt to change in a fast-paced environment.Proficient in Microsoft Word, Excel, PowerPoint, Outlook and Project.Must have skills in five key general management areas of client relationship management, consultative selling, financial / business management, portfolio / project management and team management and are usually the primary focal point for all activities on a large complex contract.PMP Certification.Knowledge of and experience in all areas of Datacenter, Network, Servers, Storage, backup, etc preferred.Experience coordinating sub-contracted vendors and offshore teams."
Split into list items:
1. Bachelor’s Degree and a minimum of 10 years’ experience with Service Delivery, Project Management or business consulting, MBA preferred, or equivalent education, training or experience preferred.
2. Exceptional communication skills and experience working with executives and C-level stakeholders.
3. Demonstrated knowledge of PMBOK, including risk management, change order management, performance measurements, financial and qualitative analysis, and project/people management.
4. Extensive experience in managing large long-term Managed Services engagements, managing profitability, and successfully meeting the client's expectations and goals.
5. ITIL V3 or 4 certifications preferred.
6. Ability to
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - Company Overview (Zones description) - Position Overview (Service Delivery Manager role description) - "What You Will Do As The Service Delivery Manager" - this is responsibilities/duties - "What You Will Bring To The Team" - this is requirements/qualifications - Salary range: "Qualified candidates can expect a salary range up to $170,000" - Benefits section: "Zones Offers a Comprehensive Benefits Package" with details - EEO/legal boilerplate at the end (should be removed) I need to structure this into appropriate sections. The job title is "Service Delivery Manager" but I shouldn't repeat it as a heading. Possible sections: - About the role (or Position Overview) - for the position overview paragraph - Responsibilities - for "What You Will Do" - Requirements (or Qualifications) - for "What You Will Bring To The Team" - Pay - for salary range - Benefits - for benefits package I should not include EEO/legal boilerplate. Let me create the HTML: First, a brief company overview paragraph? The company overview is quite long. I could include it as a short paragraph under an "About the company" section, but the instructions say to use specific headings like "About the role". The company overview is more about the company than the role. I could fold it into a short paragraph at the beginning or under "About the role". But the instructions say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention "About the company". However, the company overview is substantive information. I could include it as a
before the first heading, or under a heading like "About the company". But the example headings don't include that. The instructions say "include a section ONLY when the posting has real, specific content for it". The company overview is real content. I think I'll include it as a short paragraph at the top, maybe under a heading "Company Overview" but that's not in the example list. The example list is not exhaustive; it says "e.g." So I can use other headings. But to be safe, I'll include company overview as a paragraph before the first heading, or under "About the role"? Actually, the position overview is separate. I'll create a "Company Overview" heading (h3) and put the company description there. That seems appropriate. But the instructions: "use