> Markdown version of [/jobs/ext/3015902-data-steward-part-time](https://www.wearedevelopers.com/jobs/ext/3015902-data-steward-part-time). 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 Steward (Part-Time) - **Company:** Cleveland Cavaliers - **Location:** Cleveland, OH, United States - **Salary:** $62,400.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Customer Data Management, Data Dictionary, Relational Databases, PostgreSQL, Metadata Repositories, Markdown, SQL Databases, YAML, Git, Information Technology - **Published:** September 20, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=88b3d3bdc73758ba ## About the Role * Willing to learn SQL. You'll use it constantly and we'll teach you. * Genuinely detail-oriented. This role catches the things other people skim past * Reliable and self-directed. You'll work a queue with light supervision and we need to trust that finished means finished * Comfortable writing clearly for other people to read. Plain, specific, no fluff * Willing to ask the same clarifying question three times to three different people to get an answer right * Able to work a consistent weekly schedule, with some overlap with our core hours for questions and handoffs * Exposure to Git, pull requests, or Markdown. We'll teach it, but a head start helps * Familiarity with relational databases (PostgreSQL preferred) * Any experience with data documentation, data catalogs, or dbt YAML files is preferred * Comfort with AI assistants as a working tool. Our team uses them daily and you're encouraged to * Background in sports, entertainment, ticketing, or CRM data is a plus ## Description The Cleveland Cavaliers run on data. Every ticket sold, every campaign sent, every sponsorship report, every decision a leader makes traces back to information that someone has to keep accurate, documented, and worth trusting. Keeping it that way is how a lot of people get their start in data. We're looking for a Part-Time Data Steward to help maintain and improve the data foundation that runs our business. 20 hours a week, flexible schedule, real work on real systems from your first week. You don't need a sports background or a computer science degree. You need to be sharp, organized, and reliable. What you'll leave with is a working understanding of how a professional sports organization actually runs on data, hands-on exposure to the tools our engineers and analysts use every day, and people in this industry who know your name and your work. You'll report directly to the Director of IT Products, who grooms your queue and clears your blockers. Day to day you'll work closely with our data team, your counterparts on the technical side and the people you'll go to first with a SQL or data question., * Work a stewardship Kanban queue with a strict work-in-progress cap: pick up an item, finish it, move to the next * Document datasets, tables, and columns: what they mean, who owns them, whether they're still in use. Definitions go in the repo next to the code, submitted as pull requests * Track down the person who actually knows what a field means, ask the question, and turn the answer into a written definition. Every subject-matter-expert conversation produces a documented change, not just notes * Spot-check and validate data: null checks, duplicate checks, row counts against expectations, does this month look like last month * Verify recurring vendor file exchanges landed correctly and completely, and escalate when they didn't * Maintain the data dictionary and domain documentation on our internal portal so it stays current instead of going stale * Flag data quality issues with enough context that an engineer can act on them without re-investigating from scratch * Help identify unused and stale datasets as deprecation candidates * Assist with access reviews: confirm who has access to what and whether they still need it * Post a short weekly written update on what moved, what's blocked, and what's next ## Related Videos - [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94) - [CI/CD with Github Actions](https://www.wearedevelopers.com/videos/856-ci-cd-with-github-actions) - [Why Is Software Documentation Still Static – And Why Modern Browsers Deserve Better](https://www.wearedevelopers.com/videos/2054-why-is-software-documentation-still-static-and-why-modern-browsers-deserve-better) - [From Messy Queries to Scalable Systems - How Data Engineering actually works](https://www.wearedevelopers.com/videos/100203-from-messy-queries-to-scalable-systems-how-data-engineering-actually-works) - [Beyond SQL Generation: How to Teach Agents What Your Database Actually Means](https://www.wearedevelopers.com/videos/100127-beyond-sql-generation-how-to-teach-agents-what-your-database-actually-means) - [Git for Code Reviews](https://www.wearedevelopers.com/videos/429-git-for-code-reviews) ## Related Articles - [Making Data Warehouses Fast: A Developer’s Story](https://www.wearedevelopers.com/magazine/107-making-data-warehouses-fast-a-developer-s-story) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 139 - Soft and hard queries](https://www.wearedevelopers.com/magazine/487-dev-digest-139-soft-and-hard-queries) - [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix) - [WeAreDevelopers Dev Digest Issue 116 - The new search wars…](https://www.wearedevelopers.com/magazine/445-wearedevelopers-dev-digest-issue-116-the-new-search-wars)