Clera
Full Stack Engineer
About this role
A Seed-stage enterprise AI infrastructure company seeks an experienced Full Stack Engineer to own product surfaces end-to-end—from customer-facing interfaces to APIs and data models. You'll operate with high autonomy in a small senior team, spending roughly 60% of your time on frontend/API work and 40% on backend services, shipping to production and owning outcomes without detailed specifications.
What you'll do
- Own complete product surfaces end-to-end: interfaces, APIs, and underlying data models
- Design and ship architectures to production, then monitor and fix issues independently
- Build intuitive UIs and performant APIs that expose sophisticated backend behavior
- Make architectural decisions independently without detailed specs or design files
- Remove growth ceilings by making customer-facing products obvious and usable
- Work across the full stack to make complex system behavior legible for engineers and enterprise teams
What they're looking for
- React, Vue, or equivalent modern frontend frameworks
- Backend languages: Python, Go, Node.js, Java, or equivalent
- API design and implementation
- Database design and data modeling for real-time systems
- Full-stack architecture and independent decision-making
- Product thinking and UX sensibility
- Distributed systems and production operations
- Knowledge graphs, semantic systems, or graph databases (nice-to-have)
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 product surface you owned end-to-end—from UI design through data model—without detailed specs. How did you make architectural decisions?
- Describe your experience building frontend UIs that make complex system behavior intuitive. What's an example where you significantly improved legibility?