Skip to content

Proof Pack

.NET backend engineer who owns money-path verticals end to end — refunds, wallets, withdrawals, gateway integration — on one production travel platform.

Everything below is evidence you can check or a boundary I am naming myself. Where something is not verifiable, it says so.

What I can prove

Three pillars

Reliability Engineering

Refunds retry under a bounded cap, re-inquire with the bank instead of assuming failure, persist gateway state immediately, and lock on the credit, not the queue. The four gateways I integrated, into an abstraction I did not design, carry 98% of card volume — about 1.33M transactions in 2025.

Automation and Production Ownership

Refund turnaround dropped about 85%, a week to a day, air and hotel, finance approval retained. Mine since 2020.

Service and Component Delivery

Verticals from zero to live: two-airline interlining, an airfare limit-order engine, flexible search, gift cards. All five design specs behind the interlining ADRs are mine.

Working style

How I work

Ownership

I own verticals end to end, schema to live feature, and run them for years.

Incidents

I fix incidents on the systems I own. No formal on-call rotation.

Failure paths

Bounded retry, structured logging, locks keyed to what they protect.

Design first

Design spec before code when the decision is expensive to reverse.

Written English

English in writing every day — docs, tickets, code review.

Read the full one-pager →

Stack

What I build with

C# / .NET 10 REST / Web API on .NET SQL Server Redis MassTransit Hangfire MediatR

Contact

Istanbul. Remote only. Open to EOR contracting.