Enterprise Solution Architect

Define the target state architecture for Microsoft Fabric including: Workspaces/domains strategy aligned to enterprise operating model (centralized CoE, federated domains, or hybrid). Define patterns for ingestion and integration across source systems: Structured sources (SQL Server/Oracle/SaaS), unstructured files, APIs, events (where required).

Enterprise Solution Architect (Day 1 onsite)
Arlington, VA (Priority 1) and St. Louis, MO (Priority 2)
Experience
10–15+ years in enterprise architecture / data platform architecture
Deep experience in Microsoft Fabric + Power BI ecosystem and modern data platform principles
Proven delivery leadership for large programs (multi-domain, 1000+ user scale)
Strong background in:
Security architecture, compliance/audit, governance design
Metadata/lineage/catalog design and stewardship models
Migration modernization programs (DW/ETL/BI transformations)
Executive communication and stakeholder management experience
Key Responsibilities (Must-Have)
Enterprise Architecture
Strategy (Target State + Roadmap)
Define the target state architecture for Microsoft Fabric including:
Workspaces/domains strategy aligned to enterprise operating model (centralized CoE, federated domains, or hybrid)
OneLake architecture and multi-zone data layout (landing/curated/serving)
Standard architecture patterns for Lakehouse, Warehouse, Real-time, and Semantic models
Develop the platform adoption roadmap:
Phased onboarding strategy for 100s of teams and 1,000s of users
Capability roadmap (governance maturity, automation maturity, migration waves)
Reference implementation(s) and scaling patterns
Own architecture decisioning:
Document Architecture Decision Records (ADRs)
Ensure consistency of patterns across domains and teams
Security, Compliance, and Risk Architecture (Zero Trust
Enterprise Controls)
Design enterprise-grade security controls for Fabric:
Tenant, capacity, workspace governance boundaries
Entra ID group-driven RBAC strategy and least privilege access design
Separation of duties across Admin/Platform/Engineering/Business personas
Define compliance and auditing requirements:
Data classification and sensitivity labeling approach
Data access auditing, lineage for compliance, and evidence generation model
Retention and lifecycle controls aligned to enterprise policy (where applicable)
Enterprise Governance Architecture
Architect the enterprise governance ecosystem:
Define Purview’s role (scanning, classification, lineage, policy enforcement where applicable)
Define Atlan’s role (enterprise catalog UI, glossary, stewardship workflows, governance operating processes)
Design and guide implementation of:
Metadata synchronization strategy (system of record, mapping rules, identity resolution)
Lineage strategy (Fabric lineage + enterprise lineage consolidation)
Business glossary alignment and stewardship RACI across domains
Define governance workflows:
Data product certification/endorsement, publishing guardrails
Controlled sharing models and approvals for sensitive data
Data contract and documentation standards
Integration Architecture (Sources, Formats, and Consumption)
Define patterns for ingestion and integration across source systems:
Structured sources (SQL Server/Oracle/SaaS), unstructured files, APIs, events (where required)
Batch and incremental (CDC) ingestion strategies
Data quality and schema drift strategy
Define serving and consumption architecture:
Semantic model strategy (shared models, certified datasets, RLS/OLS patterns)
Power BI workspace/app distribution model and content lifecycle
Data sharing patterns across workspaces/domains (governed reuse, avoiding duplication)
Migration
Modernization Leadership
Lead modernization and migration planning:
Discovery and assessment of legacy platforms (DW/ETL/BI, on-prem to cloud)
Workload classification and migration wave planning
Target patterns: refactor vs rehost vs replatform
Define migration accelerators/approach:
Metadata-driven ingestion, automated reconciliation, parallel run strategy
Validation strategy: data parity, performance, security, and operational readiness
Operational Model, Observability
FinOps Strategy
Define platform operations:
SLO/SLA model for platform and critical data products
Incident/change/release management and ITSM integration
Define observability strategy:
Capacity monitoring, workload health, lineage coverage, governance compliance metrics
Own FinOps strategy:
Cost allocation model
Workload optimization and capacity planning approach
Good-to-Have
Data Mesh / Data Product operating model experience
Experience integrating external governance tools (Atlan, Collibra, etc.)
Cost management and chargeback frameworks
ITIL/ITSM operations integration (ServiceNow/Remedy, etc.)