Data Operations & Data Quality Analyst
Inspect work Four systems that run daily — what each does, and what proves it.
Detail-oriented data operations specialist with hands-on experience cleaning, validating, analyzing, organizing, and reconciling records across campaign, client, property, and internal business workflows. Owner-operator of YAHWAYLOVE LLC with practical experience building Python and AI-assisted processes, documenting repeatable SOPs, and validating outputs against source-of-truth data. Strong fit for low-meeting, accuracy-heavy roles in data operations, records management, compliance support, claims and admissions processing, and marketing operations reporting. Works independently and async. Fluent in Spanish.
Low-meeting, async-ready work style · Accuracy with repetitive records · Automation-minded, human QA intact · Spanish fluency useful to the team · Written-first, distributed teams
Plain job titles, what I would own in each, and the work that proves it.
Owns the path a record takes from export to report: ingest, deduplicate, validate against source of truth, then publish something a decision can safely rest on.
Proof — The job-search data pipeline and the YAHWAYLOVE automation lane are this job, run on my own data.
High-volume entry where the accuracy bar is the whole job. I keep a review step on anything that writes and document the process so a second person gets the same result.
Proof — Human-in-the-loop form fill; five years of detail-heavy, low-supervision work.
Checks outputs against the source they came from, separates what was measured from what was assumed, and ships a report showing exactly what changed and why.
Proof — The cleanup service's validation report, and a browser QA gate that fails a build rather than let a green metric hide a real defect.
Keeps records complete, current and retrievable, reconciles them against the system of record, and writes the SOP so the next run needs no supervision.
Proof — SOP documentation and records across current client work, plus property records and bilingual documentation at Lake Arenal Real Estate.
Structured intake at volume: apply the same criteria the same way every time, flag the edge cases instead of guessing, and leave a clean audit trail.
Proof — Built a hard requirements gate that screens hundreds of records a day against fixed criteria and refuses to publish a run it cannot trust.
Campaign and platform exports cleaned and reconciled, inconsistencies caught before they reach a decision, and reporting whose numbers survive being questioned.
Proof — Meta Ads data operations for multiple client accounts at 414 Creative.
Runs the campaign as a system: AI-assisted creative and copy variants produced in volume, structure and angle decided by me, and reported figures reconciled against platform data before anyone optimises on them.
Proof — Meta Ads operations across multiple client accounts at 414 Creative, where targeting precision and cost-per-lead improved within 2–3 months.
The cutting, transcription, captioning and scheduling are machine-run; I own the selection, the standards and the approval gate. Output scales with compute rather than with my hours.
Proof — Kingdom Clipping Expanse: a tuned OpenShorts pipeline (GPU Whisper transcription, karaoke captions) wired to Postiz scheduling with Python glue.
AI-assisted build with the checking automated: layout and copy produced fast, then held to accessibility, contrast and performance gates that fail the build rather than trusting a look-over.
Proof — This site — self-hosted fonts, light and dark themes, and a browser harness that fails the build on WCAG violations at three viewports — plus client brand sites and cinematic web builds through YAHWAYLOVE.
Builds browser-playable interactive pieces and automates the boring half — export, build and deploy run headless, so shipping a change is a command rather than an afternoon.
Proof — the-way: a 3D scroll-driven telling of the life of Jesus, built in Godot 4.3, exported and deployed headless, live and playable, with a Three.js fallback build.
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.
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.
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. 87 commits and 56 test files, because a generator that silently drops an input is worse than no generator.
A daily job pipeline: 16 source families scanned into SQLite, run through a hard requirements gate, scored, and rendered into a self-contained dashboard. 250 commits behind three gates — a 410-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.
A private, single-user widget platform: a password-gated builder plus a public embed runtime, so a marketing site can add a form, gallery or counter without an Elfsight subscription or a third-party CDN in the finished product. 35 commits and 45 test files; the embed ships as self-contained output because an embed that phones home is a dependency nobody audited.
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 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.