Skip to main content

Clera

Full Stack Engineer

San MateofulltimemidAdded today

About this role

Join a senior engineering team building AI infrastructure for enterprises. You'll own full-stack product surfaces end-to-end, balancing frontend work (60%) with backend services (40%), and make independent architectural decisions from design through production.

What you'll do

  • Own complete product surfaces across frontend interfaces, APIs, and data models
  • Design and implement production-grade APIs and backend services
  • Make architectural decisions and drive implementation through to production
  • Create UI that makes complex system behavior legible and performant
  • Monitor production systems and resolve issues as they arise
  • Build customer-facing features without relying on detailed specifications

What they're looking for

  • React or Vue
  • Python, Go, Node.js, or Java
  • API design and implementation
  • Distributed systems
  • Database design and data modeling
  • Product thinking and UI design
  • Full-stack architecture
  • Real-time systems optimization

Benefits

  • Visa sponsorship available
  • On-site location in San Mateo, California
  • Work with senior-level engineering team
  • End-to-end ownership of product surfaces
  • Building AI infrastructure for enterprise
  • Startup-speed execution environment
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 product you shipped end-to-end—how did you approach the architecture and what tradeoffs did you make?
  • Describe a time you had to design a UI for complex system behavior. How did you make it legible?