Systems Engineering, Integration & Documentation Lead

Acclaim Technical Services, founded in 2000, is a leading cyber operations, intelligence solutions and operations, network infrastructure, engineering and business enablement and enterprise operations company supporting a wide range of U.S. Federal agencies. We are an Employee Stock Ownership Plan (ESOP) company, which is uncommon within our business sector. We see this as a significant strength, and it shows: ATS is consistently ranked as a top workplace among DC area firms and continues to grow.

We are actively hiring a Systems Engineering, Integration & Documentation Lead with a clearance and to support a program in Northern Virginia. In this role you will lead the architecture, integration, organization, traceability, configuration control, and documentation. This role requires someone who can define and govern architecture while remaining grounded in the realities of runtime operations, resilience, and maintainability

Authoritative Baseline and End-to-End Traceability:

This is the center of the role.

• Own and govern the authoritative technical baseline as thesingle sourceof truth for the engagement.

• Establish andmaintaintraceability across the full chain:contract and mission requirements → discovered cryptographic assets → supporting evidence → assessed risk → recommended remediation → migration decision → validation and closure.

• Ensure the chain is navigable in both directions forward from any requirement to its closure evidence, and backward from any migration decision to the findings and analysis that justified it.

• Activelyidentifybreaks in the chain — requirements with no discovery coverage, findings with no supporting evidence, risks with no recommended remediation, decisions with no validation — and drive each to resolution with the responsible technical SME.

• Reconcile conflicting technical evidence across work streams andmaintaina clear, defensible position where sources disagree.

• Preserve architecture decision records, assumptions, dependencies, exceptions, and change history so that migration recommendationsremaindefensible over time and withstand later scrutiny.

• Integrate outputs from cryptography, PKI, discovery, application security, cloud, data, RMF, and migration work streams into a coherent technical baseline.

• Establish andmaintainthe documentation repository and artifact structure.

• Identify discrepancies among artifacts produced by different teams and drive resolution with the appropriate technicalSME.

• Ensure technical conclusions from individual work streams are integrated without altering their technical meaning.

• System architecture documentation, system context diagrams, and data-flow diagrams

• Cryptographic architecture views, interface and API documentation, and Interface Control Documents where required

• Discovery plans and procedures

• CBOM documentation and data dictionaries

• Requirements traceability matrices

• Risk and crypto-agility assessments

• Migration plans and roadmaps

• Test and validation plans, test results, and closure evidence

• SOPs and operational runbooks

• Implementation plans

• Technical decision records

• Configuration and version baselines

• Maintain document configuration management, naming conventions, version control, approvals, and change history.

• Ensure baselines are controlled and that changes are traceable to an approved decision.

• Ensure technical evidence is structured for reuse across customer briefings, technical reports, migration plans, and executive deliverables.

• Coordinate with the Engagement Lead to ensure documentation supports contractual deliverables and milestones.

• Coordinate with the PQC Architect to ensure technical conclusions accurately reflect cryptographic risk…