Senior Configuration Analyst - II

We need to output HTML fragment with sections: About the role? The posting includes description: "Syms Strategic Group (SSG) is seeking a talented Senior Configuration Analyst - II Location: Remote Department: Veterans Affairs (VA) Type: Full Time Min. Experience: Experienced Security Clearance Level: Public Trust (MBI) Salary Range: $74,325 - $82,500". Then "Essential Duties And Responsibilities" list. Then "Required Skills and Experience" list. Then "Professional Certifications", "Years of Professional Experience", "Desired experience", "Formal Education", "Citizenship Requirement", "Security Clearance Requirements", "CRITICAL NOTES" etc. We need to include sections only when posting has real specific content. We should not repeat job title as heading. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have Salary Range => Pay section. We have location remote, type full time maybe Schedule? Not given schedule details. Could include Schedule if present: maybe "Full Time" indicates schedule. Could put Schedule section with "Full Time". But rule: only include section if posting has real specific content. "Full Time" is specific enough. Could include Schedule. Benefits: not mentioned. So omit Benefits. About the role: could include brief description: "Syms Strategic Group (SSG) is seeking a talented Senior Configuration Analyst - II ...". That's about role. Use

About the role

with

. Responsibilities: Essential Duties And Responsibilities list. Use

Responsibilities

with

