Cebu, Philippines
Projects

Catalyst Hiring - Recruiting for remote VAs

July 1, 2026

Overview

Catalyst Hiring is how Catalyst Outsourcing recruits remote virtual assistants (VAs) for its client companies. Candidates find roles on a public jobs board and apply through one form. Recruiters score applicants and move them through a pipeline. They share shortlists with clients and send offer letters, contracts and NDAs that candidates sign online.

My role

Lead developer since March 2026. The client started the product in Lovable in October 2025, before I joined.
  • 1,998 commits: 84% of the commits people made
  • I made 89% of all commits from late June to late September 2026
  • Lovable built most of the AI video interview module

What I built

  • Recruiter dashboard: KPIs, applications per day, recent strong applicants and a source breakdown.
  • Letters & Contracts: offer letters, contractor, trial and NDA documents, and client service agreements. Signers draw their signature online, and the app produces the PDF.
  • Shortlists and the share page where clients review candidates.
  • Public candidate profiles and the Profile Generator that builds them.
  • Recruiter Tools hub and its Job Post Builder.
  • Pipeline board: drag applicants between stages, see AI fit chips, and switch between list, grid and board views.
  • Talent pool: fit ranking, filters, kept candidates, skills and links.
  • Status email templates with a live preview and an AI rewrite.
  • Apply flow and jobs board updates: a WhatsApp field, Google sign-in and SEO share previews.
  • Edge functions, including job-match alerts that tell candidates when a new role fits them.
  • Tests: 86 of the 90 test files.
The client started the jobs board. Lovable started the pipeline board and the talent pool, and a teammate started the email templates. I did most of the later work on all four.

How I built it

I build with Claude Code agents. I write the plan and the task specs, and I set the checks each change must pass. I wrote 14 of the 16 commits on CLAUDE.md, the rule file the agents read.
  • A tag on each task sets its checks, such as a plan review or a Playwright check.
  • A push to main goes live. So since July 2026, two reviewer agents read every nontrivial change first. They have no memory of how the code was written.
  • Agents build in parallel, each in its own folder. The repo holds 128 of these builds, 16 of them for review and verification.
  • Agents apply database migrations through Supabase's MCP server, a direct tool connection. They read the version back to confirm it.
The repo carries 15 skills (reusable task instructions) and 4 subagents (specialist agents).

Tech stack

  • Web: React 18, TypeScript, Vite, Tailwind CSS, shadcn/ui (Radix), TanStack Query, React Hook Form, Zod, dnd-kit, Recharts, jsPDF
  • Backend: Supabase (Postgres, Auth, Storage, Edge Functions), Vercel
  • Quality: Vitest, Playwright, Sentry
  • Agents: Claude Code, Codex occasionally, and Lovable until July 2026
Ask me anything