Clera
Founding Engineer
About this role
Join a seed-stage AI infrastructure startup as a Founding Engineer to design and build scalable backend services in Go that power next-generation AI applications. You'll architect microservices platforms, optimize distributed systems, and directly shape the company's technical direction alongside founders.
What you'll do
- Design and build core backend services in Go handling high-traffic, low-latency workloads
- Architect microservices platform on Kubernetes and evolve the technical stack as company grows
- Build and maintain high-quality API platforms with focus on reliability and developer experience
- Implement and optimize distributed caching and database layers (SQL, NoSQL)
- Profile and tune systems for performance under production-scale conditions
- Collaborate with founders on product direction and technical roadmap
What they're looking for
- Go (Golang)
- Distributed systems design and scalability
- Kubernetes in production environments
- SQL and NoSQL databases
- Distributed caching systems
- Performance profiling and optimization
- API platform design
- Concurrency and system design
Benefits
- Significant equity stake with meaningful ownership
- Generous total compensation package
- Direct influence on technical direction and architecture
- Remote-first opportunity with London presence
- Work on infrastructure powering AI applications
- Deep ownership and fast learning environment
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
- Walk us through a complex distributed system you've designed — what were the key tradeoffs you made between consistency, availability, and performance?
- Describe your experience migrating or scaling a system to handle significantly higher traffic. What bottlenecks did you encounter and how did you resolve them?