Hi, I'm Mehmet.

I'm a Senior Backend Engineer and Tech Lead with 9+ years of experience building and operating high-throughput distributed systems, event-driven architectures, and database infrastructure.

I'm currently at Getir, working across its food and quick-commerce verticals — GetirYemek, GetirÇarşı and GetirSu — on platforms serving 300K+ orders a day.

I own domain redesigns end-to-end — deciding how data is modelled, how services talk to each other, and how consistency is kept as the system grows. I also lead engineering teams, set architectural direction, and mentor other engineers.

İzmir, Turkey

mehmeteminimirhan@gmail.comGitHubLinkedIn

Domains I've Worked On

Backend ownership across the merchant and ordering side of the platform.

What That Work Looks Like

A general sense of the kind of problems I take on, rather than a project list.

Re-architecting the delivery area platform

MongoDB → PostgreSQL, CQRS, Kafka + CDC

Migrated a denormalized MongoDB model onto a normalized relational schema in PostgreSQL, and split write-side metadata from read-optimized listing services under CQRS. The two sides are kept in sync with Kafka and change data capture, with read replicas behind a connection proxy — which roughly halved app open times.

Rebuilding the menu domain around events

Domain events, outbox over SNS/SQS, CQRS read models

Moved denormalized MongoDB collections onto PostgreSQL and an event-driven design: domain events published over SNS/SQS using the outbox pattern, with consumers fetching the latest state per event so processing stays idempotent regardless of delivery order. Read models are projected by serverless consumers under CQRS.

Decomposing large services

Monolith → domain-aligned microservices

Broke monolithic services into domain-aligned microservices — restaurant management, menu, agreements, POS, moderation and others — to get fault isolation, independent scalability, and clear team ownership. Continued carving out narrower services as domains grew.

Reliability and production ownership

Ongoing incident response and structural follow-through

Incident response has been a constant across my time on these systems. I've led the response on high-severity outages and been pulled into many more — caching layers, database contention, message consumer throughput, third-party integrations degrading under load. The part I care about is what happens afterwards: chasing the structural fix rather than the quick patch, and leaving behind alerting and on-call practice that holds up across teams.

Scale, cost and security posture

Infrastructure tuning and dependency hygiene

Tuned database usage and Kubernetes pod resources for meaningful infrastructure cost savings, and led a cross-team effort to clear a large dependency-vulnerability backlog across a portfolio of several hundred microservices.

Where I've Worked

Education

BSc, Computer Engineering

Manisa Celal Bayar University

2012 — 2017

What I Work With

Languages

  • Java
  • TypeScript / Node.js
  • Go
  • Python
  • C#
  • Swift
  • SQL

Architecture & Design Patterns

  • Microservices
  • Event-Driven Architecture
  • CQRS
  • Outbox Pattern
  • Domain Decomposition
  • API Gateways
  • REST & gRPC APIs

Data & Messaging

  • PostgreSQL
  • MongoDB
  • Oracle
  • Redis
  • Kafka
  • RabbitMQ
  • SNS / SQS
  • Debezium / CDC

Infrastructure & Tools

  • Docker
  • Kubernetes
  • AWS
  • CI / CD
  • Observability & Monitoring
  • Git

Techniques & Practices

  • Distributed Transactions
  • Idempotency & Exactly-Once Processing
  • Query Optimization
  • Caching Strategies
  • Performance Tuning
  • Incident Response
  • Scalability & Reliability Engineering

Leadership

  • Technical Leadership
  • System Design & Architecture Review
  • Mentoring
  • Runbooks & On-Call Practice