Power BI Development for Global Hospitality Company

Power BI Frontend Specialist Requirements We are looking for a Power BI Frontend Specialist who can act as an execution partner, translating pre-built Gold data models and wireframes, or existing best-practice pages, into pixel-perfect, highly performant dashboards. This individual must combine strong UI/UX design discipline, including strict pixel alignment, information hierarchy, and clean layout grids, with software engineering rigor using .pbip files and Azure DevOps Git workflows. They must also possess advanced DAX and semantic modeling skills to ensure fast page load times, efficient calculation group implementation, and rich metadata structures that support AI and Copilot readiness. 1. DAX, Modeling & Performance DAX Formatting - All DAX measures must strictly follow standard formatting conventions, including proper indentation, capitalized keywords, and structured line breaks using tools such as DAX Formatter or Tabular Editor. Calculation Groups & Field Parameters - Dynamic measure switching and time intelligence toggles must be implemented using Calculation Groups via Tabular Editor or native Field Parameters. - Avoid nested SWITCH TRUE patterns where possible to prevent model bloat and performance degradation. User-Defined Functions - Ability to create reusable User-Defined Functions that enforce the DRY principle and centralize business logic. Model Discipline - Strong understanding of relationship configuration and star schema design. - One-to-many relationships must be maintained at all times unless an exception is explicitly approved with documented justification. - Naming conventions must strictly follow provided templates, including capitalization and formatting standards. - Exceptional attention to detail is required. AI Readiness and Copilot Optimization Metadata Description Metadata - Every measure, key dimension column, and table must contain a populated Description field explaining: - Business context - Calculation purpose - Formula intent in plain English Example: Calculates the 30-day rolling average occupancy percentage based on available room nights. Copilot Model Structuring - All exposed measures and dimensions must be assigned to clear Display Folders. - Intermediate or helper measures not intended for direct reporting or Copilot consumption must be hidden from end users. Synonyms and Natural Language Mapping - Populate Synonyms for measures and dimensions with common business terms, acronyms, and alternative names. Example: - Measure: RevPAR - Synonym: Revenue Per Available Room Data Categorization - Apply appropriate Data Categories to geospatial and temporal fields such as: - City - Country - Web URL - Date This improves natural language interpretation and AI-generated query quality. Measure Organization - All measures must reside within dedicated _Measures tables. - Measures must be organized into structured Display Folders. Example: _Measures Financials Rolling Metrics Performance Standards - Dashboard page render times must remain under 2 seconds in Performance Analyzer under standard Import mode conditions. - Technical interviews and assessments will evaluate competency in Power BI performance optimization. 2. Visual Layout, UX and UI Precision Grid and Layout Discipline Pixel Alignment - All visuals, KPI cards, slicers, and containers must use exact X and Y coordinate positioning. - Hand-dragged alignment is not acceptable. - Consistency across pages is mandatory. Information Hierarchy - Layouts should generally follow the F-pattern or Inverted Pyramid design approach: - Headline KPIs at the top left - Trend and breakdown charts in the middle - Detailed matrices and tables at the bottom Selection and Layering Order - All visual elements must be logically named within the Selection Pane. Examples: - Card - Total Revenue - Btn - Reset Filters - Related elements should be grouped appropriately. - Background shapes must be locked to prevent accidental modification. Color and Typography Semantic Color Usage - Colors must communicate meaning rather than serve as decoration. - Red, yellow, and green should be reserved for performance indicators such as variance and year-over-year results. Typography Standards - Follow the provided style guide exactly. - Use only approved font families, sizes, and weights. - Do not apply custom fonts to individual visuals. - KPI values, card labels, axis titles, and similar visual elements must maintain consistent sizing across all pages. Interactivity and Tooltips Explicit Titles - Visual titles must be customized with business-friendly and contextual naming. Slicers and Filters - Include persistent Reset Filter buttons using bookmarks. - Cross-filtering and highlighting behaviors must be intentionally configured for each visual. Bookmarks and Selection State - Bookmark naming must be clear and consistent. Examples: - BM_ResetFilters_Ops - BM_ToggleView_Monthly - Bookmarks should be grouped logically. - All bookmarks must use Selected Visuals rather than All Visuals to prevent unintended state changes elsewhere on the page. 3. Delivery Format, Git and DevOps Workflow File Architecture - Deliverables must be submitted as a .pbip Power BI Project directory structure. - Source control will be managed through Azure DevOps Git repositories. - Commit messages must be descriptive, meaningful, and traceable. 4. Operational and Communication Expectations Communication Cadence Provide a daily update or end-of-sprint summary containing: 1. What was completed today or during the sprint. 2. Current blockers or information required. 3. Planned work for the next day or sprint. Defect Response - Visual defects, calculation issues, and QA findings raised during Pull Request or testing phases must receive an initial response within 24 hours.