Jobs · Information Technology · Tennessee

Senior Systems Engineer (Production Support) - II

Syms Strategic Group, LLC (SSG) · Knoxville, TN · 1 mo ago
On-siteInformation Technology$85k–$117k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description: "Syms Strategic Group (SSG) is seeking a talented Senior Systems Engineer (Production Support) Location: Remote Department: Veterans Affairs (VA) Type: Full Time Min. Experience: Experienced Security Clearance Level: Public Trust (MBI) Salary Range: $85,389 - $116,975". Also "If you have previously applied..." etc. We need to remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also we should not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include sections only if posting has real specific content. We have content: location remote, department VA, type full time, min experience, security clearance, salary range. That's Pay and maybe Schedule? Not schedule. Benefits not mentioned. Qualifications? Could be "Required Skills and Experience" and "Professional Certifications", "Formal Education", "Citizenship Requirement". Those could go under Requirements or Qualifications. We need to decide. We have "Essential Duties And Responsibilities" list. That's Responsibilities. We have "Required Skills and Experience" long list. That's Skills. We have "Professional Certifications: None required". That's maybe Qualifications? But it's not specific content (none required) - maybe we can omit as it's not substantive? It says "None required". That's not specific content? It's a statement but maybe we can include under Qualifications? However rule: do NOT 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? Might be okay but better to omit if not substantive. We'll see. We have "Years of Professional Experience: 8+ years...". That's Requirements. We have "Desired experience" etc. That's also Requirements/Qualifications. We have "Formal Education: Bachelor’s degree...". That's Qualifications. We have "Citizenship Requirement: U.S. Citizenship required". That's Requirements. We have "Security Clearance Requirements: Must possess or qualify for a Public Trust (MBI)". That's Requirements. We have "CRITICAL NOTES..." includes many instructions: SSG will not make assumptions..., Recruiters..., This is a 100% U.S. based remote position..., candidates from certain states not considered, This is a W-2 position, All interviews..., link to LinkedIn, U.S Citizenship required again, background investigation etc. These are mostly application instructions or notes; we should remove them as per instruction: remove application instructions. Also remove duplicated lines. So we should omit those. We also need to remove EEO boilerplate at end. Thus we will produce sections: About the role (maybe a brief paragraph summarizing role), Responsibilities (list), Requirements (maybe combine experience, citizenship, clearance), Qualifications (education, certifications?), Skills (list of technical skills), Pay (salary range). Benefits not present, Schedule not present. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting that are not boilerplate. Let's extract substantive info: - Company: Syms Strategic Group (SSG) - Position: Senior Systems Engineer (Production Support) - Location: Remote - Department: Veterans Affairs (VA) - Type: Full Time - Min. Experience: Experienced (maybe not needed) - Security Clearance Level: Public Trust (MBI) - Salary Range: $85,389 - $116,975 - Essential Duties And Responsibilities (list): - 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 - Required Skills and Experience (list): - 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 - Professional Certifications: None required (maybe omit) - Years of Professional Experience: 8+ years of experience in systems engineering or a related field, particularly in production environments - 3+ years of experience with SQL query and monitoring - Desired experience: - Electronic Data Interchange X.12 (EDI) Medical Claims X.12 medical claims (837, 834, 277, etc) - Advanced certifications in relevant areas (e.g., Red Hat Certified Engineer, Microsoft Certified Systems Engineer, AWS Certified Solutions Architect) - Formal Education: Bachelor’s degree in Computer Science, Information Technology, Systems Engineering, or a related field - Citizenship Requirement: U.S. Citizenship required for this specific opportunity - Security Clearance Requirements: Must possess or qualify for a Public Trust (MBI) - CRITICAL NOTES (to be removed): many items. We need to avoid duplication: The security clearance appears both in early bullet and later; we should include once. We need to avoid repeating job title as heading. We need to output only HTML fragment. Let's decide sections: - About the role: Could include a brief paragraph summarizing the role: Syms Strategic Group (SSG) is seeking a Senior Systems Engineer (Production Support) to support Veterans Affairs (VA) cloud systems, remote full-time, requires Public Trust clearance, salary range $85,389-$116,975. But we must not invent or summarize away detail; we can paraphrase but must preserve all substantive info. Summarizing is okay as long as we don't lose detail? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details; summarizing may lose detail. Safer to keep details as separate sections rather than a summary. However we need an About the role section only if posting has real specific content for it. The posting does have a description at start: "Syms Strategic Group (SSG) is seeking a talented Senior Systems Engineer (Production Support) Location: Remote Department: Veterans Affairs (VA) Type: Full Time Min. Experience: Experienced Security Clearance Level: Public Trust (MBI) Salary Range: $85,389 - $116,975". That's specific content. We could put that as a paragraph under About the role. It includes location, department, type, clearance, salary. That's substantive. We'll keep that as a paragraph. Then Responsibilities: list of duties. Then Requirements: could include years of experience, SQL experience, citizenship, clearance, maybe desired experience? But we also have Qualifications: education, certifications. Skills: technical skills list. We need to avoid thin sections; maybe combine Requirements and Qualifications? But we have headings list; we can use multiple. We need to ensure we don't create sections with filler. We'll include:

About the role

Syms Strategic Group (SSG) is seeking a Senior Systems Engineer (Production Support) to support Veterans Affairs (VA) cloud systems. This is a full‑time remote position requiring a Public Trust (MBI) security clearance. Salary range: $85,389 – $116,975.

That preserves location remote, department VA, type full time, clearance, salary. It does not include "Min. Experience: Experienced" which is vague; we can omit as it's not substantive. Good. Then Responsibilities:

Responsibilities

  • ... each duty
Then Requirements: maybe include years of experience, SQL experience, citizenship, clearance (though clearance already mentioned in About the role; but we can still include but avoid duplication? Might be okay but we should avoid repeating same info. The instruction: "Do NOT repeat the job title as a heading" but not about repeating content. However we should avoid duplication where possible. Since clearance already in About the role, we could omit from Requirements. But we could keep it in Requirements as well; but it's duplication. Better to avoid duplication. So Requirements: years of experience (8+ years systems engineering, 3+ years SQL query and monitoring), citizenship (U.S. Citizenship required), desired experience (EDI medical claims, advanced certifications). Also maybe "Professional Certifications: None required" we can omit. Then Qualifications: Formal Education: Bachelor’s degree in CS, IT, Systems Engineering, or related field. Then Skills: list of required skills and experience (the long list). Could also include "Professional Certifications: None required" but we omit. Pay: we already included salary in About the role; but we could also have a Pay section. However we should not duplicate. The instruction: "Prefer a few substantive sections over many thin ones." So we can keep salary in About the role and not create a separate Pay section. Benefits and Schedule not present, so omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications,

Similar jobs