Skip to main content

Clera

Backend-Leaning Product Engineer

San FranciscoFrom $275kfulltimemidAdded 1 month ago

About this role

An early-stage B2B SaaS startup seeks a backend-focused engineer to own customer-facing features end-to-end, from design through production. You'll build APIs and backend systems, integrate with external tools, and ship products quickly in a small team with high autonomy and minimal PM oversight.

What you'll do

  • Own features end-to-end from design through shipping and customer iteration
  • Build and maintain backend systems, APIs, data models, and automation pipelines
  • Integrate with external tools, legacy systems, and third-party services
  • Design workflows and orchestration for AI/automation-driven product features
  • Debug production issues and make engineering trade-offs under pressure
  • Collaborate with founders and cross-functional stakeholders

What they're looking for

  • Backend software engineering
  • API design and implementation
  • Systems integration
  • Full-stack capability (secondary)
  • Python (nice to have)
  • AI/LLM workflows (nice to have)
  • Cross-functional communication
  • Product-focused engineering mindset

Benefits

  • Competitive base salary up to $275,000
  • Meaningful equity package
  • Hybrid/on-site work in San Francisco
  • High ownership and autonomy
  • Early-stage startup environment
  • Direct collaboration with founders and customers
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 backend feature you owned end-to-end—from initial design through shipping and post-launch iteration. What trade-offs did you make and why?
  • Describe a time you had to integrate with a messy external API or legacy system. How did you approach debugging and what was the outcome?
Unlock all 6 questions free — and practice them live →