Data Engineer Microsoft Fabric in London

Data Engineer Microsoft Fabric London | Hybrid currently typically 2 days per month in London or Birmingham £55,000£65,000 + 10% bonus + 7% pension + benefits If youre already building with Microsoft Fabric and want more ownership of what happens to your solutions once they reach production, this role gives you that scope. A UK Wealth Management business is moving its enterprise data platform from Azure Synapse towards Microsoft Fabric and is looking for another hands-on Data Engineer to join the team. You wont have leadership or people-management responsibilities. Instead, youll be trusted to take ownership of your own engineering work, from understanding the requirement and working through the technical problem to building, testing, deploying and supporting the solution. Youll have senior engineers around you when you need them, but this isnt a junior role. What youll be working on Microsoft Fabric is at the heart of where the data platform is going. Youll work across: Building data pipelines using Microsoft Fabric Fabric Lakehouse, Warehouse and OneLake Developing data models and analytics solutions Power BI development ETL/ELT SQL and SQL Server Azure Data Lake Internal and third-party API integrations Azure DevOps and Git CI/CD and production deployments Supporting existing Synapse solutions during the transition The client isnt looking for someone whose Fabric experience ends when a project goes live. They want an engineer who has stayed close to the solutions theyve built and understands the operational side of Data Engineering: supporting production services, investigating problems, making improvements and adapting solutions as requirements evolve. What were looking for Microsoft Fabric and Power BI are both important requirements. For Fabric specifically, you should have been hands-on in your current or most recent role . Ideally, youll have worked with Fabric for long enough to experience the full lifecycle rather than just the initial implementation. You should be able to talk about what you built, how it performed in production, issues you encountered and how the solution evolved. <...