Skip to main content

Clera

Founding Cloud Infrastructure Engineer

San MateofulltimemidAdded today

About this role

Design and build cloud infrastructure from scratch for an early-stage enterprise AI startup operating in regulated industries. You'll own the complete infrastructure lifecycle—from architectural decisions through production scaling—establishing foundational systems and best practices that define the company's technical foundation.

What you'll do

  • Design and build enterprise-grade cloud infrastructure supporting a semantic platform
  • Implement infrastructure-as-code, CI/CD pipelines, and deployment automation
  • Architect and manage production Kubernetes clusters and container orchestration
  • Build monitoring, observability, and logging systems across the stack
  • Design relational and NoSQL database infrastructure at scale
  • Establish security, networking, and access control standards

What they're looking for

  • Cloud platforms (AWS, GCP, or Azure)
  • Infrastructure-as-code (Terraform, CloudFormation, or Pulumi)
  • Kubernetes and container orchestration
  • CI/CD pipeline development
  • Observability tooling (Prometheus, ELK, Datadog, New Relic)
  • Database architecture (relational and NoSQL)
  • Infrastructure security and networking
  • Autonomous problem-solving in ambiguous environments
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 your experience designing a cloud infrastructure from scratch—what were the biggest architectural decisions you made?
  • How have you approached infrastructure-as-code in previous roles, and what tools did you prefer and why?
Unlock all 7 questions free — and practice them live →