Customer Solutions Engineer (Java / Full Stack)

Caravelo; Barcelona; Presencial; EUR 60.000 - 90.000; Jornada completa

Descripción de la vacante

Caravelo is seeking a Customer Solutions Engineer in our Professional Services team. You will bridge business requirements and the Caravelo platform, configuring and extending the system for each airline customer.

You'll translate customer needs into concrete implementations, build customer plugins, and guide implementations through development, testing, launch and stabilization, collaborating with Platform and Product engineers along the way.

Responsabilidades

• Understand customer requirements together with the Project Manager.
• Translate business and technical requirements into a concrete implementation.
• Configure and extend the Caravelo platform using the capabilities provided by our Product & Platform teams.
• Build and maintain the customer plugin that contains customer-specific logic and integrations.
• Take implementations through development, testing, launch and production stabilisation.
• Work closely with Platform and Product engineers to understand and extend the core platform.
• Solve integration problems across complex airline technology ecosystems.
• Investigate and debug production issues and upgrade connectors as systems evolve.
• Support customers through technical migrations and ensure service continuity.
• Work across the stack when needed: backend services, APIs, integrations, databases, scripts.

Conocimientos

Java

Backend engineering

API integration

Descripción del empleo

Airlines have spent decades selling one trip at a time. At Caravelo, we help them build recurring relationships with their customers instead. We build the technology behind airline subscription products used by carriers around the world, combining SaaS, payments, booking systems and airline integrations in one platform. Our Product & Platform teams build the common technology. Our Professional Services team makes it work in the real world for each airline. That is where this role comes in. Caravelo has one platform, but no two airline implementations are exactly the same. As a Customer Solutions Engineer in our Professional Services team , your job is to bridge that gap. You will learn how our core platform can be configured, integrated and extended, and use those capabilities to create the implementation each customer needs... without modifying or forking the core platform! For every airline, we build a customer plugin that wraps the specific integrations, extensions, business rules and behaviours required to make Caravelo fit naturally into that customer's technology landscape. Working closely with Project Managers and customer stakeholders, you will understand requirements, identify the peculiarities of each implementation and decide how best to solve them: configuration, extension, integration or, when justified, a dedicated service or module. The goal is simple: Make every customer rollout feel unique while keeping it cleanly built on top of a common, scalable platform.

Bring customers live You will be one of the engineers turning a signed customer into a working production implementation. That means: Understand customer requirements together with the Project Manager. Translate business and technical requirements into a concrete implementation. Configure and extend the Caravelo platform using the capabilities provided by our Product & Platform teams. Build and maintain the customer plugin that contains customer-specific logic and integrations. Take implementations through development, testing, launch and production stabilisation. You'll work closely with our Platform and Product engineers, who will provide the documentation, tooling and training needed to understand the core platform and its extension points. Your job is not to rebuild what already exists. It is to understand the platform deeply enough to use it intelligently and extend it where necessary. Solve integration problems Airlines have complex technology ecosystems. Some systems are modern. Others have been running successfully for decades. You will make them work together.

• Airline reservation and passenger service systems.
• Payment gateways and payment infrastructure.
• Identity and authentication platforms.
• CRM and communication systems.
• Loyalty platforms.
• Data platforms.
• Internal airline APIs.
• Third-party and legacy systems.

Sometimes the solution will be straightforward. Sometimes the API documentation will be incomplete, the behaviour will differ between environments, or two systems will have fundamentally different assumptions. You should enjoy figuring those problems out. Build customer-specific extensions Most customer needs should be solved using the common platform. But not all of them will be.

• Build an additional connector.
• Extend an existing workflow.
• Create customer-specific business logic.
• Develop an isolated service or module.
• Implement data transformation or migration processes.

The challenge is knowing when to configure, when to extend and when to build something new . We want engineers who can solve the customer problem without creating unnecessary complexity. Own the implementation beyond go-live Our work does not stop when a customer launches. Customer systems evolve, vendors change and integrations eventually need to move with them.You will help: Investigate and debug production issues. Maintain customer-specific integrations. Upgrade connectors as external systems evolve. Support customers through technical migrations. Replace or introduce integrations while keeping the service running. Improve existing implementations when better platform capabilities become available. For example, an airline may decide to replace its payment gateway. Your work could involve enabling the new payment connector in Caravelo, adapting the customer plugin, helping define the migration approach for existing payment tokens, validating the transition and supporting the rollout together with the Project Manager and customer team. These are not theoretical architecture exercises. They are real production systems with real customers and travellers behind them. Work across the stack when needed Your centre of gravity will be Java and backend engineering . But customer implementations do not always respect stack boundaries. You should be comfortable following a feature or problem wherever it goes: backend services, APIs, integrations, databases, scripts, d