Operations · Mid-level

AI Operations Engineer

Forward-deployed with our team and on the factory floor.

Type

Full-time

Where

Chatsworth, Los Angeles · on-site, most days

Pay

Starting at $120,000 a year

Benefits

401(k) retirement plan

We run a 20,000 sq ft skincare and OTC drug factory on software we build ourselves with AI: a factory OS, a CRM, finance, quality, cameras on the line. Most of it was built by a very small team working with Claude. This role is the second pair of hands. You sit next to the people doing the work, find the hours they lose to copy-paste, and take them back.

What you will do

• Sit with a teammate for an hour (sales, quality, the warehouse, finance), watch how they work, and come back with the two or three things AI can take off their plate.
• Connect our tools to Claude through MCP connectors, set up Claude for each person, and write the prompts and skills they use every day.
• Ship small changes to our internal apps with Claude Code: a new field, a report, a Slack alert. Then deploy them, check them and roll them back if needed.
• Own the boring parts that keep it all safe: backups, access, who has which password, what happens when something breaks at 6 a.m.
• Factory IT: install and configure IP cameras, PoE switches, routers and Wi-Fi on the floor; get a device onto the network and its feed into our system.
• Write it down: a one-page how-to for every automation you hand over, so the person using it never depends on you.

You must

• You use Claude (or a similar AI tool) every day and can show us something real you built or automated with it.
• You understand how the internet works: what a URL, DNS, an API, a webhook and an environment variable are, and why a password never goes in a chat.
• You know what a backup is, how to prove one actually restores, and the difference between a backup and a copy.
• You can get a device onto a network: IP addresses, DHCP, a router admin page, PoE. You are not afraid of a ladder and a cable tester.
• You explain clearly to people who are not technical, in plain English, and you would rather ask a question than guess.
• You decide. When there are three ways to do something, you pick one, say why, and move.

Good to have

• Claude Code, Cursor or a similar coding agent; some Git and GitHub.
• Supabase / Postgres, Vercel, Slack apps, Google Workspace admin.
• Hikvision, Reolink, Ubiquiti or similar camera and network gear; RTSP.
• Experience in manufacturing, a lab, or any place where things physically get made.
• A second language.

Your first ninety days

• Week 1–2: shadow four teams, set Claude up for each person, and hand in a list of the ten biggest time sinks you saw.
• Month 1: ship your first three automations, each with its one-page how-to, and take over the weekly backup check.
• Month 2–3: own camera and network work on the floor and one internal app end-to-end, and measure the hours saved per week.

Probably not for you if

• You want to write code all day without talking to anyone. This job is half conversations.
• You need a full spec before you start. Most of what you will build, nobody has written down yet.
• You want to work fully remote. The floor, the cameras and the people are in Chatsworth, and the best weeks here are the ones spent mostly on site.