Skip to main content

Clera

Full Stack Engineer

San MateofulltimemidAdded today

About this role

Join a seed-stage AI infrastructure startup as a Full Stack Engineer to build an enterprise context layer for AI agents. You'll own complete product surfaces end-to-end, balancing frontend (60%) and backend (40%) work while making complex distributed systems intuitive for engineers.

What you'll do

  • Design and ship complete product surfaces from customer-facing interfaces to underlying APIs and data models
  • Build frontend interfaces using modern frameworks to make complex system behavior legible and fast
  • Develop backend services and APIs with strong performance and real-time capabilities
  • Make independent architectural decisions and own them through production
  • Define product strategy and design without handed-down specifications
  • Monitor production systems and fix issues as they arise

What they're looking for

  • Full-stack web development (React, Vue, or equivalent modern frontend framework)
  • Backend development (Python, Go, Node.js, Java, or equivalent)
  • Database design and data modeling for high-performance systems
  • System architecture and distributed systems design
  • API design and development
  • Production deployment and monitoring
  • Graph databases or knowledge graphs (nice to have)
  • Real-time systems or agent-based architecture (nice to have)
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 full-stack feature you shipped end-to-end—how did you approach the frontend, API, and backend design decisions?
  • Tell us about a time you had to make an independent architectural decision in production without detailed specifications. How did you validate it?
Unlock all 7 questions free — and practice them live →