AI Systems Builder
W-2 - Full Time | Remote (North American / Central Time) | Reports to Director of Operations
The Execution Engine Behind Our Smartest Systems
Every department in this company is generating AI and automation ideas faster than they can be built. The Build Team turns those ideas into operational reality, and this is the seat that ships them. You're not advising. You're not consulting. You're Claude Code native, embedded with departments, building the AI systems, internal tools, and dashboards they need to compress the slowest parts of their week. The stack flexes by build (Claude Code, n8n, Supabase, and whichever front-end platform fits the project), and you pick up new tools the week they drop. If you see a business problem and immediately start mapping the systems chain in your head, and you find that fun, keep reading.
Profile insights
Here’s how the job qualifications align with your profile.
Skills
Do you have experience in Workforce management?
Location
Remote
Who We Are
The Uncommon Business is the world's fastest-growing AI-first education company, teaching business leaders to architect intelligent systems, not just prompt tools. We don't do busywork, legacy thinking, or 80-hour founder weeks. We build companies where AI handles the repeatable, humans drive the irreplaceable, and leaders scale without burning out. We're profitable, EOS-driven, and operate in championship-level surge cycles. You'll be promoted on impact and ownership — not tenure. High performers thrive here. Passengers don't last.
If You Worked Here Last Week
You might have:
Built V1 of a Claude skills pack for the Ops team without anyone asking you to. In a Thursday meeting, the Director of Ops mentioned the team was losing hours every week to scattered project management and inefficient meetings. By Monday morning, you'd packaged three installable skills into the shared library, with three teammates already testing them.
Embedded with the Enrollment Sales team for a day. Audited their seat data against the CRM to catch payment mismatches, built them a tracking database with your per-member notes, recorded a Loom walking the team through what you found, and sent them the SOP for how to action the fix list. They were running with it by end of day.
Shipped the new Student Success engagement dashboard from kickoff to live in a week. Monday you met with the new Director of Student Success to understand the ask: a single view of every student's engagement data. By Friday it was live with fuzzy email and name matching to reconcile call attendance against the user table, enrollment data pulled from the CRM, and everything merged into one view. Loom posted, now in maintenance mode.
Caught a silent break in the AI Applicant Scoring agent before it became a problem. The weekly run pulls candidates from the hiring pipeline, scores them on a five-dimension rubric, and posts to Slack. When a database filter quietly stopped applying mid-week, you spotted it from the agent's own no-op report, documented what happened, and shipped the fix before the next scheduled run.
Scoped a new internal affiliate software build end-to-end. Reviewed lessons learned from the last launch, then researched whether any off-the-shelf solution would fit. When nothing did, you mapped the full build: scope, data architecture, infrastructure. Submitted it to the Build Manager and Director of Operations for review.
Your Core Responsibilities
We value ownership over task lists. Here's where you'll lead:
AI Systems & Agent Builds. You're Claude Code native: agents, sub-agents, skills, MCP servers, prompt systems. You ship the AI surfaces that real teams use daily, embedded inside the department you're assigned to, replacing the manual work that used to eat their week. Production tools with structured inputs, push-back logic, and outputs formatted for wherever the workflow lives.
Embedded Department Catalyst. When you're placed with a department, you don't wait for a build queue. You spend time inside their workflow, watching how they work, asking smart questions, and mapping where AI and automation can compress the slowest parts of their week. You surface build briefs FROM the team rather than waiting for them to land in your inbox. You see what the department can't see yet, you propose builds with the tradeoffs worked out, and you ship the ones that get green-lit. The department feels different by the time you've been embedded for a week.
Dashboards & Data Infrastructure. You build dashboards and the data pipelines underneath them. The stack flexes by build. Today Supabase and Baserow on the data side, with whichever front-end platform fits the project (Vercel, Replit, Retool, Hex, or the next thing we adopt). You don't have a favorite tool. You learn new platforms fast, communicate the tradeoffs to the team, and architect the flow from data source to visible metric.
Build Queue Execution. You execute against the Build Queue at TUB pace. Express Track builds delivered in 24-48 hours, Architect Track builds delivered on scoped timelines with zero missed deadlines. You push back kindly when a brief is off, propose alternatives with the tradeoffs worked out, and know what NOT to build.
Production Ownership. Every build you ship is yours to maintain. You monitor your systems in production, catch breaks before users do, and resolve issues with the same speed you shipped them. Builds with your name on them stay alive. Documentation ships with the build: what it does, how it works, how to maintain it, where it lives. A build without documentation and a working uptime story is not complete.
The Traits We’re Calling In
We hire humans, not checklists, but success here requires:
Modern AI stack shipped end-to-end. Claude Code native: agents, sub-agents, skills, MCP. Comfortable working across n8n, Supabase, GHL, and dashboards on at least two different front-end platforms. Table stakes.
Cross-department systems thinker. When you build for one team, you instinctively map which other teams the build touches and what could ripple upstream or downstream. "If we do this, will it connect with that, and what about the other department?" is your default question.
Builder who loves the team part. You can grind solo when the build calls for it, but the embedded weeks energize you most. No ego, resourceful when stuck (you find the answer, you don't wait to be told).
Proactive, not reactive. You don't wait for the brief. You watch the workflow and surface what needs to be built.
AI is your hobby, not just your job. New Claude Code features get tested the day they ship. You think about what could go wrong before you push. And you have business acumen rooted in P&L and ROI, so you don't chase flashy AI. You build for revenue and freed up capacity.
What Success Looks Like
You own these key metrics:
Capacity Created: Your share of Ops's quarterly Capacity Created OKR, measured in full-time-employee equivalents of recurring work your builds have automated. Validated by the using department at the 30-day mark.
Build Velocity: Ship 6-10 completed builds per month through the Build Queue, ranging from Express Track (under 4 hours) to multi-day Architect Track projects.
Turnaround Time: Express Track builds delivered within 24-48 hours of assignment. Architect Track builds delivered within the scoped timeline with zero missed deadlines.
Quality & QA: 90%+ of builds pass first QA review without rework, meaning you self-checked against the scope brief before marking it complete.
Maintenance & Uptime: Automations, dashboards, and integrations you've shipped maintain 95%+ reliability. Production breaks resolved within SLA windows. You catch issues before users report them, especially during launch seasons with 300+ students onboarding simultaneously.
Documentation Compliance: 100% of completed builds include clean documentation within 24 hours of delivery: what it does, how it works, how to maintain it, where it lives.
Urgency Response Time: Same-day working V1 on leadership's true-urgency requests. Voice note or Slack ping, either way.
📋 Schedule Flexibility
Must be flexible and available for additional hours and weekend work during launch seasons, product releases, or critical business periods. We operate in championship-season cycles twice per year. These are high-intensity windows where the entire team rallies to deliver exceptional results. Outside these periods, workload is sustainable and focused on building systems for the next surge.
Time Zone: North American / Central Time preferred for overlap with leadership and embedded department.
Applications are initially reviewed using AI-assisted screening tools to assess alignment with role requirements. All hiring decisions are made by humans.
This role is open to North America (Central time). Certain locations may have additional requirements. Final compensation may vary based on location.
The Uncommon Business is an equal opportunity employer. We believe diverse teams build better companies.
The Uncommon Business | People-First. Systems-Driven. Built for Scale
Apply Now
The Uncommon Business
All Rights Reserved ©