Skip to main content

Clera

Founding Engineer

San Francisco$160k–$270kfulltimemidAdded today

About this role

Join a seed-stage graph database startup as a founding engineer to build core infrastructure for AI agent memory systems. You'll own critical components like query execution, storage internals, and distributed systems while shaping long-term architecture decisions with direct product impact.

What you'll do

  • Design and ship query engine and graph storage layer components
  • Lead distributed systems architecture decisions with production consequences
  • Conduct benchmark and research work to define the technical category
  • Participate in architecture reviews and evaluate technical trade-offs
  • Mentor team members and establish engineering culture as the team grows
  • Own large, ambiguous problems independently from inception to production

What they're looking for

  • Rust or Go
  • Distributed systems design
  • Database and storage infrastructure
  • Systems-level programming
  • Query engine architecture
  • Production-grade software delivery
  • Computer science fundamentals
  • Open source development

Benefits

  • Meaningful equity package
  • Learning and professional development budget
  • Flexible PTO
  • Wellness programs
  • Gear and software stipend
  • Direct input on product direction and architecture
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 distributed system you've designed and shipped—what were the hardest trade-offs you made?
  • Tell us about a time you owned an ambiguous, large-scope problem without a clear playbook. How did you approach it?