Clera
Software Engineer
About this role
Join a Series B fintech SaaS company as a Software Engineer to build and scale end-to-end production systems for complex B2B products. You'll own features across the full stack—from intuitive UIs to data modeling and integrations—working directly with stakeholders in a remote, startup-focused environment.
What you'll do
- Build and scale production systems spanning frontend, backend, and data layers for B2B fintech products
- Own feature development from conception through launch, including iteration and stakeholder collaboration
- Design and implement shared abstractions to make complex products intuitive for users
- Build data pipelines and ETL processes to support large-scale data systems
- Conduct code reviews and establish engineering best practices to raise team standards
- Work with Google Cloud Platform infrastructure and deployment systems
What they're looking for
- TypeScript and React
- Node.js and Python
- PostgreSQL and MongoDB
- Google Cloud Platform (GCP)
- Data pipelines and ETL processes
- Full-stack system design and architecture
- CI/CD pipelines (GitHub Actions preferred)
- Observability and monitoring tools
Benefits
- Flexible hours and unlimited PTO
- Health insurance for US and Canadian employees
- 401(k) for US employees
- MacBook Pro or Lenovo laptop provided
- Regular in-person team retreats
- Fully remote across US, Canada, and Latin America
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 feature you owned end-to-end—what was your approach to gathering requirements and shipping it?
- Describe a time you had to make a technical decision that spanned frontend, backend, and data layers. How did you approach it?