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 experience, desired experience, formal education, citizenship requirement, security clearance requirements, critical notes (some are boilerplate). 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!"? That's EEO? Might be considered encouragement but not boilerplate? It's not EEO but could be considered promotional; but we can keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Military Veterans are highly encouraged to apply!" is not EEO but could be considered encouragement; not required to remove. However it's somewhat fluff; but we can keep as part of About the role? Might be okay. We need to include sections only when posting has real specific content. We have Salary Range -> Pay section. We have no explicit Benefits or Schedule. So we should not create Benefits or Schedule sections unless stated. There's no explicit benefits listed. So omit Benefits and Schedule. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for section headings. We need to decide which sections to include based on content. We have description of role: location remote, department VA, type full time, min experience experienced, security clearance, salary range. That could go under About the role (or maybe Qualifications). We'll put About the role with that info. Responsibilities: essential duties and responsibilities list. Requirements: maybe combine Required Skills and Experience? Could be Requirements. Also we have Professional Certifications, Years of Experience, Desired experience, Formal Education, Citizenship Requirement, Security Clearance Requirements. Those could go under Requirements or Qualifications. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have multiple sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. We need to avoid thin sections; but we have enough content. We need to decide what goes where. Typically Requirements = mandatory qualifications (education, experience, certifications, citizenship, clearance). Qualifications = desired/experience? Skills = technical skills list. But we can combine. Let's parse: - About the role: brief overview: Senior Configuration Analyst - II, Remote, VA Department, Full Time, Experienced, Public Trust (MBI), Salary Range. - Responsibilities: list of essential duties. - Requirements: maybe citizenship, security clearance, education, years of experience. - Qualifications: maybe professional certifications, desired experience (EDI, HL7, FHIR). - Skills: list of technical skills (CM practices, source control, CI/CD, scripting, etc.) - Pay: salary range. We must not repeat job title as heading. Already not. We must not include Job ID/requisition numbers. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given, but we can format as

• . Must not omit any duty or skill. We need to remove duplicated lines: there is duplicate "U.S Citizenship is required for this specific opportunity." appears twice; we should keep only once. Also duplicate "Applicants selected will be subject to a government security investigation..." maybe keep once. Also "CRITICAL NOTES:" block includes many notes; some are boilerplate like "Recruiters or Third parties will not be considered", "This is a 100% U.S. based remote position... 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". These are application instructions or notes; we should remove them as per instruction: remove application instructions. Also "SSG will not make assumptions regarding your qualifications..." etc. That's also note; maybe remove as it's instruction. Also "Recruiters or Third parties will not be considered" remove. Also "This is a 100% U.S. based remote position..." remove because it's location restriction but also maybe considered instruction? It's a restriction; but it's substantive? It says candidates from certain states will not be considered. That's eligibility criteria; maybe we should keep as part of Requirements? It's a location restriction. The instruction says remove application instructions, but location restrictions might be considered part of job posting. However it's also a note about not considering candidates from certain states. Might be considered eligibility. I'd keep it as part of Requirements (or About the role). But the instruction says remove application instructions; location restriction is not exactly application instruction but a eligibility criterion. I'd keep it. But also "This is a W-2 position" is substantive about employment type; we already have Type: Full Time; W-2 is extra detail; could keep. "All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptions" is application instruction (interview process) - remove. "As part of our screening process, you will be requested to provide a link to your LinkedIn profile" - remove. "SSG will not make assumptions regarding your qualifications..." - maybe remove as it's note about screening. "Recruiters or Third parties will not be considered" - remove. "U.S Citizenship is required for this specific opportunity." - keep (already in citizenship requirement). "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." - keep as part of Security Clearance Requirements. "Syms Strategic Group, LLC is an Equal Opportunity Employer..." - remove as EEO boilerplate. "Powered by JazzHR S8B8nbztCj" - remove. Now we need to ensure we don't include placeholder text like "commensurate with experience", etc. Not present. Now craft HTML. We'll have:

  About the role

  Senior Configuration Analyst - II, Remote, Veterans Affairs (VA) Department, Full Time, Experienced, Public Trust (MBI) clearance required. Salary range: $74,325 - $82,500.

  But we need to preserve all substantive information: we have location remote, department VA, type full time, min experience experienced, security clearance level Public Trust (MBI), salary range. Also note that it's a 100% U.S. based remote position but candidates from certain states not considered. That's location restriction; we could add to About the role or Requirements. Let's add a sentence: "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 substantive. Also "This is a W-2 position." Could add. Now Responsibilities: list each duty as
• . We need to copy exactly the duties from "Essential Duties And Responsibilities". Let's list them: - 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 Requirements section: include citizenship requirement, security clearance requirements, formal education, years of experience, desired experience? Actually desired experience could go under Qualifications. Let's separate. Requirements (mandatory): - U.S. Citizenship required. - Must possess or qualify for a Public Trust (MBI) clearance. - 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. - This is a W-2 position. - 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. Also maybe include "Professional Certifications: None required, but ITIL Foundation, CMII, or equivalent CM certifications are a plus" - that's not mandatory, could go under Qualifications. Qualifications section: - Professional Certifications: 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). Skills section: list all technical skills from "Required Skills and Experience". Let's extract bullet points: - 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 We need to keep all. Pay section: salary range. Now ensure we don't include any boilerplate like "EEO", "Powered by JazzHR".