Data Architect
- Discuss this with your agent
- Open in Claude
- Open in ChatGPT
Prepare application
- Draft this with your agent
- Open in Claude
- Open in ChatGPT
Role details
Tech stack
+15 more
Job description
Tenant Management: Configure and audit tenant settings, ensuring feature parity and security compliance across the organization. Capacity Optimization: Monitor Fabric Capacity (F-SKUs) usage via the Capacity Metrics app; implement scaling strategies to balance performance and cost. Security: Enforce fine-grained access control (RBAC), Row-Level Security (RLS), and Object-Level Security (OLS) across the Fabric ecosystem. Purview Integration: Manage data discovery and lineage through Microsoft Purview to ensure data democratization remains compliant, design and enforce labels to ensure protection across Fabric. Governance : Configure DLP policies to prevent unauthorized sharing or leakage of sensitive data from Lakehouses and Semantic Models. Logging, Alerting & Capacity Management: Integrate Fabric with Azure Log Analytics for long-term auditing and trend analysis , proactive monitoring and manage throttling and smoothing events; identify ânoisy neighborâ workloads and implement scaling or staggering strategies to ensure performance. Power BI: Establishing standards and conduct training for non IT data access PowerBI users in support of our data governance programs
Architecture & Engineering Design & Implement: Oversight over build out our Medallion Architecture (Bronze, Silver, Gold) using Fabric Lakehouses and Warehouses. Providing best practices to data developers to insure fabric capacity is not over consumed and is optimized. Data Integration: Develop efficient orchestration patterns using Data Factory pipelines and Dataflows Gen2, utilizing Shortcuts to minimize data duplication. Design, implement and manage all connectivity to the MS Fabric including data load sources from SaaS providers Performance Tuning: Optimize semantic models for DirectLake mode to provide near-real-time reporting without the overhead of traditional Import modes. CI/CD & DevOps: Establish deployment pipelines using Git integration to manage lifecycle transitions between Dev, Test, and Production.
Requirements
Experience: 10 years in Data Architecture or Engineering, with at least 3-4 years of hands-on experience in Microsoft Fabric (or deep expertise in Power BI Azure Synapse/Databricks). Technical Mastery: Proficient in PySpark/Notebooks, T-SQL, and DAX. Data Strategy: Proven track record of designing âOneLakeâ architectures that break down departmental data silos.
Nice to Have Skills: Azure, Experience: 10 years in Data Architecture or Engineering, with at least 3-4 years of hands-on experience in Microsoft Fabric (or deep expertise in Power BI Azure Synapse/Databricks). Technical Mastery: Proficient in PySpark/Notebooks, T-SQL, and DAX. Data Strategy: Proven track record of designing âOneLakeâ architectures that break down departmental data silos.
Minimum Years of Experience: 10 years
Certifications Needed: Any certification is preferred but no required
Skills: Access Control, Auditing, Best Practices, Capacity Management, Computer Security, Continuous Deployment/Delivery, Continuous Integration, Data Management, DataArchitect Data Modeling Tool, DevOps, Ecosystems, Fabric Management, Git, Metrics, Microsoft Product Family, Microsoft Transact-SQL (T-SQL), Microsoft Windows Azure, Performance Tuning/Optimization, Power BI, Product Lifecycle, Security Compliance, Software as a Service (SaaS), Stock Keeping Unit (SKU), Testing, Training/Teaching, Trend Analysis
Apply for this position
This job is hosted externally. Click below to view the full posting and apply.
Prepare application
- Draft this with your agent
- Open in Claude
- Open in ChatGPT
Good distractions
Talks and stories from around this role â technically off-topic, practically not.
Moments
Explore playlistsVideos
See allRelated articles
See all
Making Data Warehouses Fast: A Developerâs Story
Data Engineer Salary UK
Graph and AI Trends 2026: Why Is AI Running but Not Yet Delivering?
Why Event-Driven Architecture Isnât About Speed (and When You Actually Need It)