Configuration Manager (Hybrid- Annapolis, MD)

Fairwinds Technologies, L
3d$85,000 - $144,000Hybrid

About The Position

The C-UAS Configuration Manager develops, reviews, and maintains the Configuration Management (CM) Plan across the full software/system lifecycle for an integrated C‑UAS capability (C2 software; RF/radar/EO‑IR sensors; networking/backhaul; trailerized kits; cyber controls; and, when authorized, EW/jamming components). The role leads CM governance, oversees software versioning/builds/releases, ensures release integrity across multi‑stage environments, and tracks/report changes through CRs, impact analyses, and version control. The Configuration Manager also establishes a documentation repository, leads software/code reviews for CM adherence, reports CM status in governance meetings, and oversees packaging of releases for testing and deployment—while managing budget and staffing for the CM function. Locations: Annapolis, MD

Requirements

  • Must be a U.S citizen with an ACTIVE security clearance of at least the SECRET level.
  • Bachelor’s degree in Engineering (Systems, Electrical, Mechanical, Aerospace), Computer Science, or a related technical field.
  • 10+ years of progressive Configuration Management experience on complex federal systems with substantial software content (preferably C4ISR/UAS/C UAS or similar).
  • Bachelor’s degree in Computer Science, Software Engineering, Systems Engineering, or related technical field.
  • Demonstrated expertise writing and maintaining CM Plans and operating CCBs in accordance with IEEE 828 and/or ISO 10007; strong grasp of identification, baselining, change control, status accounting, and audit.
  • Hands on with version control (e.g., Git), CI/CD, artifact repositories, build/release tools, and dependency/BoM management.
  • Experience supporting RMF authorization and NIST 800 53 CM controls through CM records, baselines, and change documentation.
  • Strong familiarity with DHS SELC stages and artifacts, including how CM supports technical reviews and acceptance/fielding decisions.

Responsibilities

  • Author, baseline, and maintain the Configuration Management Plan (CMP) that defines configuration items (CIs), baselines, change control workflows, status accounting, configuration audits, build/release engineering, and roles/responsibilities.
  • Tailor CM to DHS SELC phases and technical review entrance/exit criteria; ensure CM artifacts are ready for reviews and acquisition decisions.
  • Establish Configuration Control Board (CCB) charters and procedures; run CCBs and ensure timely adjudication of CRs and documentation updates.
  • Oversee branching/merging strategies, semantic versioning, build & release engineering, and promotion gates to maintain release integrity across multi stage environments in line with IEEE 828.
  • Track and report release content through CRs, impact analyses, and version control metadata; maintain authoritative Bill of Materials and release notes for each baseline.
  • Oversee packaging of software releases (installers/containers/images) for lab DT, OT venues, pilot deployments, and fielding. Align handoffs to DHS SELC test/implementation stages.
  • Stand up and administer a documentation with immutable baselines and traceability.
  • Maintain configuration status accounting dashboards; ensure accurate, current, and complete CM records for internal teams and external oversight.
  • Operate a change control process that assesses technical, security, safety, spectrum, and operational impacts prior to approval; maintain impact analysis and decision logs.
  • Plan and execute Functional and Physical Configuration Audits (FCA/PCA), verify documentation vs. product baselines, and drive discrepancy closure.
  • Collaborate with cybersecurity to ensure configuration baselines, changes, and release records support RMF authorization evidence and continuous monitoring and CM family controls.
  • Provide guidance and leadership to the CM team; define CM SOPs, enforce quality gates, and coach development and test teams on CM best practices.
  • Report CM status and risks in program reviews; escalate roadblocks early.
  • Manage the CM budget (tools, automation, storage, licenses) and staffing to meet release cadence and audit/compliance requirements.
© 2024 Teal Labs, Inc
Privacy PolicyTerms of Service