Skip to content

Full Stack Developer · Istanbul

FatihKüçükdingin.

Full Stack Developer — Backend & Distributed Systems

I'm a backend-leaning full stack developer building multi-seller marketplace and e-commerce platforms. In .NET I keep payment, ERP, logistics and high-volume data flows fast and consistent under load — and I work actively on the seller panel and storefront with Next.js and React.

Marketplace & e-commerce experience

  • Payment & bank integrations
  • ERP · accounting · e-invoicing
  • Logistics & carrier integrations
  • High-volume product, stock, price data
  • Performance & query optimisation
  • Seller panel & storefront · Next.js / React
See my workGet in touchgithub.com/kdingin(opens in a new tab)
Fig. 01An abstract flow: a request, a queue and independent consumers — events settling into a consistent state, watched over by a human and an AI agent working together.
Fig. 01An abstract flow: a request, a queue and independent consumers — events settling into a consistent state, watched over by a human and an AI agent working together. Illustrative diagram — not any company's internal architecture.

Focus areas

  1. 01Backend Engineering
  2. 02Distributed Systems
  3. 03Full Stack · Next.js & React
  4. 04AI-Augmented Development
§ 01About

Writing code is only the visible part of the job.

“To me, software development means designing systems that are reliable, scalable and built to last.”

Today I work as a backend-leaning full stack developer on a multi-seller marketplace — from .NET services to the seller panel and storefront we build with Next.js and React. A payment coming back from the bank, a parcel handed to a carrier, an invoice being issued — each of these flows touches several systems, and in each of them mistakes are expensive. So I don't just write endpoints or screens; I own the whole flow — from API to interface, from its design to how it behaves in production.

In technical decisions I value simplicity and measurement. A new service, a new cache or a new abstraction earns its place only when it solves a real problem. Before fixing something I want to see it in production, and after changing it I want to measure the effect.

My degree in Management Information Systems helps me read the business side of a problem as well as the technical one. I treat learning as part of the job, not a phase — and lately a big part of that has been working with AI coding agents without dropping engineering discipline.

§ 02Experience

Systems that run in production.

Problem spaces I've taken responsibility for, rather than a list of tasks.

  1. — Present

    Software Developer

    Goturc(opens in a new tab)

    Multi-seller marketplace platform

    I work full stack — backend-leaning — on a large, multi-seller marketplace. In .NET I own business-critical flows end to end — payments, logistics, accounting and e-invoicing — and I'm actively involved in the seller panel and storefront built with Next.js and React.

    Contributions

    • End-to-end ownership of bank, payment provider, ERP and e-invoicing (e-Fatura / e-Arşiv) integrations.
    • Designed and maintained payment flows: processing, installments, refunds, cancellations and reconciliation.
    • Architected logistics workflows: shipment creation, carrier integrations, tracking, returns and delivery lifecycle.
    • Policy enforcement workflows that turn business and compliance rules into scalable backend services.
    • High-throughput, performance-sensitive services built around consistency, idempotency and reliability — SQL Server modelling and query tuning, Redis, RabbitMQ, Elasticsearch.
    • Building the seller panel (magaza.goturc.com) and marketplace storefront (goturc.com) with Next.js and React, integrated end to end with the backend APIs.
    • Production operations, monitoring and incident investigation; contributing to architecture decisions, sprint planning and code reviews.

    Additional responsibility · Öztürk Holding

    Additional holding-level responsibilities

    Alongside my role at Goturc, I support software products and digital platforms across the Öztürk Holding ecosystem.

    • Maintaining and improving software products within the holding.
    • Operational tooling and software tasks for holding-level systems.
    • Maintenance and coordination of web applications across business units.

    Problem spaces

    • 01Payments and bank integrations
    • 02Logistics and shipment lifecycle
    • 03ERP, accounting, e-invoicing
    • 04Seller policy enforcement
    • 05Asynchronous data processing
    • 06Microservice decomposition
    • 07Seller panel & storefront

    Stack

    • .NET / C#
    • SQL Server
    • Redis
    • RabbitMQ
    • Elasticsearch
    • REST
    • Next.js
    • React
    • TypeScript

  2. —

    Software Developer

    SporYap

    Location-based social sports & events platform (startup)

    Backend work for an app that lets people create and join shared sports activities across cities. In a startup setting I focused on core application logic, API development and data modelling.

    Contributions

    • Core application logic and API development in .NET backend services.
    • Data modelling and persistence on PostgreSQL.

    Problem spaces

    • 01Location-based activities
    • 02API design
    • 03Data modelling

    Stack

    • .NET / C#
    • PostgreSQL
    • REST
