Senior Backend Engineer (Fintech Platform)
Role details
Job location
Tech stack
Job description
We're building a modern fintech platform for European SMEs: business accounts, payments, cards, integrations, and financial workflows. This is real infrastructure that moves real money, built with a strong bias for correctness, resilience, and long-term maintainability.
Requirements
Do you have experience in Terraform?, As a Senior Backend Engineer, you'll work on the core systems and the integration layer that connects us to third-party services.
Key Requirements:
-
5+ years backend development experience across paradigms
-
Ability to choose the right tool for the problem (dynamic for rapid development, compiled for production systems)
-
Experience transitioning between language paradigms based on project needs
-
Strong problem-solving skills that transcend specific language syntax
-
Understanding of language trade-offs (performance vs. development speed, type safety vs. flexibility)
-
Great person and team player; you care about others and you like to work as part of a sucessful team
What you'll work on
- Designing and building secure, versioned REST APIs for frontend and partner integrations
- Developing banking and payments integrations, including webhooks with validation, transformation, and event publishing
- Building event-driven microservices using Kafka, with robust error handling, retries, dead-letter queues, and replayability
- Creating event projections and read models optimized for fast, reliable querying
- Owning the full production lifecycle of services on Kubernetes, including CI/CD, infrastructure as code, and secure deployments
- Applying security best practices across APIs, infrastructure, and data flows (auth, secrets, RBAC, network policies)
- Building systems that correctly model banking domain concepts and handle financial data with accuracy, auditability, and regulatory awareness
Technical skills required
We're not hiring for a single framework or a narrow role. We're looking for engineers who have built and operated serious systems in production and understand the tradeoffs involved.APIs & integrations
- Deep experience designing and operating production REST APIs with clear contracts, versioning, and deprecation strategies
- Strong grasp of integration patterns: adapters, API gateways, third-party abstractions
- Hands-on experience with webhooks that are idempotent, secure, and resilient under failure
- Experience with GraphQL (queries, mutations, subscriptions) and knowing when it helps and when it doesn't
- Familiarity with open banking standards (PSD2, ISO 20022, Berlin Group) is a strong plus
Event-driven & distributed systems
- Solid experience building event-driven architectures in production
- Deep hands-on experience with Kafka or similar streaming platforms
- Experience with event sourcing, CQRS, projections, and schema evolution
- Understanding of event ordering, idempotency, retries, and replay
- Ability to design and operate microservices with clear boundaries and independent lifecycles
- Strong intuition for distributed systems tradeoffs: eventual consistency, failure modes, and recovery
Programming languages
We care more about how you think than which language you prefer. Strong candidates typically have experience across both ends of the spectrum: * Dynamic, expressive languages (Python-like): rapid iteration, prototyping, REPL-driven debugging, readable code
- Compiled, type-safe languages (Go/Java-like): performance, correctness, explicit error handling, type-driven designYou should be comfortable moving between speed and safety depending on the problem.
Infrastructure, cloud & operations
- Real-world experience running systems on Kubernetes (not just deploying once)
- Building and owning CI/CD pipelines with automated testing and security checks
- Strong experience with Infrastructure as Code (Terraform, CloudFormation, Pulumi)
- Production experience on AWS, GCP, or Azure (multi-cloud is a plus)
- Strong security fundamentals: secrets, access control, network policies, compliance-aware design
- Observability-first mindset: metrics, logs, traces, and knowing how to use them
- Experience with a service mesh is a plus, not a requirement
Nice to have
- Hands-on experience in fintech or banking, especially around payments, reconciliation, or regulated systems
- Direct exposure to open banking standards (PSD2, ISO 20022, Berlin Group) or similar regulatory frameworks
- Experience with workflow orchestration or integration-heavy systems (e.g. Temporal, Apache Camel, complex async flows)
- Strong technical communication skills, including writing ADRs/RFCs and explaining complex systems clearly
- Experience owning production incidents, running post-mortems, and helping teams get better after failures