Back to work

Backend · Integrations and migration

Flight engine: NDC integration and .NET migration

I integrated seven Air Europa NDC operations through SOAP/XML in a multi-provider flight engine. Separately, I was the sole engineer responsible for migrating four .NET engine repositories, delivered and validated in production.

Explanatory diagram; not an exact representation of the internal architecture.
Period
2026
Role
Software Engineer
Team and scope
Integration within an existing multi-provider engine and sole responsibility for migrating four critical repositories.
Status
Operations delivered to production for travel agencies.
  • C#/.NET
  • SOAP/XML
  • PostgreSQL
  • Serilog
  • Azure DevOps

Adding a provider to an existing engine

In 2026 I was responsible for the Air Europa NDC integration within a multi-provider flight engine. I worked as a Software Engineer for a B2B travel platform.

The engine already existed and was shared with the team. My work had two separate parts: implementing the provider integration, and leading the .NET migration as the sole engineer responsible for four critical engine repositories.

Seven operations

I implemented AirShopping, OfferPrice, OrderCreate, OrderRetrieve, OrderChange, OrderCancel and UpSell against PROS, over SOAP/XML with manual builders and parsers.

From search to order: the ticket illustrates offer search, price confirmation and order creation on a fictional itinerary.

Contracts and tracing

The integration required mapping the provider contract to the engine's domain: baggage, fare types, age codes and multi-segment journeys. I also worked on HTTP handling, tracing with Serilog, Grafana and Loki, payload storage in Azure Blob and multi-repository releases in Azure DevOps.

Resolving error 490

A 490 error response was resolved by fixing the DataLists wrapper. The change was in the structure of the message sent to the service.

Engine migration

The migration moved the engine from .NET 6 to .NET 10 and covered four critical repositories, described by responsibility: the flight engine, the engine backend, expenses and ticketing. I delivered them validated in production. To verify it, I checked byte-for-byte A/B parity across the evaluated case set and the write cycle, comparing the migrated behaviour with the previous engine.

Delivery

The internal work record reports successful offer retrieval and all seven operations in production with real agencies. Client code, payloads and traces are private.

Contact

I’m looking for backend or applied AI engineering roles, working on integrations and enterprise software. Remote from Peru (UTC-5).