Founding Infrastructure Engineer

You'll own the platform every one of our agents runs on — the execution layer that turns a 3,000-sheet drawing set into hundreds of verified engineering findings. That means the async worker fleet, the agent sandboxes, the LLM traffic layer, and the document-processing pipeline underneath all of it. The headline focus is our agent sandboxing platform: sandboxed code execution for LLM agents— warm pools for instant startup, strict isolation, and controlled network egress for untrusted agent-generated code.

We run on Azure Container Apps and Bicep today. We look for deep expertise in containers, workload isolation, and Azure infrastructure rather than any specific toolchain. You will lead our infrastructure decisions going forward.

What you'll do:
Own the agent sandboxing platform and keep it fast, cheap, and secure as agent traffic grows. Run the async worker fleet that processes thousands of drawing sheets per project, autoscaling from zero to hundreds of jobs and back. Own the LLM traffic layer: keep multi-tenant traffic fair, fast, and metered — every token accounted for in customer billing. Keep streaming reliable: chat and progress updates that survive deploys and disconnects.

Scale document processing: rendering, OCR, and extraction pipelines where one project can be tens of gigabytes of drawings. Own CI/CD, reliability, and cost — from the self-hosted runner fleet to incident response to the Azure bill. Ship in the codebase: contribute to our Python/FastAPI backend alongside product engineers.

• Own the agent sandboxing platform and keep it fast, cheap, and secure as agent traffic grows.
• Run the async worker fleet that processes thousands of drawing sheets per project, autoscaling from zero to hundreds of jobs and back.
• Own the LLM traffic layer: keep multi-tenant traffic fair, fast, and metered — every token accounted for in customer billing.
• Keep streaming reliable: chat and progress updates that survive deploys and disconnects.
• Scale document processing: rendering, OCR, and extraction pipelines where one project can be tens of gigabytes of drawings.
• Own CI/CD, reliability, and cost — from the self-hosted runner fleet to incident response to the Azure bill.
• Ship in the codebase: contribute to our Python/FastAPI backend alongside product engineers.
• 4+ years building and operating backend or distributed systems in production, including cloud infrastructure (Azure, AWS, GCP);
  Azure preferred.

• Strong Python — our deploy and environment tooling is Python.
• Deep production container experience. Azure Container Apps or similar preferred; AKS depth transfers.
• Workload isolation and sandboxing:
  Linux primitives (name spaces, seccomp, bubble wrap/gVisor-class tooling) and safe execution of untrusted code.
• Expert infrastructure as code in any major tool — we use Bicep today.
• CI/CD ownership with Git Hub Actions or Azure Dev Ops.
• Azure identity and networking:
  Entra , managed identities, RBAC, VNets, private endpoints.
• Production Postgres and Redis operations.
• Observability:
  Open Telemetry, Log Analytics/KQL, incident response.
• Rapid prototyping with AI coding agents (Claude Code or Codex), and the judgment to review and verify what they produce.