Business Intelligence Architect II

Gifthealth•Columbus, OH

3d•Hybrid

About The Position

At Gifthealth, we're revolutionizing the way people experience healthcare by simplifying the process of managing prescriptions and health services. Our mission is to provide a seamless, personalized, and efficient healthcare experience for all our customers. We're a dynamic, innovative, and customer-centric company dedicated to making a positive impact on people's lives. Position Summary We are seeking a Business Intelligence Architect II to own the Looker semantic layer, BI platform provisioning, and the design of external client-facing BI access, while setting technical direction for BI developers and analysts across the domain. This position plays a key role in supporting the Data & Analytics department and reports to the Manager, BI & Reporting (until that role is filled, the Director of Data & Analytics), ensuring alignment with organizational goals, operational excellence, and compliance standards. This is a platform-level individual-contributor role: there are no direct reports at this level, but the role carries technical direction and mentorship for BI developers and analysts, and real hands-on time in LookML and SQL.

Requirements

Bachelor's degree preferred; not required. We evaluate demonstrated capability rather than credentials.
7 to 10 years of experience in business intelligence or data platform work, including deep hands-on Looker/LookML project structuring and strong SQL/dbt experience. This band is guidance rather than a gate.
Deep Looker and LookML experience: has structured a LookML project, made the modeling calls, and lived with them a year later — not just used Looker.
Has designed a semantic or metric layer that other people built on, and can explain what didn't work the first time.
Strong SQL skills and enough dbt fluency to argue about where a transformation belongs and then go write it.
Experience with multi-tenant or external-facing BI access: row-level security, per-customer isolation, and the difference between hiding data and not sending it.
Willing to chase a metric definition into the operational reality behind it, and writes standards down so they can actually be found and followed.
Demonstrated application of the above Qualification

Nice To Haves

healthcare, pharmacy, or other regulated-data experience (PHI, HIPAA, masking, role-based access as daily practice)
experience migrating off a legacy BI tool
Snowflake performance and cost tuning
treating BI platform configuration as code (e.g., Terraform)
identity resolution or master data management
experience with a second BI platform such as Power BI

Responsibilities

Own the Looker semantic layer: explores, views, model files, and the boundary between dbt and LookML, writing the LookML standards that enforce it and harvesting metric logic that currently lives in the wrong place.
Own metric definitions per business domain, with domain differences documented rather than smoothed over.
Own BI platform provisioning: Looker instance configuration, model and project structure, git workflow for LookML, user and group provisioning, and connection management against Snowflake, including the dated plan for Domo retirement.
Design and own external client-facing BI access: per-client data isolation enforced in the platform, row-level and column-level access aligned with dbt masking policies in Snowflake, and a provisioning path that Legal and Security will sign off on.
Govern what "trusted" content means: certified versus ad hoc content, naming, folder structure, deprecation, and change control on metric definitions so a silent definition change never lands in a client-facing deck.
Set technical direction for the BI domain: the patterns BI developers and analysts build on, delivered through code review, pairing, and written standards rather than direct reports.
Design how the semantic layer represents the identity-resolution layer's reporting surface, accounting for match confidence and records that merge after a report has already gone out.