Senior Configuration Analyst

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

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. Given posting: Title: Senior Configuration Analyst. Location: Remote. Department: Veterans Affairs (VA). Type: Full Time. Min. Experience: Experienced. Security Clearance Level: Public Trust (MBI). Salary Range: $74,325 - $82,500. We have essential duties and responsibilities list. Required Skills and Experience list. Professional Certifications note. Years of Professional Experience: n/a. Desired experience: EDI etc. Formal Education: Bachelor’s degree or higher ... 10+ years’ relevant experience; eight (8) or more years of relevant experience may be substituted for education. Citizenship Requirement: U.S. Citizenship required. Security Clearance Requirements: Must possess or qualify for a Public Trust (MBI). Critical notes etc. We need to remove boilerplate: EEO, etc. Also remove duplicated lines, application instructions, cookie/navigation/legal, etc. Also remove "If you have previously applied..." etc. Also remove "Military Veterans are highly encouraged to apply!" maybe not boilerplate? It's encouraging but could be considered EEO? Might keep? Probably keep as part of About the role? It's not essential but could be considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The line "Military Veterans are highly encouraged to apply!" is not EEO but encouraging a group; might be considered EEO? It's encouraging veterans, which is a protected class. Might be considered EEO-related. Safer to remove. We need to preserve substantive info. We need sections: About the role (maybe location, department, type, clearance, salary?). Responsibilities (essential duties). Requirements (maybe required skills and experience?). Qualifications (maybe formal education, citizenship, security clearance). Skills (maybe list of skills). Benefits (none given). Pay (salary range). Schedule (maybe full time). We should only include sections if we have real specific content. We have salary range: include Pay section. We have schedule: Full Time. Could include Schedule section. We have benefits: none mentioned, so omit Benefits. We have About the role: could include location, department, type, clearance, maybe salary? But salary already separate. Could include location, department, type, clearance. That's substantive. Responsibilities: essential duties list. Requirements: maybe required skills and experience? But we also have Skills section for list of skills. Could split: Requirements = required skills and experience (the block "Required Skills and Experience"). Skills = maybe the list of specific technical skills? But the required skills block already includes many. Could treat Required Skills and Experience as Requirements, and then Skills maybe not needed. However we need to avoid thin sections. Perhaps combine Required Skills and Experience into Requirements, and then Skills omitted. Or we could have Requirements (experience, education, citizenship, clearance) and Skills (technical skill list). Let's see. We have "Required Skills and Experience" block with many bullet-like sentences. That's substantive. Could be Requirements. We also have "Professional CertificationsNone required, but ITIL Foundation, CMII, or equivalent CM certifications are a plus" - could be part of Requirements or Skills? Might be part of Requirements. We have "Years of Professional Experiencen/a" - not substantive. We have "Desired experienceElectronic Data Interchange X.12 (EDI) Medical Claims X.12, Medical Claims (837, 835, 277CA, etc), Health Level (HL7), Fast Healthcare Interoperability Resources (FHIR)" - could be part of Requirements or Skills. We have "Formal EducationBachelor’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" - could be Qualifications. We have "Citizenship RequirementU.S. Citizenship required for this specific opportunity" - Qualifications. We have "Security Clearance RequirementsMust possess or qualify for a Public Trust (MBI)" - Qualifications. Thus we can structure:

About the role

Remote position supporting the Veterans Affairs (VA) department. Full‑time role requiring a Public Trust (MBI) security clearance and U.S. citizenship.

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
• 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

Requirements

• 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: ITIL Foundation, CMII, or equivalent CM certifications are a plus (not required)
• 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)

Qualifications

• Bachelor’s degree or higher in Computer Science, Engineering, or a related technical discipline; 10+ years’ relevant experience (8+ years may substitute for degree)
• U.S. Citizenship required
• Must possess or qualify for a Public Trust (MBI) security clearance

Pay

Salary range: $74,325 - $82,500

Schedule

Full‑time

We should not include Benefits as no info. Check for any duplicated lines: we have not repeated. Check for boilerplate removed: we removed EEO, etc. Check for placeholders: we have no "commensurate with experience" etc. Check for minor metadata: we folded location, department, type, clearance into About the role. Good. Check for any mention of "CRITICAL NOTSSG will not make assumptions..." we removed as boilerplate/application instructions. Check for "Recruiters or Third parties will not be considered" removed. Check for "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" - that's location restriction; could be considered substantive? It's a restriction on location. Might be considered part of About the role? It's a specific eligibility criterion. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that restriction. It's not boilerplate; it's a specific eligibility criterion. Should we include it? It's about location restrictions for remote role. Could be part of About the role or Qualifications. Let's include in About the role as a note. Also "This is a W-2 position" - substantive about employment type. Could be included in About the role or Schedule? Might be part of About the role. Also "All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptions" - that's application instruction? It's about interview process; maybe considered application instructions? The instruction says remove application instructions. This is about interview process, not application. Might be considered part of process but could be considered boilerplate? It's specific to the company. Might be considered substantive? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Interview details could be considered application instructions? It's about the hiring process, not how to apply. Might be okay to keep? Safer to remove as it's about interview process, which could be considered application instructions. I'd remove. 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 "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." This is substantive about clearance and background check. Could be part of Qualifications or About the role. We already have citizenship and clearance; we could add background investigation note. Also "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." That's EEO boilerplate, remove. Also "Powered by JazzHR rARd0dBtkJ" remove. Thus we need to incorporate location restriction and W-2 and background investigation. Let's adjust About the role paragraph to include: Remote position supporting VA department. Full‑time, W‑2 position. Requires Public Trust (