Senior Application/Infrastructure Support Engineer

We need to output HTML fragment with sections: About the role? The posting includes description: "Syms Strategic Group (SSG) is seeking a talented Senior Application/Infrastructure Support Engineer". That's the role description. Could be "About the role". Then responsibilities list: "Essential Duties And Responsibilities" bullet list. Then "Required Skills and Experience" maybe as "Requirements" or "Qualifications". Also "Professional Certifications", "Years of Professional Experience", "Desired experience", "Formal Education", "Citizenship Requirement", "Security Clearance Requirements". Also "Salary Range". Also "Location: Remote". Also "Department: Veterans Affairs (VA)". Also "Type: Full Time". Also "Min. Experience: Experienced". Also "Security Clearance Level: Public Trust (MBI)". Also "If you have previously applied..." etc. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "If you have previously applied..." etc. Also remove "Military Veterans are highly encouraged to apply!" maybe not boilerplate? It's encouragement but could stay? It's not required but it's not boilerplate; but we can keep as part of About the role? Might be considered fluff but not prohibited. However we should preserve substantive info. We'll keep it maybe as part of About the role paragraph. We need sections only when there is real specific content. So we will have sections: About the role (paragraph summarizing role and location etc). Responsibilities (ul). Requirements (maybe combine skills, experience, education, certifications, etc). Benefits? Not present. Pay: we have Salary Range. So we need a Pay section. Schedule: we have Type: Full Time (maybe schedule). Could include Schedule section with Full Time. Also maybe Location? Not a section heading per rules; we can include location in About the role paragraph. We must not repeat job title as heading. So no heading for Senior Application/Infrastructure Support Engineer. We must not put Job ID/requisition numbers as headings. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state Salary Range and Type: Full Time. So we can have Pay and Schedule sections. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info: list of duties, required skills, experience, certifications, education, citizenship, security clearance, etc. We need to format using

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: combine location remote, department VA, type full time, min experience experienced, security clearance Public Trust (MBI), salary range maybe later in Pay section. Also mention encouraging veterans. Also note that if previously applied no need to reapply etc - that's application instruction, should be removed. Also remove "Applications are still under review." That's also instruction. Remove recruiter third parties note. Remove "This is a 100% U.S. based remote position..." etc maybe part of location but we can keep location remote and note restrictions (states not considered) as substantive? It's a restriction; maybe keep as part of About the role. But it's a restriction on candidates; it's substantive. We'll include. We must not include boilerplate like EEO statement at end. Remove that. Also remove "Powered by JazzHR BRLchoPgO5". Now Responsibilities: list each duty from "Essential Duties And Responsibilities". We'll convert each sentence to

