Time since we first saw it
Day 4
Early. Similar jobs usually come down between day 6 and day 52.
From 2,085 similar postings that came down. Coming down is not always a hire.
Reads like a Data Governance role: data quality and governance.
Bogotá, Bogota, Colombia
Actively hiring, first seen by us 4 days agoBenefits Base salary: $75k–$100k/year (contractor arrangement, standard for our Latin America-based team; no equity) Fully remote: This work needs deep focus, building monitors, untangling pipelines, and we trust you to manage your environment. Async collaboration is the norm.Read the full posting
Work setup in the employer’s posting: RemoteFrom the employer’s posting
Employment type in the employer’s posting: Full-timeFrom the employer’s posting
Build and scale automated freshness, schema-change and anomaly monitors, and run incidents to resolution
Define and map the long tail of semantic-layer metrics to the one-metric-one-definition standard
Review new Segment events against the governed catalog and investigate drift
Extend the lineage map beyond dbt to cover Segment events and Lightdash
Keep Lightdash workspace healthy: certification, naming, permissions and findable content
building and scaling the automated monitoring (freshness checks, schema-change alerts, anomaly monitors)
the long tail of metrics that still needs definition and mapping, done to the one-metric-one-definition standard
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
extending our lineage map beyond dbt (Segment events and Lightdash need stitching in)
certification, naming, permissions upkeep, and keeping self-serve content findable and trustworthy
From the employer’s posting.
We're a small, senior analytics team supporting the entire company: product, marketing, operations, and finance all run on the data we serve.
In the employer’s words · Read in context
Actively hiringFirst seen by us 4 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 4
Early. Similar jobs usually come down between day 6 and day 52.
From 2,085 similar postings that came down. Coming down is not always a hire.
8 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- 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.
About Analytics at LawnStarter We're a small, senior analytics team supporting the entire company: product, marketing, operations, and finance all run on the data we serve. The foundation is solid. A centralized Redshift data warehouse holds all source data, modeled in dbt and orchestrated by Airflow, with Segment feeding event data in. You won't be stitching scattered sources together. The platform exists, and your job is to make it trustworthy and keep it that way. We're mid-migration to Lightdash as our single BI platform, replacing Tableau and Metabase. Data governance is becoming a dedicated function here. You'll be its first dedicated owner, building it alongside the Data Director.
- 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.
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.
Tech You'll Touch - Warehouse & pipelines - Redshift, dbt, Airflow - Ingestion - Fivetran, plus custom Airflow pipelines
- AI tooling - Claude Code, Codex, Brain (our internal AI toolkit), and any tool that makes you more effective or efficient - Observability - an AI-powered Analytics Engineer agent (freshness monitoring, dbt job monitoring, dbt lineage) you'll extend, plus the quality and impact tooling you'll build around it You don't need every box checked. You need hands-on depth in the warehouse/pipeline layer and the instinct to automate what others check manually.
- Warehouse & pipelines - Redshift, dbt, Airflow - Ingestion - Fivetran, plus custom Airflow pipelines - Event tracking - Segment
- Event tracking - Segment - BI - Lightdash (primary), Tableau and Metabase (sunsetting) - AI tooling - Claude Code, Codex, Brain (our internal AI toolkit), and any tool that makes you more effective or efficient
Complete your application on apply.workable.com. The employer’s form will show what is required.
Already applied? Track this application
Yes. We’ve followed one other Lead Analytics Engineer, Data Governance & Platform job there since November 2026. It is still up.
LawnStarter is the nation's leading on-demand marketplace for lawn care and outdoor services, with over $150M in annual bookings. We're expanding beyond lawn care to become the one-stop shop for all home services, operating across three brands (LawnStarter, Lawn Love, Home Gnome) on a single shared platform.
We're a small, senior analytics team supporting the entire company: product, marketing, operations, and finance all run on the data we serve. The foundation is solid. A centralized Redshift data warehouse holds all source data, modeled in dbt and orchestrated by Airflow, with Segment feeding event data in. You won't be stitching scattered sources together. The platform exists, and your job is to make it trustworthy and keep it that way. We're mid-migration to Lightdash as our single BI platform, replacing Tableau and Metabase.
Data governance is becoming a dedicated function here. You'll be its first dedicated owner, building it alongside the Data Director.
You'll own LawnStarter's data governance area and build it: the person who turns the governance agenda into working systems (monitors, checks, lineage, metric definitions, tracking standards) with your own hands. You'll grow the function together with the Data Director, at the pace demand and impact call for. If you want it and the skills are there, you could become its manager one day.
"Lead" here means technical weight first. You're the reference the analysts turn to when a pipeline misbehaves, a metric definition gets contentious, or an event's data looks wrong, and the example that raises the bar for how governance work gets done. As the function grows, your leadership can widen with it.
What makes this role different:
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.
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.
Requirements
You don't need every box checked. You need hands-on depth in the warehouse/pipeline layer and the instinct to automate what others check manually.
Benefits
LawnStarter provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, or genetics. We comply with applicable state and local laws governing nondiscrimination in employment.
New Data Governance postings at the employers we follow are up 164% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under Data Governance, by the work the posting describes.
Data governance staff keep a company's data accurate, documented and used within the rules. They agree what key fields mean, set up quality checks, track who owns each dataset and look after master data.
Postings ask for SQL, a governance tool such as Collibra or Informatica, knowledge of privacy and data rules, and a lot of work with other teams.
A data engineer builds the systems that move data; governance staff set and check the standards that data has to meet.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
Benefits Base salary: $75k–$100k/year (contractor arrangement, standard for our Latin America-based team; no equity) Fully remote: This work needs deep focus, building monitors, untangling pipelines, and we trust you to manage your environment. Async collaboration is the norm.
Bogotá, Bogota, Colombia
- Base salary: $75k–$100k/year (contractor arrangement, standard for our Latin America-based team; no equity) - Fully remote: This work needs deep focus, building monitors, untangling pipelines, and we trust you to manage your environment. Async collaboration is the norm. - Flexible PTO: We focus on results. Take what you need.
No clear work-authorization passage found. Eligibility is unconfirmed.