AI Developer

We're looking for an AI-first developer who genuinely loves building and shows up with the plan. If you light up when you talk about wiring agents together, shipping internal tools fast, and using AI as a daily working partner, and you'd rather drive the build strategy than wait for a spec, we'd love to hear from you.

The Role

This is a gig-based, project-driven build role focused on internal tooling. Here's what you'd actually be doing:

- Building agents and automations from the ground up, including wiring up MCP servers and Claude Code workflows
- Building a range of internal tools for the team, the kind of things that remove manual work and speed up how we operate
- Working across APIs and integrations, including GoHighLevel, to connect the systems we run on
- Partnering with the team on what gets built and why. We work as a team to win, and you'd own the technical thinking on your side of it

Within the first 30 to 60 days, success looks like you showing up with the plan. You should be telling us what we should build next, how to approach it, and in what order. You should have a clear point of view on what's worth automating, what isn't, and what you want to ship first. The bar here is strategic ownership of the build, not waiting for a backlog to be handed to you.

Schedule

Work hours are flexible but need to overlap with our team between 9:00 AM and 5:00 PM EST during active project work. Just want to make sure you can meet inside that window.

What We're Looking For

- An AI-first mindset. You use AI as a real working partner every day, and it shows in how you work.
- Independent problem-solving. You think first, use AI to amplify your thinking, and verify before shipping anything.
- A strategy-first approach. You're someone who shows up with the plan and tells us what we should be building, testing, and improving. You partner with our team on execution, but you lead the thinking on your work.
- Deep comfort with Claude Code, GitHub, Supabase, Vercel, working with APIs, and the GoHighLevel API. We're also genuinely interested in whatever else you've built your workflow around.
- A real love for this work. That comes through fast in conversation, and we'd rather hire someone who has it than someone who's just qualified.

How to Apply

A few things we'd love you to do, in order:

1. Please start your reply with the word "Jamal." We use this as a small check to spot applicants who read instructions carefully. Without it, we won't be able to review your application.

2. Record a 5-minute video answering the questions below. No script needed. We just want to get a feel for how you think.

3. Share your full tool stack with self-ratings (1 to 10). These ones we already know we need:
- Claude Code /10
- GitHub /10
- Supabase /10
- Vercel /10
- Working with APIs /10
- GoHighLevel API /10

Then add every other tool you use, one per line, with /10. Include AI tools, frameworks, automation platforms, niche services, spreadsheets you've built, the works. Honesty matters more than scoring high. The video will give us a sense of where you actually are.

4. Walk us through your work history. For your last 2 or 3 clients or accounts:
- What size was the company or account when you started (team size, what they were running, what was manual before you came in, whatever metric fits)?
- What did you build for them?
- What was the outcome? Where were they when you started, and where are they now?
- If you have current clients, where are those projects today?

We're trying to understand how you measure your own impact. The more specific, the better.

5. Quick confirmation that you can work somewhere inside the hours described above.

How You Use AI

In your video, spend a minute or so on this. The more specific the better:

- Which AI tools you use daily, weekly, and occasionally
- A specific example of a build task in this role where AI saves you real time, and how you use it
- A time AI gave you a wrong or bad output. How you caught it, and what you did about it
- Anything you've intentionally chosen NOT to let AI do in your work, and why

We're looking for real, lived examples. The specifics tell the story.

A Few Questions for Your Video

Take these in order, and just talk through them naturally.

1. If you came on next week and we asked you to build out our internal tooling, walk us through your first 30 days. What would you want to look at, what would you build first, and how would you d ---------- the order?
2. We hand you a vague request like "we need something to make X less painful," with no spec. Walk us through how you go from that sentence to a shipped tool.
3. An automation you built has started silently failing in production. Walk us through what you check first and how you track it down.
4. Why do you love building this kind of thing? Tell us about a recent tool or automation you shipped that reminded you why you do this work.
5. What's something about building with Claude Code, MCP, or agentic workflows that's changed in the last year that you've actually adjusted your approach around?