Skip to main content

Clera

Software Engineer, AI & Data Systems

San Francisco$200k–$280kfulltimemidAdded today

About this role

Join a fast-growing data infrastructure team to design and build AI-driven data systems and customer-facing products. You'll own projects end-to-end, from architecture through production, working with founders and customers to scale backend services, data pipelines, and AI agent frameworks.

What you'll do

  • Build and ship customer-facing products and core platform capabilities across backend, data, infrastructure, and frontend
  • Design and operate high-volume data pipelines and services with strong reliability and observability
  • Develop AI agents, agent harnesses, and developer tools and scale them in production
  • Make architectural decisions and tradeoffs as product assumptions evolve
  • Collaborate directly with founders and customers to translate requirements into concrete software

What they're looking for

  • Backend development and API design
  • Distributed systems and data modeling
  • High-volume data pipeline design and operation
  • Python programming
  • Cloud infrastructure and DevOps
  • AI/LLM development and agent frameworks
  • System architecture and technical decision-making
  • Strong computer science fundamentals
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

  • Tell us about your experience designing and operating high-volume data pipelines—what challenges did you face and how did you solve them?
  • Describe a time you made a significant architecture decision that had tradeoffs. How did you evaluate the options and iterate as assumptions changed?