§ 03Expertise

Not the tools — the problems they solve.

Six areas, each with where it actually shows up in day-to-day work.

§ 04Engineering Approach

Principles only mean something once a scenario tests them.

Seven principles I care about, each paired with a typical problem. The scenarios are illustrative, not internal details of any particular system.

01 / 07 · Data Consistency

Networks retry, users double-click, providers resend callbacks. The system should still land on exactly one correct outcome.

Scenario

  1. 01 · Situation

    A payment provider sends the same confirmation twice.

  2. 02 · Approach

    The request is checked against an idempotency key and transaction state.

  3. 03 · Result

    It is applied once; the second call returns the same result.

§ 05Selected Work

Professional work and open projects.

Two separate groups: problem spaces I've owned in a commercial setting, and personal projects on GitHub.

A

Professional Engineering Work

Confidential · source not public

Commercial work. Source code and internal architecture are confidential; only the problem space and approach are described.

  1. 01

    Marketplace Core Infrastructure

    The .NET backend carrying order, seller and catalogue processes of a multi-seller marketplace.

    Confidential · source not publicRead more
  2. 02

    Payment & Financial Workflows

    Payments, installments, refunds, cancellations, reconciliation; ERP, accounting and e-invoicing integrations.

    Confidential · source not publicRead more
  3. 03

    Logistics & Integration Systems

    Shipment creation, carrier integrations, tracking, returns and the delivery lifecycle.

    Confidential · source not publicRead more
  4. 04

    Seller Panel & Storefront

    The marketplace's seller panel and storefront: Next.js and React interfaces wired end to end to the backend APIs.

    Confidential · source not publicRead more
  5. 05

    Event-Driven Data Processing

    High-volume, queue-based asynchronous processing of product, stock and price data.

    Confidential · source not publicRead more
  6. 06

    Marketplace Personalization

    Backend services feeding content and listing experiences shaped by user behaviour.

    Confidential · source not publicRead more
  7. 07

    Policy Enforcement Systems

    Seller policies, violation detection and enforcement workflows.

    Confidential · source not publicRead more
B

Open Source & Personal Projects

Learning and experimentation projects on GitHub, built to explore architectural patterns and the .NET ecosystem hands-on. Not commercial products.

All projects
§ 06AI & Modern Software Development

Engineering in the Age of AI

AI can make code faster. Owning its correctness, its security and its consequences is still the engineer's job.

I don't build models, and I don't describe myself as an ML specialist. What I do is bring AI coding agents into the software development process without giving up engineering discipline.

Working loop

  1. 01Human

    Intent

    I define the problem, the constraints and the acceptance criteria.

  2. 02Agent

    Context

    The agent reads the codebase, relevant files and past decisions.

  3. 03Agent

    Draft

    The agent proposes an analysis, a plan or an implementation.

  4. 04Human + tooling

    Verify

    Tests, builds, code review — and my own judgement.

  5. 05Human

    Decide

    A human decides what goes to production.

Where I use it

  • 01AI coding agents

    Delegating repetitive, well-defined work to agents while keeping scope and boundaries explicit.

  • 02Architectural analysis

    Comparing options and surfacing risks I might miss — then deciding based on context.

  • 03Code review & refactoring

    A second pair of eyes whose suggestions are checked against tests and readability.

  • 04Technical research

    Scanning a new library or protocol quickly, then confirming against primary sources.

  • 05Workflow automation

    Making analysis, planning and verification steps repeatable.

  • 06Human-guided decisions

    When security, data or money is involved, a human always has the final say.

Speed is only an advantage when it can be verified.

§ 07Blog

Writing is on the way.

In-depth technical articles on real engineering problems will be published here.

Visit the blog
  • Backend ArchitectureSoon
  • Distributed SystemsSoon
  • .NETSoon
  • Data ConsistencySoon
  • MicroservicesSoon
  • AI-Augmented EngineeringSoon

§ 08Contact

Let's build something solid.

Reach out about roles, engineering collaborations, or just a conversation about backend and distributed systems.

Email

fatihkdingin@gmail.com

Location

Istanbul, Türkiye

Phone

+90 555 061 12 35

GitHub

github.com/kdingin(opens in a new tab)

LinkedIn

in/fatih-küçükdingin(opens in a new tab)