Clean Inputs
Nothing downstream is trusted more than the record it came from. Ingestion, deduplication, validation and reconciliation against a source of truth, with every value traceable back to something that can be re-checked.
open to work · Fort Worth, Texas
Data Operations & Data Quality Analyst
scroll, it gets louder
01 — the short version
I clean, validate and reconcile records — then build the workflows that keep them clean. I design the system and hold the judgment; the machine does the volume.
Nothing downstream is trusted more than the record it came from. Ingestion, deduplication, validation and reconciliation against a source of truth, with every value traceable back to something that can be re-checked.
Work that runs the same way twice without supervision. Bounded scheduled loops, hard requirement gates, human-in-the-loop review on anything that writes, and documented best practices in an SOP written before the process is handed off.
A result nobody verified is not a result. Test suites, offline smoke runs, freshness gates, real-browser verification, and a validation report shipped beside the data as the evidence.
02 — what I actually use
Tools I reach for weekly, not a list of things I once opened.
03 — the road so far
Every stop was accuracy work before it was systems work. That order is the point.
YAHWAYLOVE LLC · Fort Worth, TX / Remote
414 Creative · Remote
Miracle Method / Tub Done Refinishing · Orange, TX & Boca Raton, FL
Lake Arenal Real Estate · Nuevo Arenal, Costa Rica
Corinthian · Marina Del Rey, CA
where I worked clients served: Northern California · Fort Worth, TX · Orange, TX · Indianapolis, IN · Stuart, FL
Point at or tap a pin to see the stop.
Based in Fort Worth, Texas — remote only, not relocating. 2 of 5 roles never sat anywhere on a map at all.
04 — things that run
Each one exists because a manual process was costing real hours.
A year of records that outlives the system holding them
A complete private archive of a year of coursework, built so the data survives losing access to the system it came from: every course, lesson, grade, file, video transcript and email pulled out of a hosted LMS, normalised, and stored somewhere retrievable. 127 commits, 648 tracked files. This is records management as a migration problem — get it all, keep it faithful to the source, and make it findable afterwards.
Their files stay in sync without anyone remembering to sync them
Ongoing client work across five deliverables: an AI proxy holding every API key server-side, a Dropbox-to-library autosync watcher running on a scheduled task, research and hub packs, and a site remodel. Ships behind a definition-of-done gate that has to pass before anything is called finished. 141 commits, 439 tracked files.
Structured inputs in, a finished 14-page document out
A document pipeline that takes structured inputs — a person's details, written testimony, source references and authorised context from an existing database and document corpus — and assembles a 14-page output from them. 57 commits and 47 tests, because a generator that silently drops an input is worse than no generator.
A bad run refuses to publish itself
A daily job pipeline: 16 source families scanned into SQLite, run through a hard requirements gate, scored, and rendered into a self-contained dashboard. 153 commits behind three gates — a 29-test pytest suite, an offline pipeline smoke run, and a real-browser harness across three viewports that exits non-zero on accessibility violations, console errors, layout overflow, or a dead interaction.
The proof ships with the data
A productized spreadsheet-rescue service: messy client data in, cleaned and deduplicated data out, plus a validation report showing exactly what changed and why. The report is the deliverable - the guarantee is proof, not a promise.
A green suite stopped being enough
A verification gate that made a green test suite mean something. Drives a real browser at three viewports and fails the build on accessibility violations, console errors, sideways scroll, undersized tap targets, or a page that rendered nothing - the last one because an empty page used to score perfectly.
05 — questions people actually ask
Data operations, records and QA, and data-validation roles — data entry, compliance and records processing, and AI output QA. He targets high-accuracy, low-meeting work he can run asynchronously and increasingly automate.
Yes — remote is the arrangement, not a preference. He is based in Fort Worth, TX (US Central) and is not relocating, so he works fully remote in an async, low-meeting style, comfortable with distributed teams and written-first communication.
Excel and Google Sheets for records and reporting, Python for cleaning, deduplication and validation, and AI-assisted workflows with human QA kept intact. He also builds small automation pipelines and documents the SOP so they run without him.
Every value carries its provenance, anything that writes stays human-in-the-loop, and cleaned data ships with a validation report showing exactly what changed and why. A result nobody verified is not treated as a result.
Yes — fluent English and Spanish, including bilingual documentation and translating between clients and internal teams.
06 — say hello
Fort Worth, Texas · remote · async and written-first.