• . Requirements: Could combine Required Skills and Experience, Professional Certifications, Years of Professional Experience, Desired experience, Formal Education, Citizenship Requirement, Security Clearance Requirements. But we need to follow headings: Requirements, Qualifications, Skills. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections: Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements = mandatory qualifications, Qualifications = education/experience, Skills = technical skills. But we can just put all under Requirements? However we should follow instruction: prefer a few substantive sections over many thin ones. Could combine into Requirements and Skills. But we have headings list; we can use Requirements for mandatory items, Skills for technical skills, Qualifications for education/experience. Let's parse. Mandatory items: U.S. Citizenship required, Public Trust (MBI) clearance, Bachelor’s degree or higher in CS/Engineering or related technical discipline and 10+ years’ relevant experience; eight (8) or more years of relevant experience may be substituted for education. Also "Must possess or qualify for a Public Trust (MBI)". Also "CRITICAL NOTES" about screening etc but those are not qualifications. Skills: list of technical skills: experience with CM, source control, CI/CD, scripting, etc. Qualifications: maybe Professional Certifications (none required but plus), Years of Professional Experience (n/a?), Desired experience (EDI, HL7, FHIR). But those are desired not required. Could put under Qualifications. We need to avoid filler like "n/a". The posting says "Years of Professional Experiencen/a". That's placeholder; we should not include that as content because it's not substantive. So we can omit that line. Desired experience: list of EDI, HL7, FHIR etc. That's substantive; we can include under Qualifications or Skills? It's desired experience, could be under Qualifications. Professional Certifications: "None required, but ITIL Foundation, CMII, or equivalent CM certifications are a plus". That's substantive; we can include under Qualifications. Formal Education: Bachelor’s degree or higher in Computer Science, Engineering, or a related technical discipline and 10+ years’ relevant experience; eight (8) or more years of relevant experience may be substituted for education. That's substantive. Citizenship Requirement: U.S. Citizenship required. Security Clearance Requirements: Must possess or qualify for a Public Trust (MBI). Thus we can have sections:

  About the role

  Syms Strategic Group (SSG) is seeking a talented Senior Configuration Analyst - II. This is a full‑time remote position supporting the Veterans Affairs (VA) department, requiring a Public Trust (MBI) clearance and U.S. citizenship. Salary range: $74,325 – $82,500.

  But we also have Pay section separate. Could put salary in Pay section. About the role could be brief description without salary. Let's follow: About the role: description of role and department. Pay: salary range. Schedule: Full Time. Thus: About the role:

  Syms Strategic Group (SSG) is seeking a talented Senior Configuration Analyst - II to support VA applications and lead cloud migration efforts.

  Responsibilities: list. Requirements: maybe combine mandatory qualifications: U.S. Citizenship, Public Trust (MBI), Bachelor’s degree or higher in CS/Engineering or related technical discipline and 10+ years relevant experience (or 8+ years substituting education). Also maybe "Must possess or qualify for a Public Trust (MBI)". We'll put that. Skills: technical skills list. Qualifications: desired experience (EDI, HL7, FHIR), professional certifications plus. We need to avoid duplication. Ensure we preserve all substantive information. Let's extract responsibilities list exactly: - Support VA applications and spearhead the migration to the cloud - Develop and maintain software configuration management (CM) tools to support configuration identification, control, reporting, and delivery of both internally developed software and externally purchased commercial-off-the-shelf (COTS) software products - Perform CM and release engineering tasks to ensure new software product opening parameters are documented, comply with standard hardware configurations, and are logistically sustainable - Design, develop, automate, and maintain productivity tools using programming, database, or scripting languages to improve software modeling and development - Design and implement build procedures that are used to support software product development and use - Develop software configuration standards for company-wide use - Train software developers in the use of CM tools and the implementation of software quality standards - Provide technical guidance and solutions to complex problems - Operate autonomously and make sound decisions - Ensure compliant, repeatable build and deployment processes across projects - Collaborate frequently with internal and external stakeholders - Lead and train junior analysts/engineers in CM best practices Now Required Skills and Experience list (the long bullet list). Let's capture each bullet: - A proven track record of successfully leading and delivering complex software builds and releases across multiple environments - Experience working within large, regulated enterprises or federal environments - Deep expertise in software configuration management and release engineering - A broad knowledge of development, Quality Assurance (QA), systems engineering, and DevOps - Experience with CM practices (identification, baselining, change control, status accounting) - Experience with source control systems (Git, GitLab, GitHub, Azure DevOps Repos, Subversion) and branching/merging strategies - Experience with CI/CD tools (Jenkins, Azure DevOps Pipelines, GitHub Actions) and artifact repositories (Nexus, Artifactory) - Experience with scripting for automation (Bash, PowerShell, and Python) - Experience managing COTS software, vendor patches, and version control - Experience with Infrastructure as code and environment management (Ansible and Terraform) - A knowledge of software quality standards, governance frameworks, and training developers on CM tools and quality practices - Proficiency with work management tools (JIRA, Azure Boards, Trello) and documentation tools (Confluence, Visio, Lucidchart) - An understanding of database concepts, dependency management, and build reproducibility - Strong analytical skills for investigating build failures, dependency conflicts, and deployment issues - Excellent communication skills - An ability to translate technical concepts for non-technical stakeholders - Effective collaboration and mentoring - An ability to manage multiple priorities and projects in fast-paced environments and meet deadlines - A commitment to continuous improvement and staying current with industry trends and emerging DevOps technologies Professional Certifications: None required, but ITIL Foundation, CMII, or equivalent CM certifications are a plus Years of Professional Experience: n/a (skip) Desired experience: Electronic Data Interchange X.12 (EDI) Medical Claims X.12, Medical Claims (837, 835, 277CA, etc), Health Level (HL7), Fast Healthcare Interoperability Resources (FHIR) Formal Education: Bachelor’s degree or higher in Computer Science, Engineering, or a related technical discipline and 10+ years’ relevant experience; eight (8) or more years of relevant experience may be substituted for education Citizenship Requirement: U.S. Citizenship required for this specific opportunity. Security Clearance Requirements: Must possess or qualify for a Public Trust (MBI) CRITICAL NOTES etc: we should remove boilerplate like "Recruiters or Third parties will not be considered", "This is a 100% U.S. based remote position. However, candidates from CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered", "This is a W-2 position", "All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptions", "As part of our screening process, you will be requested to provide a link to your LinkedIn profile", "U.S Citizenship is required for this specific opportunity. Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information and be able to obtain a government-granted security clearance. Individuals may also be subject to a background investigation including, but not limited to criminal history, employment and education verification, drug testing, and creditworthiness.", "Syms Strategic Group, LLC is an Equal Opportunity Employer. Qualified applicants will receive consideration for employment without regard to race, color, religion, sex, age, national origin, marital status, disability, veteran status, sexual orientation, or genetic information." These are boilerplate/EEO etc; we should remove them. Also "If you have previously applied to Syms Strategic Group (SSG), there is no need to reapply. Applications are still under review. Military Veterans are highly encouraged to apply!" That's also boilerplate/application instructions; remove. Thus we keep only substantive content: role description, responsibilities, required skills, professional certifications, desired experience, formal education, citizenship, security clearance, pay, schedule. Now construct HTML. We'll have:

  About the role

  Syms Strategic Group (SSG) is seeking a talented Senior Configuration Analyst - II to support Veterans Affairs (VA) applications and lead the migration to the cloud.

  Responsibilities

  • Support VA applications and spearhead the migration to the cloud
  • Develop and maintain software configuration management (CM) tools to support configuration identification, control, reporting, and delivery of both internally developed software and externally purchased commercial-off-the-shelf (COTS) software products
  • Perform CM and release engineering tasks to ensure new software product opening parameters are documented, comply with standard hardware configurations, and are logistically sustainable
  • Design, develop, automate, and maintain productivity tools using programming, database, or scripting languages to improve software modeling and development
  • Design and implement build procedures that are used to support software product development and use
  • Develop software configuration standards for company-wide use
  • Train software developers in the use of CM tools and the implementation of software quality standards
  • Provide technical guidance and solutions to complex problems
  • Operate autonomously and make sound decisions