Any
Open for negotiations
40
Jun 15, 2026
Summary
Vibe coder — someone who lives inside Claude Code, Cursor, or whatever tool ships
fastest, and treats AI as a teammate rather than a novelty.
Responsibilities
Build internal tools — CRM enrichment scripts, onboarding workflows, recruiter
dashboards, automation glue between Gmail / Sheets /
whatever else gets in the way of moving faster
Ship client-facing apps — portals, micro-tools, and small web/mobile products either
for our clients or as productized add-ons we sell into them
Prototype fast — when one of us says “what if we…”, you should be able to spin up
something demo-able within a day or two, not a quarter
Own the build loop end-to-end — spec, build, deploy, iterate. We’ll give you product
direction and the freedom to ship
Treat AI as a co-builder, not a crutch — you should know what good code looks like,
what bad code looks like, and when the LLM is bluffing
Requirements
2–5 years building real, deployed software (side projects count if they shipped to users)
Fluent with AI coding tools — Claude Code, Cursor, Windsurf, Aider, whatever. You can
describe your actual workflow, not just say “I use Copilot sometimes”
Stack-agnostic, JS/TS + Python by default — Next.js, React Native, FastAPI, Node,
Supabase, Vercel are all in our world. Bonus for anyone who’s wrangled
Gmail/Drive APIs, or n8n / Make
Product instinct — you don’t need a PM to tell you the button should be bigger
Comfortable with ambiguity — half our briefs are voice notes. You’re okay with that
Good taste — UI doesn’t need to win awards, but it shouldn’t look like a 2014 admin
panel
Bonus points
You’ve shipped something built primarily through AI collaboration and can show it to us
Experience with Australian or SEA SME ops, recruiting tools, or CRMs (HubSpot,
Pipedrive, GHL, etc.)
You can read a database schema and not flinch
You’ve used Claude Code in anger and have opinions about it
How to apply
Send us:
1. most interesting thing you’ve built with AI assistance — what it
does, what tools you used
2. Links to anything live (GitHub, deployed apps, screenshots, Loom videos)
3. Optional but encouraged: spend 60–90 minutes vibe-coding a small tool that solves
something on this list
Send it to