Senior Configuration Analyst
Syms Strategic Group, LLC (SSG) · Olney, MD · 1 mo ago
On-siteInformation Technology$74k–$83k/yrFull-time
We need to output HTML fragment with sections: About the role? Not present? The posting includes description: "Syms Strategic Group (SSG) is seeking a talented 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". Then bullet list of duties, then required skills, etc. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We only include sections when posting has real specific content.
We have location, department, type, min experience, security clearance, salary range. That could go under "About the role" maybe. Or we could have separate sections: "Pay" for salary range, "Schedule" maybe not given (full time). "Benefits" not given. "Qualifications" maybe education and experience. "Skills" maybe required skills. "Responsibilities" essential duties.
We must not repeat job title as heading. Also not include Job ID etc. Remove boilerplate: EEO, etc. Also remove "If you have previously applied..." etc. Also remove "Military Veterans are highly encouraged to apply!" maybe keep? It's not boilerplate? It's a statement encouraging veterans; could be considered part of posting but not essential? Might keep as prose in About the role? Probably safe to keep as it's substantive? It's not boilerplate but it's a encouragement. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The veteran encouragement is not exactly those; but could be considered a statement. I'd keep it.
We need to preserve all substantive information. So include location, remote, department VA, type full time, min experience experienced, security clearance Public Trust (MBI), salary range. Also citizenship requirement, etc. Also note about not considering certain states. Also note about W-2 position, interviews on Teams, camera on, LinkedIn link request, background investigation, etc. Those are substantive.
We need to decide sections.
Potential sections:
- About the role: includes location, department, type, min experience, security clearance, citizenship requirement, state restrictions, W-2, interview details, LinkedIn request, background investigation, etc.
- Responsibilities: essential duties list.
- Requirements: maybe required skills and experience? Could split into Skills and Qualifications. The posting has "Required Skills and Experience" and then "Professional Certifications", "Years of Professional Experience", "Desired experience", "Formal Education", "Citizenship Requirement", "Security Clearance Requirements". So we could have:
- Qualifications: formal education, years experience, certifications (optional), desired experience (EDI etc). Also citizenship requirement maybe.
- Skills: required skills list (CM expertise, tools, scripting, etc).
- Pay: salary range.
- Schedule: full time (maybe we can include schedule as full time). The posting says Type: Full Time. So schedule section could be included.
- Benefits: none given, so omit.
We must not create sections with filler like "not specified". So only include sections with real content.
Thus:
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We only include sections when posting has real specific content.
We have location, department, type, min experience, security clearance, salary range. That could go under "About the role" maybe. Or we could have separate sections: "Pay" for salary range, "Schedule" maybe not given (full time). "Benefits" not given. "Qualifications" maybe education and experience. "Skills" maybe required skills. "Responsibilities" essential duties.
We must not repeat job title as heading. Also not include Job ID etc. Remove boilerplate: EEO, etc. Also remove "If you have previously applied..." etc. Also remove "Military Veterans are highly encouraged to apply!" maybe keep? It's not boilerplate? It's a statement encouraging veterans; could be considered part of posting but not essential? Might keep as prose in About the role? Probably safe to keep as it's substantive? It's not boilerplate but it's a encouragement. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The veteran encouragement is not exactly those; but could be considered a statement. I'd keep it.
We need to preserve all substantive information. So include location, remote, department VA, type full time, min experience experienced, security clearance Public Trust (MBI), salary range. Also citizenship requirement, etc. Also note about not considering certain states. Also note about W-2 position, interviews on Teams, camera on, LinkedIn link request, background investigation, etc. Those are substantive.
We need to decide sections.
Potential sections:
- About the role: includes location, department, type, min experience, security clearance, citizenship requirement, state restrictions, W-2, interview details, LinkedIn request, background investigation, etc.
- Responsibilities: essential duties list.
- Requirements: maybe required skills and experience? Could split into Skills and Qualifications. The posting has "Required Skills and Experience" and then "Professional Certifications", "Years of Professional Experience", "Desired experience", "Formal Education", "Citizenship Requirement", "Security Clearance Requirements". So we could have:
- Qualifications: formal education, years experience, certifications (optional), desired experience (EDI etc). Also citizenship requirement maybe.
- Skills: required skills list (CM expertise, tools, scripting, etc).
- Pay: salary range.
- Schedule: full time (maybe we can include schedule as full time). The posting says Type: Full Time. So schedule section could be included.
- Benefits: none given, so omit.
We must not create sections with filler like "not specified". So only include sections with real content.
Thus:
About the role
...
Responsibilities
- ...
Qualifications
- ... maybe combine education, experience, certifications, desired experience, citizenship.
- ...
- .
Responsibilities list:
- 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 Qualifications: includes Formal Education, Years of Professional Experience, Professional Certifications (none required but plus), Desired experience (EDI etc), Citizenship Requirement (maybe duplicate but we can include), Security Clearance Requirements (maybe also). But we already have security clearance in About the role; we could keep it there and not duplicate. However Qualifications could include education, experience, certifications, desired experience.
Let's list:
- 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
- Professional Certifications: None required, but ITIL Foundation, CMII, or equivalent CM certifications are a plus
- 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)
- Citizenship Requirement: U.S. Citizenship required for this specific opportunity. (maybe we already have but okay)
- Security Clearance Requirements: Must possess or qualify for a Public Trust (MBI). (maybe duplicate but okay)
We could avoid duplication by moving citizenship and security clearance to About the role only, and Qualifications only education, experience, certifications, desired experience. That seems better.
Now Skills list: from "Required Skills and Experience". We'll list each bullet.
Skills list:
- 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
Now Pay: salary range.
Schedule: Full Time.
Now we need to output only HTML fragment, no markdown fences.
Let's craft.
Be careful to escape any HTML special characters like & etc. In text we have "&" inside "CI/CD". That's okay as is. Also we have "(COTS)" etc. Should be fine.
We'll produce:
About the role
Syms Strategic Group (SSG) is seeking a talented Senior Configuration Analyst. This is a fully remote position supporting the Veterans Affairs (VA) department on a full‑time basis. The role requires experienced candidates who can obtain a Public Trust (MBI) security clearance and are U.S. citizens. Recruiters or third‑party agencies will not be considered, and candidates residing in CA, CO, IL, MN, NJ, NY, OR, or WA are ineligible. The position is a W‑2 role; all interviews will be conducted via Microsoft Teams with camera on, and applicants will be asked to provide a LinkedIn profile link. Selected individuals will undergo a government security investigation and background check (criminal history, employment/education verification, drug testing, creditworthiness).
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
Qualifications
Skills
Pay
Salary range: $74,325 - $82,500
Schedule
Full‑time
We need to ensure we don't repeat info. Also include location remote etc in About the role. Let's extract details: About the role content: - Syms Strategic Group (SSG) is seeking a talented 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 (but we will put in Pay section) - Citizenship Requirement: U.S. Citizenship required for this specific opportunity. - 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. We should not duplicate sentences. Combine. Now Responsibilities list: The bullet points under "Essential Duties And Responsibilities". We'll copy each as