Description

The Software Configuration Management Analyst is responsible for establishing, maintaining, and controlling multiple software baselines, managing build and release activities, and ensuring that all changes are properly documented and controlled. This role supports development and integration teams by providing reliable, repeatable software builds and documented releases in accordance with program and organizational standards.

Key Responsibilities

• Plan, execute, and monitor software builds across development, integration, test, and release environments.
• Establish, maintain, and control multiple software baselines, including development, integration, test, and production branches.
• Implement and maintain configuration management processes and tools (e.g., Git, Subversion, branching/merging strategies) to ensure traceability and reproducibility of software baselines.
• Coordinate and perform documentation of software changes, ensuring that change descriptions, rationale, and impact assessments are captured and linked to the appropriate requirements, tickets, and baselines.
• Maintain documentation control for configuration management artifacts (e.g., build instructions, release notes, configuration item lists, CM plans), including versioning, approvals, and distribution.
• Manage release of documents associated with software builds and baselines (e.g., release notes, build manifests, interface control documents), ensuring correct routing, approval, and storage in the designated repositories.
• Lead or support the facilitation of change control activities, including preparation for Change Control Board (CCB) or Engineering Change Review meetings, presentation of proposed changes, and documentation of decisions.
• Ensure that all software changes and releases comply with program CM plans, standards, and applicable organizational or customer requirements.
• Collaborate closely with software development, systems engineering, test, and integration teams to ensure smooth, coordinated delivery of software builds and releases.
• Monitor CM metrics (e.g., build success rate, change backlog, baseline health) and recommend process improvements.

This reqiusition may be filled at a higher job grade based on the qualifications listed below.

This requisition may be filled as either a level 2 or level 3.

Basic Qualifications for a Level 2:

• Bachelor’s degree with 2 years of relevant experience; 0 years with a Master's. An additional 4 years of relevant experience may be considered in lieu of a degree.
• Requires an active Top-Secret/Sensitive Compartmented Information (SCI) clearance at time of application
• Involvement with software builds (e.g., build scripts, CI/CD pipelines, build automation tools such as Jenkins, GitLab CI, Azure DevOps).
• Knowledge of controlling multiple software baselines (e.g., branch management, tagging, merging strategies in Git or other SCM tools).
• Demonstrated experience in documentation of software changes, including clear change descriptions, impact analysis, and traceability to requirements or tickets.
• Knowledge of documentation control practices (versioning, approvals, distribution) using document management or ALM tools (e.g., DOORS, Jama, Polarion, SharePoint, Confluence).
• Experience with the release of documents supporting software deliveries (release notes, build reports, configuration item lists).
• Experience in facilitation of change control processes (e.g., supporting or leading CCBs, managing change requests, recording decisions).
• Strong attention to detail and discipline in following established CM processes.
• Effective communication skills and the ability to work collaboratively with cross-functional teams.

Basic Qualifications for a Level 3:

• Bachelor’s degree with 5 years of relevant experience; 3 years with a Master's; 0 years with a PhD. An additional 4 years of relevant experience may be considered in lieu of a degree.
• Requires an active Top-Secret/Sensitive Compartmented Information (SCI) clearance at time of application
• Involvement with software builds (e.g., build scripts, CI/CD pipelines, build automation tools such as Jenkins, GitLab CI, Azure DevOps).
• Knowledge of controlling multiple software baselines (e.g., branch management, tagging, merging strategies in Git or other SCM tools).
• Demonstrated experience in documentation of software changes, including clear change descriptions, impact analysis, and traceability to requirements or tickets.
• Knowledge of documentation control practices (versioning, approvals, distribution) using document management or ALM tools (e.g., DOORS, Jama, Polarion, SharePoint, Confluence).
• Experience with the release of documents supporting software deliveries (release notes, build reports, configuration item lists).
• Experience in facilitation of change control processes (e.g., supporting or leading CCBs, managing change requests, recording decisions).
• Strong attention to detail and discipline in following established CM processes.
• Effective communication skills and the ability to work collaboratively with cross-functional teams.

Preferred Qualifications:

• Experience working in a regulated or mission-critical environment (e.g., aerospace, defense, medical, automotive).
• Familiarity with configuration audits and compliance reporting.
• Experience defining or improving CM processes, standards, and templates.
• Knowledge of software lifecycle models (Agile, incremental, waterfall) and how CM supports each.

#COSpace