Marketing Operations & AI Automation Specialist
Inspect work Every project: what it does, and what proves it.
Marketing operations and AI automation specialist. Builds the systems behind lead generation and client websites — Meta Ads campaign structure and reporting, attribution and link tracking, landing pages and brand sites — and automates the repetitive half with Python, Claude Code and AI-assisted workflows, keeping a human approval gate on anything that publishes. Meta Ads work includes a two-campaign system that produced 856 leads at $4.22 each for a college client in 90 days. Data operations is the foundation: every number is cleaned, reconciled against its source and verified before anyone acts on it. Owner-operator of YAHWAYLOVE LLC, taking contract work and open to remote W-2 roles in marketing operations, automation and data operations, including records, compliance, and claims and admissions processing. Works independently and async. Professional working proficiency in Spanish, including bilingual documentation.
Marketing numbers that reconcile to the platform · Automation-minded, human approval intact · Low-meeting, async-ready work style · Accuracy with repetitive records · Working Spanish for bilingual documentation and client translation
Plain job titles, what I would own in each, and the work that proves it.
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 — A two-campaign Meta Ads system for a college client: 856 leads at $4.22 each and 127 applications at $28.43 each over 90 days, from an account with no pixel. Plus Meta Ads data operations across multiple client accounts at 414 Creative.
Gets traffic to a product and proves where it came from: tagged links, a weekly metrics loop, and results read back from the platform rather than assumed.
Proof — External traffic partner for an AI SaaS product, with attribution built in-house because there was no access to the client's analytics.
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.
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.
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, live and playable in the browser (PlayCanvas, React and Vite), with a Godot 4.3 build alongside.
Turns a manual process into one that runs on a schedule and checks itself: Python and Claude Code do the work, a gate refuses a bad run, and a person approves anything that publishes.
Proof — A daily job-data pipeline behind 451 tests that refuses to publish a run it cannot trust, and a status board over 56 projects rebuilt every morning from its sources.
Builds the tool a team keeps doing by hand: a gated builder, a public output, and tests on the parts that can fail silently.
Proof — An offline-first journal app I own and ship (460 commits), a widget builder with a public embed runtime, and a 16-page document generator behind 949 tests.
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.
External traffic partner for an AI SaaS product with no access to the client’s analytics, ad accounts or billing, so attribution was built in-house. The rig: tagged outbound links, a weekly sweep, QA and metrics loop that ranks what worked, a frame check that rejects dead footage before it reaches a posting slate, and an approval gate that creates every post as a draft and reads it back from the server before anything is scheduled. 285 commits.
A two-campaign Meta Ads system: Campaign 1 buys cold attention cheaply with video-first creative, Campaign 2 converts only the people Campaign 1 already warmed up. Over 90 days for a college client: 487,000 impressions at $0.47 CPC, 856 leads at $4.22 each, and 127 applications at $28.43 each, from an account with no prior advertising and no pixel installed. Full case study at ads.andrew-rocha.here.now.
Ongoing client work for a ministry: an AI proxy holding every API key server-side, a Dropbox-to-library autosync watcher on a scheduled task, research and hub packs, and a site remodel. A CRM data-quality audit across 2,029 contacts took customer records out of version control and added a check so they cannot return. Ships behind a definition-of-done gate that has to pass before anything is called finished. 625 commits, 1,034 tracked files.
A faith-based pregnancy journal and family keepsake app I own and ship: offline-first, no login, every entry stored on the device in IndexedDB, live on Cloudflare Pages. Includes an OWASP ASVS 5 security review with a tracked remediation plan. 460 commits.
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 an illustrated 16-page PDF from them. A versioned data schema sits under change control, with purge-and-rollback tests for sensitive records. 290 commits and 949 passing tests, 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. 315 commits behind three gates — a 451-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 complete private archive of a year of coursework, built so the data survives losing access to the system it came from: 30 courses and 268 lesson pages, with grades, files, video transcripts and email pulled out of a hosted LMS, normalised, and stored somewhere retrievable. A watcher checks 13 source syllabus documents every 30 minutes and flags any change for review instead of applying it. 407 commits, 759 tracked files. This is records management as a migration problem — get it all, keep it faithful to the source, and make it findable afterwards.
A status board covering 56 projects and the client engagements at once, rebuilt from source every morning by a scheduled task: ledgers, git state and workflow registers are read fresh each run and nothing is stored in between, so the board cannot disagree with the work. 62 commits; 125 tests across 4 test files.
A private widget platform: a password-gated builder plus a public embed runtime, so a marketing site adds a form or gallery without a subscription or a third-party CDN. 51 commits and 44 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.