About the role
What Artisan Is
We're building AI employees. Not chatbots. Not copilots. Autonomous digital workers that do real jobs.
Our first, Ava, is an AI BDR used by hundreds of companies. She researches leads, writes and sends emails in a customer's voice, runs multi-step outbound sequences, manages her own deliverability infrastructure, self-optimizes over time, and handles objections and meeting booking. She's not a tool someone uses. She's a teammate.
We're a YC W24 company, have raised $35M+ from investors including Y Combinator, and are at $9M+ ARR. We just launched Ava 2.0, a step change in what an AI employee can do. The engineering problems are hard and the surface area is enormous.
The Role
Artisan runs a platform that manages hundreds of millions of leads, orchestrates autonomous AI agents in real time, sends email at massive scale across thousands of customer mailboxes, and serves a product suite that replaces an entire sales stack (CRM, inbox, dialer, lead database, campaign engine). The infrastructure that makes all of this work reliably is the job.
You'll own the full DevOps and infrastructure layer at Artisan. This is a staff-level role where you'll set the foundation, define the practices, and build the systems that everything else depends on.
What that looks like concretely:
- Kubernetes and container orchestration. We run on AWS with Kubernetes at the core. You'll own cluster management, scaling policies, resource optimization, and the overall compute layer that serves AI workloads, data pipelines, and customer-facing product infrastructure.
- CI/CD and deployment pipelines. We ship constantly. You'll build and maintain the deployment infrastructure that lets engineers release with confidence, multiple times a day. Automated testing, staging environments, rollback strategies, feature flags.
- Observability and reliability. Monitoring, alerting, logging, tracing. When an AI agent fails to send an email or a pipeline stalls on lead enrichment, the team needs to know immediately and understand why. You'll build the observability layer from the ground up.
