Skip to main content

Clera

Software Engineer

remote (Remote)$75k–$265kfulltimemidAdded today

About this role

Join a fintech engineering team to build and scale end-to-end B2B production systems. This full-stack role spans frontend UI development through complex data modeling and large-scale integrations, with ownership from day one.

What you'll do

  • Build and scale end-to-end production systems for complex B2B fintech products
  • Own features from conception through launch and ongoing iteration
  • Collaborate with stakeholders to understand problems and drive technical solutions
  • Design shared abstractions and experiences that simplify complex products
  • Mentor through code reviews and establish engineering best practices

What they're looking for

  • TypeScript and React
  • Node.js and Python
  • PostgreSQL and MongoDB
  • Google Cloud Platform
  • Data pipelines and ETL
  • Full-stack system design
  • CI/CD and GitHub Actions
  • API and database architecture

Benefits

  • Salary: $75,000–$265,000 USD annually
  • Flexible hours and unlimited PTO
  • Health insurance (US and Canada)
  • 401(k) plan (US employees)
  • Provided laptop (MacBook Pro or Lenovo)
  • In-person team retreats
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 B2B feature you owned from conception to launch—what were the technical challenges and how did you handle them?
  • How do you approach tracing a request from the UI through your backend to the database, and what informed your architectural decisions?