• . Let's extract duties: - Perform high-level, day-to-day operational support of complex application cloud systems - Develop solutions to routine technical problems of limited scope - Follow standard practices and procedures in analyzing situations or data from which answers can be readily obtained - Detect, isolate, document, rapidly report, and resolve system outages or problems encountered during operations of the scientific workstations, which includes the collections of diagnostic data, restoring the system operation, development of workarounds, and other activities necessary for recovery of a system - Accurately document problems in logging and discrepancy reporting tools - Work directly with the customer in most aspects of the day-to-day activities - Respond to user calls regarding hardware and software problems, correcting or ensuring that problems are escalated when required - Communicate with users and senior management the status of key problem statuses - Perform maintenance/installation of computing infrastructure - Implement continuous improvement methodology through the use of IT systems or procedure - Maintain inventory of system assets - Ensure compliance with VA standards and security policies - Provide documentation, training, and additional duties as assigned Now Required Skills and Experience: we need to list as
  • . Many items. Let's extract: - Experience with AWS and/or Azure Cloud, namely S3, Step Functions, Batch Jobs, and CloudWatch - Proven track record of managing and maintaining large-scale production systems - Strong proficiency in Linux/Unix and Windows operating systems - Experience with system administration tasks including user management, permissions, and system monitoring - Proficiency in scripting languages such as Python, Bash, or PowerShell for automation and configuration management - Experience with automation tools like Ansible, Puppet, Chef, or SaltStack - Knowledge of cloud-native technologies and infrastructure-as-code (IaC) tools such as Cloud Formation - Experience with monitoring tools like DynaTrace, Science Logic, and CloudWatch - An ability to troubleshoot and optimize system performance and reliability - An understanding of network protocols of network protocols, firewall configurations, and Virtual Private Network (VPN) setup (typo but keep) - Experience with network monitoring and diagnostic tools - Experience with secure best practices for production systems - Experience with implementing security measures, conducting audits, and ensuring compliance with industry standards - Working knowledge of database systems such as AWS RDS SQL Server and Oracle RDMBS/RDS - Knowledge of database performance tuning and backup/recovery processes - Knowledge of CI/CD pipelines - Familiarity with version control systems like Git and CI/CD tools like GitHub Actions, AWS CodeBuild and CodeDeploy - Strong analytical and problem-solving skills with the ability to troubleshoot complex system issues - Excellent communication and interpersonal skills with the ability to work effectively in cross-functional teams - An ability to prioritize tasks, manage time effectively, and meet deadlines in a high-pressure environment - Strong attention to detail to ensure system stability and data integrity - An ability to quickly adapt to new technologies and processes - A willingness to be on-call for production system support as required - Strong documentation skills for maintaining system configurations, processes, and procedures - An ability to manage and contribute to multiple projects, ensuring timely completion and quality results - An ability to work collaboratively with development, operations, and security teams to ensure seamless production system operations Now Professional Certifications: "None required". That's filler? It's stating none required. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "None required" could be considered placeholder? It's a statement that no certifications required. Might be considered substantive? It's a statement about certifications. The rule says avoid filler like "not specified", "N/A". "None required" is specific. I'd keep it maybe under a Qualifications section? But we might combine certifications into Requirements. However we have a separate "Professional Certifications" line. Could include as a bullet under Requirements: "No professional certifications required". That's substantive. Years of Professional Experience: "8+ years of experience in systems engineering or a related field, particularly in production environments". Also "3+ years of experience with SQL query and monitoring". Also "Desired experience" includes EDI X.12 medical claims etc. Also "Advanced certifications in relevant areas (e.g., Red Hat Certified Engineer, Microsoft Certified Systems Engineer, AWS Certified Solutions Architect)". Also "Formal Education: Bachelor’s degree in Computer Science, Information Technology, Systems Engineering, or a related field". Also "Citizenship Requirement: U.S. Citizenship required for this specific opportunity". Also "Security Clearance Requirements: Must possess or qualify for a Public Trust (MBI)". Also note about background investigation etc. That's substantive. We need to avoid duplication: "U.S Citizenship is required for this specific opportunity." appears twice; we can keep once. Also "As part of our screening process, you will be requested to provide a link to your LinkedIn profile" - that's application instruction; remove. Also "CRITICAL NOTES: SSG will not make assumptions regarding your qualifications..." etc - that's instruction; remove. Also "Recruiters or Third parties will not be considered" - remove. Also "This is a W-2 position" - maybe keep as part of About the role? It's substantive about employment type. Could be included in Schedule? Actually W-2 indicates employment classification; maybe we can include in About the role. Also "All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptions" - instruction; remove. Now we need to decide sections: About the role, Responsibilities, Requirements (maybe combine skills, experience, education, certifications, etc), Pay, Schedule. We could also have Qualifications section instead of Requirements. The rules allow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose whichever fits. We have a lot of skill items; could put under Skills. But we also have experience years, education, certifications, citizenship, clearance. Could put under Requirements or Qualifications. Let's make sections: About the role, Responsibilities, Skills, Requirements (for experience, education, certifications, citizenship, clearance), Pay, Schedule. But we must not create thin sections. Let's see if we can combine some. Option: About the role (paragraph). Responsibilities (ul). Requirements (ul) covering skills, experience, education, certifications, citizenship, clearance. Pay (p). Schedule (p). That seems reasonable. Now we need to ensure we don't repeat content. Let's craft About the role paragraph: Syms Strategic Group (SSG) is seeking a Senior Application/Infrastructure Support Engineer for a full‑time, remote position supporting the Veterans Affairs (VA) department. The role requires U.S. citizenship and eligibility for a Public Trust (MBI) security clearance, with 8+ years of systems engineering experience (including 3+ years of SQL/query monitoring). Military veterans are encouraged to apply. This is a W‑2, 100% U.S.-based remote role; however, candidates residing in CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered. That captures location, department, type, citizenship, clearance, experience, veteran encouragement, W-2, location restrictions. Now Responsibilities ul as above. Now Requirements ul: combine skills, experience, education, certifications, citizenship, clearance? But citizenship and clearance already mentioned in About the role; we could still include but might duplicate. Better to keep them in About the role only to avoid duplication. However the rule says preserve ALL substantive information; duplication is not prohibited but we should avoid repeating. We'll keep them only in About the role. Thus Requirements ul will include: - Experience with AWS and/or Azure Cloud (S3, Step Functions, Batch Jobs, CloudWatch) - Proven track record managing and maintaining large‑scale production systems - Strong proficiency in Linux/Unix and Windows operating systems - Experience with system administration tasks (user management, permissions, system monitoring) - Proficiency in scripting languages (Python, Bash, PowerShell) for automation and configuration management - Experience with automation tools (Ansible, Puppet, Chef, SaltStack) - Knowledge of cloud‑native technologies and IaC tools such as CloudFormation - Experience with monitoring tools (DynaTrace, Science Logic, CloudWatch) - Ability to troubleshoot and optimize system performance and reliability - Understanding of