08.11.26

Placing a Power BI and Microsoft Fabric Lead to Unify Workday HR and Finance Reporting

Overview

A Fabric-based consultancy programme needed a Lead BI candidate who could sit at the exact intersection of Workday HR data and enterprise financial reporting — someone who had actually built Medallion architecture layers, not just mentioned Fabric on a CV. Dcoded ran a structured screening process against this brief, interrogating candidates on Workday-to-financial-system integration, Medallion layer design, DAX-driven semantic models, and genuine self-service BI delivery. The process surfaced candidates with specific, verifiable depth — including one Microsoft-recognised "super user," a credential held by only around 100 people worldwide — demonstrating that cross-functional HR-to-finance BI leadership is a distinct, narrower skill set than generic Power BI recruiting, and one that requires a different interview altogether.

The Challenge

Clients running Fabric adoption or BI modernisation programmes increasingly need a Lead BI hire who can do three things at once: own the semantic layer strategy, integrate HR platforms like Workday with financial systems, and mentor a team while fielding director and C-suite stakeholders directly. One brief Dcoded worked described exactly this — a Fabric Lead BI position "focusing on all things Gold Layer on a Fabric implementation," where the hire would "define the strategy alongside the wider data transformation" and act as "the bridge between the architecture team, the engineering team, and like director and C-suite level stakeholders". Another brief for a BI Lead on a major enterprise data transformation programme called for someone who could take "full ownership of BI strategy, moving the business away from messy reporting towards a proper governed semantic and self-service model built on Power BI," using DAX, Power Query and star schemas, with real stakeholder exposure and a small team to mentor.

The risk with roles like this is obvious to anyone who has screened Power BI talent at volume: plenty of candidates can describe building a dashboard, but far fewer can describe owning a Workday-to-finance integration end to end, defending a Medallion architecture decision, or explaining what "self-service BI" actually changes about how a business consumes reporting. A generic Power BI recruiter asking generic Power BI questions will not catch that gap until the candidate is three weeks into the client's programme.

The Approach

Dcoded's consultants ran technical conversations designed to separate candidates who had implemented Workday HR-to-finance integrations from those who had merely connected to Workday as one data source among many. In one screening call, a consultant asked directly: "do you have any experience working with Workday?" — and followed up by asking the candidate to explain, in simple terms, how they had implemented it. The answer that passed muster wasn't a name-drop. One candidate described connecting Workday HR data with Oracle EPBCS financial information to build a headcount and salary dashboard for a Head of HR who needed to control business costs, with the semantic model refreshing every half hour and slicers exposing tenure, location, department and salary at the individual employee level. That candidate also described the underlying connection method — native web service and IIS connections into Power BI, or a CData Power BI connector requiring substantial custom SQL — which is the kind of implementation detail a CV keyword match will never surface.

On Medallion architecture specifically, Dcoded's consultants pushed candidates past the standard bronze-silver-gold definition and into stakeholder consequence. One candidate explained that Fabric architecture requires extracting data into a bronze layer, feeding it into silver for transformation, and exposing only the gold layer to end users — with the bronze layer reserved for developers and raw data integrity, not for business consumption. That same candidate volunteered that he was a Microsoft-recognised "official super user," noting that "there are only 100 super users over the world which are recognized by the Microsoft leader, senior leadership team" — a credential that functions as a hard, checkable proof point rather than a soft claim of expertise.

Implementation

Screening calls followed a consistent structure built to test cross-functional depth rather than tool familiarity alone:

• Workday-to-finance integration experience. Consultants asked candidates to walk through a real Workday implementation, including which financial system it was joined to and what business question it answered. One candidate's answer tied Workday HCM data directly to Oracle EPBCS to solve a specific cost-reduction brief from a Head of HR.

• Medallion architecture fluency. Candidates were asked to explain bronze, silver and gold layers in their own words and to name the companies where they had built that architecture in Fabric — not just confirm they'd heard the term. One candidate named Wolseley, Einstein AI, a leading US university and a UK oil company as environments where he had delivered Fabric and Power BI projects.

• DAX and self-service BI delivery. Briefs explicitly called for candidates comfortable moving a business "from messy data and reporting towards a proper governed semantic layer and self-service models," using DAX, Power Query and star schemas. This framing was used as a direct screening prompt, not a background qualifier.

