Reign Group
E-Commerce & MarketplacesDirect Lever career site

Head of AI Developer Infrastructure

Location
Remote (US)
Job type
Full-time
Level
Executive
Listed
Today

Skills & highlights for this role

  • Kubernetes
  • AWS EKS
  • Terraform
  • ephemeral sandbox environments
  • CI/CD pipelines

Also useful

  • Datadog
  • OpenTelemetry
  • ClickHouse
  • TypeScript
Free · No account needed

How well does your resume fit this job?

Upload your resume to see your score for this Reign Group role, what matches, what's missing, and your best other matches.

Scored on our server and not saved there. The file stays in this browser so you don't have to upload it again after you sign up.

About the role

Reign is the Autonomous Commerce Platform for DTC founders. We unify storefronts, checkout, payments, and operations into one AI-native platform where agents handle the operational grind and merchants focus on growth: making the most money, with the least headache, on their own terms.

We set out to build the "Shopify of Direct Response," and along the way we recognized something bigger. Direct response is roughly a third of all ecommerce transactions, a trillion-dollar market chronically overlooked by Silicon Valley. The merchants who run it are obsessive about tooling. They live and die by velocity, conversion, and margin. They have no brand moats, so they compete purely on operations, which is exactly what makes them the earliest and fastest adopters of AI agents in commerce.

This is a category-defining bet, and we are running at it from a position of strength.

Where We Are Today

  • 8-figure ARR, growing 100%+ YoY (top 0.5% of all startups launched in 2024), and we do it with capital efficiency: there is a real chance we finish the year with more cash on our balance sheet than we have ever raised
  • Rapid merchant adoption and expanding market presence
  • On track to beat our budgeted sales target by 100%+
  • Industry-leading NPS score
  • 70% of our new deals come as referrals from existing merchants
  • Venture-backed by a multi-billionaire ex-founder and direct response industry leaders
  • An executive team that has done this before: multiple leaders who have scaled a company from zero to unicorn status
  • A founder who builds from domain expertise: he bootstrapped $200M+ in DTC revenue as a direct response merchant before starting Reign, and is building the platform he always wanted as a merchant

Why Now

This is a rare opportunity for a technical leader to step into a company with proven revenue, product-market fit, an established team, and a large market opportunity.

Three things make this an inflection point

  • Product-market fit is established. Demand continues to grow, merchant adoption is accelerating, and Reign is outperforming expectations.
  • There is an opportunity to define a category. While many companies are building AI tools for commerce, few are focused on helping sophisticated DTC operators automate revenue-generating decisions at scale.
  • Our customers are AI-ready. They adopt technology quickly when it drives measurable business outcomes, creating an ideal environment for agentic products.

Why This Role Exists

Engineering already runs on an advanced AI-native SDLC. Our engineers ship with agents every day, on a shared team brain that hands work between people and their agents, through a multi-agent pipeline that plans, builds, reviews, and verifies. Throughput is up roughly 10x since January. The factory is built, and the AI pod owns it.

The bottleneck is no longer the code. It is the infrastructure underneath it. Agents can write, review, and verify a feature in hours. Then the work waits: on tickets, on approval chains, on CI pipelines designed for humans pushing a few PRs a day, on someone in infra being available. Every idea we want to test runs into the same wall. Infrastructure built for the old way of shipping is now the slowest part of the new one.

You tear down that wall and rebuild it as something agents can use. Environments that spin up on demand and disappear when the experiment ends. Infra that AI can provision safely on its own, with guardrails enforced by the system rather than by a queue of humans. A path from idea to running experiment measured in minutes, not tickets. You are not here to maintain the current setup. You are here to prove there is a faster path that is still safe, and then make it the default.

How this fits. You report to Alvi Ali (Head of Applied AI) and Stephen Gardner (Head of AI Storefronts), who built the factory, and work hand in hand with them every day. They throw ideas at you; you test them day and night and come back with what wins. You partner with the platform group and the SRE, who keep production running, but you sit outside their process deliberately, so you can question it. From day one you have access to every infrastructure layer in the company, because you cannot change a system you are not allowed to touch.

