> Markdown version of [/jobs/ext/4657215-data-operations-analyst](https://www.wearedevelopers.com/jobs/ext/4657215-data-operations-analyst). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Data Operations Analyst - **Company:** HOLLY'S INC - **Location:** New York, NY, United States - **Salary:** $80,000 - $110,000 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Data Analysis, Data Cleansing, Data Dictionary, DataOps, SQL Databases, Tableau (Software), Data Analytics, Looker Analytics - **Published:** November 10, 2026 - **Apply:** https://www.careerbuilder.com/job-details/data-operations-analyst-new-york-ny--0f8574cf-cf84-4a1f-8b46-a100c66efe74 ## About the Role Data Analysis, Operational Audit, Data Quality, Data Analysis, Operational Audit, Tissue Engineering, Machine Tool, Reporting Dashboards, SQL (Structured Query Language), Data Cleaning, * You're strong in SQL. Complex joins don't bother you, and when a query returns something surprising you find out why instead of moving on. You've administered a BI tool before, whether that's Metabase, Looker, or Tableau. * You're naturally process-driven. You catch the error in row 4,000 and have a track record of building documentation and standards. * You can manage projects and drive results. You're capable of getting stuff done with teammates and collaborators across time zones, while keeping stakeholders consistently and clearly informed. You write clearly, manage tightly, and communicate often. * You're AI-native. You use AI in real workflows, are constantly testing new tools, and are the one your friends go to for tips. * You've been a data wizard before. You have experience in a data operations, data analytics, tech consulting, or business intelligence role. Bonus points for startup / public sector experience. Experience handling sensitive or regulated data is a plus. ## Description Holly is looking for a Data Operations Analyst to own the day-to-day health and integrity of our data. * You'll sit in the Engineering org and be active as the connective tissue between engineering and the Deployments team, making sure the information flowing through our systems is accurate, available, and governed appropriately. * This is a hands-on, high-ownership role. You'll spend your time writing SQL queries to clean data, building dashboards in Metabase, and in the operational tooling that keeps our pipelines running. * This role is a strong fit for someone who is rigorous about data quality, comfortable owning process end to end, and interested in building a data function rather than inheriting one. What you'll do * Own how data gets in. Public records requests, agency outreach, general collection and extraction. You set the cadence, track what's outstanding, and collaborate with the deployment team to ensure client launches are set-up with the right data. This will include getting on the phone and talking to agencies as well when data is missing. * Run the pipeline day to day. Monitor runs, resolve failures and reruns, and configure schedules, connections, and settings as data sources change. * Own data quality end to end. Build the validation checks and monitoring that catch problems early, investigate the ones that get through to root cause, and drive fixes with engineering. When a client flags something that looks wrong, you diagnose it, fix it or route it, and tell them what happened. * Own Metabase and the analytics work that runs on it. Dashboards, saved questions, permissions, and shared metric definitions, so the teams asking the same question get the same number. Engineering, product, and Deployments come to you for an operational question answered, an output audited, or reporting that they can run on their own. * Do the work once, then turn repeating work into tooling. Find the repetitive work and remove it, whether that's an AI workflow you build yourself, a vendor, or a well-written ticket to engineering. Leave behind documentation, operational runbooks, and data dictionaries for the whole team + future of the data org.