Peraton is looking to hire a Data Architect in the Washington DC Metro area. This role will be a remote position. At times, the role will also require travel to the Quantico client site when necessary.
The Data Architect defines the enterprise data architecture supporting operational systems, analytical platforms, and AI initiatives. The role is central to the Enterprise Data Layer (EDL), which brings together operational data stores and a data lake under common governance. The Data Architect establishes the event-driven integration patterns, governance and metadata standards, and reusable data products that enable secure, attribute-based access for enterprise teams, agency components, and authorized industry partners. Assess legacy systems to understand data structures, data quality, storage mechanisms, and transformation logic.
The Data Architect works closely with the Systems Architect on enterprise direction, with Solutions Architects on product-level data needs, and with Data Engineers who implement the patterns the role defines.
- Define the target-state data architecture spanning operational stores (relational and non-relational) and the analytical data lake.
- Develop conceptual, logical, and physical data models that support both transactional systems and analytics.
- Establish standards for how data moves from operational systems into the EDL and how it is curated for downstream use.
- Define how operational and analytical workloads are separated while keeping data consistent and traceable.
Event-Driven Integration and the EDL
- Design event-driven integration patterns that feed the EDL, using messaging and an enterprise service bus to capture changes from operational systems.
- Define standards for event schemas, change data capture, ordering, replay, and error handling.
- Leverage streaming data ingestion
- Coordinate with Solutions Architects so that product teams publish and consume data through approved EDL patterns rather than point-to-point integrations.
Data Products and Sharing
- Define reusable data products with clear ownership, documented schemas, lineage, quality expectations, and access policies.
- Establish the publishing model that makes data products discoverable and consumable by enterprise, agency, and authorized industry consumers.
- Apply data product principles influenced by data mesh, while keeping ownership and decentralization decisions aligned with program direction.
- Define versioning and deprecation practices so that consumers can depend on stable interfaces.
Governance, Quality, and Secure Access
- Define data governance, metadata, and cataloging standards, including business and technical metadata.
- Design Attribute-Based Access Control (ABAC) policies so that authorization reflects user, resource, and mission attributes.
- Establish data quality, lineage, and stewardship practices across the EDL.
- Ensure data handling aligns with privacy, security, and federal compliance requirements, in partnership with cybersecurity teams.
AI-Ready Data Enablement
- Ensure the data architecture supports analytics, machine learning, and Generative AI use cases, including feature reuse and retrieval patterns.
- Partner with Data Scientists and Solutions Architects to make trusted, well-documented data available for AI workloads.
- Define how sensitive data is protected and masked when used for model development and evaluation.