This is a Head of seat on purpose. We would rather pay for one person who can redesign how infrastructure works in an AI-native company than hire a team to keep the old model running. The scoreboard: time from idea to running experiment, time from spec to environment, how many tickets and approvals a feature no longer needs, cost per environment, and how much faster the AI pod ships because you exist.

What You'll Own

Experimentation as a service. You are the AI pod's experiment partner for orchestration and optimization. New agent topologies, model routing, parallelism strategies, runner configurations: you stand up the experiment, run it hard, measure it, and report the winner. Many ideas a week, not one a quarter.

Cloud sandboxes and ephemeral environments. Full environments, with their own databases and seeded synthetic data, created on demand by a person or an agent and torn down automatically. You decide whether today's sandbox model is the right foundation or whether something better replaces it.

AI-provisioned infrastructure, safely. Agents set up environments and infra themselves, without Jira tickets or human approval queues, inside guardrails that make the unsafe thing impossible rather than merely discouraged: policy as code, scoped and time-boxed credentials, isolated accounts, full audit trails.

Rethinking the delivery path. You question every step between a verified change and production. Do heavyweight CI pipelines belong in an agent-driven loop? Does GitHub? Do ticket-based approvals? Where the answer is no, you build the replacement and prove it out.

Compute for agent swarms. The runner fleet, the cost model, and the call on cloud vs bare-metal vs on-prem, made with real usage and cost data and revisited as the numbers change.

Runtime for the team brain and the watcher. The shared memory (Postgres with vector and full-text search) and the watcher service run 24/7 on infrastructure that is not someone's laptop. You own the runtime; the engineers who built the logic keep the logic.

Guardrails that keep it safe. Automation proves itself in a sandbox first. Production only ever sees reviewed changes. Security work never runs unattended. Less process does not mean less safety; it means the safety lives in the system instead of in a ticket queue.

What Success Looks Like in 90 Days

Day 30. Our Engineering Leads have onboarded you personally, walked you through the factory, and given you the best tools available and full access to every infra layer. You have shipped through the factory yourself and mapped every point where infrastructure slows it down, with numbers. At least one experiment the AI pod has been waiting on has been run and called. The first change that removes a ticket or an approval step from the path is live.

Day 60. An agent can spin up a full ephemeral environment with seeded data on its own, safely, in minutes, with no human in the loop. The AI pod is running multiple experiments a week through infrastructure you built. Agent swarms run off laptops on a runner fleet you own, and the compute call is made with cost data.

Day 90. The path from idea to running experiment is measured in minutes. A feature that used to need a pile of tickets and approvals ships without them, with stronger safety guarantees than before. The team brain and the watcher run as services. You have a written plan for the next two quarters of AI infrastructure, and the AI pod has signed off.

Who You Are

  • 10X cracked at this. You run agents all day, and you have built the infrastructure that lets other people do the same: sandboxes, ephemeral environments, runner fleets, model gateways. You can name the last three things you shipped with an agent and what they replaced.
  • From a dev-tools company that moves fast. You have built infrastructure whose users were other engineers, ideally at Cursor, Replit, Cognition, Vercel, Modal, or a startup doing the same thing. You measure yourself by how fast everyone else got.
  • A master of cloud sandboxes. Ephemeral environments, isolation, per-environment data, fast spin-up and teardown. You have opinions on how they should work because you have built them.
  • Allergic to old school DevOps. You respect what process was trying to protect, and you know how to protect it better without the tickets, queues, and waiting. You challenge the normal way of doing things and bring a working alternative with you.
  • An experimenter. You love taking someone else's idea, testing it overnight, and coming back with data on what won. You are comfortable being wrong fast.
  • Production AWS and Kubernetes. EKS, Terraform, and real production systems, and you have carried the pager for what you built.
  • Obsessed. You stay late because the work is that good, not because anyone asked. Our best engineers are the bar, and you will keep up with them on day one.
  • A missile, not a passenger. You operate with a lot of autonomy and solve problems instead of escalating them. You don't bring us problems; you bring solutions and the resources you need to execute.
  • Startup-forged. You've thrived in fast, resource-constrained, high-intensity environments in the last few years, or you've built something of your own.
  • No tolerance for mediocrity. The people who thrive here hold themselves and others to an extremely high standard with no exceptions. We're here to build a generational company.

