Yigit Alp Unal

One of six project leads, each owning end-to-end delivery of a core banking module.

• Own the bill-payment and collections domain across 40+ billers, each served by a Java gateway bridging into per-biller PL/SQL where settlement, accounting, and daily reconciliation are posted.
• Designed sync and async flows with retry handling so collections stay consistent under partial failures and timeouts.
• Delivered bulk SWIFT payments: up to 1,000 transfers per batch with a dedicated batch execution layer.
• Built the bank's corporate SFTP file-exchange infrastructure from scratch; adopted as the standard corporate transfer channel.

Platform team owning cross-cutting backend services across all digital banking product lines.

• Designed a Redis caching layer for high-traffic mobile screens, cutting Cards screen load time by ~16x.
• Built .NET Core APIs and microservices on consistent command–query separation across independently deployed domains.
• Escalation point for production incidents across all domains; owned the CI/CD lifecycle through to production.

Core systems of Türkiye İş Bankası, founded 1924.

• Shipped checkbook and safe-deposit products serving 25M+ customers across ~1,000 branches.
• Worked a hybrid legacy stack — IBM DB2, COBOL, Java, C# — tracing failures through the bank's COBOL and MQ backbone.
• Served scheduled 24-hour on-call rotations covering production batch jobs.

SAP business partner delivering enterprise software and consulting.

• Built CRM features on Spring Boot and JSF, and consulted across client projects in React, Angular, Vue, and .NET Core.

Where it started: full-stack web development across client projects.

Open-source MCP server giving AI coding agents persistent memory across sessions: hybrid retrieval (BGE-M3 dense + BM25 sparse, fused over Qdrant), a temporal knowledge graph with belief revision and epistemic typing, and 15 MCP tools.

Distributed core banking system of 13 microservices: SAGA orchestration over Kafka, database-per-service, SEPA and SWIFT payments (ISO 20022), AML sanctions screening, and a full observability stack.

A payment microservice built around correctness under failure: dual-layer idempotency (Redis + PostgreSQL) preventing duplicate charges from timeouts and retries, with optimistic locking and automatic retry on version conflicts.

Why persistent memory is becoming the layer that separates an assistant from a collaborator — and what it meant to independently arrive at the same architecture as Karpathy's LLM Wiki.