Assignment Description

We are looking for skilled a Backend Engineer to take part in developing a cloud-native adapter layer that connects a variety of APIs with several digital touchpoints. This initiative aims to replace legacy systems with a modern, scalable architecture designed for the cloud. The solution will streamline data flow between services, abstract key business logic, and ensure seamless API integration aligned with OpenAPI standards.

The work centers around developing and maintaining services using TypeScript with NestJS/Node.js, all built to support global operations at scale. Reliability and offline capability are key requirements, with infrastructure handled through automated pipelines and Infrastructure as Code practices. You’ll be working closely with the architecture team to shape a robust and flexible backend that meets both technical and operational needs.

This position requires fluency in Spanish and the ability to work onsite in Madrid three days per week.

Required Qualifications:

• Proficiency in spoken and written Spanish.
• Hands-on experience with cloud-native architecture and deployment, particularly within Google Cloud Platform (GCP).
• Practical knowledge of setting up and managing CI/CD pipelines using GitHub Actions.
• Strong background in Infrastructure as Code (IaC), with proven use of Terraform to automate cloud environments.
• In-depth experience building backend systems using TypeScript and the NestJS/Node.js framework.
• Familiarity with integrating APIs in line with OpenAPI standards across diverse systems.
• Ability to design solutions with offline resilience in mind, suitable for globally distributed environments.
• Skilled at structuring and isolating business logic to ensure clear separation between service layers.

The most valued qualifications for this role include extensive experience in backend development using TypeScript and the NestJS/Node.js framework, a strong background in designing and deploying cloud-native services with a focus on Google Cloud Platform, and a deep understanding of API integration based on OpenAPI specifications.