Clera
Founding Engineer, Infrastructure
About this role
Founding infrastructure engineer at an agentic integration platform, responsible for designing and operating the runtime, agent infrastructure, and observability stack from day one. You'll work directly with the CTO on a leadership track, setting architectural patterns for future hires while shipping to production constantly.
What you'll do
- Design and operate a mini cloud platform for integration runtime with durable execution, sandboxing, and self-healing
- Build and scale agent infrastructure enabling coding agents to write, test, and deploy integration code in production
- Own the full observability pipeline (logs, metrics, tracing) as a single-tenant, self-hostable product
- Establish architectural patterns and engineering standards for future infrastructure work
- Partner with founders on rapid iteration and production deployments
- Hire and mentor the infrastructure team growing around this domain
What they're looking for
- Infrastructure and platform engineering (3+ years)
- Observability pipelines (logs, metrics, distributed tracing)
- Kubernetes and Docker
- AWS cloud services
- TypeScript
- PostgreSQL
- System design and architecture
- Leadership and mentorship
Benefits
- Founding engineer role with clear leadership track
- Direct partnership with CTO and founders
- Immediate impact and broad ownership scope
- Visa sponsorship available
- San Francisco on-site location
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 CleraLikely interview questions
- Describe a production observability system you've designed—what were the key components and trade-offs you made?
- How would you approach designing a runtime platform that balances durable execution with resource constraints?