Service Delivery Manager

We need to output HTML fragment with sections: About the role? Actually we have sections: About Fluid2Chip (company description) maybe not needed? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - About Fluid2Chip (company description) - maybe "About the role"? Actually "About the role" is generic; but we have a "Job Summary". Could map to "About the role". We'll include a section with heading

  About the role

  and then a

  containing the Job Summary paragraph. - Responsibilities: The "Essential Functions" with subcategories (Project Execution & PM Leadership, Client & Stakeholder Management, Financial Monitoring & Reporting, Demand-Side Labor Forecasting, Business Development Support). Those are responsibilities. We can list them as bullet points under

  Responsibilities

  . Each bullet can be a concise summary of each subcategory. Must preserve all substantive information; we cannot summarize away detail? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we need to keep details, not just high-level summary. However we can keep the details within bullet points, maybe each bullet includes the subheading and details. Could also break into multiple bullet points for each subpoint. But we need to avoid too many thin sections; but we can have a single Responsibilities section with a list that includes all details. We need to ensure we don't lose any detail. The Essential Functions section includes percentages and details. We should preserve them. Thus under Responsibilities we can have a
  with each
  • containing the subheading and details. For example:
  • Project Execution & PM Leadership (40%): Oversee execution performance across assigned projects, ensuring scope is delivered consistently, efficiently, and to F2C technical standards. Directly manage, mentor, and develop Project Managers; elevate capability in planning discipline, risk identification, client communication, and financial management. Conduct weekly project execution reviews with each PM, covering schedule status, manpower forecast, risks, action items, and deliverables. Serve as the first escalation point for project-level execution issues; escalate to appropriate leaders for technical or commercial support. Validate PM project plans, schedules, and sequencing; identify and correct execution drift early. Maintain accountability for PM performance standards and prepare PMs for increasing project complexity over time.
  Similarly for other categories. - Requirements: The "Position Requirements" bullet list includes many items. We can put under

  Requirements

  a
  with each requirement as
  • . Must preserve all. The list includes: Bachelor's degree in Engineering, Construction Management, or related field - or equivalent experience. 5+ years of high purity process cooling or mission-critical construction experience. 3+ years in a people leadership or resource management role. Knowledge financial acumen - comfortable with project P&L, labor forecasting, and variance analysis. Skilled in Smartsheet, VantagePoint, and MS Office Suite. Strong risk identification, escalation discipline, and mitigation planning capability. Ability to operate effectively in a high growth, distributed, remote environment. Ability to leverage AI-enabled and digital tools to improve workforce visibility and reporting. Knowledge of electrical, mechanical, and controls system principles. Skilled at using MS Office Suite (Excel, Word, Outlook, PowerPoint, Teams), along with exceptional organizational skills for file management. Skilled in completing assignments accurately and with attention to detail. Ability to leverage AI and emerging technologies to streamline workflows, optimize operational processes, and contribute to company-wide innovation. Ability to work successfully in a remote environment through effective communication and organizational skills, self-motivation, proactiveness and resourcefulness in a distraction free workspace. Ability to follow company and site safety requirements. Ability to analyze and prepare documents, reports and correspondence. Ability to communicate effectively in both oral and written form (technical and non-technical information). Ability to communicate effectively directly with clients and serve as primary point of client contact. Ability to work successfully as a member of a team and independently with moderate supervision. Ability to work under pressure and meet close deadlines. Ability to effectively plan and delegate the work of others. Ability to achieve certification for NFPA70E and / or OSHA training as / if required. Organizational skills, with the ability to manage multiple tasks simultaneously. We need to avoid duplication: there are repeated mentions of MS Office Suite etc. We'll keep each as separate bullet but could combine similar? The instruction says preserve ALL substantive information; we can keep duplicates but maybe we can merge similar points to avoid redundancy while preserving info. However merging might be considered summarizing away detail? It's okay to combine similar points if we don't lose any info. For example "Skilled in Smartsheet, VantagePoint, and MS Office Suite." and later "Skilled at using MS Office Suite (Excel, Word, Outlook, PowerPoint, Teams), along with exceptional organizational skills for file management." These are distinct; we can keep both. - Benefits: There's a Benefits paragraph with list. We'll create

    Benefits

    with
    items. - Pay: The posting includes "The Pay Range For This Role Is 140,000 - 170,000 USD per year (Remote (United States))". Also earlier there is a Salary paragraph: "Salary Fluid2Chip recognizes salary ranges from job boards do not necessarily reflect our pay ranges. In many instances we out-compete those ranges for well-qualified candidates." That's not specific numbers. The specific range is given later. So we should include Pay section with that range. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated, so include. - Schedule: Not mentioned explicitly; there is travel up to 25% but not schedule like full-time/part-time. So we should not create Schedule section. - About the role: we have Job Summary. Could also include "About Fluid2Chip" as company description but not required. The instruction says use headings like About the role, Responsibilities, etc. So we will include About the role. We must remove boilerplate: EEO, Notice To Third Party Agencies, etc. Also remove duplicated lines. We need to output only HTML fragment. Let's craft. Structure:

    About the role

    Job Summary paragraph.

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Benefits

    • ...
    ...

    Pay

    The Pay Range For This Role Is 140,000 - 170,000 USD per year (Remote (United States)).

    We might also include a short paragraph for metadata like location? Not needed. Check for any other substantive content: "Physical Demands Duties" and "Travel Requirements". Those are substantive but not covered by headings we have. Should we include them? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for those categories if present. Physical Demands and Travel Requirements could be placed under Responsibilities or maybe a separate section like "Working Conditions". But not in the list. However we must preserve ALL substantive information. We could incorporate Physical Demands and Travel Requirements into Responsibilities or a separate section like "Working Conditions". Since not in the prescribed headings, but we can still use

    for any section heading; the examples are not exhaustive. The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when applicable, but we can also use other headings if needed. However to keep to a few substantive sections, we could fold Physical Demands and Travel Requirements into Responsibilities or maybe a new section "Working Conditions". But the instruction says "Prefer a few substantive sections over many thin ones." So maybe we add a section "Working Conditions" with Physical Demands and Travel Requirements. But we need to decide if we should create a new heading. The examples are not exclusive; they just give examples. So we can add a section like "Working Conditions". However the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. So we can add. But we must ensure we don't create sections with filler. Physical Demands and Travel Requirements have real content. Thus we could have:

    Working Conditions

    • Physical Demands: ...
    • Travel Requirements: Up to 25%, ...
    But we need to preserve all details. Let's extract Physical Demands Duties text: "Physical Demands Duties The following physical demands must be met by the employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. While performing the duties of this job, the employee is: Frequently required to remain in a stationary position.Frequently moving through office, facility and other environments.On occasion the employee may need to move stationary items weighing up to 30 pounds." We need to format as bullet. Travel Requirements: "Travel Requirements Up to 25%, this may include travel to any or all 50 US states.Must be located near a major airport.Effective May 7, 2025, and in accordance with U.S. federal regulations for domestic air travel, a valid REAL ID (or an acceptable alternative, such as a passport) is required for travel associated with this position.Travel may involve transportation by car or plane depending on the destination and nature of the business need.Travel is defined as physically leaving home on behalf of business activities including but not limited to client sites, meetings with other employees, meetings for business development purposes, running errands on behalf of the business, attending industry conferences, etc." We'll include that. Now check for any other sections: "Qualifications" maybe same as Requirements. We'll keep Requirements. "Skills" maybe overlapping with Requirements; we could combine but we already have Requirements covering skills. Could also add Skills section but that would be thin. Better to keep Requirements. Now ensure we removed boilerplate: EEO, Notice To Third Party Agencies, etc. Also remove duplicated lines like "Skilled in MS Office Suite" appears twice; we keep both as separate bullets