Clera
Backend Engineer
About this role
Join this fintech company as a Backend Engineer to design and build scalable, high-trust systems and APIs that power global compliance infrastructure. You'll take ownership of core backend architecture while shaping engineering practices for a growing, senior-focused team.
What you'll do
- Design and build clean, testable, and efficient backend systems and APIs
- Architect scalable infrastructure capable of handling high-volume, high-trust requirements
- Establish and advocate for strong testing, quality, and maintainability standards
- Solve complex product challenges by analyzing user needs and system behavior
- Mentor and shape engineering culture through collaborative, hands-on leadership
What they're looking for
- Backend engineering (5-7+ years production experience)
- Node.js/TypeScript, Python, Go, or Java
- API and distributed systems design
- Relational databases (Postgres or MySQL)
- Message queues and event-driven architectures (Kafka, RabbitMQ)
- Containerization and cloud deployment (Kubernetes, AWS)
- Systems architecture and long-term thinking
- Fintech, payments, or regulated environment experience
Benefits
- Fully remote position with flexible European timezone requirement
- Competitive base salary (EUR 116,000–146,000)
- Opportunity to shape technical strategy and engineering culture
- Periodic in-person team gatherings
- Senior-level team environment
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 backend system you architected for high-trust or regulated requirements—what were the key design decisions?
- How do you approach testing strategy and quality standards when building new APIs or services?