Senior Analytics Engineer

Own PayJoy's Unity Catalog governance model e.g. catalog and schema architecture, tagging and metadata standards, lineage, grants, and PII controls, so that data access is provable to an auditor and self-evident to an analyst rather than tribal knowledge held by a few people

Define and operate the standards that make data trustworthy by default: a tiered certification standard strong enough to carry regulated reporting, service-level objectives on the highest-traffic data products, and strong detection quality on alerts, while retiring the duplicate and abandoned models that dilute trust

Own the governed semantic layer and the transformation development loop (conformed dimensions, canonical entity keys, and single definitions for every cross-functionally consumed measure) so that two teams asking the same question get the same answer, AI-assisted analysis inherits sound semantics, and a new contributor ships a correct model in their first week

Establish how experimentation works at PayJoy, owning the measurement substrate (e.g. experiment metric definitions, exposure tables, guardrail metrics, readout correctness) while advising on tooling selection, statistical approach, and instrumentation architecture with Product Engineering.

Deliver scoped enablement projects whose primary output is a reusable pattern, which can be used as a standard others build against.

Bachelor’s in a related field or equivalent; Master’s a plus

10+ years of experience

Deep data governance expertise on a modern lakehouse e.g. Unity Catalog or equivalent at multi-catalog scale: schema architecture, metadata and tagging strategy, lineage, grants, row- and column-level security — You have designed a governance model, not only worked inside one someone else designed

Expert-level data modeling expertise, with defensible positions on test strategy, incremental model semantics, and when a model should not exist

Track record of driving adoption — a standard, tool, or platform that teams outside your reporting line changed their behaviour to use

Strong communicator — able to explain complex analytical concepts to technical and non-technical audiences.

Comfortable working in ambiguous, high-impact environments with broad scope and autonomy.