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 problemsAirlines have complex technology ecosystems.
Some systems are modern. Others have been running successfully for decades.
You will make them work together.
Depending on the customer, you may integrate Caravelo with:
- 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.When there is a genuine gap, you may:
- 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-liveOur 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 neededYour 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, data migrations or occasional frontend changes in Vue.
You do not need to be a frontend specialist.
You do need to be comfortable enough to understand the problem, use AI-assisted development effectively and validate that the result is production-quality.
Use AI as an engineering toolWe actively use AI coding tools such as Claude Code, Cursor, Devin and similar assistants.
You will use them for things like:
- Implementation.
- Exploring unfamiliar code.
- Writing and extending tests.
- Debugging.
- Refactoring.
- Documentation.
- Working with APIs and integrations.
- Accelerating occasional frontend work.
We are particularly interested in
Spec-Driven Development (SDD): defining clearly what needs to be built before asking AI to help implement it.
AI should make you faster. It should not replace engineering judgment.