Systems Engineer II

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have job summary, duties, education/experience, certifications and other requirements, physical demands. We need to map to sections. We should not repeat job title. No Job ID. Remove boilerplate (cookie/navigation/legal/EEO etc). There's none. We need to preserve all substantive info. We need to decide which sections to include: About the role (job summary), Responsibilities (duties), Requirements (maybe education/experience?), Qualifications (certifications?), Skills (programming, etc), Benefits (none), Pay (none), Schedule (none). Since no explicit benefits, pay, schedule, we should not create those sections. We need to include sections only when posting has real specific content. So we can have About the role, Responsibilities, Requirements, Qualifications, Skills. Possibly also Physical Demands as a separate section? Not in list but we could maybe put under Requirements or a separate section like "Working Conditions". But instruction says use those headings only; we can add 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; we could also add other headings if needed? Probably better to stick to those. Physical demands could go under Requirements or maybe under Skills? Might be better to include as a separate section like "Working Conditions" but not in list. Might be considered extra heading not allowed? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." So we could include Physical Demands as its own section maybe "Physical Demands". However they didn't list that as example but could be okay. Safer to include under Requirements or maybe a separate "Working Conditions". I'd include a section "Physical Demands" as its own heading, as it's substantive. We need to use

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

  for prose. We need to preserve all substantive info. Let's extract content. Job Summary paragraph: "The Quantum Systems Engineer II plays a critical role in the advancement, programming, and operational maintenance of the company’s cutting-edge quantum communication network. This position provides technical leadership and cross-functional collaboration in the design, deployment, and optimization of quantum networking systems. Reporting to the Quantum Systems Manager, the Engineer will independently engage with internal teams, external vendors, and industry partners to drive strategic initiatives that enhance the scalability, resilience, and security of the quantum network infrastructure." That's About the role. Duties And Responsibilities: list bullet points. - Lead and support initiatives to optimize the performance of the quantum network, including minimizing optical losses, implementing advanced control mechanisms, integrating high-speed polarization systems, and incorporating new quantum components in collaboration with external research and industry partners. - Coordinate and contribute to the expansion of the quantum network by planning and executing the integration of new quantum data centers, ensuring robust connectivity and operational excellence. - Evaluate and lead technical efforts to extend the quantum network's reach through long-distance interconnections with regional and national quantum networks. - Spearhead initiatives to validate and demonstrate quantum-enabled cybersecurity capabilities on the company’s operational systems, with a focus on real-time monitoring, data analytics, and the enhancement of grid resiliency and quantum-secure applications. - Lead cross-functional project teams to implement, configure, and support quantum networking solutions, ensuring timely delivery and alignment with technical and business requirements. - Serve as a primary escalation point for technical troubleshooting and post-deployment support of the quantum network infrastructure, including participation in a 24/7 on-call rotation as needed to maintain service availability. - Communicate complex technical concepts clearly and effectively to a variety of stakeholders, including engineering teams, business leaders, and non-technical personnel. Education And Experience: paragraph. "Associate's or Bachelor’s degree in a related technical discipline. Equivalent work experience in quantum networking or a closely related field may be considered. Minimum of 2+ years of hands-on experience with quantum communication systems, quantum key distribution (QKD), or related technologies. Industry-recognized certifications in networking, cybersecurity, or quantum technologies (e.g., CCNP, CISSP, or vendor-specific certifications) is preferred. Strong programming skills with proficiency in languages such as Python, C/C++, and experience with relevant development environments (e.g., Visual Studio). Proficient understanding of telecommunications infrastructure, including networking protocols, routing, switching, and firewall technologies. Proven ability to manage and resolve complex technical issues involving both quantum and classical network components. Experience implementing security architectures in alignment with compliance frameworks and risk management practices." Certifications And Other Requirements: list. - Possess and maintain a current, valid driver's license in state of residence and demonstrate safe and responsible operation of motor vehicles. - Must be insurable under the company's insurance policy. - US citizenship is required. - Excellent interpersonal, written, verbal, presentation, and time management skills. - Detail-oriented with a critical degree of accuracy used to manage complex systems. - A self-starter, able to work assigned tasks with minimal direction, and be able to think independently. - Ability to critically assess the results of tasks and directed checks to ensure successful outcomes. Physical Demands - Additional Information: paragraph. "Fast-paced and heavy workload to be expected and must continually meet deadlines. Will require sitting, typing, communicating, walking, and long hours. After-hours and weekends will be needed for emergencies; maintenance activities and on-call will also be needed." We need to decide sections. We could have:

  About the role

  ...summary...

  Responsibilities

  ... each duty as
  • ...

  Requirements

  maybe combine Education And Experience and Certifications And Other Requirements? But we have separate sections for Qualifications and Skills. Could map Education/Experience to Requirements, Certifications to Qualifications, and Skills to Skills. Thus:

  Requirements

  Associate's or Bachelor’s degree ... 2+ years ...

  Qualifications

  list of certifications and other requirements? Actually Certifications And Other Requirements includes driver's license, US citizenship, interpersonal skills etc. Those are more like qualifications. We'll put them there.

  Skills

  maybe list programming skills, telecom understanding, etc. But those are already in Education/Experience paragraph. Could split: Skills section for programming languages, telecom infrastructure, etc. However we must not invent or summarize away detail; we need to preserve all info. If we split, we need to ensure we don't lose any info. Could keep Education/Experience as Requirements, and then Skills as separate list for programming, telecom, etc. But the Education/Experience paragraph also includes those skills. Might duplicate if we split. Better to keep Requirements as education/experience, Qualifications as certifications/other requirements, and Skills as programming/technical skills. But we need to ensure we don't lose any detail: we can extract programming skills etc from Education/Experience and put them in Skills, but then we would be removing them from Requirements, losing detail. However we could keep them in both places? That would be duplication, but instruction says preserve ALL substantive information; duplication is not prohibited but maybe not ideal. Better to keep them in one place. So we could have Requirements include education/experience plus programming/telecom etc. Then Qualifications include certifications and other requirements (driver's license, US citizenship, interpersonal skills). Skills maybe not needed if we already covered. But we could still have Skills section empty? Not allowed. So we could omit Skills section if no specific content beyond what's already covered. But we have some skills like "Strong programming skills with proficiency in languages such as Python, C/C++, and experience with relevant development environments (e.g., Visual Studio)." That's a skill. Could be placed in Skills section. But then we would need to remove from Requirements to avoid duplication. However we could keep a brief note in Requirements about degree and experience, and move specific skills to Skills. That would preserve all info, just split. That seems acceptable. Let's parse Education/Experience paragraph into chunks: - Associate's or Bachelor’s degree in a related technical discipline. - Equivalent work experience in quantum networking or a closely related field may be considered. - Minimum of 2+ years of hands-on experience with quantum communication systems, quantum key distribution (QKD), or related technologies. - Industry-recognized certifications in networking, cybersecurity, or quantum technologies (e.g., CCNP, CISSP, or vendor-specific certifications) is preferred. - Strong programming skills with proficiency in languages such as Python, C/C++, and experience with relevant development environments (e.g., Visual Studio). - Proficient understanding of telecommunications infrastructure, including networking protocols, routing, switching, and firewall technologies. - Proven ability to manage and resolve complex technical issues involving both quantum and classical network components. - Experience implementing security architectures in alignment with compliance frameworks and risk management practices. We could move the certifications bullet to Qualifications (since it's about certifications). The programming skills, telecom understanding, ability to manage issues, security architecture experience could go to Skills. The degree, equivalent experience, years experience go to Requirements. Thus: Requirements: degree, equivalent experience, 2+ years experience. Qualifications: certifications (industry-recognized certifications...), driver's license, insurable, US citizenship, interpersonal skills, detail-oriented, self-starter, ability to assess results. Skills: programming skills, telecom infrastructure understanding, ability to manage/resolve technical issues, experience implementing security architectures. Physical Demands: separate section. Now we need to format. Use

  for each section heading. Use

  for prose (like summary, requirements paragraph maybe). Use

  • for lists. We need to ensure we don't include boilerplate like "EEO". Not present. Let's craft HTML. About the role: use the job summary paragraph exactly. Responsibilities: list each duty as
  • . Requirements: maybe a short paragraph combining degree, equivalent experience, 2+ years. Could be a

    with sentences. Qualifications: list items: certifications, driver's license, insurable, US citizenship, interpersonal skills, detail-oriented, self-starter, ability to assess results. Skills: list items: programming skills, telecom infrastructure understanding, ability to manage/resolve technical issues, experience implementing security architectures. Physical Demands: maybe a

    with the paragraph. Check that we haven't missed any info: Let's verify each original bullet. Original Education/Experience bullets: 1. Associate's or Bachelor’s degree in a related technical discipline. -> Requirements. 2. Equivalent work experience in quantum networking or a closely related field may be considered. -> Requirements. 3. Minimum of 2+ years of hands-on experience with quantum communication systems, quantum key distribution (QKD), or related technologies. -> Requirements. 4. Industry-recognized certifications in networking, cybersecurity, or quantum technologies (e.g., CCNP, CISSP, or vendor-specific certifications) is preferred. -> Qualifications. 5. Strong programming skills with proficiency in languages such as Python, C/C++, and experience with relevant development environments (e.g., Visual Studio). -> Skills. 6. Proficient understanding of telecommunications infrastructure, including networking protocols, routing, switching, and firewall technologies. -> Skills. 7. Proven ability to manage and resolve complex technical issues involving both quantum and classical network components. -> Skills. 8. Experience implementing security architectures in alignment with compliance frameworks and risk management practices. -> Skills. Certifications And Other Requirements bullets: - Possess and maintain a current, valid driver's license in state of residence and demonstrate safe and responsible operation of motor vehicles. -> Qualifications. - Must be ins