• End-to-end ownership, not just development. One candidate described a full 360-degree role — taking requirements from stakeholders, defining metrics, building the semantic model, running user acceptance testing, documenting the solution and submitting the finished dashboard — after having implemented an entire Power BI infrastructure from scratch at London Stock Exchange and Post Office.

• Stakeholder and mentoring capability. Lead roles required managing both the technical build and junior staff. One candidate described leading a team of 10 to 12 people at Bank of Ireland, sitting directly with stakeholders to gather requirements and training junior BI consultants as a routine part of the role.

• Contract structure and compliance terms. Where roles were pitched outside IR35, Dcoded consultants were explicit about what that status permits — flagging, for example, that "mentoring" junior staff is compatible with an outside-IR35 engagement where "managing" them would not be.

Each conversation also tested whether a candidate could demonstrate their work live. One candidate offered to share his own Power BI portfolio and screen-share the semantic model he had built joining Workday and financial data, backed by his own Power BI licence — the kind of verifiable, show-your-work evidence that separates a genuine Lead BI candidate from someone who can talk convincingly about the architecture without having shipped it.

Separately, Dcoded ran comparable Fabric and Power BI screening on contract-focused briefs, including a four-month BI Lead engagement at a day rate of around 450 to 500 outside IR35, built around moving a business from messy reporting toward a governed semantic and self-service model with hands-on architecture and stakeholder exposure. This confirms the same technical-depth bar applies whether the engagement is permanent leadership or a focused contract placement.

Results & Impact

The screening process surfaced candidates who could answer the three questions a generic Power BI interview never asks: how did you actually join Workday to a financial system, what does your Medallion architecture look like layer by layer, and can you show me the semantic model rather than describe it. One candidate demonstrated direct, hands-on Workday-to-Oracle EPBCS integration delivering half-hourly refreshed headcount and salary reporting, sliceable by employee, tenure, department and location. Another demonstrated verifiable Fabric and Medallion architecture delivery across named enterprise clients, backed by Microsoft super-user recognition — a status held by roughly 100 people globally. A third demonstrated end-to-end Power BI infrastructure build-out from requirements gathering through to documentation and sign-off at major enterprise clients.

For Fabric adoption programmes, this matters because the brief itself demanded someone who could be "the bridge between the architecture team, the engineering team, and like director and C-suite level stakeholders" while also mentoring junior Power BI developers and data analysts, some offshore, under a consultancy delivery model. A candidate who can describe Medallion layers in the abstract but cannot name a real HR-to-finance integration they have shipped will fail that brief regardless of how polished their CV looks. Dcoded's screening approach — asking candidates to explain Workday implementations "a bit simpler" and walk through the mechanics in plain language — is designed specifically to catch that gap before a client ever sees the shortlist.

Key Takeaways

• HR-to-finance BI integration is a distinct skill, not a Power BI add-on. Candidates who can genuinely join Workday HR data to systems like Oracle EPBCS and build governed, scheduled reporting on top of it are demonstrably rarer than candidates who list "Power BI" and "Workday" as separate CV bullet points.

• Medallion architecture fluency has to be tested, not assumed. The strongest candidates could explain why only gold-layer data reaches end users, while bronze remains a developer-only raw layer — and could name the specific enterprise environments where they built that structure.

• Hard credentials beat soft claims. Microsoft's official "super user" recognition — held by roughly 100 people worldwide — is the kind of checkable proof point that separates a genuine BI leader from a confident generalist.

• Self-service BI and DAX depth are screening criteria, not nice-to-haves. Briefs that call for moving a business from "messy reporting" to "governed semantic layer and self-service models" require consultants to probe DAX, Power Query and star schema experience directly, not take it on faith.

• End-to-end ownership separates leads from developers. Candidates who had taken a Power BI implementation from stakeholder requirements through to documentation and sign-off — not just built reports against someone else's spec — were the ones who matched genuine Lead BI briefs.

• IR35 structure shapes what a Lead role can actually include. Mentoring juniors is compatible with outside-IR35 contracting; managing them is not — a distinction Dcoded's consultants raise explicitly during screening, not after placement.

If your Fabric adoption programme needs a Lead BI hire who can genuinely bridge Workday HR data and financial reporting — not just talk about Medallion architecture in an interview — that's the exact screening gap Dcoded is built to close. Get in touch to discuss your brief.