Automation & Systems Engineer | Make, n8n, Zapier, GHL, Airtable (Part time to full time)

We run a lead-generation company in the home-services space. Our stack is a living system — automations, CRMs, dashboards, and custom endpoints that move real money and real leads every day. We need an engineer who can keep it fast, debug it when it breaks, and proactively make it leaner. This is hands-on. You'll go from "an account manager says X is broken" to a fix in the same day, and from "this automation costs too much / runs too slow" to a rebuilt version that doesn't. What you'll do day-to-day: ⦁ Debug & data pulls. Account managers surface issues — you triage and fix them. When someone needs data that isn't in a dashboard yet, you go get it. ⦁ Build & fix dashboards by vibe-coding with Claude Code. We already work this way; you should be fluent in it, not learning it on our dime. ⦁ Optimize automations for speed & cost across Make.com, Zapier, and n8n. You understand operation counts, payload sizes, when to use a built-in node vs. code, and how to cut waste without breaking the flow. ⦁ Build & manage CRM automations in GoHighLevel, Airtable, or our custom CRM. Where this goes (the longer-term ideal) ⦁ Independently build vibe-coded endpoints, front-end apps, and small tool/API integrations for B2B software. ⦁ Optimize the database & loading speed as our data samples get larger — query/index work, schema decisions, caching. ⦁ Spot and implement efficiency wins proactively — not just close tickets. Remove waste, migrate clunky processes to streamlined systems, and tell us where the bottlenecks are before we ask. Our stack: Make.com · n8n · Zapier · GoHighLevel (GHL) · Airtable · Cloudflare (Workers/Pages) · Supabase · ad-platform integrations (Meta / Google / TikTok / LinkedIn) · Claude Code for vibe-coding. You don't need to be expert in all of it, but you should be strong across automation (Make/n8n/Zapier) + at least one CRM (GHL/Airtable) + comfortable shipping code with Claude Code. Cloudflare/Supabase/SQL experience is a big plus. The arrangement: ⦁ Part-time for the first 3–6 months, converting to full-time after that if it's a good fit (and we expect it to be). ⦁ $50–$90/hr depending on proven ability. ⦁ Available during 9 am - 5pm EST M-F What makes you a fit ⦁ You think in systems and leverage — you'd rather build the thing once than do it by hand every week. ⦁ You ship fast, learn from what breaks, and course-correct. Speed of iteration over perfection. ⦁ You can read someone else's automation/codebase and improve it, not just greenfield your own. ⦁ You communicate clearly and don't disappear. To apply (read carefully — this filters out copy-paste proposals) 1. Start your proposal with the word LEVERAGE so we know you read this. 2. Answer this in 3–5 sentences: Describe one automation you optimized for speed or cost — what was slow/expensive, what you changed, and the measurable result. Be specific (operation counts, runtime, $$, whatever you tracked). Generic "I'm passionate about automation" answers get skipped. We read every proposal that follows these two steps. We ignore the ones that don't.