I build the automations and systems that let small teams stop doing the same work twice.
Most of my work starts the same way: someone has a process living in voice notes, spreadsheets and DMs, and nobody is sure what happens next. I turn that into a workflow that runs — and then I test it, because I came up through QA and I don't call something done until I've tried to break it.
WHAT I BUILD
• Workflow automation — n8n (self-hosted and cloud), Make, Zapier; API integrations, scheduled jobs, and LLM-assisted steps with human review built in
• Internal tools — React, TypeScript, PHP, Supabase, MySQL; small apps and dashboards teams actually use
• Operations systems — Notion and ClickUp hubs connecting contacts, tasks, deliverables, meetings, reporting and email into one place
• Software QA — test case design, manual testing, regression, smoke, UAT, and bug reports precise enough for a developer to fix without asking follow-up questions
RECENT WORK
• Built and self-hosted an n8n pipeline (Docker, Google Sheets, Telegram) that scrapes job posts, scores fit, and drafts applications for review before anything is sent
• Authored QA workbooks covering 5,209 planned test scenarios and executed 615 manual test cases on a property management platform; found a critical access-control defect that became a platform-wide fix
• Helped define and launch an operations hub for a research and impact organisation, replacing scattered trackers with one connected system
BS Information Technology, cum laude (1.43 GWA), Cavite State University. Career Service Professional Eligibility, 2025. C2 English.
I verify before calling something done, and I use AI as a multiplier rather than a shortcut. If you have more moving pieces than systems to hold them, message me.
Verified
