Cloud Data Architect (Contingent)
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have content: About the role (the description paragraph). Then responsibilities: "What You'll Be Doing" list. Then requirements: "What You'll Bring" and "Requirements". Also there is mention of contract contingency notice, but that's metadata; we can fold into a short
maybe. We need to avoid boilerplate like "Contract Contingency Notice:"? It's not boilerplate but it's a notice; we can include as a paragraph. We must not include application instructions, EEO, etc. There's none. We need to produce sections: About the role (
About the role
then...). Responsibilities (
Responsibilities
then- ...). Requirements (
Requirements
then- ...). Possibly Qualifications? The "What You'll Bring" could be qualifications. But we can treat as Qualifications. However we need to decide: The posting includes "What You'll Bring" which lists Azure Data Environments, Azure Government and Azure Commercial, Databricks Architecture and Compliance Documentation, Demonstrated expertise managing and documenting technical architecture, security and compliance strategies, and data platform engineering, Relevant Disciplinary Expertise: Expertise in the disciplines and technical areas related to the platform architecture, security, and compliance tasks described above. That's qualifications. Also "Requirements" includes authorization to work, public trust, reside in US, production system monitoring schedule, contract contingency.
Thus we can have sections: About the role, Responsibilities, Qualifications, Requirements. Possibly Skills? Not separate.
We must not create Pay/Benefits/Schedule unless stated. There is schedule mentioned: "Production system monitoring and support coverage runs 7:00 a.m. to 8:00 p.m. Eastern Time, with participation in a 24/7 on-call escalation process for urgent issues." That's schedule info. So we could include a Schedule section. However the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule, so we can include Schedule section. But we also have schedule info within Requirements; we could move to Schedule section. However we need to preserve all substantive info; we can either keep schedule in Requirements or create Schedule section. The instruction: Prefer a few substantive sections over many thin ones. So maybe we keep schedule within Requirements rather than create a separate Schedule section, to avoid thin section. But schedule is specific; but we can incorporate into Requirements as a bullet. That's fine.
We must not repeat job title as heading. Not include Job ID.
We must output only HTML fragment.
Let's extract content.
About the role paragraph: "Wilcore is hiring a Cloud Data Architect to support an enterprise cloud-based data and analytics platform for a federal health agency. The platform provides governed data storage, engineering and analytics tools, platform integrations, and policy controls for data practitioners across the enterprise, and supplies the technical foundation for component data platforms managed by other parts of the agency. In this role you will establish and continuously steward enterprise platform architecture, security baselines, and Authority to Operate-aware provisioning across the platform and its component platforms, so that teams build on governable, interoperable, and cost-effective designs."
We could also include the Contract Contingency Notice: "This position is contingent upon contract award. Employment offers will be extended only upon successful contract award and client approval. Candidates may be considered and interviewed in advance to support rapid onboarding should the contract be awarded." This is metadata but we can include as a short paragraph maybe under About the role or separate? It's not a section heading; we can fold into a short
after the About the role paragraph. Now Responsibilities: list items from "What You'll Be Doing". Let's capture each bullet: - Set a Policy-First Foundation: Establish and operate clearly documented rules and guardrails around security, compliance, identity and access, data handling, and application design that drive consistent, governed behavior for platform teams and customers. - Publish the Enterprise Blueprint: Create and maintain the enterprise reference architecture, roadmap, and policies spanning the platform and its component platforms, with clear guardrails for lakehouse tiers, approved consumption patterns, cross-platform integration, and identity and access architecture. - Standardize Designs and Data Management: Define authoritative reference patterns, interfaces, and guardrails aligned with Zero Trust Architecture principles and ATO considerations. Set platform-wide data management standards — medallion, lineage, catalogs, open formats — for consistent lakehouse operations. - Define and Operate Interoperability: Specify identity, networking, and trust models for on-premises and third-party interconnections. Document approved connection patterns and maintain boundary diagrams and Ports, Protocols, and Services Management documentation for approved system interconnections. - Operate Architecture Governance: Run Architecture Review Boards, capture Architecture Decision Records, and maintain a Register of Exceptions, keeping decisions traceable to the enterprise reference architecture and visible across cloud platforms. - Provide Solution Architecture: Deliver architectural guidance and cloud cost estimates for customer initiatives and evaluate additions to platform capabilities when needed. - Plan and Govern Hosting Transitions: When authorized, provide design and risk guidance on identity, networking, resiliency, cost and performance, and ATO impacts for hosting transitions, integrating decisions into the enterprise reference architecture and compliance artifacts. - Manage ATO and Change-Driven Security: Execute Risk Management Framework-aligned ATO activities to sustain confidentiality, integrity, and availability. Govern Security Impact Analysis through intake and review workflows, recording approved designs and mappings before implementation. - Set Observability and DevSecOps Standards: Establish platform-wide observability and auditability requirements and DevSecOps practices. Define logging, metrics, and trace schemas, retention and routing, SLO and SLA monitoring, and incident playbooks. Require secure CI/CD with quality gates, code scanning, and secrets management. - Ensure Data and Model Parity: Operate and improve the platform's delta lake patterns and dedicated pool usage, ensuring parity of data and models migrated from other platforms before customer release. - Coordinate Across Platforms: Coordinate with experts across other agency data platforms to align modeling, metadata, and analytics approaches with component platforms, legacy warehouse data architecture, and domain subject-matter experts. - Optimize Cloud Cost and Performance: Monitor resource provisioning and utilization and provide visual reports, projections, and automated flags when costs increase, to support FinOps-informed decisions through a FinOps Dashboard. Now Qualifications (What You'll Bring): items: - Azure Data Environments: Azure Government and Azure Commercial, should also be familiar with Databricks Architecture and Compliance Documentation - Demonstrated expertise managing and documenting technical architecture, security and compliance strategies, and data platform engineering. - Relevant Disciplinary Expertise: Expertise in the disciplines and technical areas related to the platform architecture, security, and compliance tasks described above. We could format as bullet list. Now Requirements: items: - Applicants must be authorized to work in the United States. - Must be able to obtain and maintain a federal Public Trust (Tier 2 / Moderate Risk) background investigation. - Must reside and perform all work within the continental United States. - Production system monitoring and support coverage runs 7:00 a.m. to 8:00 p.m. Eastern Time, with participation in a 24/7 on-call escalation process for urgent issues. - This position is contingent upon contract award. (maybe we already included earlier; but we can keep as a note.) We could combine contract contingency note into a paragraph. Now we need to output HTML. Structure:
About the role
Wilcore is hiring a Cloud Data Architect to support an enterprise cloud-based data and analytics platform for a federal health agency. The platform provides governed data storage, engineering and analytics tools, platform integrations, and policy controls for data practitioners across the enterprise, and supplies the technical foundation for component data platforms managed by other parts of the agency. In this role you will establish and continuously steward enterprise platform architecture, security baselines, and Authority to Operate-aware provisioning across the platform and its component platforms, so that teams build on governable, interoperable, and cost-effective designs.
Contract Contingency Notice: This position is contingent upon contract award. Employment offers will be extended only upon successful contract award and client approval. Candidates may be considered and interviewed in advance to support rapid onboarding should the contract be awarded.
Responsibilities
- Set a Policy-First Foundation: Establish and operate clearly documented rules and guardrails around security, compliance, identity and access, data handling, and application design that drive consistent, governed behavior for platform teams and customers.
- Publish the Enterprise Blueprint: Create and maintain the enterprise reference architecture, roadmap, and policies spanning the platform and its component platforms, with clear guardrails for lakehouse tiers, approved consumption patterns, cross-platform integration, and identity and access architecture.
- Standardize Designs and Data Management: Define authoritative reference patterns, interfaces, and guardrails aligned with Zero Trust Architecture principles and ATO considerations. Set platform-wide data management standards — medallion, lineage, catalogs, open formats — for consistent lakehouse operations.
- Define and Operate Interoperability: Specify identity, networking, and trust models for on-premises and third-party interconnections. Document approved connection patterns and maintain boundary diagrams and Ports, Protocols, and Services Management documentation for approved system interconnections.
- Operate Architecture Governance: Run Architecture Review Boards, capture Architecture Decision Records, and maintain a Register of Exceptions, keeping decisions traceable to the enterprise reference architecture and visible across cloud platforms.
- Provide Solution Architecture: Deliver architectural guidance and cloud cost estimates for customer initiatives and evaluate additions to platform capabilities when needed.
- Plan and Govern Hosting Transitions: When authorized, provide design and risk guidance on identity, networking, resiliency, cost and performance, and ATO impacts for hosting transitions, integrating decisions into the enterprise reference architecture and compliance artifacts.
- Manage ATO and Change-Driven Security: Execute Risk Management Framework-aligned ATO activities to sustain confidentiality, integrity, and availability. Govern Security Impact Analysis through intake and review workflows, recording approved designs and mappings before implementation.
- Set Observability and DevSecOps Standards: Establish platform-wide observability and auditability requirements and DevSecOps practices. Define logging, metrics, and trace schemas, retention and routing, SLO and SLA monitoring, and incident playbooks. Require secure CI/CD with quality gates, code scanning, and secrets management.
- Ensure Data and Model Parity: Operate and improve the platform's delta lake patterns and dedicated pool usage, ensuring parity of data and models migrated from other platforms before customer release.
- Coordinate Across Platforms: Coordinate with experts across other agency data platforms to align modeling, metadata, and analytics approaches with component platforms, legacy warehouse data architecture, and domain subject-matter experts.
- Optimize Cloud Cost and Performance: Monitor resource provisioning and utilization and provide visual reports, projections, and automated flags when costs increase, to support FinOps-informed decisions through a FinOps Dashboard.
Qualifications
- Azure Data Environments: Azure Government and Azure Commercial, should also be familiar with Databricks Architecture and Compliance Documentation
- Demonstrated expertise managing and documenting technical architecture, security and compliance strategies, and data platform engineering.
- Relevant Disciplinary Expertise: Expertise in the disciplines and technical areas related to the platform architecture, security, and compliance tasks described above.
Requirements
- Applicants must be authorized to work in the United States.
- ...). Possibly Qualifications? The "What You'll Bring" could be qualifications. But we can treat as Qualifications. However we need to decide: The posting includes "What You'll Bring" which lists Azure Data Environments, Azure Government and Azure Commercial, Databricks Architecture and Compliance Documentation, Demonstrated expertise managing and documenting technical architecture, security and compliance strategies, and data platform engineering, Relevant Disciplinary Expertise: Expertise in the disciplines and technical areas related to the platform architecture, security, and compliance tasks described above. That's qualifications. Also "Requirements" includes authorization to work, public trust, reside in US, production system monitoring schedule, contract contingency.
Thus we can have sections: About the role, Responsibilities, Qualifications, Requirements. Possibly Skills? Not separate.
We must not create Pay/Benefits/Schedule unless stated. There is schedule mentioned: "Production system monitoring and support coverage runs 7:00 a.m. to 8:00 p.m. Eastern Time, with participation in a 24/7 on-call escalation process for urgent issues." That's schedule info. So we could include a Schedule section. However the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule, so we can include Schedule section. But we also have schedule info within Requirements; we could move to Schedule section. However we need to preserve all substantive info; we can either keep schedule in Requirements or create Schedule section. The instruction: Prefer a few substantive sections over many thin ones. So maybe we keep schedule within Requirements rather than create a separate Schedule section, to avoid thin section. But schedule is specific; but we can incorporate into Requirements as a bullet. That's fine.
We must not repeat job title as heading. Not include Job ID.
We must output only HTML fragment.
Let's extract content.
About the role paragraph: "Wilcore is hiring a Cloud Data Architect to support an enterprise cloud-based data and analytics platform for a federal health agency. The platform provides governed data storage, engineering and analytics tools, platform integrations, and policy controls for data practitioners across the enterprise, and supplies the technical foundation for component data platforms managed by other parts of the agency. In this role you will establish and continuously steward enterprise platform architecture, security baselines, and Authority to Operate-aware provisioning across the platform and its component platforms, so that teams build on governable, interoperable, and cost-effective designs."
We could also include the Contract Contingency Notice: "This position is contingent upon contract award. Employment offers will be extended only upon successful contract award and client approval. Candidates may be considered and interviewed in advance to support rapid onboarding should the contract be awarded." This is metadata but we can include as a short paragraph maybe under About the role or separate? It's not a section heading; we can fold into a short