Sr. AI Engineer
Must have:
You have shipped agentic systems with Claude, OpenAI, or similar and know where they break in production
Experience writing production-grade Next.js + React + TypeScript and you are not afraid of a Supabase schema or a Stripe webhook.
You are comfortable being the only engineer in the room and making the call on architecture, scope cuts, and trade-offs.
Strong communication
Platforms You'll Live In:
Claude Code (CLI). Primary build surface. Comfortable in long agentic sessions, can debug a stuck run without restarting.
Claude Desktop(Chat/Cowork/Code). Stand up a working member assistant in under an hour with the right system prompt and uploaded context.
Cursor. Daily driver for repo work, fluent with composer and agent mode.
Replit. Spin up a working prototype in a single sitting when speed matters more than infra.
Lovable. Ship a member-facing UI from a prompt and then hand-edit the output without breaking it.
Vercel. Deploy Next.js, configure middleware, set env vars, debug a failed build from the log.
n8n or Make. Build a multi-step pipeline with branching, retries, and error handling that does not silently drop data.
Airtable. Model a working CRM with views, automations, and interface pages a non-technical owner can use.
Supabase. Auth, row-level security, edge functions, and a schema you would not be embarrassed to inherit.
GitHub. Branch, PR, review, and ship clean commits; comfortable as the only committer on a repo.
Telegram Bot API. Wire real workflows and real bot interactions end-to-end without copy-pasting from a tutorial.
What We're Looking For:
You have shipped 10+ real applications that real users used, not side projects that died in a repo.
You can sit in a scoping call with a non-technical business owner, ask the right five questions, and walk out with a build plan.
You can deliver a working POC inside a week on your own, with no PM, no spec doc, and no design hand-off.
You write production-grade Next.js + React + TypeScript and you are not afraid of a Supabase schema or a Stripe webhook.
You are comfortable being the only engineer in the room and making the call on architecture, scope cuts, and trade-offs.
You communicate in plain English with people who do not know what an API is, and you do not condescend.
Nice to Have:
You have built tools for small business operations, sales workflows, or service businesses before.
You have worked inside a CRM or marketing automation stack as an operator, not just a contractor.
You have run your own consulting or contract work and know how to scope, build, and close out a project.