Skip to main content

Clera

Founding Cloud Infrastructure Engineer

San MateofulltimemidAdded today

About this role

A founding infrastructure engineer role at an early-stage AI infrastructure startup in San Mateo. You'll architect and build cloud infrastructure from scratch for an enterprise AI agent platform, owning all design decisions and establishing foundational practices across the entire stack.

What you'll do

  • Design and build cloud infrastructure from the ground up for a semantic, AI-focused platform
  • Own full lifecycle management from architecture through production deployment and scaling
  • Establish infrastructure standards, best practices, and tooling for the organization
  • Build and maintain CI/CD pipelines and deployment automation systems
  • Architect and manage Kubernetes clusters and container orchestration in production
  • Implement monitoring, observability, logging, security, and networking infrastructure

What they're looking for

  • Cloud platform expertise (AWS, GCP, or Azure)
  • Infrastructure-as-code tools (Terraform, CloudFormation, or Pulumi)
  • Kubernetes and container orchestration
  • CI/CD pipeline design and automation
  • Database infrastructure (relational and NoSQL systems)
  • Infrastructure security and networking
  • Data pipeline or data infrastructure (preferred)
  • AI/ML platform infrastructure (preferred)
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Clera

Clera builds an agentic operating system that automates complex workflows and processes through AI agents, with a platform designed to simplify distributed infrastructure management for developers. The company is hiring Founding Engineers, Customer Engineers, and Product Engineers to develop both backend systems and user-facing interfaces across their AI automation products.

View all jobs at Clera

Likely interview questions

  • Walk us through a time you designed cloud infrastructure from scratch—what were your key architectural decisions and how did they evolve as the system scaled?
  • Describe your experience with infrastructure-as-code: which tools have you used, and how have you structured IaC to balance flexibility with maintainability?