Clera
Backend-Leaning Product Engineer
About this role
Join a lean, early-stage team building AI and automation products as a backend-focused engineer who owns customer-facing features end-to-end. You'll make independent product and engineering decisions, integrate with messy third-party systems, and ship 0-to-1 products with direct impact in a fast-moving SF environment.
What you'll do
- Own features end-to-end from design through implementation, shipping, and iteration
- Build and maintain backend systems, APIs, data models, and automation pipelines
- Make independent product and engineering trade-offs with minimal PM oversight
- Integrate with external tools, legacy systems, and third-party services
- Design workflows and orchestration for AI/automation-driven products
- Debug production issues and collaborate with founders and customers
What they're looking for
- Backend engineering and system design
- API design and integration
- End-to-end feature ownership and shipping
- Cross-functional collaboration and communication
- AI/workflow orchestration (nice to have)
- Python or modern web backend stacks
- Third-party service integration
- Full-stack capabilities when needed
Benefits
- Base salary up to $275,000
- Meaningful equity package
- Hybrid/in-office work in San Francisco
- Direct impact on product direction
- Minimal bureaucracy and high ownership
- Close collaboration with founders and customers
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 0-to-1 product you shipped end-to-end—what was most challenging about owning the full lifecycle?
- Describe a time you had to integrate with a messy or poorly-documented third-party API. How did you handle it?