Programmer Engineer, Sr.

We need to output HTML fragment with sections for headings that have real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We have: - About the Role: content present. So

About the role

then

with prose. - Responsibilities: list of duties. So

Responsibilities

then

• each bullet. - Requirements: The posting has "Required Qualifications". That's essentially requirements. So we can use

  Requirements

  (or Qualifications). The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have both Required Qualifications and Preferred Qualifications (none). Also Skills & Competencies. Education & Experience. Work Arrangement & Schedule (but schedule not specified). Compensation & Benefits (not specified). So we need to decide which sections to include. We must include a section only when posting has real, specific content. So: - About the role: yes. - Responsibilities: yes. - Requirements: we have Required Qualifications with bullet points (though they are not bullet list but sentences). We can treat as list? The instruction: Use
  • for any list of duties/requirements/benefits. The Required Qualifications are a list of abilities. We can format as
    • each. - Qualifications: we have Preferred Qualifications (none). So we should not include Qualifications section because no specific content. - Skills: we have Skills & Competencies list. So include

      Skills

      with
      • . - Education & Experience: we have Education (none specified) and Experience (some prose). The instruction says include section only when posting has real, specific content. Experience has some content: "The position requires deep technical expertise and hands-on capability..." That's specific enough. Education: none specified, so we might not include Education heading. But we could combine Education & Experience as one section? The headings list includes Education & Experience? Not explicitly, but we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No Education & Experience. So we should not create a section for education/experience unless we map to Requirements or Qualifications? Probably we should include Experience under Requirements? But we already have Required Qualifications. The experience description is somewhat similar to qualifications. Could merge. However we must preserve all substantive information; we cannot drop the experience detail. We could include it under Requirements as additional bullet points. Or we could create a separate section like "Experience" but not in allowed headings. The instruction says use those headings for section headings; but does not forbid other headings? It 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 sections; but we could also use other headings if needed? Safer to stick to those. We can place experience content under Requirements or Qualifications. Since we have Required Qualifications already, we can add experience bullets there. - Work Arrangement & Schedule: schedule not specified, work arrangement not specified, only mention on-site/remote. The posting says: "On-Site / Remote: The role supports both on-site commissioning and remote diagnostics." That's specific content about work arrangement. So we could include a section for Schedule? But schedule not specified. However we could include a section for "Work Arrangement" but not in list. Could we include under "Schedule"? No. Could we include under "Benefits"? No. Could we create a custom heading? The instruction says use those headings for section headings (e.g. ...). It doesn't explicitly forbid other headings, but says "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should limit to those. However we have relevant info about on-site/remote. Could we put that under Responsibilities? Not really. Could we put under Requirements? Not ideal. Could we create a section "Work Arrangement" as

        Work Arrangement

        though not in list; risk of violating instruction. Better to incorporate into Responsibilities? Maybe as a bullet: "Support on-site commissioning and remote diagnostics." Already present in responsibilities bullet list: there is "Support project turnover activities." and "Perform on-site commissioning and remote diagnostics as required." Actually we have that bullet: "Perform on-site commissioning and remote diagnostics as required." So that's already covered. So we don't need separate section. - Compensation & Benefits: not specified, so omit. - Pay: not specified, omit. - Schedule: not specified, omit. Thus sections: About the role, Responsibilities, Requirements (including Required Qualifications + Experience), Skills. We need to preserve all substantive information. Let's extract content. About the Role paragraph: The block after "## About the Role". It contains two sentences? Actually: "Facility Engineering Services (FES) is seeking a **Senior DDC Engineer / Programmer** with strong technical expertise in **building automation systems (BAS), direct digital controls (DDC), programming, integration, and commissioning**. This is a hands-on leadership role focused on complex project delivery, field commissioning, troubleshooting, technical guidance, and client support. The Senior DDC Engineer / Programmer will collaborate with engineering, construction, service, and technical teams to deliver reliable, high-performance building control solutions. The role also includes mentoring DDC technicians, providing system training to clients, and supporting both on-site commissioning and remote diagnostics." We need to preserve all info, no markdown. We'll output as

        with that text, stripping markdown **. Responsibilities bullets: list after "## Key Responsibilities". Each bullet starts with "*". We need to capture each bullet text, removing the leading "* " and any trailing period? Keep as is. Let's extract: * Collaborate with the Engineering Department to review and advise on control drawings and project submittals.* * Program, integrate, and commission DDC systems and field devices across multiple platforms.* * Verify the accurate operation of building control sequences, alarms, trends, and archives.* * Develop and implement custom graphics for end-user building automation interfaces.* * Train and mentor DDC technicians and provide system training for clients.* * Integrate building automation systems (BAS) with third-party building systems, including chillers, generators, and lighting.* * Troubleshoot complex building automation system and network issues.* * Diagnose and resolve BACnet IP, BACnet MS/TP, LAN, and WAN networking issues.* * Read and interpret mechanical drawings, sequences of operation, and project specifications.* * Prepare and deliver as-built documentation.* * Support project turnover activities.* * Perform on-site commissioning and remote diagnostics as required.* * Provide technical direction and support for complex controls projects. Note some have trailing ".*" due to markdown. We'll remove the final ".*" and keep sentence. Now Required Qualifications bullets: * Deep technical expertise in **building automation and control systems**.* * Hands-on experience with **DDC programming, integration, and commissioning**.* * Ability to troubleshoot complex BAS system and network issues.* * Knowledge of **BACnet IP, BACnet MS/TP, LAN, and WAN** networks.* * Ability to read and interpret mechanical drawings, sequences of operation, and specifications.* * Ability to work with building control sequences, alarms, trends, archives, and graphics.* * Ability to integrate BAS with third-party systems such as chillers, generators, and lighting.* * Ability to support field commissioning and remote diagnostics.* * Ability to collaborate with engineering, construction, and service teams. Again strip markdown. Experience paragraph: Under Education & Experience: **Experience** * The position requires deep technical expertise and hands-on capability in building automation and control systems, DDC programming, integration, commissioning, and troubleshooting.* Specific years of experience are not provided in the original job description. We need to preserve that. The second sentence says specific years not provided - that's not specific content? It's still info but maybe we should keep? It's not placeholder like "not specified"? It says "Specific years of experience are not provided". That's still info but maybe we can keep as it's factual. However instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not include a section that only contains filler. But we are including experience as part of Requirements; we can include the first sentence (specific) and maybe omit the second sentence about years not provided because it's filler. However we must preserve ALL substantive information; the second sentence is not substantive (it's just saying not provided). So we can drop it. Thus we will include experience sentence: "The position requires deep technical expertise and hands-on capability in building automation and control systems, DDC programming, integration, commissioning, and troubleshooting." Now Skills & Competencies bullets: * DDC programming * Building Automation Systems (BAS) * Building controls * Automatic temperature controls * System integration * Field commissioning * BAS troubleshooting * BACnet IP * BACnet MS/TP * LAN/WAN networking * Control sequences * Alarms, trends, and archives * Custom graphics * Mechanical drawings and specifications * Technical documentation and as-built documentation * Project turnover * Technician mentoring and training * Client training * Technical leadership * Problem-solving * Client-facing communication We need to strip the leading "* " and keep. Now we need to output HTML fragment: sections with

        and then either

        or

        • . We must not include any extra text like comments. Let's craft. First section: About the role.

          About the role

          Facility Engineering Services (FES) is seeking a Senior DDC Engineer / Programmer with strong technical expertise in building automation systems (BAS), direct digital controls (DDC), programming, integration, and commissioning. This is a hands-on leadership role focused on complex project delivery, field commissioning, troubleshooting, technical guidance, and client support. The Senior DDC Engineer / Programmer will collaborate with engineering, construction, service, and technical teams to deliver reliable, high-performance building control solutions. The role also includes mentoring DDC technicians, providing system training to clients, and supporting both on-site commissioning and remote diagnostics.

          Second: Responsibilities.

          Responsibilities

          • Collaborate with the Engineering Department to review and advise on control drawings and project submittals.
          • Program, integrate, and commission DDC systems and field devices across multiple platforms.
          • Verify the accurate operation of building control sequences, alarms, trends, and archives.
          • Develop and implement custom graphics for end-user building automation interfaces.
          • Train and mentor DDC technicians and provide system training for clients.
          • Integrate building automation systems (BAS) with third-party building systems, including chillers, generators, and lighting.
          • Troubleshoot complex building automation system and network issues.
          • Diagnose and resolve BACnet IP, BACnet MS/TP, LAN, and WAN networking issues.
          • Read and interpret mechanical drawings, sequences of operation, and project specifications.
          • Prepare and deliver as-built documentation.
          • Support project turnover activities.
          • Perform on-site commissioning and remote diagnostics as required.
          • Provide technical direction and support for complex controls projects.
          Third: Requirements (including Required Qualifications + Experience).

          Requirements

          • Deep technical expertise in building automation and control systems.
          • Hands-on experience with DDC programming, integration, and commissioning.
          • Ability