Data Operations Director

2 days ago

Maryland, MD, United States Foureyes Full-time

Who We Are

Headquartered in Oregon, Foureyes® is a remote-first company with employees in two dozen states. We are privately owned and focused on the automotive vertical.

We believe human intellect paired with data-driven AI is the winning combination. It always has been. And we're on a mission to bring that winning combination to automotive dealerships with easy-to-love software. We're a software company that thinks about people first. With every innovation, we seek to put humans back in the starring role.

If this sounds like the kind of company you want to be a part of, there’s good news. We’re hiring for a Data Operations Director

About the role

Your mission: dealers never find a data problem before we do.

Foureyes is a data and analytics platform for automotive dealerships. We pull CRM, DMS, website and inventory data into one place so dealers can see what's working and act on it. Good data is our core promise, and dealers can't use Foureyes if their data is wrong, stale, or stopped flowing three days ago.

As our first Data Operations Director, you'll own data health. You'll know at any moment whether there are data issues, where they are, and where we are on fixing them. You won't fix everything yourself, but you'll own getting it fixed. Think of this role as a hybrid of part data analyst, part integrations engineer, part product manager, and fully accountable for the outcome. If there is a data issue, you will be the first call.

What you'll own

  • Define healthy data from the dealer's point of view. Set clear standards for freshness (is data arriving on schedule), completeness (is the volume what we expect) and accuracy (do the numbers match the source) for each data source. This role will also include customer facing views of data health

  • Monitoring and anomaly detection. Set baselines by source and rooftop, find the gaps in what we can see today, and build what's needed to close them. You will start from existing anomaly dashboards and data observability work, but you own creating the monitoring and detection you need to be successful.

  • Daily health review. Every day, answer: is the data we expect showing up where we expect it?

  • Triage and resolution. Find where a failure is happening, pull in the right team (engineering, onboarding, the account team, data science or a vendor) and drive it to resolution. You won't fix everything yourself, but you own getting it fixed. Some problems will call for you to work directly with dealers and their CRM, DMS and website vendors to troubleshoot and get them solved.

  • Engineering prioritization for data issues. Set the priority of data issues in the engineering support queue and work directly with the on-support engineer. When you can't diagnose something without engineering's help, define the tooling or visibility you need and make the case for it.

  • One view of all data issues. Keep a single, current picture of every open data issue, its owner, priority and expected fix date. Keep internal stakeholders (support, sales engineers, customer success) informed so they can update dealers with confidence.

  • Playbooks and handoffs. Turn one-off fixes into repeatable systems: severity levels, runbooks, and agreed handoffs with onboarding, support and engineering on what each team takes, in what format, and how fast.

  • Push for change. If we can't resolve issues fast or consistently enough, you're the one who proposes a different approach, a new build, or more resources.

Data in scope: customer data from CRM, DMS and website tracking, and inventory data from our proprietary engine and DMS inventory data.

Not in scope: building net new integrations (CRM, DMS, inventory tracking templates, website frameworks) and owning the systems behind them. Those stay with product and engineering; you're their partner on keeping existing integrations healthy.

What success looks like

In your first 90 days you will:

  1. Audit what we can see today, find the gaps, and put a plan in place to close them.

  2. Define data health for each major source, with baselines and the signals that flag a problem.

  3. Run it: daily review, triage, driving resolution, and reporting out on the measures below.

In your first year: data issues are caught by us first, every open issue has a