Job Opportunities API

ABOUT THE ROLE We're standing up a unified data and analytics platform that consolidates artist performance, revenue, royalties, audience, and operational data into a single queryable layer in BigQuery. This role owns the architecture: warehouse design, source-system integration strategy, entity resolution across platforms, and the transformation layer that turns fragmented exports into a coherent picture of an artist, a release, and a project. PLEASE NOTE THIS IS A SHORT TERM (6 MONTH) CONTRACTED POSITION You'll lead a small team (2 fractional engineers + a front-end contractor) doing genuinely hard integration work — aggregation across sources, entity matching, and reconciling numbers that don't agree out of the box. You'll partner closely with our internal data team, business owners across the platforms we ingest, and an executive sponsor. The near-term deliverable is a working analytics layer by end of year; the medium-term deliverable is the foundation under our next-generation Label Analytics Dashboard and AI-augmented reporting products. KEY RESPONSIBILITIES - Act as the bridge between technical implementation and business reality. You’ll work directly with stakeholders across Finance, Label Services, Marketing, Operations, and Executive Leadership to determine how the business should be represented in data. This includes driving decisions around metric definitions, source-of-truth ownership, reconciliation rules, and exception handling when systems disagree. - Design the data warehouse: schemas, transformation layer, semantic conventions, access patterns. You'll make the structural decisions that shape how every downstream team queries the business. - Lead the integration work across systems: entity resolution, aggregation, and reconciliation. Artists, songs, venues, and partners don't share canonical IDs between FUGA, Luminate, Chartmetric, Salesforce, and Airtable; you'll design how they will. Streams, royalties, and revenue numbers reported by different systems don't always agree; you'll set the rules for what's authoritative and how discrepancies get surfaced. We also need to integrate Salesforce and RAMP (cost data). - Lead a small delivery team (data engineers and application contractors) responsible for building the warehouse, transformation layer, reconciliation pipelines, and analytics experiences. You are not expected to be the primary front-end developer, but you should be comfortable defining the data contracts and architectural patterns those applications rely on. - Choose and stand up the transformation tooling (dbt, SQLMesh, Dataform, or other). Argue the trade-offs honestly; we don't have a religious preference yet. - Set the standards for testability, observability, and data quality monitoring across the warehouse. QUALIFICATIONS - 3 to 8+ years of data engineering, analytics engineering, or data architecture experience. We care more about evidence of production ownership than tenure. Candidates should be able to demonstrate hands-on experience designing data models, integrating multiple systems, and making architectural decisions in real-world environments. - Strong engineering fundamentals are required. We expect candidates to be capable of independently designing systems, writing code, debugging integrations, and reasoning about data architecture without relying on AI tools. Familiarity with modern AI-assisted development workflows is welcome, but not a substitute for core technical competence. - Deep experience integrating complex data across heterogeneous sources — aggregation, entity matching, and reconciliation. You've built or led systems that stitched identities and reconciled numbers across disparate feeds, and can speak to the trade-offs (deterministic vs. probabilistic matching, human-in-the-loop review, source-side keying vs. downstream resolution, how to handle disagreeing sources of truth). - Experience managing teams doing this kind of work. Not