Time since we first saw it
Day 4
Early. Similar jobs usually come down between day 8 and day 57.
From 9,995 similar postings that came down. Coming down is not always a hire.
Reads like a Data Leadership role: running a data team.
Bogotá, Bogota, Colombia
Likely evergreen, first seen by us 4 days agoBenefits Base salary: $75k–$120k/year 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 the data roadmap by turning product, marketing, ops, and finance needs into prioritized platform work
Run automated monitoring on source data, pipelines, and reports, and resolve incidents
Maintain data lineage and assess downstream impact before production changes ship
Administer Lightdash permissions, workspace structure, and the migration from Tableau and Metabase
Govern Segment event tracking against the event catalog and naming standards
The data roadmap - discovering what product, marketing, ops, and finance need from data, prioritizing it against platform health, and sequencing the investment.
automated monitoring across source data, pipelines, and reports; catching upstream schema and source changes before they break anything downstream; running incidents to resolution when they happen
when a production change is proposed, its downstream impact on pipelines, metrics, and reports gets assessed before it ships, not discovered after
Lightdash - administration, workspace structure, permissions, and the rollout itself.
reviewing new events against its standards, keeping it matched to what production actually sends
This is a hands-on role, every manager at LawnStarter builds, and this one is no exception.
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
Likely evergreenReposted 2 times since Sep 29, 2026. A role that keeps coming back is often kept open to collect applications rather than to fill one seat.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications. We count a repost when the same title and location comes back as a new listing within 60 days of the last one coming down. Some hiring systems expire listings on a schedule, so repost rates vary by system.
Day 4
Early. Similar jobs usually come down between day 8 and day 57.
From 9,995 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, one person covering ground that used to take a team. You also see the reverse direction: AI agents consume our data daily, and making the warehouse safe and legible for them is part of governance now. This is unlikely to be a good fit if you're skeptical of AI tools or prefer to do everything manually. - A hands-on manager. You've been accountable for other people's output, allocating their time, owning their priorities, and you never stopped building yourself. You write the SQL, debug the Airflow DAG, and configure the permissions personally. This is unlikely to be a good fit if seniority took you away from the keyboard, or if you've never been responsible for anyone's work but your own. - Product-minded. You start from what the business is trying to decide, not from what the pipeline does, and you can turn a vague stakeholder ask into a prioritized plan. This is unlikely to be a good fit if you need requirements handed to you, or if roadmap conversations feel like a distraction from the real work.
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 where all source data lands, modeled in dbt and orchestrated by Airflow, with Segment feeding event data in. You won't be stitching scattered sources together, the platform exists; 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. Here's the honest gap: everyone on the team today is an analyst. Data quality, tracking standards, and platform hygiene get done as side work, squeezed between analyses. Nobody wakes up thinking about them, which is exactly the job we're hiring for.
Tame event-tracking entropy Segment events power our funnels and product analytics, and they're implemented by many engineers across many teams. The guardrails exist, a governed event catalog with naming standards, a property dictionary, a review lifecycle, and automated drift detection against production. What's missing is a dedicated owner: someone who holds every new event to the standard, keeps the catalog matched to what production actually sends, and evolves the guardrails as tracking grows. Without that, entropy wins, events drift and silently degrade when features change. Get ahead of breakage instead of chasing it Today, when production data changes upstream, we too often find out when a pipeline breaks or a stakeholder flags a wrong number. You won't start from zero, an AI-powered Analytics Engineer agent already runs freshness monitoring, metric anomaly detection, and dbt-based lineage checks, but it doesn't yet run at the scale or coverage we need. You'll take detection from partial to comprehensive, extend lineage beyond dbt (Segment events and Lightdash need stitching in), and wire it into engineering's change review, so a proposed production change comes with a downstream impact assessment instead of a postmortem. The end-state is data contracts: breaking changes caught in engineering's workflow, not ours. What Success Looks Like (Year 1)
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, anomaly detection, dbt lineage) you'll scale up, plus the quality and impact tooling you'll add around it You don't need every box checked. You need hands-on depth in the warehouse/pipeline layer and credible experience keeping a BI tool and tracking plan healthy at company scale.
- Warehouse & pipelines - Redshift, dbt, Airflow - Ingestion - Fivetran, plus custom Airflow pipelines - Event tracking - Segment
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. You'll build the intake and prioritization that turns them into a roadmap , one that balances stakeholder needs against platform health, survives contact with a changing business, and that your stakeholders can see themselves in. The hard part: saying "not yet" to important people, with a reason they respect. Make the Lightdash migration a step-change, not a re-platforming We're replacing Tableau and Metabase with Lightdash. Done poorly, we trade two messy tools for one messy tool. You'll design the structure, spaces, permissions, certification, naming, that lets stakeholders self-serve at the speed the company needs without creating an uncontrolled dashboard-growth nightmare. The hard part: autonomy and tidiness pull in opposite directions, and you have to deliver both. Finish and defend the semantic layer We just shipped our semantic layer for our most critical metrics, one governed definition per metric, so "two dashboards, two numbers" can't happen. The unglamorous truth: a long tail of metrics still needs definition and mapping, and a semantic layer only stays trustworthy if someone curbs its growth. You'll own both, extending coverage and keeping one-metric-one-definition true as the layer scales.
- Zero freshness incidents - stakeholders never open a stale dashboard. - Every area of the business manages on official, well-maintained metrics and dashboards - product, marketing, ops, and finance self-serve in Lightdash against a fully mapped semantic layer; Tableau and Metabase are retired; arguments about whose number is right don't happen. Not because you built the dashboards - because you built the system that keeps them trustworthy. - Every Segment event has an owner and a standard - new events ship compliant, and degradation gets caught automatically, not by accident.
- 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 Analytics Engineering Manager, Data Platform & Governance job there since November 2026. It is still up.
About LawnStarter
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.
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 where all source data lands, modeled in dbt and orchestrated by Airflow, with Segment feeding event data in. You won't be stitching scattered sources together, the platform exists; 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.
Here's the honest gap: everyone on the team today is an analyst. Data quality, tracking standards, and platform hygiene get done as side work, squeezed between analyses. Nobody wakes up thinking about them, which is exactly the job we're hiring for.
The Role
You'll be the first person at LawnStarter dedicated to data governance, the owner of whether our data can be trusted, and of the roadmap that makes it more trustworthy every quarter. Trust means the quality and freshness of our source data, pipelines, and reports; the definitions behind our metrics; the standards behind our Segment event tracking; the health of our Lightdash workspace; the data feeding our machine learning models; and the security of the data itself. The roadmap means sitting with product, marketing, ops, and finance to understand what the business needs from data, turning that into priorities for the platform, and sequencing the work, yours and, soon, your team's.
This is a hands-on role, every manager at LawnStarter builds, and this one is no exception. You'll start solo, with the Analytics team around you: building automation, writing checks, fixing what's broken, and putting processes in place that scale past you. Once you've landed, we open a Lead Analytics Engineer role reporting to you, you'll help choose them, and the function grows from there as scope demands.
What makes this role different:
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. You'll build the intake and prioritization that turns them into a roadmap , one that balances stakeholder needs against platform health, survives contact with a changing business, and that your stakeholders can see themselves in. The hard part: saying "not yet" to important people, with a reason they respect.
Make the Lightdash migration a step-change, not a re-platforming We're replacing Tableau and Metabase with Lightdash. Done poorly, we trade two messy tools for one messy tool. You'll design the structure, spaces, permissions, certification, naming, that lets stakeholders self-serve at the speed the company needs without creating an uncontrolled dashboard-growth nightmare. The hard part: autonomy and tidiness pull in opposite directions, and you have to deliver both.
Finish and defend the semantic layer We just shipped our semantic layer for our most critical metrics, one governed definition per metric, so "two dashboards, two numbers" can't happen. The unglamorous truth: a long tail of metrics still needs definition and mapping, and a semantic layer only stays trustworthy if someone curbs its growth. You'll own both, extending coverage and keeping one-metric-one-definition true as the layer scales.
Tame event-tracking entropy Segment events power our funnels and product analytics, and they're implemented by many engineers across many teams. The guardrails exist, a governed event catalog with naming standards, a property dictionary, a review lifecycle, and automated drift detection against production. What's missing is a dedicated owner: someone who holds every new event to the standard, keeps the catalog matched to what production actually sends, and evolves the guardrails as tracking grows. Without that, entropy wins, events drift and silently degrade when features change.
Get ahead of breakage instead of chasing it Today, when production data changes upstream, we too often find out when a pipeline breaks or a stakeholder flags a wrong number. You won't start from zero, an AI-powered Analytics Engineer agent already runs freshness monitoring, metric anomaly detection, and dbt-based lineage checks, but it doesn't yet run at the scale or coverage we need. You'll take detection from partial to comprehensive, extend lineage beyond dbt (Segment events and Lightdash need stitching in), and wire it into engineering's change review, so a proposed production change comes with a downstream impact assessment instead of a postmortem. The end-state is data contracts: breaking changes caught in engineering's workflow, not ours.
What Success Looks Like (Year 1)
Requirements
You don't need every box checked. You need hands-on depth in the warehouse/pipeline layer and credible experience keeping a BI tool and tracking plan healthy at company scale.
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 Leadership postings at the employers we follow are up 8% 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 Leadership, by the work the posting describes.
Data leaders run data teams or design how a company's data fits together. Managers hire, set priorities and answer for whether the data work pays off; architects choose the systems and the shape of the data.
Expect years of hands-on data work, experience leading people or projects, and the ability to explain tradeoffs to executives.
Unlike a senior engineer or analyst, most of a data leader's week goes to people, planning and decisions rather than building.
The government has no code for data leaders, so these figures are for the closest group, computer and information systems managers, which includes data processing and data operations managers.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 11-3021.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
Benefits Base salary: $75k–$120k/year 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–$120k/year - 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.