Remote Sprinkler Designer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Include a section only when posting has real specific content for it; never emit heading with filler placeholder. We need to parse the job description. Content: - Job Title: Remote Sprinkler Designer (but we don't repeat as heading) - Job Description: We are seeking an experienced Sprinkler Designer with 3-9 years of experience, including specific expertise in data centers. The ideal candidate will be responsible for designing and coordinating sprinkler systems using AutoCAD, Revit, and Navisworks. You will be expected to read and interpret blueprints, and prepare shop drawings and plans that comply with applicable codes and manufacturer requirements. Collaboration with local officials, engineers, architects, and customers will be a key part of your role. A NICET level 2 or 3 certification is preferred. - Responsibilities: list: - Design and coordinate sprinkler systems using AutoCAD, Revit, and Navisworks. - Read and interpret blueprints to prepare shop drawings and plans. - Ensure designs meet applicable codes and manufacturer requirements. - Collaborate with local officials, engineers, architects, and customers. - Provide expertise in data center sprinkler design. - Essential Skills: - 3-9 years of experience in sprinkler design, including data center experience. - Proficiency in AutoCAD, Revit, and Navisworks. - Ability to read and interpret blueprints. - NICET level 2 or 3 certification preferred. - Additional Skills & Qualifications: - Experience with electrical systems is a plus. - Job Type & Location: This is a Contract position based out of Hanover, MD. - Pay And Benefits: The pay range for this position is $43.27 - $52.88/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: - Medical, dental & vision - Critical Illness, Accident, and Hospital - 401(k) Retirement Plan - Pre-tax and Roth post-tax contributions available - Life Insurance (Voluntary Life & AD&D for the employee and dependents) - Short and long-term disability - Health Spending Account (HSA) - Transportation benefits - Employee Assistance Program - Time Off/Leave (PTO, Vacation or Sick Leave) - Workplace Type: This is a fully remote position. - Application Deadline: This position is anticipated to close on Oct 5, 2026. - About Actalent: description (company info). This is boilerplate? It's about the company, not necessarily required? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Actalent" section is not exactly boilerplate but is company description; maybe we keep as "About the company"? However the allowed headings list includes "About the role". There's no explicit heading for company description. We could include a

  about Actalent as part of the description? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the Actalent description. But we need to decide where to place it. Possibly under a heading "About the company" but not in allowed list. However we could just include it as a

  without a heading, as 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, but says use those for section headings. It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings when appropriate. For company description, maybe we can use "About the role"? No, that's about the role. Could use "About Actalent" as a heading but not in list; but maybe we can still use

  for it; the instruction didn't forbid other headings, just gave examples. Safer to include as a

  without a heading, or we could add a heading "About Actalent". I'd lean to include as a

  after the main content, as it's substantive. - Then there is EEO statement etc: remove. - Also there is San Francisco Fair Chance Ordinance etc: remove as legal boilerplate. - Also "Use of Artificial Intelligence (AI):" etc: remove as boilerplate. - Also "Application Deadline" is substantive; we could include as a

  or maybe under a heading? Not in list; but we could just put as a

  . - "Workplace Type" is substantive; we could include as a

  . - "Job Type & Location": we could include as a

  . - "Pay And Benefits": we have pay and benefits details; we should create sections for Pay and Benefits if they exist. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Pay and Benefits into one section? But we have separate headings Pay and Benefits in allowed list. We could make a

  Pay

  with the pay range, and

  Benefits

  with list. That seems appropriate. - "Schedule": not present; we should not create Schedule section. - "Requirements" and "Qualifications": we have Essential Skills and Additional Skills & Qualifications. Could combine into Requirements/Qualifications. The instruction: Use headings for Requirements, Qualifications, Skills. We have Essential Skills (which could be Requirements) and Additional Skills & Qualifications (maybe Qualifications). We could make a

  Requirements

  with the essential skills list, and

  Qualifications

  with additional skills? Or we could combine. But we have both; better to separate: Requirements = essential skills (3-9 years experience, proficiency, ability to read blueprints, NICET preferred). Qualifications = additional skills (experience with electrical systems is a plus). Also we have "Skills" heading; we could list skills under Skills. But we already have skills in essential skills. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section "Requirements". But we have allowed headings; we could just use "Requirements" and include both essential and additional. Or we could use "Skills" for the technical skills (AutoCAD, Revit, Navisworks, blueprint reading) and "Qualifications" for experience and certifications. However we need to avoid thin sections. Let's think: The posting includes: - Responsibilities (list) - Essential Skills (list) - Additional Skills & Qualifications (list) - Job Type & Location - Pay And Benefits - Workplace Type - Application Deadline - About Actalent (company description) We need to output HTML fragment with headings for sections that have real content. We can choose headings: About the role (maybe the initial paragraph), Responsibilities, Requirements (combining essential skills and additional skills), Benefits, Pay, Workplace Type (maybe as part of Job Type & Location?), Schedule (not present, omit), etc. But we must follow instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings as appropriate. We need to decide which headings to use: - About the role: we have the initial paragraph describing the role. That's substantive. So

  About the role

  with

  containing that paragraph. - Responsibilities: list as

  • ... - Requirements: we could put essential skills (3-9 years experience, proficiency, ability to read blueprints, NICET preferred) as
    • ... - Qualifications: we could put additional skills (experience with electrical systems is a plus) as
      • ... but that's thin. Could combine into Requirements. - Skills: we could list technical skills (AutoCAD, Revit, Navisworks, blueprint reading) but that's overlapping with essential skills. Might be thin. Better to have: About the role, Responsibilities, Requirements (including essential skills and additional), Benefits, Pay, Workplace Type (maybe as part of Job Type & Location), and maybe Application Deadline as a

        without heading. But we need to avoid creating sections with filler like "not specified". We have actual content for Pay and Benefits. Pay: we have pay range. So

        Pay

        with

        containing the pay range sentence. Benefits: we have list of benefits. So

        Benefits

        with
        • ... Workplace Type: we have "This is a fully remote position." Could be under a heading "Workplace Type" or just a

          . Since we have allowed heading Workplace Type? Not in list but we could still use

          Workplace Type

          . The instruction didn't forbid other headings, just gave examples. I'd include it. Job Type & Location: "This is a Contract position based out of Hanover, MD." Could be under heading "Job Type & Location". Not in list but okay. Application Deadline: "This position is anticipated to close on Oct 5, 2026." Could be under heading "Application Deadline". Not in list but okay. About Actalent: company description. Could be under heading "About Actalent" or just a

          . I'd add heading "About Actalent". Now we need to remove boilerplate: EEO, legal, etc. Also remove duplicated lines (the job description appears twice at start). Also remove navigation etc. We must output only HTML fragment, no /, no markdown fences. Let's craft:

          About the role

          We are seeking an experienced Sprinkler Designer with 3-9 years of experience, including specific expertise in data centers. The ideal candidate will be responsible for designing and coordinating sprinkler systems using AutoCAD, Revit, and Navisworks. You will be expected to read and interpret blueprints, and prepare shop drawings and plans that comply with applicable codes and manufacturer requirements. Collaboration with local officials, engineers, architects, and customers will be a key part of your role. A NICET level 2 or 3 certification is preferred.

          Responsibilities

          • Design and coordinate sprinkler systems using AutoCAD, Revit, and Navisworks.
          • Read and interpret blueprints to prepare shop drawings and plans.
          • Ensure designs meet applicable codes and manufacturer requirements.
          • Collaborate with local officials, engineers, architects, and customers.
          • Provide expertise in data center sprinkler design.

          Requirements

          • 3-9 years of experience in sprinkler design, including data center experience.
          • Proficiency in AutoCAD, Revit, and Navisworks.
          • Ability to read and interpret blueprints.