Our Stack

  • AWS (EKS, RDS MySQL, ElastiCache Redis in cluster mode, S3 with KMS, Secrets Manager), GCP, and Cloudflare Workers.
  • Terraform for infrastructure.
  • GitHub Actions with a per-service matrix and queued production deploys.
  • Request-isolated PR sandboxes on EKS.
  • Datadog and OpenTelemetry.
  • ClickHouse Cloud with CDC from MySQL and schema as code.
  • Postgres with pgvector for the team brain.
  • A TypeScript monorepo (NestJS, Node, pnpm, seven services, 26 shared packages) and a React portal.
  • Claude Code with tiered models, the Anthropic SDK, an MCP server, a promptfoo-based agent harness, multi-agent code review, and git worktree lanes.
  • Claude Code is a real part of the daily workflow here, not a garnish.
  • Every piece of this is open to being replaced if you can show something better.

Huge Plus

  • You have built AI-driven or self-service infrastructure provisioning where agents or users create environments without a human approval step.
  • You have run self-hosted CI runners, sandbox fleets, or browser test fleets at scale and can say what each run cost.
  • You have replaced or radically simplified a traditional CI/CD or source control workflow and lived to tell about it.
  • Bare-metal cost arbitrage with the receipts.
  • You have evaluated open-weight models on hosted providers for real workloads.
  • Commerce, checkout, or payments infrastructure, or any environment where PCI was real.
  • You've been a founder, or an early operator who owned the outcome.

Our Values

We are a value-driven company. These aren't words that we just put on a wall. They dictate how we hire, fire, and promote.

All In to Win. Operate with urgency and a relentless focus on excellence.

A Players Only. Build and maintain exceptional talent density. Pure meritocracy.

Merchant First. Every decision is measured by merchant impact.

Entrepreneurial Spirit. Move quickly, stay resourceful, and take ownership.

No Ego. The best ideas win regardless of title or tenure. No BS politics.

Reign is mission-first and performance-driven. We operate with urgency, give direct feedback, and expect high ownership. If you thrive under pressure and love building in fast-moving environments, you'll do great here. If you strongly prioritize predictability, comfort, and work/life separation, this 100% isn't the right role.

We operate as a flat, high talent density, meritocratic organization.

Read the original posting

From Reign Group's careers page, first listed on Rolev.ai on November 19, 2026. Rolev.ai is not the employer.

How Rolev.ai helps with this application

Rolev.ai is a job search and application tool for US job seekers. For this Head of AI Developer Infrastructure role at Reign Group, it shows how your resume fits, tailors your resume to the posting, and prepares the application for you to review.

  • See how you fit

    Openings from employer career sites are ranked against your whole resume—and searchable inside Claude, ChatGPT, and Cursor via Rolev.ai MCP.

  • Tailor without inventing

    Every change to your resume is checked against your original. New experience goes in only with your yes—zero fabricated claims.

  • Draft the full kit

    Tailored and Full Match resumes, role-specific cover letters, and answers to employer screening questions are prepared in seconds.

  • 1-Click Extension Autofill

    The Chrome extension fills the employer's Greenhouse, Workday, Lever, or Ashby form in 1 click. You review it and press Submit.

Common questions

Where is the Head of AI Developer Infrastructure job at Reign Group located?

Yes, this Head of AI Developer Infrastructure opening at Reign Group is listed as Remote (US). Always check Reign Group's application page for specific state eligibility or relocation policies.

What qualifications are required for Head of AI Developer Infrastructure at Reign Group?

For the Head of AI Developer Infrastructure role, Reign Group highlights experience with Kubernetes, AWS EKS, Terraform, ephemeral sandbox environments, CI/CD pipelines. Rolev.ai can score your existing resume against these requirements and show any skill gaps before you apply.

How do I apply for the Head of AI Developer Infrastructure position at Reign Group?

This listing links directly to Reign Group's Lever application page. You can apply directly on Reign Group's site, or use Rolev.ai to check your resume fit, generate a zero-hallucination tailored resume and cover letter for this posting, and autofill the Lever application form in 1 click with the Rolev.ai Chrome extension. You always review the form and press Submit yourself.