facilita.etc
← Todas as vagas

Lead Analytics Engineer, Data Governance & Platform

Vagas Externas — Remotar · Remoto · CLT · senior
🌐 Entre para traduzir esta vaga

Descrição

What You'll Own - Quality and freshness machinery, building and scaling the automated monitoring (freshness checks, schema-change alerts, anomaly monitors) that catches upstream changes before they break anything downstream, and running incidents to resolution - Semantic-layer coverage, the long tail of metrics that still needs definition and mapping, done to the one-metric-one-definition standard, plus the hygiene that keeps the layer tidy as it grows - Event-catalog operations, reviewing new Segment events against our governed catalog's standards, keeping the catalog matched to what production actually sends, and investigating drift when detection flags it - Lineage tooling, extending our lineage map beyond dbt (Segment events and Lightdash need stitching in) so downstream impact of a production change can be assessed before it ships - Lightdash hygiene, the hands-on side of workspace health: certification, naming, permissions upkeep, and keeping self-serve content findable and trustworthy - The data roadmap, increasingly, working with the Data Director to turn what product, marketing, ops, and finance need from data into priorities for the platform, and owning more of that roadmap as the function grows Scope here widens with demand and with what your work proves. As the function takes on more, more of it becomes yours to run, including helping hire the people it adds. Problems to Solve Take detection from partial to comprehensive An AI-powered Analytics Engineer agent already runs freshness monitoring, dbt job monitoring, and dbt-based lineage checks, but not yet at the scale or coverage we need. You'll extend it until "a stakeholder found the problem first" stops happening. Map the long tail of the semantic layer Our most critical metrics have one governed definition each, in code. Well over a hundred more still need defining and mapping: unglamorous, high-judgment work where every shortcut becomes someone's wrong number later. Keep the event catalog honest Segment events are implemented by many engineers across many teams, and entropy is relentless: new events drift from standards, and existing ones silently degrade when features change. The guardrails exist. You're the person who runs them and catches what they miss. Turn business needs into a data roadmap Every area of the company wants something from data, and today those asks reach the Analytics team as a stream of interruptions. With the Data Director, you'll turn them into priorities that balance stakeholder needs against platform health. The hard part: saying "not yet" to important people, with a reason they respect. What Success Looks Like (Year 1) - The monitors you built catch problems before stakeholders do, pipeline and freshness incidents get found by automation, not by someone opening a stale dashboard - The semantic layer's long tail is mapped, every reported metric has exactly one governed definition, and arguments about whose number is right don't happen - Event reviews run on a steady cadence, new events ship compliant, drift gets investigated within days, and the catalog matches production - You're the acknowledged technical reference, when something data-related looks wrong anywhere in the company, people know who to bring it to, and you usually already know - Data-trust asks come to you, stakeholders bring their data-quality and governance requests to you directly, and you hold a slice of the roadmap with the Data Director

Requisitos

Who You Are - Governance is your craft, not your chore. You enjoy making data systems trustworthy and tidy. You're the person who can't leave a broken naming convention alone. This is unlikely to be a good fit if you see governance as a stepping stone to "real" analytics work - AI-native. You use AI tools (Claude Code, Copilot, ChatGPT) daily to build quality checks, write automation, triage anomalies, and document as you go. This is unlikely to be a good fit if you're skeptical of AI tools or prefer to do everything manually - A hands-on builder at a lead bar. You write the SQL, debug the Airflow DAG, and ship the monitor yourself, and the way you do it becomes the way the team does it. This is unlikely to be a good fit if your instinct is to spec work for someone else to execute - Automation-first. Your instinct for any recurring check is to build a monitor, not a checklist. This is unlikely to be a good fit if your quality practice depends on manual review and discipline - A technical reference people seek out. You explain clearly, answer patiently, and leave people smarter. Your influence comes from that, before any title does. This is unlikely to be a good fit if you need formal authority to get people to follow a standard - Open to growing with the function. If the area grows into a team and leading it suits you, you're open to developing the management side to get there. If it doesn't, staying the technical lead of this area is a full, senior role here, not a consolation prize. This is unlikely to be a good fit if you'd take the role mainly for the title it might lead to This Role Is NOT - A BI analyst role. You won't spend your days building dashboards for stakeholders. You build the machinery that keeps everyone else's dashboards trustworthy - A title with a timeline, or a guarantee. There's no promotion date. If the role grows into managing the function, the Manager title follows the work you're already doing. If the function needs a manager before that happens, or the fit isn't there, we'd hire one, and you'd remain the technical lead of the area - A hands-off role. The building is the job now, and it stays core as your scope grows. If you want to step away from the keyboard, this isn't it

Candidatar-se

Esta vaga é agregada de Vagas Externas — Remotar. A candidatura é feita no site da fonte.

Candidatar-se no site da fonte