Adana, Turkey · Open to international and remote opportunities
I build and operate backend systems for commerce, trading, payments, operator workflows, and real-time products.
My work spans architecture, implementation, code review, database performance, incident response, delivery, and engineering leadership.
Portfolio | Resume | Projects | Case Studies | Architecture
Two-page resumes tailored to the role.
- Mathematical Game Lab — three Godot prototypes driven by Bayesian inference, timed routes, and computational geometry. C#, GDScript, and private source.
- Cat Keyboard — a native Windows keyboard guard with manual locking, tray controls, and emergency unlock. C#/.NET; private source.
- Together Meet — two-person WebRTC calls, chat, and device diagnostics. Public web/signaling code; newer Android work remains private and needs real-device ringing verification.
Public open source · TypeScript library
Zero-dependency comparisons for nullable object paths, deep equality, validation helpers, and defensive property access.
Public integration project · NestJS / PostgreSQL
Normalize two job-provider payloads into shared entities, with TypeORM persistence, migrations, Docker, and health checks.
WebRTC client and server
Public demo · React / Socket.IO
Two-person calling, signaling, room state, and chat. Try the meeting room.
Public open source · Rust / Axum learning project
Typed routes, separate domain logic, structured logging, health endpoints, and HTTP integration tests.
The Portfolio Platform is also deployed: its Next.js/NestJS/PostgreSQL source remains private, with public architecture and case studies.
Browse the complete public repository archive →
| Signal | Evidence |
|---|---|
| Engineering leadership | Began managing engineers in early 2024; now lead eight backend engineers at LicenseMarket, with hiring, one-to-ones, performance reviews, mentoring and delivery planning. Coordinated 5+ major releases. |
| Reliability | Maintained 99.9% LicenseMarket platform uptime over approximately six months, tracked with UptimeRobot and CRM incident records. |
| Performance | Reduced average API latency by 40% through caching, indexing and query optimization, validated with database/API timing tests over approximately six months. |
| Real-time scale | Supported 500+ concurrent users in production at Mobasher, with observed messaging latency of 100–150 ms. |
| Financial systems | Built trading, pricing, wallet, transaction, payment, KYC/AML, and verification workflows. |
| Enterprise systems | Contributed to the Symorgh ERP platform using ASP.NET Core, Entity Framework Core, MySQL, and Angular. |
Client and employer source code remains private. The portfolio case studies describe the work without exposing confidential implementation details.
Production figures are my reported results from private company records. Mobasher’s latency figure measures messaging, not voice or video.
Ongoing freelance work includes GBT Market and Keyvangold, two separate trading-platform engagements started in 2025.
Core: TypeScript, Node.js, NestJS, PostgreSQL, MongoDB, Redis, RabbitMQ, Prisma, TypeORM.
Real-time and operations: Socket.IO, WebRTC, Docker, Nginx, Linux, CI/CD.
Personal projects: Rust/Axum APIs, Go applications, Godot simulations, and native C# utilities.
Build predictable APIs, make data ownership explicit, keep background work observable, and define how real-time features recover from failure. I value clear documentation and code the next engineer can debug.
- Portfolio Playground: try browser demonstrations; each explains its scope and source availability.
- WebRTC meeting room: open the same room on two devices. Client and server source are public.
- Quit Together: a private Go product with a public landing page; an account is required to explore it.
- Story Platform: a public reading interface backed by a private personal repository.
For senior backend, backend lead and engineering manager opportunities, read the recruiter brief, choose a role-specific resume, or email me.
More about the workshop
I build small open-source tools, explore real-time infrastructure, and turn recurring backend problems into reusable utilities and engineering notes. Historical exercises and experiments remain in the complete public archive; they are not all production systems.