Backend engineer specializing in operational complexity — aviation systems, enterprise workflows, and the state-heavy architectures most developers avoid. I build the systems your business depends on when failure is not an option.
Each engagement is scoped, time-bounded, and delivered with full documentation.
You need a backend system built for operational reality — not a clean demo that breaks when an edge case hits production. I design and build the state-heavy systems airlines and aviation operations depend on: baggage workflows, crew scheduling, passenger integrations, approval engines, and the kind of domain logic that takes weeks to understand before you can safely build it.
Right for you if your operational system can't afford an incident and can't afford a rewrite.
Your legacy system is slowing you down — not because it's old, but because it carries years of undocumented decisions that nobody wants to touch. I execute careful, zero-downtime modernizations: schema redesign, entity mapping, transformation pipelines, migration validation, and operational history preservation. The business keeps running while I transform what's underneath.
Right for you if your technical debt has become an operational risk.
You have repetitive operational processes consuming hours of staff time every week. I build intelligent automation pipelines using n8n, OpenAI, and custom integrations — systems that generate, route, approve, and publish without manual coordination. Built with error handling, exception queues, and human-in-the-loop checkpoints where they actually matter.
Right for you if you're paying people to do work that a well-designed pipeline should handle.
Not sure which applies? Most engagements touch more than one. Let's scope it together.
Discuss Your Project →Enterprise workflow platform — manual approval chains replaced with state-machine engine, full audit trail, and role-based routing.
AI automation pipeline — n8n, OpenAI, and Telegram replacing repetitive operational cycles with continuous autonomous processing.
Baggage management, crew scheduling, passenger integration, and partner data exchange — all running in live airline operations.
Legacy migrations completed with full reconciliation. Operational systems designed so failures aren't possible, not just unlikely.
These are outcomes from real production systems — not feature deliveries. Every number is a business result that continued delivering value after the engagement ended.
Production systems. Airline operations. Real operational impact.
I spent five years building mobile applications — Flutter, Firebase, real products shipped to the App Store and Google Play. Booking systems, marketplaces, payments, real-time chat. That background gave me something most backend engineers don't have: a precise understanding of what the product layer actually needs from a backend.
I moved deliberately into backend engineering because that's where the problems that actually interest me live. Operational complexity. State machines with real consequences. Migrations that can't fail because the business never stops. Aviation systems don't have staging environments — they have live airlines and passengers.
My backend foundation is focused and production-proven: ASP.NET Core, EF Core, Dapper, SQL Server, CQRS, Clean Architecture. On top of that, I've built systems integrating with Navitaire and SITA/JAF, executed zero-downtime legacy migrations, and more recently extended into AI automation — n8n, OpenAI, Telegram — applying the same orchestration thinking to a different layer of the stack.
When I take an engagement, I'm not closing tickets. I'm accountable for the outcome: documented decisions, clean handoffs, and systems your team can maintain in three years without calling me.
I don't list every framework I've touched. This is what I use at depth, in production, in environments where operational failure has real consequences. New tools get added when a problem genuinely demands them — not to fill a resume.
Systems that work under load, in the dark, without supervision. Airline operations don't stop. Neither do the systems I build.
Rushing into implementation is the most expensive form of speed. A baggage workflow state machine has to be right the first time — there's no quick patch in production.
Your team will inherit my code. I design for the engineer who joins 18 months from now, not the sprint review tomorrow.
I'm accountable for outcomes. Closing a ticket is not the same as solving the operational problem behind it.
The most sophisticated thing I can do is make operational complexity feel simple. Unnecessary abstraction is a failure of understanding.
Good architecture survives scale, team changes, and the requirements nobody anticipated when the system was first designed.
On aviation systems, reliability, and the backend engineering mindset.
Baggage workflow, lost & found handling, approval chains — every operational aviation system is a state machine in disguise. Here's how to stop pretending it isn't and start designing for it explicitly.
The airline never stops operating. That constraint changes everything about how you design a migration. The transformation pipeline comes before any cutover — not as a nice-to-have but as the only viable strategy.
Seat adjacency lookups, surrounding-passenger queries, booking references — real aviation integrations expose patterns that generic REST API tutorials never cover. The domain shapes the design.
If you've built CQRS systems, you already think in commands, queries, and event flows. n8n is just that model with a visual surface. The jump from ASP.NET Core to n8n orchestration is shorter than it looks.
I take on a limited number of engagements at a time. If the problem is operationally complex, the standards are high, and long-term reliability matters — let's talk.