Senior Configuration Analyst

We need to output HTML fragment with sections: About the role? Not present. Responsibilities: list of duties. Requirements: list of required skills and experience. Possibly Benefits? Not given. Pay: salary range given. Schedule: not given. So include Pay section with salary range. Also maybe include location remote etc as a short paragraph. We must not repeat job title. No headings for Job ID etc. Use

for section headings. We need to preserve all substantive info: location remote, department VA, type full time, min experience experienced, security clearance public trust MBI, salary range, note about previous applications, veterans encouraged, essential duties list, required skills list, professional certifications note, years of experience note, desired experience (EDI etc), formal education, citizenship requirement, security clearance requirements, critical notes (screening questions, recruiters not considered, remote position but certain states excluded, W-2, interviews on Teams, LinkedIn link request, citizenship repeated, background investigation, EEO statement). We should remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The EEO statement is boilerplate; we should remove it. Also "Powered by JazzHR e2OoSLu6Je" remove. Also "Critical notes:" maybe keep as part of responsibilities? It's not a duty but notes about process; maybe we can include as a short paragraph under a section like "Important Notes". But we must only include sections when posting has real specific content. The critical notes contain specific info: screening questions, recruiters not considered, remote position but certain states excluded, W-2, interviews on Teams with camera on, LinkedIn link request, citizenship requirement repeated, background investigation. That's substantive. Could be placed under a section like "Important Notes". However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections; but we could also use other headings? Safer to stick to those. We can map critical notes into maybe "Requirements" or "Qualifications"? But they are not qualifications. Could be under "Requirements" as additional requirements (citizenship, location restrictions). However we already have qualifications etc. Might be better to create a section "Important Notes" but that deviates from guidance. The guidance says use those headings for section headings (e.g. ...). It doesn't explicitly forbid other headings, but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". Likely they expect only those headings. So we should fit content into those categories. We have: About the role (maybe a brief description). Responsibilities (list). Requirements (list of required skills/experience). Qualifications (maybe education/certifications). Skills (maybe separate from requirements? Could combine). Benefits (none). Pay (salary range). Schedule (none). So we need to decide. We could put location, department, type, clearance under About the role. Responsibilities list. Requirements list (required skills and experience). Qualifications list (education, certifications, years of experience, desired experience). Skills maybe redundant; we could omit Skills section if we put skills under Requirements. But we need to avoid thin sections. Could combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we need to follow instruction: use headings for those categories if we have content. We could have About the role, Responsibilities, Requirements, Qualifications, Pay. That's fine. We must not include Benefits or Schedule if no content. Now we need to preserve all substantive info. Let's extract. About the role: 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). Also note: Military Veterans highly encouraged to apply. Also note: If previously applied, no need to reapply. Applications still under review. Also note: U.S. Citizenship required. Also note: Recruiters or third parties not considered. Also note: 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 note: This is a W-2 position. All interviews will be conducted on Microsoft Teams with camera on; no exceptions. As part of screening, you will be requested to provide a link to your LinkedIn profile. Also note: 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 criminal history, employment and education verification, drug testing, and creditworthiness. We need to keep all that but not duplicate. We'll include in About the role maybe a paragraph summarizing. Responsibilities: list of essential duties (the bullet list). We'll convert to

• . Requirements: list of required skills and experience (the long list). We'll convert to
  • . Qualifications: includes Professional Certifications note, Years of Professional Experience n/a, Desired experience (EDI etc), Formal Education, Citizenship Requirement (U.S. Citizenship required), Security Clearance Requirements (must possess or qualify for Public Trust MBI). Also maybe note about critical notes? Already covered. We need to avoid duplication: citizenship appears both in About the role and Qualifications; we can mention once. But we must preserve all substantive info; duplication removal is allowed? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we can remove duplicated lines. So we should not repeat same info twice. So we need to decide where to place each piece without duplication. Let's list unique items: - Company: Syms Strategic Group (SSG) seeking Senior Configuration Analyst. - Location: Remote. - Department: Veterans Affairs (VA). - Type: Full Time. - Experience: Experienced (maybe not needed). - Security Clearance: Public Trust (MBI). - Salary Range: $74,325 - $82,500. - Veterans encouraged. - If previously applied, no need to reapply. - Applications still under review. - U.S. Citizenship required. - Recruiters/third parties not considered. - 100% US-based remote position; candidates from CA, CO, IL, MN, NJ, NY, OR, WA not considered. - W-2 position. - Interviews on Microsoft Teams with camera on; no exceptions. - LinkedIn profile link requested as part of screening. - Applicants selected subject to govt security investigation; must meet eligibility for classified info and obtain govt clearance. - Background investigation: criminal history, employment/education verification, drug testing, creditworthiness. - Essential duties list (many). - Required skills/experience list (many). - Professional certifications: none required but ITIL Foundation, CMII, or equivalent CM certifications a plus. - Years of Professional Experience: n/a (maybe not needed). - Desired experience: EDI X12 medical claims, HL7, FHIR. - Formal Education: 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. - EEO statement: remove. We need to avoid duplication: citizenship appears also in security clearance requirement? Actually citizenship required separate; security clearance requires public trust MBI which also requires citizenship but we can keep both but not duplicate same sentence. We'll mention citizenship requirement once. Now craft HTML. We'll start with

    About the role

    then a

    containing the summary. Then

    Responsibilities

    then
    • each duty. Then

      Requirements

      then
      • each required skill/experience. Then

        Qualifications

        then
        • for certifications, desired experience, formal education, citizenship requirement, security clearance requirement maybe. Pay:

          Pay

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

          We should not include Benefits or Schedule. Check for any placeholder like "n/a" - we should avoid sections with filler. For Qualifications we have content. Now ensure we don't include any boilerplate like EEO statement. Remove. Now produce HTML fragment. Let's draft. About the role paragraph: Combine: Syms Strategic Group (SSG) is seeking a talented Senior Configuration Analyst for a remote, full-time position supporting the Veterans Affairs (VA). The role requires a Public Trust (MBI) security clearance and U.S. citizenship. Military veterans are encouraged to apply. Note: if you have previously applied to SSG, there is no need to reapply; applications are still under review. 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. The position is W-2, interviews conducted on Microsoft Teams with camera on (no exceptions), and as part of screening you will be asked to provide a LinkedIn profile link. Selected applicants will undergo a government security investigation and must be eligible for access to classified information and able to obtain a government-granted security clearance; they may also be subject to a background investigation including criminal history, employment and education verification, drug testing, and creditworthiness. That covers many. Now Responsibilities list: copy each duty line. Let's list them exactly as in posting: - 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 list: copy each required skill/experience line. 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